DEV Community: Farukh Saifi

There's something off in the "dev with AI or die" narrative

Farukh Saifi — Tue, 26 Aug 2025 22:42:42 +0000

It's everywhere, it's eating up every other dev topic debate: learn to dev with AI or you'll be replaced. As a dev, I can't help but feel threatened by these claims. Way more than I should.

I mean, I love hacking around with the new cool toy as much as anybody. I use code assistants all day long, from Cursor tab to RefactAI. I felt so clever when I automated ticket creation with Jira MCP with full codebase and commit history knowledge. I felt not so clever when my "instant" refactoring took me a full day to review and rewrite to fix "just that little bug". I love automating my work as much as the next dev, but I also love to measure the results of automation.

So when big names come up with dull articles about the "4 levels of dev with AI" which is that close to "top 5 agents to pop up a unicorn out of thin air in 2025", I feel something weird. They use code assistants dozens of times less than I do, yet they see "evidence" of a total world transformation I don't even see the beginning of in my day-to-day use.

Where is the collapse of LLM reasoning? Where are the small models winning in the end? Where are the control groups? Show me the data, I'll believe you. Where are the failures too? I've experienced more than one, surely you have data about that too if you're a big tech CTO, no? And then again, why prophesy so much before having the data? The natural move would be to train your team, maybe even a bit secretly, then outperform everybody and finally brag once you have secured the win. Right?

There must be something else.

"Something else" is often money

The first obvious reason is of course to have people burn billions in LLM tokens. This kind of narrative is really effective with C-levels who aren't really using it daily. It make them feel they are losing ground on a huge competitive advantage and they'll force their teams to use LLMs for everything.

There is a nice side effect: you get social experimentation for free. I mean, hacking around commands, cursorRules and CLAUDE.md files is fun, but really the final product will have most of it baked in. But people are doing it for free—nope, people are paying to do that! They are running the experimentation at scale while burning tokens, documenting failures on the way. How convenient for an LLM provider?

And last but not least: hype drives capital. Meredith Whittaker puts it better than anybody:

Now, that a token dealer overhypes their product, I get why. That other "big money people" would be so eager to buy it that they wouldn't run A/B testing or measure gains? There's a bit more than FOMO or paying rent forever to an LLM provider. When I hear "Most of your code will be written by AI", I can't help but hear "now I own your means of production, so you better keep a low profile".

The good ol' dehumanization dream

How many times have we seen a desperate look from a PO, customer or designer that says "But, it's just a form, why is it that hard? You lazy devs will invent anything to avoid working". Because, we are a bunch of unmanageable weirdos aren't we? Sometimes I wonder if I don't ship software just to prove I'm an uncontrollable smartass. Why do we always have an obscure HN link that makes our CEO's "big vision" fall flat? Why is there always one of us to run a script proving financial forecasts are wrong? Why do we keep inventing squads and guilds and chapters and epics? Can't we just sit—not STAND—at our desks and do as the boss says?

Now, if you're managing a lot of devs, I get the temptation: "I have a big vision for humanity—that incidentally makes me rich and famous, but that's not the point—AI transforms that into a polished product". No more "what about… ?", no more pushbacks. No more human messiness. And if humans are not happy, the "big boss" can now close the precious token tap and give it to someone else. This would be much simpler, right? This would be all too tempting to make the devs more replaceable, more interchangeable, wouldn't it? Truly, I find it hard to ignore the power dynamics behind all of that.

It's a pattern we've seen before, from the Luddites to mines, from silk workers to the automotive industry or agriculture. With any wave of automation, there's also a shift of power that gets pushed. Whether it's wages, whether it's unions, whether it's outsourcing, there's often a power struggle that goes far beyond the actual productivity gain. And power is where we believe it is, right? (Yes, I'm totally citing Game of Thrones as the top of my philosophical references).

Be careful what you wish for

For the sake of argument again, let's admit that AI indeed replaces a good part of "the work". Now let me put a caricatured problem to emphasize things. We have two teams designing the same product. One is business school only with zero tech or design knowledge and automates engineering and design with AI. The other one is a group of hacky devs and UX who will automate PPTs, marketing and C-level jobs. Who do you place your money on, honestly?

