DEV Community: Farukh Saifi

Claude AI, Cursor, and Amazon Q: AI Coding Tools Compared

Farukh Saifi — Sat, 06 Jun 2026 22:16:55 +0000

AI Coding Assistants Compared

AI coding tools are transforming development workflows by automating boilerplate and accelerating debugging. Choosing between Claude AI, Cursor, and Amazon Q depends on whether you need a standalone LLM interface, a full IDE integration, or enterprise-grade cloud deployment support.

Direct Answer

Claude AI is a powerful general-purpose LLM often used via a web interface or API, whereas Cursor is a specialized fork of VS Code that integrates AI directly into the IDE. Amazon Q is an enterprise-focused assistant tailored for AWS infrastructure and internal corporate codebases. Claude AI outages are typically caused by extreme surges in user traffic or high-load capacity constraints during major model updates.

Comparison Table

Tool	Best For	IDE Integration	Key Strength
Claude AI	Complex reasoning	None (Web/API)	Superior logic & context
Cursor	Active coding	Native (VS Code)	Codebase awareness
Amazon Q	Cloud/AWS work	IDE extension	Security & AWS context

Why Does Claude AI Go Down?

Users often report "Claude is at capacity" messages. This is not a software bug in your code; it is a scaling challenge. Because Anthropic provides access to high-compute models (like Claude 3.5 Sonnet), they limit concurrent requests to ensure response quality. During peak hours, the infrastructure reaches its throughput limit, triggering a temporary lock to prevent degradation of model accuracy.

How to Minimize Downtime Issues

Use the API: API users typically have priority access over free web-tier users. If your work relies on Claude, integrate it into your workflow via API.
Cursor Integration: If you use Cursor, you can set your API key to access Claude's models directly through the IDE, bypassing the public web interface queues.
Switch Models: Use a local model or a less-demanding model (like Haiku) within your tools to maintain momentum when flagship models are throttled.

Which Tool Should You Choose?

Choose Cursor if you want a seamless coding experience where the AI understands your entire repository.
Choose Claude AI if you are performing architectural research, documentation, or complex logic planning outside the editor.
Choose Amazon Q if you work primarily within an enterprise AWS environment that requires strict security compliance.

Discussion

Have you experienced significant downtime with Claude AI while in the middle of a complex refactor, or have you found a more reliable alternative for your specific stack? Let me know in the comments.

Spotify API Implementation: Build Your Own Music Apps

Farukh Saifi — Sun, 31 May 2026 20:12:07 +0000

Unlocking the Power of Sound: Your Guide to Spotify API Implementation

The world of music is vast and vibrant, and the Spotify API offers a gateway to integrate this incredible soundscape into your own applications. Whether you're a budding developer looking to build your first music app or an experienced programmer aiming to enhance an existing service, mastering Spotify API implementation is a game-changer. This comprehensive guide will walk you through everything you need to know to get started, from setting up your developer environment to making your first API requests.

What is the Spotify Web API?

The Spotify Web API is a RESTful web service that allows developers to access data from the Spotify catalog, manage user's music libraries, control playback, and much more. It's the backbone of countless innovative Spotify API projects, enabling personalized experiences and powerful integrations. By learning how to use Spotify API, you can unlock endless possibilities for Spotify app development.

Why Implement the Spotify API?

Personalization: Create tailored music experiences based on user preferences.
Automation: Automate playlist creation, track management, or playback controls.
Integration: Combine Spotify's vast music library with other services or platforms.
Innovation: Develop unique applications that stand out in the crowded app market.

Getting Started: Your Spotify Developer Journey

Before you can dive into Spotify API implementation, you need to set up your developer account and register your application.

1. Become a Spotify Developer

Navigate to the Spotify Developer Dashboard. If you don't have a Spotify account, you'll need to create one first. Once logged in, you'll gain access to all the tools and documentation necessary for Spotify developer activities.

2. Register Your Application

Click on "Create an app" in your dashboard. You'll need to provide:

App Name: A descriptive name for your project.
App Description: Briefly explain what your application does.
Redirect URIs: These are crucial for API authentication Spotify. When a user grants your app permission, Spotify redirects them to this URI with an authorization code. For local development, http://localhost:8888/callback is a common choice.

