3 ms·
I’d agree with the ‘combination’ option. I was the second person in the team, and the one who hired me was very good. I’d learned discipline at my first job wh
by MBCook 8y ago
I’d agree with the ‘combination’ option.
I was the second person in the team, and the one who hired me was very good. I’d learned discipline at my first job where I worked on (and later solely owned/ran) two systems that handled money. If something went wrong you could trivially figure out how much your screw up just cost the company. So you had to be very careful, which was a great lesson.
The people hired after me were generally quite good (to excellent), but even without much experience they came into an environment where production was very stable and we were careful to keep it that way.
If the people weren’t good enough they wouldn’t have been capable of keeping up that standard. Some didn’t cut it.
I really lucked into a lot of opportunity and fantastic lessons at my first jobs and had great bosses who did good mentoring. I know that’s hard/impossible to replicate on demand.
I agree about negative value. Having seen so much through my jobs I can clearly see bad decisions that make the product less reliable being made, or at least horrible problems being ignored because customers aren’t complaining so let’s make tiny feature X instead.
It seems like most people in the job just have no idea how to manage software development for the long term and can’t see past short term goals/ideas.
That’s probably common across all types of projects/industries, I just wonder if it’s even worse in our industry.