Hacker News new | ask | show | jobs
by lykr0n 2693 days ago
I guess this depends on the person, but for me- My boss 100% hands off on my day to day work.

I can chose what I work on for the day, week, month, or Quarter. I have my work area, but within that I have 100% freedom to figure out what I need to do- the only thing I need to do is to be able to justify it. I can select the tickets I want to work on, areas to improve, initiatives to take up, or software to build.

Also, the core business drive of measuring and qualitating your work. So, you can see the impact you are having on the business (positive or negative- NOT in a way that affects your job, but in a way that you can say "I did X which made Y faster, causing a 3% growth in click-though rates).

But I do wish I had a more private workplace. Hexes are better then the nightmare of open offices, and I work on a quiet floor, but sometimes I wish I had a door I could close.

2 comments

Funny enough I've been obsessing over this concept of "aligning vectors" / measuring the impact of personal KPIs against the total progress of a business.

“Every person in your company is a vector. Your progress is determined by the sum of all vectors.” — Elon Musk

It's quite nice to see the positive impact you have on the rest of the business. It gives value to what you do day to day. Where I work is very data driven, so any chance can be measured if you know how to look
I don’t have that much freedom of the what when it comes to business features but I do have freedom of the how and I’m good with that.

I also have a great deal of influence over my hobby horses - infrastructure (AWS) and Devops.

We're large enough where we have a specific DevOps Teams and the Team doing AWS is doing it wrong. If I didn't have the freedom I have now, I would have a very different opinion of this place and be looking for a smaller shop
Your probably not doing "DevOps" if they hired a "team" for it, sounds like ops on aws
"DevOps" doesn't mean shit. It's a bullshit term define by who is using it. That team is in charge of kubernetes, and automated application deployment stuff, so they are the team ensures developers can push to production quickly. Which, now that I google it- it's exactly what the "official" definition is.
Well, in our case, dev ops means the developer is also responsible for setting up the CloudFormation template to create any resources, CodeBuild to create packages and CodePipeline or Octopus Deploy to deploy code.
Suppose I think "Devs doing ops" (less boundaries between teams), but agree it's a bullshit term