Upon successful registration, you will be assigned a Client ID and a Client Secret. These are your application's credentials and are vital for OAuth 2.0 Spotify authentication. Keep your Client Secret confidential!

Spotify API Authentication: The Key to Access

The Spotify Web API uses OAuth 2.0 for authentication, ensuring secure access to user data. There are several authorization flows, each suited for different application types.

Understanding OAuth 2.0 Flows

Authorization Code Flow:
- Best for: Server-side applications or single-page applications with a backend.
- How it works: Your app requests authorization from the user, Spotify redirects with a code, your backend exchanges this code for an access_token and refresh_token. The access_token is used for API calls, and the refresh_token obtains new access tokens without re-authenticating the user. This is the most secure and common flow for user-specific data.
Client Credentials Flow:
- Best for: Applications that only need to access public data (e.g., searching for tracks, artists, albums) and don't require user-specific information.
- How it works: Your app directly exchanges its Client ID and Client Secret for an access_token with Spotify's authorization server. No user interaction is involved.
Implicit Grant Flow (Deprecated for most new uses):
- Historically used for: Client-side only applications.
- Why less common now: Less secure as access_token is exposed in the URL fragment. Authorization Code with PKCE is preferred for client-side applications.

Implementing Authorization Code Flow (Recommended for User Data)

Here's a simplified overview of the steps:

Construct the Authorization URL:

GET https://accounts.spotify.com/authorize

    ?response_type=code

    &client_id=YOUR_CLIENT_ID

    &scope=user-read-private%20user-read-email%20playlist-read-private%20playlist-modify-public

    &redirect_uri=YOUR_REDIRECT_URI

    &state=OPTIONAL_STATE_VALUE

The scope parameter defines the permissions your app requests.

Redirect User to Authorization URL: Your application redirects the user's browser to this URL. The user logs into Spotify (if not already) and approves your app's requested permissions.
Spotify Redirects Back to Your App: Upon approval, Spotify redirects the user back to your redirect_uri with an authorization code and the state parameter (if provided).

Exchange Code for Tokens (Server-side): Your server makes a POST request to Spotify's token endpoint:

POST https://accounts.spotify.com/api/token

    grant_type=authorization_code

    &code=THE_RECEIVED_CODE

    &redirect_uri=YOUR_REDIRECT_URI

    &client_id=YOUR_CLIENT_ID

    &client_secret=YOUR_CLIENT_SECRET

Spotify responds with an access_token, refresh_token, and expires_in.

Store Tokens Securely: Store the refresh_token securely in your database. The access_token should be used for subsequent API calls until it expires. When it expires, use the refresh_token to get a new access_token.

Making Your First Spotify API Requests

Once you have an access_token, you can start interacting with the Spotify Web API endpoints. All requests to endpoints that require user data must include your access_token in the Authorization header.

Request Structure

GET https://api.spotify.com/v1/me/playlists

Authorization: Bearer YOUR_ACCESS_TOKEN

Common Spotify API Endpoints

GET /v1/me: Get current user's profile information.
GET /v1/search: Search for tracks, artists, albums, or playlists.
GET /v1/me/playlists: Get a list of the current user's playlists.
POST /v1/users/{user_id}/playlists: Create a playlist for a user.
PUT /v1/me/player/play: Start/resume playback on the user's current device.
GET /v1/artists/{id}/albums: Get an artist's albums.

Each endpoint is meticulously documented in the Spotify API documentation, providing details on required parameters, response formats, and necessary scopes.

Popular Spotify API Projects & Use Cases

The possibilities with Spotify API implementation are vast. Here are some ideas:

Custom Music Players: Build a unique interface for playing Spotify content.
Playlist Generators: Create intelligent playlists based on mood, genre, or activity.
Social Music Apps: Share music with friends, discover new tracks together.
Recommendation Engines: Develop sophisticated systems to suggest music.
Data Analysis Tools: Analyze listening habits, track trends, and visualize music data.
Home Automation Integrations: Control Spotify playback with voice commands or smart home routines.

Best Practices for Spotify API Development

