Lawand

@thekitze the file name being SmartActions is ironic af

llms are imbecilles i set a swiftlint rule of max 200 lines file size and instead of extracting methods etc into files the fucking donut just split the current offenders into Part01 Part02 Part03 lmaoooo

serverless is amazing. you get: - cold starts - 14 dashboards - functions timing out because JSON was 3kb too large - logs delivered sometime between now and your retirement - a billing model based on quantum mechanics all to avoid managing a VPS that has had a working tutorial since 2009

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.

My average 3AM session with Claude..😄

If your startup does not have a UUID microservice you’re ngmi

a CTO has three jobs. everything else is noise. 1. create clarity. in the AI era, code is cheap. coherence is expensive. your job is to make the system understandable — clear architecture, clean interfaces, predictable infra, documented decisions. humans and AI both build better when the environment makes sense. 2. prevent chaos before it compounds. AI can generate thousands of lines overnight. it can also generate thousands of future problems overnight. great CTOs obsess over reliability, security, monitoring, testing, and deployment discipline because every inconsistency becomes future confusion at scale. 3. make engineering predictable. the best engineering teams are not the fastest. they are the most dependable. when every deploy is calm, every service behaves as expected, and every engineer knows the patterns — velocity becomes automatic. predictability is leverage. this is the entire job. - not chasing every framework. - not attending endless meetings. - not pretending complexity is sophistication. the modern CTO is no longer the best programmer in the room. they are the person who designs an environment where humans and AI can ship great software safely, repeatedly, and without drama.

Introducing SubQ - a major breakthrough in LLM intelligence. It is the first model built on a fully sub-quadratic sparse-attention architecture (SSA), And the first frontier model with a 12 million token context window which is: - 52x faster than FlashAttention at 1MM tokens - Less than 5% the cost of Opus Transformer-based LLMs waste compute by processing every possible relationship between words (standard attention). Only a small fraction actually matter. @subquadratic finds and focuses only on the ones that do. That's nearly 1,000x less compute and a new way for LLMs to scale.

you can outsource your thinking but you cannot outsource your understanding

@ideavim 🤩

IdeaVim 2.33.0 ships VimEverywhere🎉: vim keyboard navigation outside the editor. - Hint labels over every clickable UI element - NERDTree mappings in any focused tree - Vim window-motion inside tool windows Stop reaching for the mouse! Check it out: github.com/JetBrains/idea…

@SergiiShymko As the famous saying goes, culture is who you hire, who you fire, and who you promote. And product is equal parts what you choose to build and what you refuse to build. Without the power to unilaterally control all of that, you cannot succeed.

“Everyone can code now!” Dude, no one can code now.

🤣

@thenanyu great .. another chat box

You can talk to Linear now btw. It’s awesome.

Digging into reports, most of the fastest burn came down to a few token-heavy patterns. Some tips: • Sonnet 4.6 is the better default on Pro. Opus burns roughly twice as fast. Switch at session start. • Lower the effort level or turn off extended thinking when you don't need deep reasoning. Switch at session start. • Start fresh instead of resuming large sessions that have been idle ~1h • Cap your context window, long sessions cost more CLAUDE_CODE_AUTO_COMPACT_WINDOW=200000 We're rolling out more efficiency improvements, make sure you're on the latest version. If a small session is still eating a huge chunk of your limit in a way that seems unreasonable, run /feedback and we'll investigate

Thank you to everyone who spent time sending us feedback and reports. We've investigated and we're sorry this has been a bad experience. Here's what we found:

this isn't a huge deal but this is really the flavor of our times everything is just sloppy. everything has 20% margin of error. nothing has precision just automate it. just select all. just make ai figure it out i do it too and it all adds up to a gross feeling world

@AxelTalksFilm AI

the contrast is insane

I'm usually not one to write thought pieces without much technical depth. But here we go. Slow the fuck down. mariozechner.at/posts/2026-03-…