"Curiosity" is a more powerful force than ever in the age of AI.

I completely agree; I don't know how to code at all. For the agent-based products I'm building now, I delegate code review to a dedicated "reviewer" agent, and then the primary agent makes further modifications based on the errors found—repeating the process until every issue is resolved. To my surprise, this approach not only achieved my initial goals but also resolved other underlying issues within the workflow, far exceeding my expectations. This way, AI development isn't limited by my own input and output capabilities.

X (formerly Twitter)

Uncle Bob Martin (@unclebobmartin) on X

@ori_pomerantz I’m significantly older than you. I started coding in the late 60s. My current strategy is to not read any of the code written by ...

“The real story is actually pretty boring: we just sat at our computers for six years and coded.”

Today GPT-5.6 SOL it performed another 5 hours optimization. Its first test failed, and I thought it took a week for the quota to come out of the shit mountain code. The results exceeded my expectations and it fixed many issues that were not considered before. And the just failed test is a more complex modification that goes beyond the scope of my scenario. It wants to do things so much. 😂 View quoted note →

Pura Vida #Nostr 🤙

In the end, the task took just over seven hours to complete. Previously, I had only dared to assign development tasks requiring one or two hours. GPT-5.6 sol is amazing. View quoted note →

I’ve been so immersed in "vibe coding" that I almost forgot what the Zap⚡️ feeling is like. That Zap⚡️ feeling is really great.

I assigned got-5.6 sol a critical infrastructure refactoring task; it has been running for over four hours, and now—after I’ve finished my workout and a meal—it is performing the final verification. The ability to accurately execute and verify long-running tasks gives me the time to go work out.

Pura Vida #Nostr

Recently I debugged a pretty absurd Codex CLI incident. My new 18-core Mac was usually running only two Codex terminals, but the fans suddenly went crazy, the machine got hot fast, and on battery it drained extremely quickly. Activity Monitor did not show an obvious app causing it. Eventually I checked the process table and found 16 orphaned Codex CLI processes in the background.Each was using close to 100% CPU, together consuming roughly 16 CPU cores. Root cause: I used to quit Codex by directly closing the Terminal window. After the window disappeared, some Codex processes did not exit properly. Their TTY became ??, stdin/stdout became (revoked), the parent process was adopted by launchd, but the Codex main process kept spinning. Debug command: ps -axo pid,ppid,tty,pcpu,command | grep codex If you see tty=?? and high CPU, it is likely an orphaned process. Fix / prevention: 1. Do not close the Terminal window directly to quit Codex. Use /exit or /quit first. 2. Wait until you are back at the normal shell prompt, then close the terminal. 3. Periodically check for orphaned Codex processes. 4. If you find orphans, only clean up Codex processes with TTY=??. Do not run pkill codex, or you may kill your active Codex session too. #codex

The Age of AI Exploration is here. The so-called career crisis is largely an illusion. Young people who master frontier AI technologies no longer have to spend years serving the old guard before earning the chance to create and express themselves. This will be an era of abundance, creativity, and vitality. Great ideas will no longer be buried beneath seniority. In a new age of exploration, having a mission and setting sail matters more than waiting for the perfect mission.

Pura Vida #Nostr 🤙

The mummy has been awakened.

Pura Vida #Nostr 🤙

Pura Vida #Nostr 🤙

Pura Vida #Nostr 🤙