> [...] I proudly called myself a coder as opposed to an engineer. In my eyes, this highlighted the way I focused on the details, performance optimization, knowing the intricacies of the language, and being able to explain how things work, as opposed to juggling Java-esque abstractions.
Ouch. There's an idea that I've seen a few times now that there are two key types of developers: developers who thrive on building products and solving problems through the existence of code, and developers who thrive on the process and the low-level puzzle of getting that code to work and then to work well.
The former are having a really great time right now. The latter are feeling justifiably threatened.
I am in the former group, and while I agree the prospects are not singularly bad and I see enormous amounts of work that will need to be done, I don't think I/we are having a great time. Working harder than ever under unrealistic expectations and general chaos from everones FUD. In my area the need for software is huge but there has never been no nearly enough money. Maybe we can finally build some of it.
I agree that the threat is more specific to the more detail oriented kind of person/role, though.
Ouch. There's an idea that I've seen a few times now that there are two key types of developers: developers who thrive on building products and solving problems through the existence of code, and developers who thrive on the process and the low-level puzzle of getting that code to work and then to work well.
The former are having a really great time right now. The latter are feeling justifiably threatened.
I agree that the threat is more specific to the more detail oriented kind of person/role, though.