How blessed are we that Coke Zero doesn’t travel through the strait of Hormuz
Posts by Mikkel Malmberg
"Useful as shit!" – tunaformac.com
yo, 😍
Sorry, I meant people! Personal blogs of people
People. People are great.
What are some well-designed, simple but beautiful blogs? Microblog, macroblog, static, dynamic, whatever. Any favorites?
After hearing that @mikker.dev will no longer work on LeaderKey, I had to come up with something that fits my workflow. Let's see where this is going ⌨️
Super cool!
Yes, it's called "Menu Items" 😉
Exploring Fuzzy mode in Tuna – maybe you'll learn a trick or two.
youtu.be/NBLhM9sdr6c
“Det’ sguda grineren” får mig til at grine hver eneste gang. Vidunderligt naiv men præcis beskrivelse af at vokse op i 90er-00erne
the extremely modest confetti canon makes me lol every single time
I love how agents will be hesitant, inheriting caution from their feeble creators.
"This is a big refactor, it might take a while. Maybe just do the small version now."
Absolutely not, my boy. Go, run like a wild horse. I'll see you in 5 minutes when you're done.
That’s it. And. Just let the boring task be boring
In some ways. Depends. Are you working on the smoking hottest path of the web app where every ms counts? Or adding more fields to the admin interface? Something like the latter, I could easily get trapped in contemplating the "smart" solution instead of just doing it.
Yesterday I had Codex write all the first-pass docs for Tuna and it got it 90% great. I edited 5% and decided to not care about the last 5%.
And now I’m wondering: how could this look for every other aspect of my business? What if I didn’t care so much about the tone of the marketing. What if I didn’t care so much about the shape of customer service. What happens if i make it about the outcome and not the structure?
Now that I don’t have to care about most of it on my own stuff, it’s suddenly staring me in the face how much faster one can move, when you don’t hem and haw over every single micro decision.
The goal of this was to have a codebase that was easy to work in, easy to reason about. Easy to maintain. Almost none of it was to further the product. If so, only in a sort of meta work indirect way.
It is increasingly obvious to me how much energy I used to spend on making the code a product on its own. So much thought into the right abstractions, the right structure. Not the outcome, the structure.
Considering enforcing a strict release train with feature freeze and all to keep my split git worktree personalities to align. As soon as one is about ready to release, another has started a new epic
actually, having a folder full of markdown files written by and for claude to "maximize productivity" is the exact opposite of productivity
Man of culture. I love it
It’s in System Settings > Keyboard. Unmap the system one and it’ll work
It’s easier because we all have instant answer machines, ready 24-7. Because you dont *need* to learn the right APIs or frameworks to express your artistic skill. It’s not easier to have taste but it’s easier to learn how and to express it.
The Claude frontend skill outputs are already recognizable. Off-the-shelf aesthetics become cringe so fast. See Bootstrap, Material, etc etc.
There’s no way around learning what goes into good design. That means open eyes, lots of practice. Easier than ever but fundamentals same
New season of The Finals looks great
This lets me, the reviewer, have a chance of seeing what you can do with AND without AI. And I don't have to squint all the time to try and guess whether or not you added Tailwind 3 instead of 4 or the bots did and you didn't care.