31 karma · joined January 12, 2023
We're building a collaborative platform to gather and share best coding practices.
In short, it helps us highlight code snippets from the IDE (JetBrains, Visual Studio, VS Code), discuss them in Slack (or MS Teams or Discord or Mattermost), and document them with contextual examples.
It really depends on your audience. If you're building a developer tool, it's always features over benefits.
It could be for different reasons. One alternative would be to submit your blog post ideas to existing publications. Then cross-post them to your own domain. Always own your content.
Also, I'd recommend dev.to and/or Hashnode instead of Medium -- both platforms have a more developer-friendly reading experience (i.e. dark mode support).
In addition, I'd recommend:
Read and acknowledge the coding standards and best coding practices.
An efficient onboarding process on best coding practices would definitively save you time for your first code reviews with your team.
For example, at Promyze, we set up “Discovery Workshops,” some interactive coding challenges to discover/learn our best coding practices with concrete code snippets from the codebase.
The concept is simple:
- We built a list of best practices we want to introduce,
- We select for each practice some examples and counter-examples from the practice documentation,
- Then, each new team member will have to find in the source code where some best practices have been followed or not.
This really helps make onboarding and work more productive -- and fun.
- 30-min sessions to introduce new learning, from a blog post, a tech conference, or a book;
- Technical agile coaches;
- 2 to 3-day, 10-people training sessions;
- E-learning platform;
- Wiki;
- Linters and code analysis tools;
- Code reviews;
- Pair and mob programming sessions;
- Coding Dojos;
- Technical communities, or communities of practices;
- Craft Workshops;
I got so into it that I wrote a series of blog posts on how to create a learning culture in software engineering teams: https://www.promyze.com/set-learning-culture/
Sorry to plug my own thing, but poured months into it, and genuinely thought it would help you!
That'd be the right choice IMHO.
How we work is inspired by Raycast, i.e. monthly focus documents (1): it starts with defining the goal for the month, then lists the projects we focus on.
My step 1 is to remove/delete/trash lists, then - step 2 - define 2/3 top priorities of the day, and - step 3 - just f* do it :)
FWIW Product Hunt recently released a complete launch guide here: https://www.producthunt.com/launch
1 - https://github.com/filipelinhares/awesome-slack 2 - https://github.com/mhxion/awesome-discord-communities
> If you want to appeal to Hacker News readers, tell them how something complicated works. Especially if most people either don't know, or are mistaken about, how it works.
Source: https://twitter.com/paulg/status/1553708274465140736
1 - https://review.firstround.com/collections/advice-for-making-... 2 - https://adplist.org/
1 - https://news.ycombinator.com/item?id=31836974 2 - https://news.ycombinator.com/item?id=34334887
Is it a methodology you implemented yourself? Curious about what your key learnings are.