Ranter
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
Comments
-
Root797676y@Lyniven That's how I managed my teams. My devs enjoyed a lot of freedom. I didn't care what they did, what they built or worked on, or when/where they worked so long as they completed their projects well. I had (and have) high standards for quality they still needed to meet 🙂 That was the only thing I was strict on. I was even pretty lenient with deadlines if I saw good progress or blockers. I still fired a lot of devs for writing absolutely terrible code, or for slacking way too much.
Generally I'd promote someone if they did as much dev work as I did as dev manager, and their work showed at least decent quality. I miss my team. -
Lyniven44536y@Root Yeah that's probably one of the most efficient and pleasant method to work.
Obviously we meet to respect agile meeting and more to maintain cohésion.
Sometime it's necessary to fire someone, some devs literally deserve to stop exercising this job. -
Root797676y@Humanoid- Speed comes with practice and experience. Though quality always matters more than haste.
-
Lyniven44536y@Humanoid- don't "just make it work".
Think wisely first.
Writting quality, readable and secure code is your preoccupation.
Doing it everytime will make you faster by experience as 🌱 said.
Else you'll be stuck in a loop where you write shit and try to fix it, not leveling up, becoming one of those retarded " Senior devs" in 10 years
That moment when your manager tells you that he's okay with ultra-flexible schedules, because "I trusts you 100%. You proved your value, please come late if you prefer"
I love my job
rant