Annoyance, money loss, on AWS, missing out on customers, data loss, damages, lawsuites
Horizontal axis: Amount of tests.
| sport | |
| prost | |
| Bier-Tanke Antik-Rebe Eiter-Bank KI-beraten Bi-Raketen Bakterien Benkert-AI |
| 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 | |
| } | |
| } |
| git ls-files | sed 's/.*\.//' | sort | uniq -c | sort -u |
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.
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Gamepad test</title> | |
| <link rel="stylesheet" href="styles.css"> | |
| </head> | |
| <body> | |
| <div id="player"></div> |