Comments on: Why we will not have senior developers anymore http://www.ardonio.com/2008/01/14/why-we-will-not-have-senior-developers-anymore/ Wed, 14 Dec 2011 13:12:31 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: Don Ardonio http://www.ardonio.com/2008/01/14/why-we-will-not-have-senior-developers-anymore/#comment-4 Don Ardonio Tue, 15 Jan 2008 10:10:00 +0000 http://www.ardonio.com/2008/01/14/why-we-will-not-have-senior-developers-anymore/#comment-4 It wasn't my intention to argue against higher level languages. I merely tried to get the point across that people should understand the 'pointer hell' before moving to higher levels, and a lot of that I somewhat blame on our educational system. They try to be fancy and avoid the nitty gritty matters by jumping into higher level languages right away. which means that the developers coming out of there are like constructors that can build a wonderful house, but just have no clue you need a solid foundation. It wasn’t my intention to argue against higher level languages. I merely tried to get the point across that people should understand the ‘pointer hell’ before moving to higher levels, and a lot of that I somewhat blame on our educational system. They try to be fancy and avoid the nitty gritty matters by jumping into higher level languages right away. which means that the developers coming out of there are like constructors that can build a wonderful house, but just have no clue you need a solid foundation.

]]> By: DefV http://www.ardonio.com/2008/01/14/why-we-will-not-have-senior-developers-anymore/#comment-3 DefV Tue, 15 Jan 2008 09:40:00 +0000 http://www.ardonio.com/2008/01/14/why-we-will-not-have-senior-developers-anymore/#comment-3 It seems you're arguing against high-level languages because the programmer isn't aware of the lower workings of the language, the memory allocation, pointer hell, and so on. I agree with you to some point. <br/><br/>It's important to know what a language does exactly to debug such problems as memory leakage, high memory usage, long runtime on certain "blackbox" functions and so on. But to me, there it stops. High level languages have set a new cruise speed for most applications, that could've never been reached with the low-level ones. It has fired up a whole new way of working, and I truly believe that hardware upgrades are cheaper then developer time.<br/><br/>This of course doesn't mean you should strive for "quick and easy" code. This means it gives you a chance to write your code As Beautiful as you can, without having to worry about system performance because you've added an extra MySpecialObject.<br/><br/>To me, a senior developer is a person who has experience with all sorts of different design patterns, algorithms and methodologies to get things done. And to be honest, I don't care if (s)he does it in C, ASM, ...<br/><br/>(And if you're creating software for embedded devices, you have an argument, but you have exceptions for everything ;-)) It seems you’re arguing against high-level languages because the programmer isn’t aware of the lower workings of the language, the memory allocation, pointer hell, and so on. I agree with you to some point.

It’s important to know what a language does exactly to debug such problems as memory leakage, high memory usage, long runtime on certain “blackbox” functions and so on. But to me, there it stops. High level languages have set a new cruise speed for most applications, that could’ve never been reached with the low-level ones. It has fired up a whole new way of working, and I truly believe that hardware upgrades are cheaper then developer time.

This of course doesn’t mean you should strive for “quick and easy” code. This means it gives you a chance to write your code As Beautiful as you can, without having to worry about system performance because you’ve added an extra MySpecialObject.

To me, a senior developer is a person who has experience with all sorts of different design patterns, algorithms and methodologies to get things done. And to be honest, I don’t care if (s)he does it in C, ASM, …

(And if you’re creating software for embedded devices, you have an argument, but you have exceptions for everything ;-) )

]]>