Handle Rate Limits: Spotify imposes rate limits to prevent abuse. Implement exponential backoff or retry logic if you receive a 429 Too Many Requests status.
Error Handling: Always anticipate and handle errors gracefully (e.g., 401 Unauthorized, 403 Forbidden, 404 Not Found).
Secure Your Credentials: Never expose your Client Secret in client-side code. Use a backend server for token exchange.
Request Minimal Scopes: Only request the permissions (scopes) your application absolutely needs.
User Experience: Design your application with a smooth and intuitive user flow, especially during the authorization process.
Stay Updated: The Spotify Web API is continuously evolving. Regularly check the developer documentation for updates and new features.

Tools and Libraries for Easier Implementation

While you can interact with the Spotify Web API using raw HTTP requests, several libraries simplify the process:

Python: Spotipy is a popular, easy-to-use Python library for the Spotify Web API. It handles authentication and provides a convenient wrapper for most API endpoints.

import spotipy

from spotipy.oauth2 import SpotifyOAuth

scope = "user-read-private user-read-email"

sp = spotipy.Spotify(auth_manager=SpotifyOAuth(scope=scope))

results = sp.current_user_playlists()


for i, playlist in enumerate(results['items']):


    print(f"{i+1} {playlist['name']}")

JavaScript: spotify-web-api-js is a lightweight wrapper for the Spotify Web API that can be used in both Node.js and browser environments.
Other Languages: Community-maintained libraries exist for Java, PHP, Ruby, and more. Check the Spotify Developer documentation for a comprehensive list.

Conclusion: Your Journey with Spotify API Implementation

Embarking on Spotify API implementation opens up a world of creative possibilities. From building simple playlist managers to complex recommendation engines, the Spotify Web API provides the tools you need. By following this Spotify API tutorial, understanding API authentication Spotify, and utilizing best practices, you're well-equipped to develop powerful and engaging music applications. Start experimenting today, explore the extensive Spotify API documentation, and bring your unique musical ideas to life!

M4 Pro vs M5 Pro: Which Apple Silicon Chip Wins?

Farukh Saifi — Sun, 31 May 2026 14:46:45 +0000

M4 Pro vs M5 Pro: The Battle of Apple Silicon Chips

When choosing between the latest Apple MacBook Pro models, understanding the core differences between the M4 Pro vs M5 Pro is essential. As Apple continues to push the boundaries of ARM architecture, each iteration brings significant leaps in efficiency and raw computational power. In this guide, we break down everything you need to know.

Architectural Evolution

The M4 Pro chip is built on a second-generation 3nm process, offering a masterclass in thermal efficiency and performance density. However, with the emergence of the M5 Pro, users are seeing a transition toward even smaller node enhancements.

Transistor Density: The M5 Pro features an increased transistor count, allowing for more complex operations per clock cycle.
Neural Engine: Both chips excel at AI-driven workflows, but the M5 Pro offers expanded TOPS (Trillions of Operations Per Second) for local LLM processing.

Performance Benchmarks: M4 Pro vs M5 Pro

In synthetic benchmarks like Geekbench 6, the M4 Pro remains an absolute powerhouse, capable of handling 8K video editing and heavy compilation tasks with ease. The M5 Pro improves on this by optimizing single-core speeds and enhancing multi-core throughput for parallel computing.

Feature	M4 Pro	M5 Pro
Memory Bandwidth	273 GB/s	300 GB/s+
GPU Architecture	Enhanced Ray Tracing	Next-Gen Unified Memory
Power Efficiency	Industry Leading	Advanced Node Optimization

Real-World Use Cases

1. Content Creators and Editors

For video editors using Final Cut Pro or DaVinci Resolve, the M4 Pro is already more than sufficient. The jump to M5 Pro is primarily beneficial for those working in 3D rendering or complex VFX, where the increased memory bandwidth provides a noticeable buffer for heavy cache files.

2. Developers and Data Scientists

If you are running local large language models or containerized environments, the M5 Pro provides the extra overhead required for faster context switching and data throughput. The improved Neural Engine in the M5 series specifically targets these machine learning workflows.

Is the M5 Pro Worth the Upgrade?

Deciding between the M4 Pro vs M5 Pro comes down to your current hardware cycle:

