In such an environment, spending the extra time to re-invent the wheel whenever we want to design the next model of a Toyota sedan strikes me as rather counter-productive.ĭon’t get me wrong. Why couldn’t we just say that, like most other professions, the regular, meat-and-potatoes work of a developer has significantly changed over time? We stand on the shoulders of giants, and we live in a commercial world that emphasizes efficiency. If they aren’t often used in a practical setting, their main effect would probably be to make us feel more secure in our identities as programmers. While following his recommendations would probably improve our coding fundamentals, these skills need to be used regularly to be maintained. With all due respect to Hanselman, though, I’d like to suggest an alternative view. He talked about how we all feel unworthy sometimes and suggested a skill-building regime of Code Katas, Project Euler problems and, well, programming without googling. Hanselman was very respectful to the poster, I thought. That post was inspired by a plea from a young reader to resolve something of an identity crisis about whether they were “really a developer or just a good googler”. I recently saw a blog post by Scott Hanselman that got me thinking about what it means to be a developer these days.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |