Totally but thats why they’re called estimates. We cant tell the future

Yea estimating sucks ass. But in that situation id give a large range with low confidence

How to estimate:

1. Give a range and confidence rating
2. Track all estimates and how long it actually took
3. Refine future estimates to more closely match past features with similar complexity/effort required

Yea just draw the rest of the owl duh! 🙄

Well i just saw pugjesus move ~10 comms to piefed so…

Reading and writing programming syntax uses the same areas of the brain that handle language. Knowing a programming language is very much a skill that erodes quickly when not used

Is there a “luigi” somewhere in your posts lol

Do you even get told what you upvoted that was ‘problematic’ or just gotta guess outta the 37 things you upvoted yesterday? Lol

Don’t forget these responses

why do you want to do X?? Why don’t you do it Y way (that doesn’t actually solve the problem)

but then we’ll figure something out.

It’s not a trivial problem to solve lol

Such as…?

I would 1000% become dumb as a rock with someone watching me not to mention in a high risk setting such as an interview

Write multiple versions of docs for different audiences

Ideally the solo dev and visionary would cease development and move into a product owner role. Bringing other devs up to speed on the code base while also maintaining quality, vision, and cultivating a team is no trivial task. Not to mention this particular dev may not want or be able to such things.

Paprika 3 is great! Highly recommend

60m? Ms got a steal no wonder Reddit can’t monetize

Need to throw a rand() in there to make it less easy to unfuck