| Website | https://mikkelmalmberg.com |
| https://twitter.com/mikker | |
| GitHub | https://github.com/mikker |
| Bluesky | https://bsky.app/profile/mikker.dev |
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.
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.
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?
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.
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.
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
