{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiezi4xmsqbc6yfov4admfgkcvi2uf3x4ug27tmln6f6ic6tl6tcqa",
    "uri": "at://did:plc:25rdn5elo5izoxrmtis34zuk/app.bsky.feed.post/3mpsf4v2ns622"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreibhoysfbjtyp6t3okduiq34btltbrhaaz3discfhkxa6bx6uz57eu"
    },
    "mimeType": "image/webp",
    "size": 72462
  },
  "path": "/rahul_agarwal18/90-of-developer-portfolios-are-making-this-exact-same-mistake-37ng",
  "publishedAt": "2026-07-04T05:49:56.000Z",
  "site": "https://dev.to",
  "tags": [
    "career",
    "webdev",
    "programming",
    "beginners"
  ],
  "textContent": "I’ve looked at dozens of developer portfolios recently, and almost all of them are making the exact same critical mistake.\n\nThey focus entirely on _what_ technologies they used, and say absolutely nothing about _why_ they built it or the _impact_ it had.\n\nA project section that says:\n\n> _\"Built a Weather App using React and Tailwind\"_\n>  is boring. 🥱\n\nA project section that says:\n\n> _\"Built a real-time Weather Dashboard in React that caches API requests to reduce load times by 40%, solving the issue of slow refreshes for mobile users\"_\n>  gets you hired. 💼\n\nRecruiters and Senior Devs want to see that you can solve actual problems, not just follow a tutorial. They want to know the architecture decisions you made, the bugs you overcame, and why you chose a specific database over another.\n\n**Drop a link to your portfolio in the comments and I’ll give you some honest feedback!** 👇",
  "title": "90% of Developer Portfolios are making this exact same mistake. 🛑"
}