コーディング — 今週のランキング

You might believe you should spend less time thinking about code because of AI. I strongly disagree! We’re watching this play out live where tons of AI generated code becomes a liability. At the end of the day, an engineer needs to be responsible / on call for code that gets shipped to production. If you don’t understand the system you’re trying to debug, you’re probably going to have a bad time. Yes, AI can help with all of this, if you set up the proper systems. You can have agents triage prod logs, look at errors, etc. You can speed up parts of the investigation, but an engineer needs to make the call. There might be serious customer or financial implications from that change. I expect the trend continue for trimming dependencies, vendoring code so you can modify it directly, preferring simpler systems with fewer abstractions, and spending waaaay more time thinking about system design and code maintenance. I’ve said this before, but it’s a great time to get familiar with CS fundamentals and some of the history behind what great software looks like. Many parts will be different in the coming years as AI progresses, but also a lot more than people realize will stay the same.

So here's my latest set up Every site I have is a profile on Termius like > hoodmaps .com I click it and immediately I'm in my server and I get dropped in a tmux session that's always tied to the corresponding site I wanna log in to To make this work I have this startup snippet in each site's Termius profile: > cd /srv/http/hoodmaps.com && tm (so /srv/http is where my sites are and then hoodmaps .com is the example site here, and "&& tm" is the important part here) Then in my ~/.bashrc file I added this (written by Claude Code) which defines the "tm" function, again all it does it just put me in the right tmux session based on the folder I'm in The result is I can switch without interruption from my laptop to phone in Termius with auto reconnecting sessions and usually I just have Claude Code open in each session to work Before I had to mess around with 1) not having smooth switching from laptop to phone, I'd have to use Claude Code's /resume for it, annoying, 2) having multiple sessions for same sites, gets messy and confusing fast, now it FORCES me into one session per site, this just works so well, I'm so fast, and each of my sites is just an open tab in Termius, I've never worked so structured and clean! Here is the code, maybe it helps somebody: # tmux session per folder. `tm` (no args) attaches to / creates a session # named after the current dir's basename. `tm name` overrides the name. # Works whether already inside tmux (uses switch-client) or outside it. tm() { command -v tmux >/dev/null 2>&1 || { echo "tmux not installed"; return 1; } local name="${1:-$(basename "$PWD")}" # tmux session names can't contain '.' or ':' — replace with '-' name="${name//./-}" name="${name//:/-}" if [ -n "$TMUX" ]; then tmux has-session -t "$name" 2>/dev/null || tmux new-session -d -s "$name" -c "$PWD" tmux switch-client -t "$name" else tmux attach -t "$name" 2>/dev/null || tmux new -s "$name" -c "$PWD" fi } # Auto-attach on interactive login: picks a session named after wherever # you land. Plain `ssh server` lands in $HOME → session "root". Use # `ssh server -t "cd /srv/sm.levels.io && bash -l"` to land in a site # folder → session "sm-levels-io". Skips inside tmux and non-interactive # shells so scp/rsync/scripted ssh keep working. if command -v tmux >/dev/null 2>&1 && [ -z "$TMUX" ] && [[ $- == *i* ]]; then tm fi

A nice way to stay safe is to ask Claude Code to audit your devices I do same on my VPS servers, so today I tried it on my MacBook Pro and it's pretty good at it too It founds lots of stuff that was not secured, I actually forgot to enable FileVault when I got this new MBP in 2025, also some local networking stuff Just ask it "can you security audit my computer"

Most people think AI coding is about generating snippets faster The real shift is much bigger: agents that can plan, build, debug, and ship full-stack products I spoke w/ @AnthropicAI about what we learned building @emergentlabs with Claude and much more The full-conversation is live! https://t.co/6ZkGd494sb

A lot of people are building with the assumption that the codebases we work in today will still matter next year. I’m not sure if that’s the case.

You vibecoded a website somewhere other than Replit? That’s not wise, but okay… we’re going to let you import it and get a free mobile app. Yes, FREE MOBILE APP!

“I built my first three apps using Cursor and thought that was fast, but trying Replit for Dial completely blew me away. I built the MVP over a single weekend, and it actually got approved by Apple on the very first try—which has never happened to me before.”

Clearly these people haven’t experienced the magic of Gemini 3.5 Flash Preview on High in the new Antigravity CLI

Code is actually the right abstraction. Too often I see the future of software engineering diminished down to, effectively, writing and reviewing markdown files. Yes, it will be hard to review thousands of lines of agent code. But maybe the takeaway is that you want less code? Rather than just giving up ("well I guess we won't read the code, or we'll read this lossy markdown summary") this should be a signal forcing you to think about better systems. - How can we make our codebase more verifiable? For example, fast/robust/stable tests, or moving to a typed language. - How can we deslop or improve the architecture/abstractions of the code generated by agents? For example, spending more time up front on the codebase architecture/types before yolo generating all of the code. - How are we going to maintain and evolve this codebase over time? The slop compounds. One great solution here is... you guessed it, learning from the past decades of software engineering! For example, you might just have the wrong abstraction entirely, leading to a ton of duplicated code. I think the markdown folks *are* right in some ways. If you are using skills every day, for many different prompts and workflows, isn't that effectively "coding with markdown"? Kinda. There's been plenty of ink spilled on the merits and benefits of skills. To me, skills make your style of working legible for agents. They don't replace code and that's not really the point. In reality, there's this messy and constantly re-evolving future in which both of these things are true: 1. Skills (and markdown) are important for how you give input to the agents and ensure high-quality code & systems are created 2. Looking at the actual code will not be replaced by markdown summaries or a collection of spec documents that ignore the lower level details of the code In summary: reality has a surprising amount of detail (and nuance)!

code interpreter is a light weight code execution environment lets you do: - RLMs - programmatic tool calling - more! without having to spin up a full sandbox we'll be writing a lot more about the use cases here, but check it out!

TanStack types are basically all inferred, so you could say we were token efficient before tokens even mattered 😝 . Even if they weren’t, I’d still make my agent use types.

"Hey little bro, I need a website by tonight". Me: "Done" Thankyou Cloudflare + TanStack Start + AI

gotta say Codex is completely unrecognizable from 3 months ago. guys went extreme founder mode on this thing @gabrielchua was demoing this and i was like “you guys have agentic excel on mac”

Apparently at @AIEMiami geoff complained about @SAPConcur being dead software and a SAP guy was in the audience and invited him to SAP to advise on how to do AI transformation for 6800 employees TLDR he made fun of SAP, and SAP… concurred

re github should we all just be deploying to our own servers instead? keep code local? only publish open source code?

trillion $ idea... claude but it actually follows your instructions

AI coding is obviously not perfect right now. Everyone knows that. But some people are reacting like their whole identity is under attack because now more people can build things without needing years inside the tech industry. That’s the real reason behind a lot of this anger. Earlier, coding was a strong gatekeeping skill. Now AI is slowly removing that wall. Of course some people won’t like it. AI keeps getting better every few months while the same people keep saying it will never replace. We’ve seen this story before with every big technology shift.

In the near future, say within the next one to two years, I want Codex to replace software engineering completely and eliminate 99% of traditional jobs. That’s my dream. That’s our future.