I still don't think PHP is a good idea for a greenfield project or anything, but they have done a good job of hiding all the footguns.
Agreed. I remember happily starting a couple of new PHP projects in the last decade and the frameworks felt like working in any other programming language.
Like many other things, PHP makes it easier to do the wrong thing than other languages which make you do the same thing correctly.
They switched to blue/green deploys for the new site (which I suspect was done at the server level, not with symlinks or the like).
Indeed! I suppose I misunderstood my manager's direction to onboard the new guy.
Anyone else see the exact opposite, that out of N people that _could_ become managers, it’s the worst individual contributors that do? Mostly because they want it most. People who love being individual contributors are going to become good at it, and they’ll resist management tasks.
I think this is great and very natural. But there’s a kind of zombie myth that engineering managers are the best former engineers that refuses to die. It’s decent engineers with some aptitude and/or desire to manage.
Anecdotally, the two worst managers I've had were developers, but I've had three really good managers that were formally developers. Then the best manager I've had used to be a business analyst.
It doesn’t help that most of the management advice you find on the internet assumes that inside every employee is a happy, productive worker and their manager can unlock it with the right words.
In the real world the range of employee types is very large. Some of them are just toxic and you’re not going to coach it out of them. Knowing when and how to cut your losses is important for preserving the rest of the team.
Too right. Hire slow and fire fast was a saying that I saw recently.
It's interesting how everyone thinks they're "managers" in "agile" teams.
Scrum Masters, Product Owners. I've even had Designers and QAs trying to make decisions on behalf of the team.
Oof, hits close.
Suggestion from a QA to implement some feature that is hugely difficult to implement? Business agrees so developers now need to make it happen.
What I find fascinating about this is how predictable people become once you know the different personalities and their nuances. It helps tremendously to also be interested in getting to know people. And yes, you will encounter people that are disruptive. Usually, and I can only speak for my environment, the team itself is quite good at handling that. I just need to give them room and provide a setting where they can talk about the issues at hand on a constructive base.
That's why I love my job, and it may sound weird - but I'm the guy who can ask all the obvious questions that come to mind and others don't dare to ask. I love that I can build myself a toolbox to use in different (and difficult) situations. And I love to see my team succeed on the one hand, and learn from failure on the other.
I will never cease to be amazed at managers who don't do this. I've seen enough managers who pick fights with the wrong subordinates then have to scramble to replace key staff when they leave.