Mauve 👁💜 @mauve@mastodon.mauve.moe

we need to stop letting them use the term vibe coding and take it as our own, real vibe coding would be opening up an ide at like 4 am while having dim lights listening to the most autistic music on the planet with plushies on ur desk as emotional support

Something I'm learning in my adventures in Linux is that it's vital to have a second, working computer with you in order to search for ways to fix the thing you've just massively broken.

#vibecoding be like

(I often still don't understand the topic but at least they got to have fun infodumping :3)

Two different approaches to debugging a software problem:

The Sudoku approach: stare at the limited set of clues you have, and think harder and harder about them until you find a way to deduce something useful.

The Minesweeper approach: don't even try to figure out the solution from only the clues you have right now. Instead, focus on finding a way to acquire another clue, and then using that to get another, and so on. Eventually you've collected so many clues that the answer is obvious.

Sometimes the Sudoku approach is necessary, because you've got all the clues you're ever going to get. But I think my new motto is "Never Sudoku a problem when you can Minesweeper it."

Programmers are usually fed a steady diet of features and bug fixes. But occasionally they get to work on performance problems. This development methodology is known as intermittent fasting.