Roadmap to a better programmer [closed]

Answer 1

1. Learn your 1st programming language a new programming paradigm or a
2. find a mentor you can learn from
3. Apply what you've learnt in a real world project
4. Learn from your mistakes and successes and goto step one

The trick is knowing what to learn first:

• Programming languages - this is the place to start bcause you cannot write software without knowing at least one of these. After you've mastered one language try learning another.
• Programming paradigm - i.e. object oriented, dynamic/functional programming etc. Try to learn a new one with each new language.
• Design concepts - S.O.L.I.D, design patterns as well as architectural concepts.
• People skills - learn to communicate your ideas.
• Team leadership - learn how to sweep others and how to become a team or technological lead.

After that the sky is the limit.

Answer 2

Practice, practice, practice.

Once you're over the basic hump of being able to program, you can also read useful books (i.e. Code Complete, Effective Java or equivalents, etc.) for ideas on how to improve your code.

Answer 3

All questions are rhetorical and meant to stimulate thought.

Technical parts:

• Design Patterns - There are probably some specific to a domain but generally these are useful ways of starting parts of an application. Do you know MVC or MVP?
• Basic algorithm starting points - Divide and conquer, dynamic programming, recursion, creating special data types like a heap, being greedy, etc.
• Problem solving skills - How easily can you jump in and find where a bug is? Can you think of multiple solutions to the problem?
• Abstract modelling - How well can you picture things in your head in terms of code or classes when someone is describing a problem?
• High level versus low level - How well do you understand when one wants something high or low? This is just something I'd toss out there as these terms get through around a lot, like a high level view of something or a low level language.

Process parts:

• Agile - Do you know Scrum, XP, and other new approaches to managing software projects? How about principles like YAGNI, DRY and KISS? Or principles like SOLID? Ideas like Broken Windows?
• Developer Environment - How well do you know the IDE you use? Source Control? Continuous Integration? Do you know the bottle necks on your machine in terms of being productive?
• xDD - Do you know of TDD, BDD, and other developments driven from a paradigm?
• Refactoring - Do you go back over your old code and make it better or do you tend to write once and then abandon your code?

Soft skills:

• Emotional Intelligence - Can be useful for presentations and working with others mostly.
• Passions/Motivation - Do you know what gets your juices flowing and just kick butt in terms of being productive? Do you know what you would like to do for many many years?

Answer 4

As well as looking at 'last weeks code', talk to users of your work after delivery - be one yourself if possible.

Its not my bag, but some of the best coders I know have spent time supporting applications. The experience improved their product I'm sure.