Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "autonomy"
-
the most incompetent person that ever worked with me had no proactivity, always waited for an explicit order to start to do anything and had absolutely no autonomy. this guy would frequently ask me stuff that he could find with a google search.
when the IT team was let go, the company lined me up for another job, and my boss actually told me "you work well so i can refer you, but i can't do the same for <that guy>". i honestly thought that was his first job, but no. i have no clue how he managed to work in a hospital before that.6 -
I'm pretty much at my dream job currently. A lot of autonomy as a developer, solo projects, as there are only two developers in-house and each of us is covering roughly half of the systems, we rarely work on the same thing at the same time. We do have weekly sync checkins to keep each other appraised and offer a helping hand/eye when needed.
But.
There's always a but.
Our IT department used to service 500 to 1000 employees 7 years ago, and now, through growth, opening new sibling companies, and merging with our competitors we're at 6k, give or take.
Maybe it's the aftermerge crunch to harmonize our IT systems but I've been working 10+ hours from August. It's an interesting couple of new pieces of software that I'm writing but, the deadlines are pretty tight and business requirements are anything but tight still.
I love my job, but I wish to get the bigger stuff done soon so I can take it easy. -
#Suphle Rant 2: Michael's obduration
For the uninitiated, Suphle is a PHP framework I built. This is the 2nd installment in my rants on here about it.
Some backstory: A friend and I go back ~5 years. Let's call him Michael. He was CTO of the company we worked at. After his emigration, they seem to have taught him some new stack and he needed somewhere to practise it on. That stack was Spring Boot and Angular. He and his pals convinced product owner at our workplace to rebuild the project (after 2+ years of active development) from scratch using these new techs. One thing led to the other, and I left the place after some months.
Fast forward a year later, dude hits me up to broach an incoming gig he wants us to collab on. Asks where I'm at now, and I reply I took the time off to build Suphle. Told him it's done already and it contains features from Spring, Rust, Nest and Rails; basically, I fixed everything they claimed makes PHP nonviable for enterprise software, added features from those frameworks that would attract a neutral party. Dude didn't even give me audience. I only asked him to look at the repo's readme to see what it does. That's faster than reading the tests (since the docs are still in progress). He stopped responding.
He's only the second person who has contacted me for a gig since I left. Both former colleagues. Both think lowly of PHP, ended up losing my best shot at earning a nickel while away from employed labour. It definitely feels like shooting myself in the foot.
I should take up his offer, get some extra money to stay afloat until Suphle's release. But he's adamant I use Spring. Even though Laravel is the ghetto, I would grudgingly return to it than spend another part of my life fighting to get the most basic functionality up and running without a migraine in Spring. This is a framework without an official documentation. You either have to rely on baeldung or mushroom blogs. Then I have to put up with mongodb (or nosql, in short).
I want to build a project I'm confident and proud about delivering, one certified by automated tests for it, something with an architecture I've studied extensively before arriving at. Somewhere to apply all the research that was brainstormed before this iteration of Suphle was built.
I want autonomy, not to argue over things I'm sure about. He denied me this when we worked together. I may not mind swallowing them for the money, but a return to amateur mode in Spring is something I hope I never get to experience soon
So, I'm wondering: if his reaction reflects the general impression PHP has among developers globally, it means I've built a castle on a sinking ship. If someone who can vouch for me as a professional would prefer not to have anything to do with PHP despite my reassurance it'll be difficult to convince others within and beyond that there could be a more equipped alternative to their staple tool. Reminds me of the time the orchestra played to their deaths while the titanic sank16