Github has suffered reliability issues as of late, due to 10x commit volume from vibe coding, leading many seeking other providers or self hosting their own git repositories.

Instead of using a third party provider, you can use your own cloud storage, such as Google Drive, to store your private git repositories. This approach works with Google Drive, MS One Drive, iCloud, DropBox, Backblaze or any cloud storage that has a desktop client. No additional servers are needed, and syncing uses the exact same git commands you are familiar with : git push, pull, fetch , gc etc.

One responsibility of engineers & especially leads is managing many channels of signals : emails, blog posts (internal and external), tags , push notifications, group chats, alerts from dashboards and more.

These signals tend to scale exponentially to the number of projects & people that you are responsible for.

Quickly you’ll need to set up a system to make sure that you are receiving high-signal information and filtering out low-signal noise. How do you do that?

Next time you create a post with code snippets–like here on dev.to or stackoverflow–consider sharing a working and buildable gist along with it. By doing so, others can clone, reproduce your results, and commit new variants much more easily.

With the process below, your gist becomes a sharable laboratory. Since the gist contains all of the code variants and test cases, any team member can create a variant and run the tests against all existing variants.