Max is a life enhancer for tech & entrepreneurship. Which seeks to blend both to build innovative products or services for the world that solves hard problems.
Mainly web development for money. Everything else for fun :) Rust, WebAssembly, Flutter, ML, C64 Assembly, Raspberry, ... a lot of plans, much less free time to work on them.
True, but then estimates are just estimates and are always bound to certain premises.
The real problem starts when clients take those estimates for hard facts and/or meddle with the premises thinking that such changes won't have any substantial effects on those estimates.
Max is a life enhancer for tech & entrepreneurship. Which seeks to blend both to build innovative products or services for the world that solves hard problems.
Hi i'm an avid web and app developer in search for creativity and always going after new ideas.
Developer of Atomics Digital, Invoice Me and Reactor JS
That's the classic π€£
Client: How long will this take you? By the way, we need it by Friday. π€ Such projects are usually doomed. And it's not because of the devs.
Max is a life enhancer for tech & entrepreneurship. Which seeks to blend both to build innovative products or services for the world that solves hard problems.
Giving estimates even if you don't know how long it will take.
In these cases one of my colleagues is more than happy to give "500 +/- 490 hours"-like estimates :)
True, but then estimates are just estimates and are always bound to certain premises.
The real problem starts when clients take those estimates for hard facts and/or meddle with the premises thinking that such changes won't have any substantial effects on those estimates.
Yeah.. that's usually the case when they are non-technical in nature and they want a rough date in their planning to get things done.
π β¨
I wish I agreed less...
nailed it man
Exactly.
Giving estimates when Manager has already set a deadline!
Plot twist
That's the classic π€£
Client: How long will this take you? By the way, we need it by Friday. π€ Such projects are usually doomed. And it's not because of the devs.
I got to agree with that and negotiating on the deliverables is not fun.
Giving estimates while still in the meeting with the stakeholders and before being able to think on the requirements.
Of course you do not know it, that is why it is called an estimate :-)
The main problem is with people who treat an estimate as a promise and/or do not care about context and do not follow-up on information changes.