Added pi to the list. Unironically considering it as the base for AI setup. bsky.app/profile/max....
12.02.2026 02:28
👍 0
🔁 0
💬 0
📌 0
Added pi to the list. Unironically considering it as the base for AI setup. bsky.app/profile/max....
PSA for those caught in the AI hamster wheel, something I wrote in my college notebook 22 years ago, still holds up:
Happiness is a cause, not an effect.
Get happy now, in your mind, then do things. You don't work towards it, you start with it, and it enables everything else.
Here's where the puck is going: AI will replace software. You ask it to solve problems, you instantly get custom apps. All computing will become this. We will be sharing T=0 prompts that produce useful results. All software engineering will become about improving AI itself.
My attempt at deciding on an AI orchestrator. So many out there. Suggestions/corrections welcome. gist.github.com/maxim/c6ef7f...
If you're gonna embrace non-determinism at all stages of software dev, including verification, why even make software? Just have AI be the software. Why have an "if" condition when AI can decide. Unironically, that's where we're going. It's moving ground all the way down.
Of all the AI artifact-managing solutions I've seen so far, beads is the one that nails it.
Is it just me, or @github.com's PR reviews have been getting more and more buggy? Now when editing a pending comment, all formatting is lost. Bullet points, paragraph breaks, `code` quotes. You just get a chunk of plain text and have to redo the formatting by hand.
If you've seen my blog post 4 years ago titled "Don’t Build a General Purpose API To Power Your Own Front End", I've finally finished writing a "4 years later" follow up to tell how it played out, and answer some piled up questions. max.engineer/server-infor...
Some updates: @topazlabs.bsky.social acknowledged the issue and made it right. @simpleanalytics.bsky.social fixed the SSL problem. Commento.io is still unresponsive, had to start a dispute. Thankfully I found a recent backup of my comments, and was able to move to FastComments.
Everything seems to have broken. @topazlabs.bsky.social is failing all my family video renders (for days now). commento.io is down (expired domain?), so can't keep working on my response-to-comments blog post. @simpleanalytics.bsky.social won't provision SSL for my domain. Wtf is going on internet?
MacOS >=13 hides accurate AI-based OCR called LiveText. It's very good, it's what lets you select text in images. I was working on a Ruby-Swift bridge for it, to make scanned PDFs searchable, but a few hours ago this project beat me to it. Much recommend! github.com/mkyt/OCRmyPD...
Most software has the same relatively simple data transforms, under different names and reasons. Could it be that if we (developers) focused less on business jargon in types and hierarchy, and more on the story of data transformation, we would get code that's easier to follow?
Which AI does stock market best. A fun thing to observe. hkuds.github.io/AI-Trader/ (GitHub here: github.com/HKUDS/AI-Tra...)
When you ask LLM for sources, and it gives them to you, you better damn well read them. This just happened yesterday in a codex session: news.ycombinator.com/item?id=4575...
In what I’ve seen, doesn’t seem TPTBs make decisions based on numbers. It’s more about specific arguments. Having 30 comments say “we want the default without the ugly comment” won’t move the needle as much as one person laying out simple and clean strategy kinda like you did.
I was thinking why AI code doesn’t sit right with me even if it gets very good in the future, and it’s about possibility of human intervention. Wrote a small opinion here, curious what you think. max.engineer/failover-to-hi
A controversial Monday thought for you: ~15 years of experience is when a programmer is the most dangerous for the ecosystem. That's when you beautifully wrap up your subpar experiments with a pretty bow on top for others to use, and they actually gain traction.
A thing that bothers me about total AI takeover narrative is the perpetual need to have its back "just in case", and what that actually implies. max.engineer/failover-to-hi
Curious why you don't prefer to specify rate limits per controller, seems clearer in our case. As far as state, it seems to be kept in redis, have you tried digging in to see what/how it stores? (I haven't)
After considering elaborate ways to make TinyMCP support different return formats, finally arrived at this "genius" 3 line solution, which brings you version 0.2.0. Keep it simple folks. github.com/maxim/tiny_m...
For example, if I'm in a repo, use the top search bar, and find nothing after a couple of attempts, I cannot go back to the repo I was in without pressing back multiple times.
UX issue on Github: if you search, there is no way back to where you were before. You must either back-back-back in the browser, or enter the original url again. It's interesting, because it feels super annoying in practice, but actually not obvious from webdev standpoint.
Is it now _outdated_ to care about code quality minutia, and not losing my ability to focus insanely well on little details? I guess all of you folks in the "syntax doesn't matter" camp should be happily embracing LLMs. Working code is all that matters, right?
Even 1-shot-correct code by Claude 4 is subtly bad. Gotta read it with fine tooth comb when project matters. What's worse, "instructing LLM" brain mode feels mutually exclusive with "writing code" brain mode. It hurts to switch (and I'm an easy context switcher).
I notice that especially older gems tend to not separate layers. If you want to
do_specific_thing
most of the time you should:
1) def do_generic_thing(options)
and then
2) def do_specific_thing; do_generic_thing(CONFIG_FOR_SPECIFIC_THING) end
Just edited the wording. Plz let me know if that still reads dissonant. Appreciate the feedback!
I took @avdi.codes‘s advice to add that. 😅 But now that I have a few people in the list, I have no idea what to do with that info. Was traveling once, and asked if anyone wants to hang out while I’m there (in case anyone’s there) but no takers. I’m probably doing “finding friendship” wrong.
Potentially an AI could learn how groups of colleagues think and leave reviews that are likely to match their behavior. That could be an interesting way to address what you said.
That’s exactly it, our perception is the only thing that matters, and all rules and “laws” are incidental, and may help or hurt case by case. But my advice generally has been that we should lean on our colleagues’ review, since most codebases are maintained by small groups.
Ironically, maybe ai can help us measure that. A while ago I wrote about 3 maintainability questions: how what and why max.engineer/maintainable.... Maybe we can get AI to review PRs for how well they answer them. Would be an interesting experiment (haven’t tried). This isn’t a “how much value” ofc.