Stick with M4 Pro if: You currently own an M4-series machine or find that your current workflow is not hitting a thermal or memory ceiling.
Upgrade to M5 Pro if: You are coming from an Intel-based Mac or an M1/M2 Pro, and you need the absolute latest in silicon longevity, GPU acceleration, and neural processing capabilities.

Conclusion

While the M4 Pro is currently one of the most capable chips on the market, the M5 Pro represents the bleeding edge of what is possible in a mobile workstation. By focusing on memory bandwidth and neural processing, Apple has made the M5 Pro a future-proof investment for high-end creative and technical professionals.

How to Use Free AI Models: A Comprehensive Guide

Farukh Saifi — Sun, 31 May 2026 12:11:19 +0000

Unlock the Power of Free AI Models

Artificial Intelligence is no longer reserved for tech giants. Today, anyone with an internet connection can leverage sophisticated technology to enhance their productivity, creativity, and problem-solving skills. Learning how to use free AI models is one of the most valuable skills in the modern digital landscape.

Top Platforms to Access Free AI Models

Accessing advanced large language models (LLMs) has never been easier. Here are the leading platforms where you can start for free:

ChatGPT (OpenAI): The gold standard for conversational AI. The free tier now offers access to powerful models like GPT-4o with usage limits.
Claude (Anthropic): Renowned for its natural writing style and massive context window, perfect for long-form content.
Google Gemini: Seamlessly integrated with Google Workspace, making it ideal for users who rely on Docs and Gmail.
Hugging Face: A hub for open-source AI enthusiasts who want to run models locally or via API testing.

Mastering Prompt Engineering

Knowing how to talk to an AI is just as important as the model itself. Follow these core principles for better results:

Be Specific: Instead of asking 'write a post,' try 'write a 500-word blog post about the benefits of renewable energy for small businesses.'
Assign a Persona: Start your prompt with 'Act as an expert SEO strategist' to refine the model's tone and depth.
Provide Context: Tell the AI who the audience is, what the goal is, and any specific constraints like word count or tone.
Iterate: If the first result isn't perfect, use follow-up prompts to tweak specific sections.

Common Use Cases for Free AI

Content Creation: Drafting emails, blog posts, and social media captions.
Coding Assistance: Debugging snippets or generating boilerplate code for web development.
Brainstorming: Using AI as a creative partner to overcome writer's block.
Learning: Summarizing complex academic papers or explaining difficult technical concepts.

Ethical Considerations and Best Practices

While using free AI models is incredibly beneficial, it is important to remember that AI can sometimes 'hallucinate' or provide inaccurate information. Always verify facts, especially when dealing with legal, medical, or financial data. Additionally, avoid inputting sensitive personal or company information into public AI models to protect your privacy.

By following this guide, you are well on your way to mastering the tools that will define the future of work and creativity.

Embracing AI Development: A Guide to Modern Innovation

Farukh Saifi — Sun, 31 May 2026 12:07:25 +0000

The Shift: Why AI Development is Changing Everything

In the rapidly evolving landscape of technology, AI development has emerged as the definitive catalyst for innovation. Businesses no longer view artificial intelligence as a futuristic concept; it is now a fundamental requirement for staying competitive. If you are looking to change your operations with AI development, understanding the core components is essential.

Core Pillars of AI Transformation

To successfully transition to an AI-driven model, consider these critical areas:

Data Strategy: AI is only as good as the data it consumes. Establishing high-quality data pipelines is the first step.
Machine Learning Algorithms: Implementing predictive models that evolve with your specific business needs.
Automation Workflows: Reducing repetitive tasks by integrating intelligent agents into your existing software ecosystem.
Scalability: Choosing cloud-native architectures that allow your AI models to grow alongside your user base.

Steps to Kickstart Your AI Journey

Changing your infrastructure to support AI development requires a strategic roadmap. Start by identifying high-impact use cases, such as customer support automation or supply chain optimization. From there, assemble a cross-functional team that balances data science expertise with business intelligence.

Future-Proofing Your Business

The integration of AI development is not a one-time project but a continuous cycle of learning and optimization. By focusing on ethical AI practices and maintaining transparency in your algorithms, you not only improve operational efficiency but also build long-term trust with your customers. Embrace the change today to lead your industry tomorrow.

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?