Emaz

@OmerGronich @atmoio @acoyfellow I’m putting that on my profile. And résumé.

@atmoio @acoyfellow Software engineer => Markdown shaman

Uppercasing letters and softening “MUST run” to “run” is proof that even Karpathy is not immune to doing rain dances to try to appease the unpredictable LLM gods. Talking to a computer used to be deterministic. Now you pray.

@JoePro @explorersofai My MCP uses Claude. This gives me conversational access to all my data in my own database, all local. Super valuable.

@explorersofai lol, I have my AI make MCPs but rarely use them. I see the use for sure. My systems just don't want to use 'em much.

ok, so we are done with MCPs?

Claude: MCP is still the foundational layer for how AI agents access tools and data, and most of the ecosystem hasn’t fully utilized it yet. The criticism isn’t that something better replaced it - it’s that the protocol is maturing and now has sibling protocols handling adjacent problems (agent-to-agent communication, commerce, identity). The whole stack is filling in around MCP, not replacing it.

@explorersofai Oh hell no. Just getting started.

@neda_sefati Virtual travel tours with Neda!

LIVE from Malakka, Malaysia! x.com/i/broadcasts/1…

@MeMansi12 Congrats on 6 digits!!!

I launched my SaaS 6 months ago. Here's my MRR progress 👇 Month 1 : $0 Month 2 : $00 Month 3 : $000 Month 4 : $0000 Month 5 : $00000 Month 6 : $000000

@explorersofai Amen! I won't even open up a beta without an extensive admin panel. That's a DAY ONE feature.

Set yourself up for success by adding an admin panel to your app. Fast debugging: inspect user states, logs, and data issues in seconds Safer support workflows: resolve tickets without touching production code Better visibility: monitor usage, errors, and trends in one place Faster iteration: test fixes and feature flags without full deploy cycles Team scalability: empower non-engineers to handle routine ops tasks A simple admin panel today saves hours of chaos later.

40 years as a software engineer checking in here. I think we need to update the meaning of vibe coding. It used to imply a very hands-off style, where you just let AI do everything without trying to understand it, and without any guard rails and attempting to build a solid product. That's not what you described at all. You're basically self-taught as a developer and you're taking it seriously. I've hired plenty of self-taught developers in my career. A developer is a developer. Every experienced software engineer that I know has fully embraced AI as their primary tool set. Anyone who hasn't has already been left behind. Very few of us are writing code completely from scratch anymore. What we ARE doing is watching for LLM mistakes (still common), bad architecture, and edge cases. You as a self-taught developer will deal with those same issues in the same way that an experienced developer will. We may have been doing it for longer, and we may have some insight and intuition but it's a skill that can be learned by anyone. Welcome to the team!

I won't be doing daily lives anymore simply because this platform does not award it so my videos will be on Youtube. But I will share them with you here (and get deboosted for doing so.) Let me know what you think about this 👇👇 HAPPY SUNDAY youtu.be/J9m2rucVmho?si…

Perfectly said. I said something similar in my reply, but this was much more elegant. I am more creative and productive than I’ve ever been. Once you see the superpower, you can’t go back. Also as you point out - edge cases. We still need to see those, plan for those and find them. AI seems to be fantastic at catching some of them yet oblivious to others. And it’s pretty much a roll of the dice. Longer discussion, but it seems that now a lot of people are comfortable putting out a product and letting their users find those edge cases. Not sure how I feel about that lol. I don’t like it, but it sure does bring you speed to market. And iteration is blazingly fast.

I went through this exact thing about ~8 months ago. Everyone must pass through the phase of AI existential dread and developer ego death. After much internal deliberation I've come to the realization: The genie is out of the bottle, and instead of just three wishes, it comes with 𝗶𝗻𝗳𝗶𝗻𝗶𝘁𝘆 𝘄𝗶𝘀𝗵𝗲𝘀 😅 So, the focus changes from the artisanal line by line code crafting and shifts into deeper architectural & product decisions, that 𝗜 𝗱𝗿𝗶𝘃𝗲. It's now 99% product planning & research around edge cases/what's possible/competitors and like 1% typing syntax. Instead of the 75% code / ~25% planning of yesteryear. Once you see it, you see it.

@charliegreenman I was writing a video compression algorithm before JPEG was a standard. And then ended up on the MPEG committee. I remember when yahoo was a blue font directory of homepages. The first software I published was a flat file database on C64. It’s been a wild ride.

It's alot of fun to talk to nearly retired programmers these days. They saw punch cards, personal computers, internet and now AI. It's like watching the universe be born and die in 45 years

@atmoio @Sentdex The harder problem is spending more time thinking about architecture so that when you hand it off to AI it handles everything including edge cases that a lesser prompt would miss. Unfortunately that’s not the same job as coding. But that’s where we’re at.

@Sentdex i’m not sure if it’s necessarily about the challenge. but in any case, what’s a “harder” problem in the AI age? all problems are practically equal for an llm. maybe it’s increased scope? but that isn’t necessarily more intellectually fulfilling

I was a 10x engineer. Now I'm useless.

I’m actually more productive than ever. By using these tools, I can create more than ever. It has unlocked a million ideas. So my passion remains. Also, AI is not infallible. Nobody can convince me that when you do a complex project completely hands off that there aren’t bugs or bad architecture that you didn’t notice. Those edge cases are still going to bite you. And the real artisans are putting all their passion into extremely detailed architecture so that the AI execution theoretically does not get anything wrong. So I’ve reached a different conclusion - we still need engineers. 10X doesn’t mean how fast can you code anymore. It means how much can you think through the architecture?

Heavily, yes. I see it as a roller coaster. It’s often a 10x speed improvement. Sometimes 20x. But it can and does make mistakes. Usually small mistakes that are easily corrected. But I occasionally it makes gigantic blunders that eat into your speed gains. Still an overall net positive. You need to do a LOT of planning, have a lot of guardrails and monitor like a hawk.

@em_az From your POV, where does LLM assisted coding come in with your workflow. Do you use it at all?

Hello vibe coders

@aschmelyun Oh hey, look at me telling you to do a substack when I finally see that you have an actual site. Now I have to go down the rabbit hole. Thank you very much lol

You've built so many of these. You need to put these all together, man. Cool stuff, sub stack or something. lol Ironically, I have a project that required me to work on a receipt printer, I know that that's the one that you've done, so I had some fun with that one too. I have a sarcastic AI that will just spit out comments to me throughout the day on the receipt printer.

You’re still getting Sentry notifications through email or texts? That’s cute.

Lol

@ZaKMcKrackeN @aditiitwt Still have mine lol Published my first database on C-64

@aditiitwt Hold my beer...

You may be old But are you this old

@aditiitwt I’m this old

@SirAlexthomson What did Dario say?