I have been looking at a lot of mermaid diagrams lately (Agents love them).
Most platforms don't render them very well.
But, @craftdocs gave us beautiful-mermaid (thank you!)
I built a small local-first editor/viewer on top of it
Link below -
data centres are draining bengaluru’s ground water. right now there are 31 data centres in bengaluru. data centres consume roughly 20 million litres of water EVERYDAY.
where will that water come from because bengaluru has no river and is entirely dependent on groundwater.
more data centres are planned and upcoming. our country will not survive this. the planet will not survive this. we will not survive this.
In my Applied AI Cohort, at the end, when we chit-chat, someone asked this question: Given that AI is generating most of the code, is it even useful to learn new languages deeply? Here is my take.
You should learn at least one programming language really well - like, really, really well - and know the specifics of others.
For example, if you are building something in Go for the first time, you can get far by prompting your way through it. You can ship working code without knowing the basics.
But yes, you can read the code, but can you truly understand it? Let me double down...
Go has goroutines and channels. Rust has ownership and lifetimes. These are not syntax details; they are mental models.
AI can generate code in a language you do not know, but it cannot generate intuition for a language you have never understood.
When a deadlock happens, memory usage balloons, or a race condition surfaces, you need that mental model to reason about it. AI cannot hand you that reasoning.
According to me, what AI changes is the ramp-up time - more specifically, syntax friction. That cost is now close to zero. The remaining work is the interesting part: building intuition for how the language thinks.
So, you do not need to memorize every standard library method in every language. But you do need to deeply understand at least one language and then pick up the specifics of others as needed.
That depth in one language gives you the mental model to reason about all the others.
As engineers, our job is to solve problems, not necessarily to write code.
Hope this helps.
If you're looking for an order to try this in:
1. mise
2. hk (parallel git hooks will change your life)
3. aube (you are now immune to JS hacks)
4. pitchfork (a 'nicer' foreman)
5. fnox (higher up if your team is heavy into password managers and everyone uses diff ones)
Lovable just made TanStack Start the foundation of every new app it ships. ~100,000 new apps a day.
TanStack has 13 named public sponsors across Gold, Silver, Bronze. Lovable isn't on the list.
At $400M ARR and $6.6B valuation, that should change.
i’ve started sponsoring young indian builders / devs / security researchers who are doing genuinely cool work. only sponsored @amanvarshney01 and @ni5arga so far, but i want to scale this up over time
there are so many young indian devs doing insanely cool shit with basically zero support. i want to help with that
more of this soon
@shadcn I needed the same. Todos and Scratchpad in Solo from @aarondfrancis is pretty good for this usecase for now and I am not tied to any specific cli or harness for it.
think back to projects you've worked on in the past
it's hard not to imagine they'd have been completed way faster now that we have ai
but everything still feels as slow and as difficult as ever
https://t.co/gHoAUUfHAR - boot once, run everywhere.
A MicroVM that runs on hardware you already own.
Close your laptop and it hands off to another host.
Works across macOS, Linux, and Raspberry Pi. (aarch64)
just enabled a minimum age on npm package installs for my machine, should've done this sooner but if you haven't either here's a prompt for your coding agent to configure it for you:
""Find my package manager (bun/pnpm/npm/yarn) and configure a 3-day minimum-release-age / cooldown for installs to blunt supply-chain attacks. Exempt my workspace scopes. Verify the exact config key in current docs before writing."
Many recent TanStack Router versions from earlier today were compromised via a Mini Shai-Hulud Supply-Chain Attack.
We've already unpublished affected versions and are still taking every action possible to secure our publishing pipelines.
Luckily there's a lot of maintainers and talented people working on the issue.
Follow the @Tan_Stack account or the tweet below for ongoing updates.
i think skills are a mistake and the wrong abstraction. i almost never want my agent auto invoking them and i have built custom tooling to "toggle" them on/off to prevent them from always being present in my context window.
@tanishqk Looks beautiful.
I had built something similar that I had been using quite heavily to share diagrams with my team. Beautiful-mermaid is a great lib.
https://t.co/NHiOHotr9V