3 ms·
I would recommend just writing one yourself. It's not very hard, and the process of writing it will make you intimately familiar with how it works, so you won't
by resonious 3y ago
I would recommend just writing one yourself. It's not very hard, and the process of writing it will make you intimately familiar with how it works, so you won't feel overwhelmed.
Just writing simple software feels way better than reading docs for an arcane tool that will change on you over time due to updates.
- michaelbuckbee 3y agoThere's a joke that goes like: "What's the first thing a developer does when they want to publish a blog post? Write a SSG."
- jjice 3y agoRelevant article with a graph that always gives me a laugh: https://blog.ashfaqfarooqui.me/post/blogging/ https://blog.ashfaqfarooqui.me/post/blogging/ I think may of us here are guilty of the right hand side.
- corytheboyd 3y agoYep just write your own, you can finish it in hour(s) if you yourself don’t overcomplicate things ;) You might come back to it in a year and hate it, but that’s also part of the SSG vision question every software engineer is required to go through.