Fun fact, there are only two things where I'm sure AI is saving me a lot of time as of now: writing tickets and doing large searches. Claude Code (or Goose) with Jira MCP is excellent at writing tickets from messy feedback and looking in the codebase to see if the workload is OK. Perplexity can save me an afternoon of searching with excellent links I could never have found. Large code refactoring though? Some of them "worked", but I'm still unsure if I spent more time reviewing them and eliminating dead code than I would have writing them from scratch.

And then, what if in the end we only need very small local models, called by pretty sophisticated agents that are a lot of regular code? What if it's pseudo-code to code models, transformers or SyntaxGuidedSynthesis that wins? Why do we need "Language" models, if it's autonomous anyway? Or is it? What if writing a specialized agent for your codebase becomes a required skill? Kimi K2 or Devstral aren't that far away, we don't need an expensive Claude to grep and make todos, to name only a few things.

At this point, I think we just don't know what "AI for dev" means. We don't know "how much" and we don't know "what kind". I have zero clue which approach will work or not, nor at which magnitude. What I see though, is that there's one narrative that's pushed way harder than the others. One where devs lose power and buy tokens by the billions.

How convenient, because in many other narratives there are teams of 5 hackers disrupting giants on the cheap, like early Rails days on steroids.

What's the sane approach then?

If authoritarianism is bourgeoisie being scared, then what to think of Sam Altman being scared by GPT-5 and doing whatever he can to convince your boss that you're gonna be addicted to his tokens? Maybe he is more scared for his job than for ours. We don't have proof of either, but this should at least be explored, right?

In this light, the skeptic developer crowd is absolutely needed. We need to have some people not budging until the product is actually good with proven gains. They are the reference against which we measure, the control group. Early adopters should be outliers, not the bulk of the market. This is how we develop good products in the first place and why we don't like it forced on us. The urge to push an unfinished product feels dubious to us at best and rightfully so.

The sane approach is just to stay curious, test and measure. You're a hacky enthusiast? Fine, build some agents and test them. You're a pragmatic skeptic? Totally fine as well, don't use it until it makes your job really faster. We need to know that too. I totally understand that a large company would run an A/B test of teams with and without LLM tools and measure the output. I don't understand why they would force the results if it's really efficiency that is at stake.

All those prophecies really make me think that it's not only efficiency that is at stake though. It's shifting people's perception of where the power is. But remember, if a "visionary" CEO fires you to be replaced by AI, don't forget to run Claude on your full company folder and ask it to make the slides, financial projections and OKRs for the quarter. Whether you email that to them as a middle finger or keep it to yourself to spin up your own thing is up to you. Just note that maybe it's not you who's been replaced by AI in the end.

Arriving to a new milestone in my career

Farukh Saifi — Tue, 26 Aug 2025 22:40:21 +0000

## What This Milestone Represents
Reaching this milestone represents more than just professional progress—it’s a moment of personal growth. It’s a sign that the dedication and passion I’ve invested are paying off. Whether it’s mastering a new skill, taking on leadership responsibilities, or completing a major project, this achievement is a reminder that perseverance, curiosity, and a love for what I do are key drivers of success.
## The Challenges That Shaped Me
Of course, no journey is without its hurdles. There were moments of doubt, failed prototypes, and unforeseen obstacles that tested my resolve. However, those challenges taught me the importance of adaptability, creative thinking, and collaboration. They pushed me to improve, to think outside the box, and to view setbacks not as failures, but as opportunities to learn and grow.
## Embracing New Opportunities
This milestone is also an opportunity to embrace new challenges and expand my horizons. Whether it’s exploring emerging technologies, diving deeper into specific fields of interest, or taking on a mentorship role, I’m excited about what lies ahead. The engineering and design landscape is constantly evolving, and staying curious and open to new ideas is what keeps this career path so rewarding.
## Gratitude and Acknowledgment
I’d be remiss if I didn’t take a moment to acknowledge the mentors, colleagues, and collaborators who have been part of this journey. Their insights, support, and shared enthusiasm have been invaluable. Reaching this milestone is as much a testament to their influence as it is to my individual efforts.
## Looking Ahead
While I’m proud of how far I’ve come, I know this is just one milestone in a much larger journey. The road ahead is filled with exciting possibilities, and I’m eager to continue pushing boundaries, learning new things, and contributing to meaningful projects. If there’s one thing I’ve learned along the way, it’s that every new milestone is not an end, but rather a launchpad for the next chapter.
Thank you for being part of this journey with me, and here’s to the adventures yet to come!

Blog Syndication Platform Plan

