|
|
|
|
|
by lanyard-textile
446 days ago
|
|
It is not a fun reality — but in a business where profit is the goal, cadence deadlines are helpful. When used right, they give you a good gauge on how much time the company would like you to spend on the problem. Ideally they calculated that risk higher up for the business’s needs, and you are being assigned the work for a strategy. The frustrating part is this rarely happens in practice :) I’m working at a place now where they actually do this, and they strike the right balance: Not too demanding, but gives a good idea on the effort I’m expected to give for this, and my work clearly has an effect on the grander vision. I can make a beautiful program in one month — or I can make some compromises and get it out by Friday. That’s programming vs. engineering. |
|
“We’re going to spend the next two weeks working on X, so scope your ambitions accordingly—what’s realistic to expect in that timeframe?” seems like a perfectly reasonable and healthy negotiation to have, one compatible with respectful working relationships.