JafTalks

I've been programming since I was 15 and I've loved technology and programming every since, during that period I’ve learned some lessons that i would like to share.

Here are my most memorable 15 lessons so far.

• Set a time expectation of every task- don’t sit in from of the monitor trying to solve a problem for 8 hours. Set a time table for yourself of 1 hour, 30 minutes, or even 15 minutes. If you can't figure out a solution to your problem within your time frame, ask for help or research your problem on the Internet instead of trying to be super-coder.
• All languages are languages - Over time, once you understand how one language works, you'll notice similarities between other languages, but try to know more than one language.
• Always backup your code - I've experienced a complete hard drive failure and lost a lot of code when I was younger and felt horrible because of what had happened. The one time you don't back up your data may be the one time where you have a strict deadline with a client and they need it tomorrow. Source code/version control applies here as well.
• You are not a Super Coder. Live with it. - I always thought that I knew so much about programming, but there is always someone out there better than you. Always. Learn from them.
• Learn to learn more
•  Change Management - Your knowledge of technology and/or programming should be similar to how you treat stocks.
• Support entry level developer - Assist and train the junior/entry-level developers on good programming guidelines and techniques. You never know...you may move up in rank and you'll feel more confident having personally trained and prepared them for their next position.
• Simplify the algorithm - Once you're done, go back through your code and optimize it. A little code improvement here and there will make support happier in the long run.
• Document your code - Comment your code.
• Test, Test, And Test – even if you hate testing and test cases, Ah yes I really hate them.
• Celebrate every success – it’ll let you feel better, and satisfied.
• Have Code Reviews Frequently - Don't look at it as people crucifying your coding style. Think of it as constructive criticism. Review your code and always ask, "How could I have done it better?" This will accelerate your learning and make you a better programmer.
• No project is ever simple - I've been asked by friends, family, and associates to just "whip something up for me." To "whip" up a program or web site, it takes planning from both parties to complete something that both sides can appreciate. If someone needs a 3-page web site with Microsoft Access from the start, it winds up becoming a 15-page web site with SQL Server, a forum, and a custom CMS (Content Management System).
• Never take anything for granted - If you take on a simple project, you may think that a certain section will be easy to complete. Don't think that even for a moment.
• Software is never finished - Software is never finished, it's "temporarily completed." Sound advice. I hope this list of lessons learned have either inspired or provided a help for some people.