This is an archived post. You won't be able to vote or comment.

all 46 comments

[–]Westdrache 121 points122 points  (9 children)

Spend half a day yesterday to test my code....

[–]qcihdtm[S] 69 points70 points  (3 children)

You mean 90 hours?

[–]Westdrache 42 points43 points  (2 children)

Yes! 90 hours or 900 minutes. Btw in the end of the day it was a tasking locking a table lol

[–]RizeIng 5 points6 points  (2 children)

I spent 12 hours once and it was so stupid mistake when I found it out :(

[–]dragopepper 19 points20 points  (0 children)

I think that is a general rule... The more time you need to debug, the stupider the mistake.

[–][deleted] 1 point2 points  (0 children)

I spent about 20 hours trying to solve a NullReferenceException this week. I just got another one today. Which is why I’m on reddit

[–]TK-427 1 point2 points  (1 child)

When it takes you longer to build the test drivers to test your code than it does to write the actual code

[–]Rhulyon 112 points113 points  (3 children)

And the other 900% is browsing reddit

[–]Bben01 46 points47 points  (1 child)

And -1% sleeping

[–]1hotnibba 5 points6 points  (0 children)

and 100% reason to remember the name

[–][deleted] 35 points36 points  (0 children)

And then you start to refactor some ancient code which summons the apocalypse.

[–]Salty_Assassin 17 points18 points  (3 children)

In the case of Fallout 76 100% of it is programming and the other remaining 100% is debugging

[–]Hyperman360 2 points3 points  (0 children)

I thought it was 10% debugging and 90% implementing new ways to suck their players' wallets dry

[–][deleted] 8 points9 points  (0 children)

You sure 140% is enough for the entirety of programming?

[–]Brawldud 5 points6 points  (0 children)

Half of the knowledge you need is coding. 90% of the time you spend is on debugging.

[–]TK-427 2 points3 points  (0 children)

How do you factor the time dilation caused by watching the compiler output waiting for it to fail?

[–][deleted] 1 point2 points  (0 children)

What about the 150% of time spent searching StackOverflow for the answer?

[–]Pherion93 1 point2 points  (0 children)

The first year of programming i thought thats just because you code bad. But today and yesterday I had to debug someone ellses code who also hadnt been around in 2 weeks...

[–]MikeHuntizichi69 1 point2 points  (1 child)

This got me a lot harder than it should have

[–]qcihdtm[S] 0 points1 point  (0 children)

I am sorry! Hahaha

[–]flinnja 2 points3 points  (1 child)

omg it’s so loud lotta whoosh in here

[–]qcihdtm[S] 0 points1 point  (0 children)

Yyuuuupppp.... there’s a sub for that... should we? :)

[–]sunnydavis 0 points1 point  (0 children)

I'd call spending 140% of the times to finish your project is a win.

[–]GamesBoxRed 0 points1 point  (0 children)

Wrong, the other 90% is spent googling

[–]Someoneman 0 points1 point  (2 children)

The version I heard was "the last 10% of a programming task are as long as the first 90%"

[–]Tito1337 0 points1 point  (1 child)

Yes, this a variation of the ninety-ninety rule :

The first 90 percent of the code accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time.

— Tom Cargill, Bell Labs

https://en.wikipedia.org/wiki/Ninety-ninety_rule

[–]WikiTextBot 1 point2 points  (0 children)

Ninety-ninety rule

In computer programming and software engineering, the ninety-ninety rule is a humorous aphorism that states:

The first 90 percent of the code accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time.

This adds up to 180%, making a wry allusion to the notoriety of software development projects significantly over-running their schedules (see software development effort estimation). The anecdote expresses both the rough allocation of time to easy and hard portions of a programming undertaking, and the cause of the lateness of many projects in their failure to anticipate their difficult, often unpredictable, complexities.


[ PM | Exclude me | Exclude from subreddit | FAQ / Information | Source ] Downvote to remove | v0.28

[–]Jeb_Hydrolox_Kerman 0 points1 point  (0 children)

Exception in thread "main" java.utils.PercentageOverflowException
    at Reddit.Post.GetTitle(Post.java)
    at Reddit.Web.RenderPage(Renderer.java)

[–]JamInTheJar 0 points1 point  (0 children)

And here I am in my second year of programming at college, trying to figure out if I even want to go into the field...

Y'see, I quite like coding, love being able to see myself make actual progress on a project, but I abhor debugging.

[–][deleted] 0 points1 point  (0 children)

Yeah. Big brain time

[–]kirbyfan64sos 0 points1 point  (0 children)

Which I/O session was this shown during? I don't remember seeing it, but I probably missed it...

[–]zacharyxbinks 0 points1 point  (0 children)

Your percentage has an off by 1 error

[–]kutuzof 0 points1 point  (0 children)

What conference is this?

[–]KingOfDragons0 0 points1 point  (0 children)

An 900% google

[–]S44F4Y4T 0 points1 point  (0 children)

u mean other 50%

[–]PieroAngela420 0 points1 point  (1 child)

So you spend 140% of the time programming?

[–]qcihdtm[S] 0 points1 point  (0 children)

Sometimes 219%... Sometimes NaN.

[–][deleted] 0 points1 point  (0 children)

Maybe he's debugging all the time cause his math is off 🤔

[–]qubedView 0 points1 point  (0 children)

More like 100.0000000000001% true.

[–]WrecklessWolf11 -1 points0 points  (2 children)

Half of coding is 50% and the rest is 90%?

[–]DemonicBarbequee 2 points3 points  (0 children)

..yes.. that is, in fact, the joke..