I actual care more about the product and how it's built, the standard it is built to and the processes used to build and manage it.
Any manager that's worth working for still codes. Once they code no more they care more about process and profit.
185 karma · joined February 5, 2012
I actual care more about the product and how it's built, the standard it is built to and the processes used to build and manage it.
Any manager that's worth working for still codes. Once they code no more they care more about process and profit.
18 years ago we had much of what we had today. Things might move on but they do not change. I mean hey, everyone still hates Visual Basic!
At least 18 years ago we were actually writing the majority of our code rather than relying so heavily on libraries and third party code. I mean someone only has to pull a Node.js plugin for padding and there is complete melt down!
As a CTO I have long appreciated real world knowledge and experience over inexperienced, cheap, eagerness. Our employee's are all 30+, most have families and I believe that leads to well balanced and focused employee's. That is not to say I would not hire a younger employee but with age comes the kind of experience you need when building a new company quickly.
To be honest the "we work hard and play hard - we are a family" line would have put me off of a role even in my early 20's. Just because I want to work hard, it doesn't mean I want to always be hanging out with a team, I want a life as well.
I actually think that the ageism in tech is a result of it being a young industry. As more and more dev's go grey the problem will resolve itself.
One final note I have seen here and on other places - The why not become a CTO or Start your own company suggestion is fine for those that want to but there are a large number of developers who actually _love_ being a developer and have no interest in moving up into management. That's great and I hope that as the industry matures people realise that being a developer for your whole career is a choice and not a failure.
For my day job I have a PC Specialist Cosmos IV (https://www.pcspecialist.co.uk/notebooks/cosmosIV-15/) maxed out with a Full HD IPS screen, 16gb, SSD & traditional disks and it is currently running Windows 8.1. It's a good PC replacement and I have used PC Specialist for about 10 years for work laptops. I have to say this is the first one I have had some concerns about as the keyboard is wearing out after 18 months. My first one from them lasted through 4 years at my first start-up where I was using it 6 days a week 12 hours a day.
I agree with the comments below that state code the simplest solution to make your tests pass but learn the best approach to tackle given problems so they are second nature.
My experience has shown me that learning various principles and pattens results in smaller code bases that make maintenance and refactoring easy. In turn you are able to deliver quicker.
That being said, its not always so easy to achieve with established code bases.