Skip to content
View eimf's full-sized avatar
🔴
Debugging my existence
🔴
Debugging my existence

Sponsoring

@codediodeio

Block or report eimf

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
eimf/README.md
header

I used to be a developer.

Pause.

Now I manage machines that write code faster than I ever could.

That's not a tragedy. That's leverage.


⏪ The Before Times

For 13+ years I shipped software. Fast. Across industries, across stacks, across clouds. I wrote the code, reviewed the code, deployed the code, debugged the code at 2 AM, and mass produced the code again on Monday.

I knew my languages. I knew my frameworks. I could scaffold a REST API before my coffee got cold. Coding speed was a competitive advantage, and I had plenty of it.

That era is over. Not because I got slower. Because something else got impossibly fast.


⚡ The Plot Twist

AI doesn't write code the way I did. It writes code the way I wished I did — instantly, tirelessly, and without opinions about tabs vs. spaces.

So my job changed. I don't produce keystrokes anymore. I produce decisions.

  • What to build. Why to build it. How the pieces compose.
  • I don't fight the tools. I orchestrate them.
  • I'm not an "AI slave." I'm an AI middle-manager with opinions and commit access.

The code still ships. It just ships at the speed of existential crisis now.


🔀 Then vs. Now

🏛️ THEN — Classical Stack

The era of hand-crafted artisanal software.

Languages: TypeScript, JavaScript, Python, Java, PHP, Go, SQL

Cloud: AWS, GCP, Vercel, Heroku, Netlify, Fly.io

DevOps: Docker, Kubernetes, CI/CD pipelines, Bash scripts held together by hope

Tools: VS Code, Sublime Text, Node.js, and 47 Stack Overflow tabs

Vibe: "I built this entire feature in a weekend" (it had three bugs)

🧠 NOW — Post-Stack Stack

The era of designing systems that build things for you.

AI IDEs: Cursor, Kiro, Windsurf, and whatever ships next Tuesday

Models: Large ones, small ones, local ones, hosted ones, the one that turned a napkin sketch into a working app

Workflow: Agents, copilots, orchestration layers, prompt chains, context engineering

Tools: Still Docker. Some things are eternal.

Vibe: "I shipped this entire feature in 20 minutes" (the AI introduced three bugs, but also wrote the tests and the fix)


🎭 Honest Observations

  • I write prompts instead of for-loops now. My WPM went down. My output went up. Make it make sense.
  • Code reviews now involve a silicon coworker that never sleeps, never gets offended, and never leaves passive-aggressive PR comments. Progress.
  • I shipped more in the last year than in the previous five. That sentence is recursive and so is my workflow.
  • The stack matters less than the system. The system matters less than the thinking. The thinking doesn't matter if you can't ship.
  • So I ship.

🔭 The Closer

I don't just write software anymore.

I design systems that write it. I decide what gets built, how it composes, and where the humans still matter — spoiler: everywhere that isn't boilerplate.

13 years of building things by hand taught me what to build. The next 13 will be about building the machinery that builds it.

The future isn't "AI replaces developers." The future is developers who refuse to evolve get quietly left behind.

I chose to evolve. And honestly? It's more fun on this side.


Typing SVG

🤝 Let's Connect


Profile Views
footer

Pinned Loading

  1. eimf eimf Public

    3

  2. sheets sheets Public

    application for the girls to log the services

    TypeScript 2