The Open Source Expert | Revenue & Trends

The hottest Substack posts of The Open Source Expert

And their main takeaways

Turn off unused GitHub features to make your repo look cleaner and more inviting for viewers.
Common features to disable include Packages, Releases, Wiki, and Discussions if they aren't being used yet.
You can easily re-enable these features later when your project starts using them more actively.

A good GitHub README should be informative and engaging. Include key elements like a description, features, and visuals to attract users.
Avoid adding things like a table of contents or large documentation directly in the README. This can overwhelm visitors and is often redundant.
It's essential to get feedback on your README from others, especially new users. Their fresh perspective can help you improve it significantly.

Getting a repo's setup right is important. A good description and a clear README help users understand the project quickly.
Having key documents like a Code of Conduct, License, and templates for issues and pull requests makes collaboration smoother.
Using labels for issues helps keep everything organized, making it easier to find what you need in a busy project.

Using NextJS helps streamline your project with standardized setups, making it easier to onboard and rapidly develop features.
Automating tasks with GitHub Actions can save time and reduce errors, giving you quick feedback on your code changes.
Feature flags from Flagsmith allow you to control which features are visible without needing to redeploy your app, making it easier to manage updates and A/B tests.

Using Alerts in GitHub Markdown helps highlight important information, making it easier for readers to notice. There are different types of alerts like notes, tips, and warnings that you can use.
To create an Alert, you simply need to use specific Markdown code, starting each line with a '>' symbol. This format makes your content stand out more effectively.
It's important not to overuse Alerts, or they might lose their impact. Use them sparingly to ensure readers pay attention to the key points.

Get a weekly roundup of the best Substack posts, by hacker news affinity:

A great client has done their research on you and knows your skills. This means they understand what you offer and how you can help them.
Good clients are open about money. They discuss budgets clearly and have reasonable expectations for what they can afford.
Respect is key in a client relationship. A good client values your work and understands that your rates reflect the quality you provide.

Sometimes, despite a lot of hard work and support, a project just doesn't succeed as hoped. It's important to recognize when to let go.
Managing a community project and running a business can be very different. The needs of the community may not always align with business goals.
Feeling overwhelmed by notifications and contributions can lead to burnout. It's key to balance community engagement with personal well-being.

Look out for clients who can't clearly tell you what they want. If they keep changing their mind or seem confused, it could be a sign of trouble.
Be cautious of clients who expect free work or make promises about future jobs that never happen. It's usually better to get a commitment upfront.
Always have a retainer agreement in place. This helps set clear expectations and protects you if things go wrong.

Using Husky for Git hooks gives you quick feedback before making a commit. This helps catch errors early, saving time later.
Automating checks like linting or testing before a commit prevents you from forgetting to run them manually. It improves the code quality before you share it.
Even with local hooks, don't skip CI checks since they're still important. CI runs on a fresh setup and ensures everything works properly in the project.