Bernhard Häussner bxt

Inverting the testing pyramid

Why avoid bugs?

Annoyance, money loss, on AWS, missing out on customers, data loss, damages, lawsuites

What is a testing pyramid?

Horizontal axis: Amount of tests.

199X-XX-XX: Someone lends me their Roland Jupiter-4 and I'm supposed to learn to play the piano on it. However, the classical education and what you can do with an analog synthesizer drif apart somehow. It was fun to play with it though, I did not know modern styles of music too much though. After a few years when the realization kicked in that those instruments are very valuable I had to return it.
200X-XX-XX: Eventually I got a basic Yamaha Clavinova and some piano lessons. However, I was always too lazy to pracitce and maybe also not very talented? It lead nowhere, but I learned the basics. The Circle of fifths was a big mystery for me – why is it structured like this? When I moved to a different city I gave it away.
200X-XX-XX: I remember seeing Garage Band for the first time on some tiny Apple conference, and being pretty excited about it.
200X-XX-XX: A friend also tought me to play the drums for

Tapas

More

Awesome tools to process lots of files

When dealing with large, old code bases (like I'm doing on a daily basis) you'll often want to migrate something in a large quantity of files. For this, you should have the necessary tests and linters in place, to be able to change things confidently. However, you still need to edit a huge amount of files, probably more than you can change by manually. And what happens when errors happen? I adopted some tools for dealing with errors in a large number of files.

	use std::iter::Peekable;

	fn take_when_3(peeky: &mut Peekable<impl Iterator<Item = u8>>) -> Option<u8> {
	if let Some(3) = peeky.peek() {
	peeky.next()
	} else {
	None
	}
	}

	sport
	prost


	Bier-Tanke Antik-Rebe Eiter-Bank KI-beraten Bi-Raketen Bakterien Benkert-AI