Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
bagfox71940dWell currently you’re asking for it.
You should mofo specialize on one thing and do that one thing good and efficient.
junon284540dThis is how the field works. This is why senior engineers are often very grumpy, low-patience individuals.
Hate to break it to you. If you ever find a job that isn't like this, stick with it.
bagfox71940d@OliverTramp They keep on pushing that until you actually refuse it. They don’t understand what you’re actually doing.
If you can’t make the deadline, let that be it. Your health is more important than a deadline.
Don’t let them read those medium articles. They need to listen if you actually don’t make the deadline, otherwise they expect that you can still do faster.
jeeper534640d@junon I disagree. All jobs have crunch times, but very few would have you in 12 hour days for 3 years straight as a “part time” developer.
OP you’ve got 3 years professional dev experience. It’s time to brush up that resume and start job hunting. You alone are not going to be able to change that culture. Maybe you can if you are the only dev, but even then the executives have already formed these unrealistic expectations and it might be better to do a clean break.
devphobe778340dMy 2 cents:
- Push back on irrational deadlines
- say no to unreal feature requests
- ask for more defined tickets instead of accepting vague requirements
If your product owner can’t handle it, find a job that can. It’s not worth your mental health if they don’t understand were all human.
@devphobe I just talked to my boss, the more I push the deadlines, the more he seems to push back. And giving me vague requirements doesn't help either.
So, I also said to myself "fuck it, I'll do my best and push average code and let him learn from the experience that it doesn't help anyone when you push your developer into corner like that"
The third point is really the one I should work on most I think. I accept vague requirements and then over deliver, which I thinks makes them think that, the time it takes to write vague, one line feature requests is the amount of time it takes to push it to production lol