A QA engineer walks into a bar. Orders a beer. Orders 0 beers. Orders 99999999999 beers. Orders a lizard. Orders -1 beers. Orders a ueicbksjdhd.
First real customer walks in and asks where the bathroom is. The bar bursts into flames, killing everyone.
This is the Facebook playbook: you lure in publishers by promising them a traffic funnel ("post excerpts and links and we'll show them to people, including people who never asked to see them"), and then the rug-pull: "Post everything here, don't link to your own site"
Instant and delayed rewards from writing tests may disappear when we write tests last.
This means we'll be less likely to write tests.
What are these disappearing rewards? Short thread.
In addition to AI, one of my other passions is public transit. My favorite youtuber is @RM_Transit
Here are AI generated Subway Maps in the style of famous artists.
1. Vincent van Gogh
Unpopular opinion: Pull requests are a terrible idea in almost all contexts.
Focus on finishing things as a team instead of keeping everybody busy. Do code reviews in real-time through pairing or ensembling instead of blocking the flow of work waiting for a pull request review.
Yeeesssss!! Lowkey obsessed with decision records/ADRs right now. If I were starting a new company (which I *am not,* and *will never*) I would be using these from day one.
And not just for technical decisions, either. For any decision with a blast radius of >1 group.
One of the oddest agile software development dysfunctions I see so often: same old big upfront solutioning with a delusion of certainty, and then squeezing that solution through Scrum with no feedback, no working product increments, and no retrospection. Like … what’s the point?
There's a comparison between writing maintainable code and playing pool/billiards.
If you're bad at shooting pool like I am, you make the easiest shot you can, hit a ball into a pocket, and the cue ball rolls wherever it rolls on the table. 1/7
Committing at least once a day, reduces the blast radius of your changes: if it's good you can build on it more quickly; if it fails you find out and fix it more quickly.
Huge thanks to our wonderful CAE community for all your support over the years. There won't be any meetups scheduled for the forseeable...
...but we're still here! Find us on Slack or contact the CAE crew @sprky@simolaw@Labyrinthsprite