this post was submitted on 25 Oct 2023
539 points (100.0% liked)

196

16237 readers
19 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago
MODERATORS
 
top 9 comments
sorted by: hot top controversial new old
[–] Anangrierterrarian@lemmy.blahaj.zone 43 points 11 months ago (1 children)

oooh thats my code never works

i forgot to time travel to spend 90% of my time doing the last 10% of code. i get it now

[–] subignition@kbin.social 15 points 11 months ago (1 children)

Gotta get that sweet 180% time per time

[–] aluminiumsandworm@kbin.social 11 points 10 months ago* (last edited 10 months ago) (1 children)

oh, no, it's far worse than that. the last 90% is enough time to make what you thought was the first 90% become 10%.

so 0.9*expected time = 0.1* actual time

which, if you can do some very basic algebra, results in 900%. this implies that every project will seem "almost done" for about 9x the length of time you thought the project would take. in my experience, this is roughly correct

[–] Johanno@feddit.de 5 points 10 months ago

As someone who has been working on a "almost done" Task for 2 years I can confirm.

[–] fer0n@lemm.ee 21 points 11 months ago (1 children)
[–] aksdb@feddit.de 6 points 11 months ago

I also heard (and used) it as a mix of both: "the last 20% take as long as the first 80%"

[–] KSPAtlas@sopuli.xyz 14 points 11 months ago (1 children)

I mean, it makes sense, 90% of the code is probably relatively easy while the 10% is intricate

[–] henfredemars@infosec.pub 3 points 10 months ago

Embedded dev: basic OS functions not so bad.

Task switcher and interrupt code, short but painfully difficult to write correctly.

[–] AVincentInSpace@pawb.social 8 points 10 months ago

it do be like dat. you thought you were almost done with this project but nooooooo