3 ms·
Are you on a product team? What level of experience do you have? I joined a unicorn recently and have felt similar feelings, however I am on an infrastructure
by jb3689 6y ago
Are you on a product team? What level of experience do you have?
I joined a unicorn recently and have felt similar feelings, however I am on an infrastructure team and there is tons of work to do so it's relatively easy to not stay blocked (if we are blocked it's usually our fault). That said, we end up blocking a lot of teams (lack of resources, lack of tooling, things just take a long time). I find the architecture pretty standard so it's easy to navigate around though
> only a few very small changes get done
I can echo that. I've tried to make bigger/more changes but the team can't keep up with them and they introduce too much risk. A lot of my day-to-day winds up being balancing risk, change, and upside. The work is a lot more deliberate which is good for big changes and bad for small ones
> I normally work about one day trickle out my changes during the the week
To be clear, I would not recommend doing this. I strongly prefer to work hard and then find a place where people work as hard as you. Complacency is the worst (for me)
> it's possible the rest of the team is doing that too, but I have no way of knowing
It's a bit unsettling that the team doesn't talk about things like this
> when I look back at the progress made since I joined and estimate the cost to the company (salary, servers, etc) it's frankly disgusting
How much value have you added though? At my company we have multiple simple fixes that save multiple millions of dollars annually. It's pretty easy to justify cost at scale. Maybe you need to examine the value you're providing further?
> I find it unsatisfying and like a waste of my time on earth
This says "it's time to move on" to me. I would go to a smaller company personally or move to a different function (e.g. infrastructure). I sympathize with your comments about dev speed - that's a huge one for me. It sucks to be bottlenecked by development process rather than bottlenecked by something more in your control