Greetings, dear readers! This is my brand-spanking-new coding blog, as opposed to my leadership blog over at http://www.dare2xl.com/. Dare2XL is mainly about daring to stand up to The Man for what's right, such as choice of language, "wasting" time on developer-level testing, and so on, including many situations having nothing whatsoever to do with software development. This blog will be about how to choose and use your language, write and run unit and integration tests, and other aspects of software development -- primarily those dealing directly with code, versus, say, requirements definition, or writing documentation. You know, the fun stuff! :-)
Why "codosaurus"? Long story short, let's just say I'm a bit older than most of my current colleagues -- enough so, that I grew up on plain old C, not Java. But I'm not a dinosaur, as this old mammal continues to learn new tricks. I learned C++, Java, Python, Javascript (including AJAX), Perl, Ruby (including Rails), and a lot more, in my spare time. This blog is my way of sharing the overall software engineering experience I've gained over the years -- though often instantiated via specific languages, especially the ones the li'l whippersnappers have probably been exposed to -- or might want to be exposed to.
Now it's your turn. What advice would you seasoned programmers/engineers/developers/whatever, give to today's up-and-comers? What questions would you ask of me? What is the airspeed velocity of an unladen swallow?
I have one piece of advice:
ReplyDeleteThere is no good reason to worry about not being the best. All you can do is give your best effort. If you fail, don't give up. Your only competition is your own fears.