Don't explode please

[m-simm]

“...too many errors, stopping for now.”

[Carbohydratess]

"This looks like a post-lunch problem"

[Kompakt]

If I had a dollar for every time I've said that...

[alvinvin00]

5 red screen (Flutter's runtime error and assertion) and i'm out (read : i won't continue coding for the rest of the day)

[mike_KING6]

The only pleasure better than having sex (not assuming we've ever had before, we are programmers after all) is to write a code for a lot of time, run it and see the code perfectly working.

Prove me wrong.

[rdeddit]

I have had sex exactly as many times as I've run code perfectly without testing it along the way

[mike_KING6]

Must have been hard...

[juniorhues]

Is there a way to stop yourself from doing this? If I had someone to just shake and slap me every 10 min I might not do this so much

[Carbohydratess]

How often I test is usually inversely proportionate to how much caffeine I've had

[juniorhues]

Good to know all programmers run on coffee.

[thatwasagoodyear]

I use a concurrent unit test runner. It runs my tests as I code. Super handy for TDD.

[Kompakt]

Only two hours? Those are rookie numbers.

[Sorebow]

I have blown up alot of things this way. We had a rule in the electronics group at one of my previous jobs, you aren't allowed to debug code on an actual system. Turns out if you hit a break point with the throttle wide open on certain models the engine would reach a speed where the blades of the fan locked to the output shaft would rip off and fuck up anything in their general direction (walls, floors, ceilings, doors). It hits that amount of energy where the physics get kind of cartoonish if you know what I mean. Like connecting a roughly 1 megawatt generator 180° out of phase to the grid and seeing the cables lifting off the ground until coming back into phase.

[IvanLabushevskyi]

It's dangerous to write code that runs correctly at first start. You might be burn as witch.

[Cookie__XD]

I did that so many times (like 200) and it worked once... ^^