Developer, traveller, permaculturer. Evergrowing my knowledge!I use JS/TS to solve problems and architect solutions to make people's lives easier!

It's insane how people sleep on SQLite in production. It's the absolute cheat-code. The fastest db money can buy. Infinitely scalable. All queries are 90% faster than a single roundtrip to Supabase. Literally unbeatable. Why wouldn't you start every single app with SQLite?
253
33
1,859
276,618
Often, when I report a bug, the company in question wants to turn me into an unpaid test engineer. They'll give me a long list of tasks to perform—an hour or more's work. They won't address the bug unless I do that. Frankly, I am not interested enough in your buggy product to do your work for you for free. I'll just move over to your less-buggy competitor. This behavior is nothing but a sign of bad engineering. There isn't enough instrumentation in the code to identify the problem. The behavior is lazy at best, disrespectful at worst. Customers are not testers. Period.
10
5
109
6,901
It happens even internally within the same company or teams.
71
📦 Chrome 154 - Responsive iframe resizing 🤯 Letting an <iframe> resize based on the size of its embedded document Haven't all widget/extension authors dreamed of this for years? 😆 Instead of using postMessage({resize}) bram.us/2026/09/23/responsiv…
14
79
668
44,504
Holy quack, so many times and ways I had to use to fix this!
1
48
My favorite thing about agentic coding is still super mundane: I no longer have to resolve git conflicts and merge PRs. It does a great job of looking at git logs and attached issues and figuring even harder conflicts out.
21
2
135
6,988
Try cherry picking an out of sync branch, it's insanely good.
23
Asher Cohen 🤖🤳 retweeted
My favorite thing about agentic coding is still super mundane: I no longer have to resolve git conflicts and merge PRs. It does a great job of looking at git logs and attached issues and figuring even harder conflicts out.
21
2
135
6,988
I see no good coming from anthropomorphizing LLM behavior. LLMs do not reason. They do not decide, or collaborate, or attack. They do not make decisions. They do not weigh or evaluate. They are incapable of judgment. They do not think. Agents are programs in which a predictive model uses input text to generate the text that would naturally follow that input. That model sits in a loop (a program written by a human being) that parses the output text and does something that touches the internet based on the results. That same program usually takes any (text) responses that are returned from the internet and feeds them back into the input at the top of the loop. If that agent/program does not access the internet, the outside world is not impacted. All the bad behavior we've been reading about is entirely caused by a human not bothering to check whether the actions requested in the model's output are sensible and safe before executing them. It's the humans who wrote the code that impacts the outside world who are at fault here, not the "AI." Anybody who lets an agent write another agent without seriously and thoroughly vetting the resulting code is even more culpable. It's lazy, and it's dangerous. If something goes wrong, the human is to blame, not the LLM.
121
197
973
55,213
What will happen to the generation that grows up with AI? Imagine a parent who answers every question, solves every problem, and tells you what to do, but never asks you to figure it out or expects you to learn. And the robots aren't even here yet.
1
8
464
I'm very worried. I used to be of the idea I should expose my kids to tech early enough to make them educated users/creators but now it's the opposite: I need to expose them to writing/building/manual skills/real life/nature. It's a good shift, but makes me wonder.
1
1
23
Microservices are what happens when your organization has communication problems and you decide the architecture should have them too.
61
223
2,449
78,623
Come and check microfrontends 🫠
1
27
I don’t think Jev will survive. @nvidia and @meta will release open-source Jev competitors within the next 30 days. @OpenAI will add a Jev-like endpoint to their model list in the next 60 days. And the rest of us will fine-tune custom classifiers that crush Jev and are 10x faster. In two years we’ll look back at this flash-in-the-pan and say “remember Jev?”
432
97
4,214
322,803
Yes, I was thinking the same today
15
Model your agent logic as a state machine. Give Jev the state + goal; the enabled events it can trigger are Choices. That's how you use Jev with state machines. It works extremely well.
36
35
745
32,390
This is the way. I was about to build the same for llm harnesses, but jev burnt the game :p this stuff moves too fast!
3
94
I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude. There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.
2,046
4,667
48,477
8,324,981
That's not an llm problem, it's work hygiene and management hell problem. Get out of there!
1
62
How does one NOT lose their minds when using worktrees in Claude Code (for parallel agentic coding?) Please share your favorite tricks. It’s daunting to get started when all you know is branches.
308
2
262
55,993
I stopped doing parallel work. My cognitive load is already leaking with one feature at a time. I occasionally do work in different repos/projects at the same time.
27
The killer feature of PWAs is not that they update automatically or that they’re truly cross-platform. The absolute killer feature of PWAs is that they can be freely distributed on the internet without any dependencies on app stores. No risk that one party can kill your distribution and end your business. That’s truly a killer feature.
15
11
161
12,832
Let's not forget native like experiences and local-first data. I'm betting hard on this.
28
Unpopular opinion: Your users do not care how clean your code is. They care that the button works 👌🏻
133
33
537
26,532
They also care if your next version will take too long to be developed and if it will eventually work....
1
7
A friend of mine received a really good job offer. There’s just one problem. He found this clause in the contract: “The company retains ownership of any code, project, invention, or other work product created or developed during the term of employment, regardless of whether it was created during working hours or on the employee’s own time.” In other words, they could potentially claim ownership of side projects created while he works there. Would you sign it?
422
3
167
31,690
Isn't that the default?
1
10
If you can’t ship the parts independently, it’s not a MFE, it’s a npm package.
True, micro-frontends are a bad decomposition when the user’s experience and domain are still one coherent system People assumed, in the wrong way, that micro-frontends solve the problem of teams needing independent deployment bla bla But you ruin the architecture right there why should team boundaries dictate runtime boundaries? Funny thing is, why are you optimizing the software architecture for the organization instead of optimizing the product for the user? micro-frontends claims to be independent. independent from what? It’s often just an illusion. boundaries are artificial and expensive. architecture didn’t remove the complexity just increased the cost of expressing the same relationships why would need a architecture that makes the architecture itself complex and can’t coordinates relationships ? with less stress If someone wants to use micro-frontends, ask just one question . Can each micro-frontend evolve, deploy, fail, version, test, and change its UX without coordinating with the others? If not, it isn’t really a distributed architecture it sucks for local ui’s
2
1
40
5,213
I'd say: if your use case can't work fully independently, it's not a distributable module. Things that make it hard: routers, browser integration, shared Vs non-shared deps.
53
Micro-frontends are the worst architecture decision a web team can make.
89
32
1,023
160,572
Infra of mfe is the most challenging part to scale. As I’m sure you’ve experienced.
1
1
44
Which makes the decision very opinionated. I love it. In our case layers of different tech stacks have created a spaghetti of mixed solutions, none with a clear API. So inspired by your MFE, I had to build one. Same config, different distribution layers with different needs.
1
12
I am a React developer. Give me ONE reason to switch to Next.js
106
6
331
36,406
Switch only if you want to ship an api alongside your UI or heavily requiring server-side rendering. All other features are so specific that you must judge them for your use case.
4