Crunkle_Foreskin
Seethetarians in this thread
Update: spoke to the Head Dev this morning and made sure I knew what my position was, so it’s definitely prioritising the project’s speed first.
Then spoke with the Senior in question and apologised for any friction, and suggested we do a debrief after the first phase of development and go back and smooth things over.
All went well! Thanks for your thoughts everyone.
I wouldn’t necessarily say OpenAPI and Composer are new technologies, they’re tried and tested and commonplace across most PHP projects. I totally get his point. He’s an older dev who’s sat comfortably for too long with an ageing stack, and now is completely behind the new guys who are coming in from other companies and wanting to change things.
I think the place we disagree is that I believe technology is a place where progression is a hard requirement of the job. Computers get better, customers get more demanding, old solutions improved. You need to improve, every day.
My issue is more when the response to a new piece of minor technology that will make our lives easily is: “I don’t want to learn YAML”.
The thing I worry about is the salary and job responsibilities. The interview for the role was completely different from what I am now doing.
It was advertised as a modernization role, and now I’m just a web developer. Do they expect the interview or the current position?
The Senior doesn’t really know Laravel or any advanced patterns that I’d expect a mid level developer to know.
I think intentionally picking the wrong solution makes you an irresponsible developer. Not only are you introducing technical debt immediately but slowing down your future progress.
But, you’re probably right about leaving him alone and letting him own these problems. I’ve suggested OpenAPI, he picked Google Docs. I’ll be there when we have to spend a few days rewriting the specs in OpenAPI.
