Thursday, February 10, 2011

IE9 Release Candidate (RC)

I never liked IE personally to use, specially IE6 which gave so many heart attacks (headache precisely) to almost every web developer and I'm a victim too. But after listening so many feedback and research work, I'm keen to try the new IE9 RC, and I hope this become irrelevant



Few good points in terms of performance and standards, which I hope stands true are
  • Faster with real world sites
  • Faster script engine
  • Improved rest of the browser
  • Network cache Tuning
  • New Compiler optimization

Read more & Download  IE9 here:

Friday, February 4, 2011

Become a better developer

Search for the term ‘better developer’ and you find nearly 61 million results. It seems like everybody has an opinion on how to become a better developer, even the bad developers will tell you how to be a better programmer. After reading many of these programming self-help articles on being a better developer I found that the core message was all the same! If I could boil down the advice of all these results into a succinct list of how to be the best developer we are left with the following…

  • Read Everything
  • Learn Fast
  • Practice What You Know
  • Try New Things
  • Strive for Simplicity
  • Write and Teach
  • Assume Nothing
  • Question Everything
  • It is Not Personal
  • Rinse and Repeat
There is no one Golden Rule for becoming a better developer. Instead of single rule or a unifying theory of software development we have a set of core beliefs and best practices.

Here is the insight from many other developers on how to be a better software developer. In reading their advice, think what is universally true for all developers. What can we learn from each other, no matter
the development platform or programming language we use?
  •  Becoming a Better Developer
    • Find/Rediscover Your Passion
    • Remove Distractions
    • Listen tPodcasts & Read Blogs
    • Blog
    • Learn a New Technology Each Month
    • Get Involved in an Open Source Project
    • Seek out Local .NET Groups or Nerd Dinners
  • 8 Tips To Become A Better Developer
    • Write the simplest code possible
    • Use the simplest technology
    • Focus on your actual task
    • Dnot write temporary code or it will last forever
    • Invest time tthink about the best technology and approach tuse
    • Apply design patterns and good OOP principles
    • Write semantic code
    • Don't be afraid of saying “I don’t know”
  • How to be a better developer?
    • Assume You Know Nothing
    • Listen tPodCasts
    • Watch WebCasts
    • Watch ScreenCasts
    • Forum Participation
    • User groups meetings / Community meetings
    • Read Books
    • Read Blogs
    • Learn tuse other technologies
    • Adopt a Development Methodology
    • Dnot procrastinate
    • Try thang up with people that love software development
  • 7 ways to be a better developer
    • Keep your ear tthe ground
    • Give your users a place ttalk teach other
    • Start a public bug tracking system
    • Release early, release often
    • Talk tyour users
    • Be responsive
    • Participate in the development community
  • How to be a better developer?
    • Know what your framework has toffer, use it
    • Extend the wheel, dnot reinvent it
    • Write technical articles
    • Give technical presentations
    • Write quality code
    • Dnot write “temporary code”
    • Test your code
  • Being A Better Programmer
    • Plan For The Worst
    • Expect TForget
    • Document Choice
    • Human Error and Monkey Business
    • Admit Your Own Limits
    • Fix It, Don’t Hack It
    • Step Softly and Carry Nothing
    • Don’t Get Personal
  • Six ways to build a better developer
    • Never stop learning
    • Reuse, reuse, reuse
    • Understand the business side
    • Get a mentor, or be one
    • Don’t be afraid to critique your code
    • Be nice to nontechies
  • Becoming a Better Developer
    • Ensure your foundations
    • Target what interests you
    • Read beyond the official documentation
    • Write code regularly
    • Try explaining what you’ve learnt tothers
    • Enjoy it
    • Look at and learn from other people’s code
    • Learn from other developers mistakes
    • Know yourself
  • Becoming a Better Developer
    • Know Your Core Competencies
    • Enjoy the Panorama
    • Know What You’re Building
    • Don’t Use a Dull Knife
    • Become a Manager
    • Know Your Archetype
    • What DYour Colleagues Think of You?
    • Get a Massage (and Get Your Boss tPay For it)
  • Being a Better Developer… in 6 months
    • Reading
    • Writing
    • Speaking
    • Community
    • Learning
    • Code, Code, Code and more Code
  • 4 ways to become a better programmer
    • Read
    • Write
    • Review
    • Contribute
  • 8 ways to be a better programmer in 6 minutes
    • Use a bigger font size
    • Make hard-coded strings look ugly
    • Pick an ‘obscure’ keyword and master it
    • Increase code-coverage by 1%
    • Read the code from an open source project
    • Run a static analysis tool against your code
    • Pick an ugly method trefactor
    • Stop reading, start writing
  • Become a Better Developer in 6 months. How?
    • Spending more time looking at art works
    • I’m going tstart playing with Lego’s again
    • I’ll start learning Ruby On Rails
    • Play chess a bit more
    • Read Freakonomics
    • Keep blogging, writing articles and answering questions in the forums
Source : email

LinkWithin

Related Posts with Thumbnails