NoSQL was such a pressure-cooker when it was hyped. It was a real relief for me when I settled into a mindset of "Okay, there is definitely a place for this technology, but I am so cool not adopting this."
I think the way the MEAN stack was marketed towards bootcamps and junior developers was a really bad thing for the ecosystem. It really was marketing too. Where were all the PEAN stack advocates. Somehow if you were in the full-stack JS ecosystem you also got shoved into NoSQL.
As for my own answer — hard to articulate, but I'd say I've changed my mind about any project management approach being inherently good or bad, and I just focus a lot more on the tweaks to get the right fit for the team and the tasks at hand. That's sort of vague, but I used to take harder stances from time to time which I just can't see myself doing anymore.
As a former PM, I've got agree with you re: methodologies. It's unfortunate that there are a lot of places that force everything into a single methodology, when in reality, each project should demand a certain methodology. When you've got a vague scope doc, unrealistic promises from sales, and high turnover in your dev team, clearly traditional waterfall methods are the way to go, right? (I'm not specifically calling out any one agency here, but I am definitely thinking of one in particular.)
I switched to PM after about three years as a dev, so I didn't learn the lesson until after I became a PM, but the thing that devs should be aware of is to never have strong opinions on approaches to solving a problem. There is no one-size-fits-all-solution and there's more than one way to skin a cat.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
NoSQL was such a pressure-cooker when it was hyped. It was a real relief for me when I settled into a mindset of "Okay, there is definitely a place for this technology, but I am so cool not adopting this."
I think the way the MEAN stack was marketed towards bootcamps and junior developers was a really bad thing for the ecosystem. It really was marketing too. Where were all the PEAN stack advocates. Somehow if you were in the full-stack JS ecosystem you also got shoved into NoSQL.
As for my own answer — hard to articulate, but I'd say I've changed my mind about any project management approach being inherently good or bad, and I just focus a lot more on the tweaks to get the right fit for the team and the tasks at hand. That's sort of vague, but I used to take harder stances from time to time which I just can't see myself doing anymore.
As a former PM, I've got agree with you re: methodologies. It's unfortunate that there are a lot of places that force everything into a single methodology, when in reality, each project should demand a certain methodology. When you've got a vague scope doc, unrealistic promises from sales, and high turnover in your dev team, clearly traditional waterfall methods are the way to go, right? (I'm not specifically calling out any one agency here, but I am definitely thinking of one in particular.)
I switched to PM after about three years as a dev, so I didn't learn the lesson until after I became a PM, but the thing that devs should be aware of is to never have strong opinions on approaches to solving a problem. There is no one-size-fits-all-solution and there's more than one way to skin a cat.