craked.dev
Quantify your developer impact—check how cracked you are.
Developers spend hundreds of hours building complex projects, contributing to open-source repositories, and honing their craft. Yet when it comes to showcasing our actual impact, we’re still stuck using static GitHub profiles or text-heavy resumes that barely tell the full story.
They rarely capture real code quality, problem-solving depth, consistency, or engineering velocity.
That’s why I decided to build craked.dev.
💡 What is craked.dev?
craked.dev is designed to give software engineers a data-driven, engaging way to quantify their real developer footprint—and finally give a definitive answer to the question: how cracked are you really?
Instead of relying on raw contribution graphs or bullet points on a resume, craked.dev analyzes your engineering activity to highlight key strengths, performance traits, and quantifiable metrics.
🛠️ What’s Next?
I’m currently building out the core features and refining how developer stats are processed and visualized. My main goals right now are:
Getting early feedback from fellow indie hackers and engineers.
Fine-tuning the metrics so they accurately reflect developer productivity and code impact.
Adding more integrations to give a holistic view of a developer's workflow.
I’d love to hear your thoughts! What metrics do you feel are most underrepresented in traditional developer portfolios or GitHub profiles? Let’s chat in the comments!
2 Comments
for someone like myself who constantly suffers with imposter syndrome but also loves data, i feel like i'd love to ground my progress in data using something like this
The interesting part is that the moment you turn developer activity into a score, you're no longer just displaying data — you're making a judgment about what “good” engineering looks like.
That feels like the harder problem underneath the metrics.