News for hackers. Stuff that matters.
Re:You don’t need reproducible builds by hinkley on Wednesday August 05, 2020 @01:33PM (#24063339)
Scientific method debugging as well.

If the new version is busted, I want to rebuild the same output only changing the compiler, or package manager, or one of the library upgrades, and see what happens.

If I can't reproduce last tuesday then how do I get back to Friday when shit wasn't on fire?

Re:You don’t need reproducible builds by hinkley on Wednesday August 05, 2020 @02:00PM (#24063635)
This also goes the other way too. Repeatability is daylight that removes our ability to delude ourselves that a new problem must be someone else's code.

I don't want to police my coworkers. I just want to know that the infrastructure will hold my proverbial weight when I step on it, so I don't have to be afraid of side effects all day.

I want to know what I can trust them to do, and work to expand that envelope. If people break stuff, I eventually want them to be able to figure it out, reproduce it, and fix it all under their own steam, and [believe] that it's the right thing to do.

My automation strategy is a superset of a list I'm sure you've all heard already:

Make it documented

Make it work (automated)

Make it right (trustworthy)

Make it recommended

Make it easy (may include fast)

Make it mandatory

Make it an HR problem

About the time the tool is starting to get easy, you can start teasing people for not using it, but at some point it's expected behavior. More peer pressure from more sources. If they still like to cowboy, that speaks to trust, and they start getting delisted from new initiatives. If that still doesn't work (which, sadly, occasionally is the case), they are compartmentalized and shortlisted for the next reorg or layoff.