uses.dev started from a practical need that I’ve encountered countless times throughout my career. As developers, we often want to share our setups, our favorite tools, and the technologies we use, but the process can be cumbersome and time-consuming. Creating a personal website from scratch, maintaining it, keeping it visually appealing, and updating it regularly – it all requires effort that most of us would rather put into coding, learning new things, or just enjoying our projects.

I wanted to build something different – something that doesn’t feel like an additional burden but rather a seamless, efficient way to showcase who we are as developers. The idea is simple: provide a modern, aesthetically pleasing platform where developers can easily present their tech stack, work environment, and skills without the hassle of setting up and maintaining a personal site.

The project took shape after years of seeing fragmented solutions – some too simplistic, others overly complex. I thought, why not create a platform specifically designed for developers, where they can effortlessly display their professional identity while keeping things dynamic and up to date?

One of the key inspirations came from the realization that developers need more than just a list of technologies on a resume. We want to show how we use those tools, what our setup looks like, and how our environment reflects our way of working. It’s about more than just skills – it’s about context.

The focus was always on simplicity, customization, and practicality. The platform had to be straightforward to use while allowing enough freedom to present individuality. I’m constantly refining and adding features based on my own experience and feedback from fellow developers because I believe this platform can become a valuable part of how we present ourselves professionally.

In the end, uses.dev is more than just a project – it’s a tool I wanted for myself and knew others would appreciate. It’s about making it easy to be proud of our setups and sharing them with the world without feeling the pressure to maintain a full-blown personal website.

Inspired by the excellent work of Wes Bos and his project uses.tech, I wanted to take the concept further — to create something that’s not just a list, but a free personal profile, almost like a digital developer business card.

Wes Bos’s uses.tech showed how powerful it could be to see what tools and setups developers around the world are using. It sparked a sense of community and gave a glimpse into the diverse ways we approach our work. But as much as I loved the concept, I felt there was room to make it even more personal and dynamic.

I wanted a platform where developers could not only list their favorite tools but also present their setups in a way that reflects their individuality. Something that would evolve along with their career, allowing them to add, change, and update their tech stack and work environment without hassle. A space that feels like theirs, visually appealing and easy to maintain.

I also realized that developers often want to connect their professional presence with other platforms – social profiles, repositories, communities – in one cohesive profile. The idea was to blend the simplicity of a list with the depth of a personalized profile, giving developers a place to showcase their skills, tools, and professional identity in one place.

That’s how uses.dev came to life – as a natural progression from the idea that Wes Bos started, but reimagined to be more than just a collection of lists. It’s a way to present ourselves as developers, in a format that’s modern, flexible, and truly our own.

Connect with fellow developers, get support, and share your projects on our Discord server!

The versioning system of uses.dev is a hybrid model combining marketing and technical versions.

The versioning system of uses.dev follows a hybrid approach, combining both marketing and technical versioning to effectively communicate updates and improvements. Inspired by the Epoch-Semver method, it balances the clarity needed for users with the precision developers expect. This system ensures that every version tells a story, both from a product and a technical perspective.

The first part of the version number represents major product milestones and announcements. It’s designed to indicate significant changes that impact the user experience, such as major new features or substantial updates. This makes it easier for users to understand when the platform takes a big leap forward, like introducing a new feature set or redesigning the interface.

The second part follows a more technical, semantic versioning pattern. It includes detailed information about breaking changes, new features, and bug fixes. This way, developers have a precise understanding of what has changed behind the scenes. By combining these two approaches, uses.dev provides a versioning system that communicates both user-facing improvements and technical progress transparently.