Our Biggest Enemy Isn’t Developers Who Refuse To Move Forward, It is Developers Who Pretend To Move Forward
Software Engineering is such a nascent practice that we have very little that we can point at for facts, and instead spend much of our time listening to circumstantial evidence from developers who have tried and had success with different tools or techniques. And at the same time, since we don’t have an infinite amount of bandwidth to try everything for ourselves, we will often listen to other developers that we trust when they say that something is not good or adds needless complexity.
Now, there are some developers take the time to carefully evaluate and think about all of the tools and practices that come there way, but just like in every industry, there is a vast majority who do not put this kind of thought and work into their endeavors. This is something that is to be expected almost everywhere though, you have a small piece of the overall populace who puts in more work, has more insight, and who shares this knowledge, and they are looked at for leadership and guidance by the majority. You know the kind of people that I am talking about, the Martin Fowlers, Bob Martins, and Kent Becks of the world.
Read the rest of this post at CodeThinked.com
- Login or register to post comments
- 2098 reads
- Printer-friendly version
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)




Comments
Tab Hockamier replied on Fri, 2009/10/09 - 12:32pm
I DO agree with what you say and being at the mid 40's range in age I find that if I want to be relevant then I MUST move forward. I do enjoy moving forward but I also DO NOT offer thoughts about technical details unless I know my facts. It's so hard for many to say: "I don't have a good answer for you".
Joel's comment was better left untyped and unsent - I would guess he knows that now.
I offer one consideration in one narrow area not exactly related: Just because something is new (hence, often the need to move forward) that does not mean that it is worth moving forward for. I do not need a long list of bad ideas - Microsoft has tried many things that were crap in implementation: ActiveX Docs anyone?
Just my opinion.