When I started dabbling in the web industry over 15 years ago I knew very little what was involved to become a developer. Back then the Internet had just taken off and the resources were scarce.

Fast forward to present, it is simply amazing to see so many software technologies and techniques emerging rapidly. Yet, I can't help but think one would easily become overwhelmed or even confused in this vast amount of information.

Perhaps you are an aspiring software junkie, or a software engineeing student, or a junior developer, or an established developer who is stuck at where you are at - I would love the opportunity to start a conversation with you on how to become an above average developer.

The goal here is to push you to go even further and to become a GREAT developer - but let's be honest, a great developer cannot be taught, not to mention that I don't even see myself as a great developer, yet. You see, the real goal here is to inspire you to get to a stage where you would have more chance to succeed.

Over the past few years I have started collecting ideas on topics I'd like to cover. Some of the topics are (draft only, in no particular order):

• Where to start (your career)?
• Attidue: question things
• Champion individual vs champion team
• Personal / social branding
• In for the money? Prospect? Experience? Or something else?
• Documentation
• They pay for what you do; they pay for what you know; they pay for your wisdom.
• Ideas vs execution
• Learn to say no
• The art of asking questions
• Be a responsible developer
• Handle politics
• Attention to detail
• UI / UX
• Refactor code, when and how?
• Finding leisure activities that boost your productivity
• Chicken and egg problem - how to solve?
• Optimise readability vs optimise performance
• Code tests
• Adjust your confidence level
• Help vampires
• "Invest" the right amount in your employer
• Effective use of source control
• Team dynamics
• Communication
• Second system syndrome
• Software engineering is like playing a real time strategy game like StarCraft II - importance of checking your "minimap"
• "Experience is overrated"
• Social investment
• Open source
• Software architecture
• SOLID principles
• CRAP principles
• Stable team vs stable project
• Is agile for you and your team?
• Effective agile planning sessions
• When and why to switch jobs?
• … and more :)

I intend to write the book in a casual tone for an easy read, with not only tips and ideas, but also first hand experiences and stories - funny or sad. ;)

Now, it's time for you to show me how much you value your career by signing up and letting me know what you think the book is worth.