That’s easy: If there are competing priorities then there are also competing interests and stakeholders.
If these are internal, then nicely and professionally relay that some of these will need to take a backseat and then let the stakeholders argue and decide what needs to happen.
Also drop hints that a larger technical team would help. If you’re doing things that matter, then sooner or later you’ll find yourself with a team because it’s the stakeholders pushing for it.
The worst outcome is that you burn yourself out trying to do it all, which is expected in startups but very counterproductive when the organization matures a bit.
> Also drop hints that a larger technical team would help. If you’re doing things that matter, then sooner or later you’ll find yourself with a team because it’s the stakeholders pushing for it.
Never works. If there's one thing the PHBs and their MBA goons hate it's paying people. That sounds like sarcasm but it's not. I've yet to hear some high-flying MBA tell me that the solution is to give me more money and hire more people. My favorite is that sales, a field probably just as important as developers, is not minimized and sales doesnt have to deal with "two pizza" non-sense, ping pong tables as a benefit, and long hours working literally for free because of the magic of salary. Sales gets to go home on the weekend and suckers like me are stuck doing pagerduty. Of course, when review time comes around there's never enough money in the pot to pay me more...
To these idiots, developers are a cost center to be minimized. Hence why as a developer you regularly wear the hats of 3 different subfields. For example, as a backend/systems engineer there are days I spend more time maintaining terraform/k8/whatever than actually writing code. Or even worse these days - maintaining code written by foreign contractors because labor arbitrage is the new hotness.
The industry needs an entire upheaval and software engineers need to stand up for themselves. Until that happens, the suffering will continue even if you're tied to the wall with golden handcuffs.
If these are internal, then nicely and professionally relay that some of these will need to take a backseat and then let the stakeholders argue and decide what needs to happen.
Also drop hints that a larger technical team would help. If you’re doing things that matter, then sooner or later you’ll find yourself with a team because it’s the stakeholders pushing for it.
The worst outcome is that you burn yourself out trying to do it all, which is expected in startups but very counterproductive when the organization matures a bit.