ram

AI architect who passionately wants to teach and support anyone interested in creating this new future

[ram @rammaree]

Definitely. But politics may never allow it.

When you think about job titles and organisational hierarchical control structures are more about control and accountability false done adhered to in the name of productivity and maximising ROI

[Zara Zhang @zarazhangrui]

We should stop categorizing people as “technical” and “non-technical”

[ram @rammaree]

@emollick Most of enterprise AI adoption is automation, which was possible even before AI, but not its cheaper and accessible or comprehensible to senior leadership. Very few know how to harness the real power of AI or even comprehend what it means: let alone doing the work required.

[ram @rammaree]

@KaranD93 @emollick Organisations are built for control and not for innovation. And the legacy tech worked perfectly to implement that. AI implemented properly should collapse that and create innovation. So organisations will say they want AI but will never truly adopt it.

[ram @rammaree]

@svpino Personal apps have increased. It’s mainly an obsessive toy for me to build a lot of stuff. The real problems have not been solved yet.

[ram @rammaree]

@acatovicx @emollick make me a billion $$ while I am asleep 🥳

[ram @rammaree]

@AlexShtf @emollick That’s not how it works. Simple way to think it is: the US controls the world and makes the rules 😵‍💫

[ram @rammaree]

@Team2Trading What held into the close is what I watch next → https://t.co/fuZzxHEW6L

[ram @rammaree]

@Barchart What held into the bell, logged for tomorrow → https://t.co/Uu8DFjPDtn

[signüll @signulll]

a founder has three jobs. everything else is serious amounts of noise.

1. you have to tell the story. roughly in three registers. first investors need inevitability. customers need to *feel* what you do/stand for. & your team needs a mission worth their best years.

2. you must secure the capital before you need it. running out of money is running out of options. you have to be relentless about it.

3. you must obsess over the product. product is the story made accessible for everyone. every shipped detail is a sentence back into the narrative in point number one.

this is the entire job.

everything else you either delegate or kill. early on with a really small team, delegation is a huge tax so you have to learn to kill more than you delegate.

[ram @rammaree]

@naval are you serious? no real man who had power or the resources fought wars in the frontlines. Only the powerless slaves and destitute were forced into the frontlines, which literally was suicide.

wars were never a noble deed.

[ram @rammaree]

@elonmusk What culture itself is is the deeper question. It is what the majority agree on and can feel they belong to. There’s a different feeling when you can see bloodlines across millennia vs those who barely can call any city their home.

Times have changed. So hLanguage and meaning

[ram @rammaree]

@vijayshekhar @satyanadella He isn’t saying new. MS is fighting for its survival. Only time can tell if they’ll come out of the other end in one piece.

Nothing innovative about what he is saying. All intelligence has moved to the LLM/agentic layer neither of which Microsoft control.

[ram @rammaree]

We are the sun. It’s been said by all the actual wise men before us.

But we’re lost in a world obsessed with technology (and the opinions of billionaires)

[Elon Musk @elonmusk]

Just the very early stages of the singularity.

We are currently using much less than a billionth of the power of our Sun.

[ram @rammaree]

@SebJohnsonUK @KanishkaNarayan I don.t get this. AI killed the need for e-leanring courses and the govt creates and boasts about an e-learning program.

Get them to just use Chatgpt and learn?

[Andrej Karpathy @karpathy]

A few random notes from claude coding quite a bit last few weeks.

Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent.

IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits.

Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased.

Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion.

Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage.

Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building.

Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it.

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements.

Questions. A few of the questions on my mind:
- What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*.
- Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro).
- What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music?
- How much of society is bottlenecked by digital knowledge work?

TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

[ram @rammaree]

@zarazhangrui You should do this at the start of the project when you evaluate architectural options by doing deep research on what’s out there and what other are saying on each component.

[ram @rammaree]

@BrianNorgard great idea. sell it first and then - the possibilities of building the solution have become easy

[ram @rammaree]

@EliaAlberti @JoschuaBuilds can you share workflow and prompt please?

[Hiten Shah @hnshah]

Most people have no idea what it actually takes to be a founder. They talk about vision, grit, or passion. Those words are props.

What you really sign up for is a life where every decision feels like it costs something real. You will spend years being misunderstood. By your team, your family, even the people you hire to help you. You will fail in public and still need to keep the energy up in private. Every founder lives with the weight of knowing that you can do everything right and still get crushed by luck, timing, or somebody else’s mistake.

Founders aren’t braver than anyone else. They just get used to uncertainty, then stop waiting for clarity. Most of your wins won’t feel like wins at all. The first revenue will be too small. The first team will outgrow you or leave. The first product that feels right will barely matter to the market. You will doubt yourself in private, sometimes every week. The founders who last figure out how to keep moving while the ground shifts underneath them.

Most outsiders want the founder badge but none of the scars. They want the upside, not the drag. The hardest part is sticking around after every plan gets blown up and you have to rebuild with less optimism and more scar tissue. What makes it work isn’t relentless hustle or some mythical trait. It’s learning to make peace with constant discomfort, and then making decisions anyway.

If you need constant reassurance, you’ll give up before the real work begins. If you want everyone to like you, you’ll never make the calls that matter. If you can’t handle months where nothing feels certain, this life will eat you alive.

But if you can hold your own in chaos, get better at being wrong, and still want to show up and try again, you just might have a shot at building something that matters.

That’s what it actually takes. And nobody cares until you make it work.

[ram @rammaree]

@LoganTGott @claudeai In a new chat I ask it what my current instructions are and in light of the more recent conversations how should I update my core project instructions and then go update them. Because I found unusual not only forget the original instructions I set, they become outdated.

[ram @rammaree]

@dejavucoder that's where the learning is, isn't it?