Farukh Saifi — Tue, 26 Aug 2025 20:20:29 +0000

Of course. Based on the development plan, here is a detailed prompt you can use with an AI-powered IDE like Cursor to generate the initial codebase for your blog syndication application.

This prompt is designed to be comprehensive, providing the AI with the necessary context, technology stack, and feature requirements to build the Minimum Viable Product (MVP).

Prompt for Cursor IDE

"You are an expert full-stack software developer. Your task is to generate the initial codebase for a blog syndication application based on the following detailed plan.

Project Goal:
Create a web application that allows a user to write a blog post in a central dashboard and then publish it to their Medium account. This is the MVP for a larger system that will eventually support multiple platforms.

Technology Stack:

Backend: Node.js with Express.js
Frontend: React with Vite
UI Components: shadcn/ui
Database: PostgreSQL
Styling: Tailwind CSS

File Structure:
Please create a monorepo structure with two main packages:

/server: For the Node.js/Express.js backend.
/client: For the React frontend.

Backend (`/server`) Requirements:

API Server Setup:
- Set up a basic Express.js server.
- Include cors middleware to allow requests from the frontend.
- Use dotenv to manage environment variables.
Database Schema (PostgreSQL):
- Please define the database schema. You can use a simple SQL script or an ORM like Prisma.
- posts table:
  - id (Primary Key, UUID)
  - title (TEXT, NOT NULL)
  - content_markdown (TEXT)
  - status (VARCHAR, e.g., 'draft', 'published')
  - created_at (TIMESTAMP)
  - updated_at (TIMESTAMP)
- credentials table:
  - id (Primary Key, SERIAL)
  - platform_name (VARCHAR, e.g., 'medium')
  - api_key (TEXT, should be encrypted)
  - user_id (placeholder for future multi-user support)
API Endpoints:
- POST /api/posts: Creates a new post in the posts table. Expects { title, content_markdown } in the request body.
- GET /api/posts: Retrieves all posts.
- PUT /api/credentials/medium: Saves or updates the user's Medium API key in the credentials table.
- POST /api/publish/medium:
  - Takes a { postId } in the body.
  - Retrieves the post content from the posts table.
  - Retrieves the Medium API key from the credentials table.
  - Makes a POST request to the Medium API (https://api.medium.com/v1/users/{{authorId}}/posts) to publish the article.
  - The request to Medium should include title, contentFormat: "markdown", content, and publishStatus: "public".
  - Update the post's status in the database.

Frontend (`/client`) Requirements:

Setup:
- Initialize a React application using Vite.
- Set up Tailwind CSS and initialize shadcn/ui.
Components and Pages:
- Dashboard Page (/):
  - This should be the main view.
  - Display a list of all posts fetched from GET /api/posts. Use the Table component from shadcn/ui.
  - Include a Button to navigate to the "New Post" page.
  - Include a link/button to the "Settings" page.
- New Post / Editor Page (/editor):
  - An Input for the post title.
  - A Textarea for the Markdown content. Make it large and suitable for writing.
  - A Button to "Save Draft" which calls POST /api/posts.
  - A Button to "Publish to Medium" which first saves the post and then calls POST /api/publish/medium.
- Settings Page (/settings):
  - An Input field for the user to enter their Medium Integration Token (API Key).
  - A Button to "Save" which calls PUT /api/credentials/medium.

User Flow for the MVP:

The user navigates to the Settings page and saves their Medium API key.
The user navigates to the Dashboard and clicks "New Post".
On the Editor page, they write a title and content.
They click "Publish to Medium".
The app communicates with the backend, which then uses the saved API key to post the content to Medium.
The post list on the Dashboard should reflect the new post.

Please generate the complete file structure and boilerplate code for both the client and server based on these requirements."

My Portfolio React Js to Next Js

Farukh Saifi — Fri, 14 Mar 2025 20:22:14 +0000

I started the year by creating my portfolio, which is like a showcase of my coding journey so far. It shows off my skills and projects in HTML, CSS, JavaScript, React.js, Next.js, and more. As I start looking for my first Tech Blog website, I’d love to hear from fellow developers who have been in this position before.

Live site: https://www.farukh.me/

GitHub repository: https://github.com/FarukhSaifi/farukhportfolio

Questions for you reading this post:
Is there anything important missing from my portfolio?

Is it easy to navigate?

What are your overall thoughts on the site?