thanks
you really started a trend bro.
congrats and thanks for the trend.
you inspired me to update my old readme to a really great store front readme.
yeah, bro also you guys are managing the no. stats easily but when I just set up one download counter my mind blowed, it was not working automatically manual run workflow was only working how do you guys manage it?
Do you mean the automatic scheduled workflow didn't work? If that's the issue, sometimes it has some delays, it can run a bit later than scheduled, but it'll eventually run.
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
The 3-second download test is the right frame. I ran something similar when I moved my project links above the fold — bounce rate on my profile dropped hard because people stopped scrolling for the "see releases" link. One thing I'd push back on: the .zip direct download is clean for desktop apps, but if any of these ever ship as web services, you'll want a live demo link next to the download, not buried. Four apps with four buttons is a strong start though — most profiles I see have zero.
Treating a README as a storefront is a mindset shift that a lot of developers miss, often getting bogged down in flashy badges and contribution graphs that don't actually tell a recruiter or collaborator what you can build. I've found that the most effective profiles focus heavily on the "why" and the "how" rather than just a list of technologies. Instead of just listing React or Go, showing a quick architectural breakdown or a link to a specific, well-documented problem you solved makes a much stronger impression. One thing to watch out for is over-engineering the README itself; if it takes more time to maintain your profile than your actual projects, you've crossed the line from storefront to distraction. Keep the documentation lean and let the code do the heavy lifting.
Spot on. Honestly, I’m so tired of scrolling through endless contribution snakes and generic stats cards just to figure out what someone actually builds. Treating a README like an app store listing is a solid mental model. It cuts straight to the value proposition.
Glad you agree, Akhouri. At the end of the day, a hiring manager or open-source maintainer wants to see your impact, not your setup. A profile README should act like a pitch deck for your skills—show me the live demo links, the architecture layout of your top project, and what problem you actually solve. The generic stats cards just create unnecessary noise and bloat.
This is actually a much better way to think about a GitHub profile. Most profiles look nice, but I rarely know what I’m supposed to click first. Putting the actual apps and download buttons front and center makes the page feel way more useful.
Cách tiếp cận coi README là storefront thực sự thay đổi tư duy của mình về việc xây dựng thương hiệu cá nhân. Thay vì lấp đầy trang cá nhân bằng các badge màu mè hay những dòng quote vô nghĩa, việc tập trung vào các dự án thực tế và cách chúng giải quyết vấn đề cụ thể sẽ gây ấn tượng mạnh hơn với nhà tuyển dụng. Một kinh nghiệm mình rút ra là đừng chỉ liệt kê tech stack, hãy thử đính kèm một vài con số hoặc kết quả thực tế từ các dự án đó. Nó giúp người xem hình dung ngay lập tức năng lực thực chiến của bạn thay vì chỉ nhìn vào một danh sách từ khóa khô khan.
I write about Next.js + TypeScript + AI engineering, with a focus on making sites discoverable to LLMs and AI search. Long-form notes at mudassirkhan.me
the manifesto as image (rule 5) is the one that scales. a banner you can read in half a second stays with people after they close the tab. "zero telemetry. zero cloud. zero subscriptions." is compact enough to repeat and specific enough to mean something. most bios try to say everything and end up saying nothing.
the ~/apps path naming is also doing more work than it looks. it's not just aesthetic: it tells someone scanning the page in two seconds that the person behind it works on the command line. that's a signal before they read a word.
one thing worth testing: does the download button convert better before or after the screenshot? some product pages put the action above the fold, others let the visual do the selling first. curious which one your bounce data says.
Independent AI Engineer & Complex Systems Architect. Building open-source tools, experimental systems, developer infrastructure, and products across AI, simulation, geospatial data, RF, and procedural
I really like it, it's well-organized and impactful. It’s certainly not my style (it reminds me of cyberpunk), but it’s perfect for what you’re working on.🦾
Love these practical actionable rules! I’m so tired of bloated profile READMEs full of random badges and decorative gimmicks. Definitely going to refactor my own profile following your layout tips.
thanks.
I am glad to see many of you getting inspired by me to update your readme.
thanks for that.
also remember one thing always make your readme like a storefront not a portfolio website type look.
Software Architect, FullStack Dev. Since 2016 bringing innovative and objective solutions focusing on simplicity and efficiency using PHP, Laravel, Javascript and other web technologies
Thanks for the mention. I really like your version, you nailed it!🔥
thanks
you really started a trend bro.
congrats and thanks for the trend.
you inspired me to update my old readme to a really great store front readme.
I'm glad I indirectly contributed to that!
yeah, bro also you guys are managing the no. stats easily but when I just set up one download counter my mind blowed, it was not working automatically manual run workflow was only working how do you guys manage it?
Do you mean the automatic scheduled workflow didn't work? If that's the issue, sometimes it has some delays, it can run a bit later than scheduled, but it'll eventually run.
Like I waited for 3hours but I set it to 30minutes update.
I will try it to setup one more time.
Awesome, another top post!👏
another top? bro it is not viral till now.
oh yeah sorry sorry I just seen this post is also viral
500 views crossed just.
bro have you seen my new readme?
waiting for this badge lol.
source: screenshot taken from @xulingfeng 's profile badges
bro how can I get that badge any tips?
You just need someone to send you two diamonds.
The 3-second download test is the right frame. I ran something similar when I moved my project links above the fold — bounce rate on my profile dropped hard because people stopped scrolling for the "see releases" link. One thing I'd push back on: the
.zipdirect download is clean for desktop apps, but if any of these ever ship as web services, you'll want a live demo link next to the download, not buried. Four apps with four buttons is a strong start though — most profiles I see have zero.thanks for the feedback
but I didn't understand
feeling glad that you liked my readme
Treating a README as a storefront is a mindset shift that a lot of developers miss, often getting bogged down in flashy badges and contribution graphs that don't actually tell a recruiter or collaborator what you can build. I've found that the most effective profiles focus heavily on the "why" and the "how" rather than just a list of technologies. Instead of just listing React or Go, showing a quick architectural breakdown or a link to a specific, well-documented problem you solved makes a much stronger impression. One thing to watch out for is over-engineering the README itself; if it takes more time to maintain your profile than your actual projects, you've crossed the line from storefront to distraction. Keep the documentation lean and let the code do the heavy lifting.
yeah bro I will manage & maintain it.
Thanks for the advise
Spot on. Honestly, I’m so tired of scrolling through endless contribution snakes and generic stats cards just to figure out what someone actually builds. Treating a README like an app store listing is a solid mental model. It cuts straight to the value proposition.
yeah actually right.
Glad you agree, Akhouri. At the end of the day, a hiring manager or open-source maintainer wants to see your impact, not your setup. A profile README should act like a pitch deck for your skills—show me the live demo links, the architecture layout of your top project, and what problem you actually solve. The generic stats cards just create unnecessary noise and bloat.
I am also fall into a README.md black hole, but at least I zip my CV to one line:
single line CV: Creator of mordorjs and TifY also pipeline-operator fanatic. 🇭🇺
The placeholder image just is a beginning something new which will be comming ...
github.com/Pengeszikra
The most important part is where my dev.to post link to my repo.
This is actually a much better way to think about a GitHub profile. Most profiles look nice, but I rarely know what I’m supposed to click first. Putting the actual apps and download buttons front and center makes the page feel way more useful.
yeah that's why I called it a storefront.
and I would recommend every developer if they are shipping apps then make github profile readme like me.
Cách tiếp cận coi README là storefront thực sự thay đổi tư duy của mình về việc xây dựng thương hiệu cá nhân. Thay vì lấp đầy trang cá nhân bằng các badge màu mè hay những dòng quote vô nghĩa, việc tập trung vào các dự án thực tế và cách chúng giải quyết vấn đề cụ thể sẽ gây ấn tượng mạnh hơn với nhà tuyển dụng. Một kinh nghiệm mình rút ra là đừng chỉ liệt kê tech stack, hãy thử đính kèm một vài con số hoặc kết quả thực tế từ các dự án đó. Nó giúp người xem hình dung ngay lập tức năng lực thực chiến của bạn thay vì chỉ nhìn vào một danh sách từ khóa khô khan.
"Your profile has one job, make it a button" is such a sharp idea. The single-width rule and self-hosted SVGs are underrated details.
Yeah, thanks
the manifesto as image (rule 5) is the one that scales. a banner you can read in half a second stays with people after they close the tab. "zero telemetry. zero cloud. zero subscriptions." is compact enough to repeat and specific enough to mean something. most bios try to say everything and end up saying nothing.
the ~/apps path naming is also doing more work than it looks. it's not just aesthetic: it tells someone scanning the page in two seconds that the person behind it works on the command line. that's a signal before they read a word.
one thing worth testing: does the download button convert better before or after the screenshot? some product pages put the action above the fold, others let the visual do the selling first. curious which one your bounce data says.
I really like it, it's well-organized and impactful. It’s certainly not my style (it reminds me of cyberpunk), but it’s perfect for what you’re working on.🦾
yeah, I make it feel like a premium readme and a great storefront combo.
Love these practical actionable rules! I’m so tired of bloated profile READMEs full of random badges and decorative gimmicks. Definitely going to refactor my own profile following your layout tips.
thanks.
I am glad to see many of you getting inspired by me to update your readme.
thanks for that.
also remember one thing always make your readme like a storefront not a portfolio website type look.
Thanks for sharing this. This will improve my profile.