Developers are phenomenally talented at forming communities.

We have IndieHackers, YouTube channels and Twitch streams like The Primeagen and Theo and sub-reddits like r/softwaredevelopment and r/softwareengineering. We have countless hashtags, viral milk memes on Twitter and much more.

Our communities could be more.

Twitter’s algorithm, and thus our community and the way we interact with it, changed overnight when Elon took over. Reddit’s communities are prone to censorship and their mods tend to be overzealous. Many of our communities are incredibly healthy, but they are disconnected from the larger body of developers by niche and focus.

None of them adequately capture the wealth of knowledge and wisdom that our community has to offer, and I think we can do better.

Dev CheatSheets

My goal for Dev CheatSheets is to build a community of developers where knowledge sharing is treated as the primary mode of interaction between developers, where we can build in public as a default instead of as a marketing tactic.

I want to build a place where we can store and create our knowledge and share it with the world, a central community where we can build relationships just as readily as we build applications.

I want a place where each piece of code we build is linked with code written by others, where the knowledge builds upon itself and where the boundaries between Personal Knowledge Management and Social Media is broken.

If this sounds like the community for you, sign up for the newsletter and follow this blog. I’ll be updating both as time goes on and development is built out further.