Recently, it has come to my attention that not all developers have the ability to make an impact.
But that begs the question, what does making an impact mean?
Making an impact.
It's coming out the door - swinging. So much of a developers role, especially in a start up, is determined by their first 3 days. Day 1, yes, come in, settle down, welcome aboard. Day 2, start asking all of the questions you had from day 1, and for heavens sake, do something besides look busy.
Day 3, you better have your shit together, and you should be swinging for the fences.
Don't ask for something to do, demand a project. And while you're doing, don't ask questions the very second you think you don't know something.
Look for the answer first.
It's this mentality that I find so damn frustrating - all of the answers should be in the code base. Run a damn grep on your project base, and find an answer. There's no excuse for any mid, to upper mid level programmer to be asking stupid questions. By stupid question, I'm refering to in the inabilty to traverse the code base in search of functions, methods, answers.
Make an impact, 3 days.
1 Comment to Make an Impact
Leave a comment
Most Popular Posts
- Learning Python the Disappointing Way
- RockMelt Browser – Future of Browsers?
- Adding Syntax Highlighting – Yay!
- PHP Tip: Handling Form Data
- Q&A: Which Framework Should I Use?
- Make an Impact
- Someone Failed to Inform Me
- Modrewrite and Short Urls – What you really want to know.
- Professional PHP
- Google Speaks on Net Neutrality and Benefits of caching