Code safely or try'n break things?

@AlexDeLarge @Alice you two are cute together :p

First:
Add some unit-/integration-tests on the subject you want to break.

Next:
Break it, refactor it and fix everything till the tests work again.

;)

break it and send it to your underlings to fix it.

Blackbox testing

@Alice @AlexDeLarge taken? Nooo

Break it good, break it hard, and learn how to put it back together... just don’t send the broken bits to production 😏

@C0D4 I see that way to often

@Alice haha, your ridiculous :D

@AlexDeLarge I am weird. There you go.🦄

I don’t think you should “try” to break things, however you should build and innovate without the fear of breaking things; shit happens.

Break everything. Break it all, you can learn some really helpful stuff from FUBAR code, just do it with a separate copy or use version control.

Break things like Zucc?
I'd rather "code safely" (whatever that means) than (brainamputatedly) break things.

I see "code safely" as looking ahead and think before you code. When you change code, think where else you have to change code so the behaviour is still intact.

The 2 Juniors that started in our company also had the mindset of "break things". They had to pretty much learn it the hard way in 2 days, that quality is always preferable to quantity. Boy did they mess up our code in the week of a release.

Both