-
I wrote about building a dev blog, why I decided to work in public on my hobby code projects (even though it can be scary), and how it helped me build better code and be more participatory with the larger community. fightwithtools.dev/posts/writing/play-to-find-out-on-showing-your-code/On twitter.com
♻️ 1 Retweets
❤️ 8 Favorites
Mood 0
-
I think the answer to this question has to be working very publicly and in as participatory a way as possible Chronotope/1390700217838841860Permalink On twitter.com
❤️ 2 Favorites
Mood 0
-
Credit to pfrazee and helenhousandi who both gave great examples of working in public that were formative towards my approach here.Permalink On twitter.com
❤️ 3 Favorites
Mood +3 🙂
-
Anyway... as I said on day 1 ( fightwithtools.dev/posts/projects/devblog/hello-day-1/ ) I'm not a designer, so if you have strong feelings about it looking bad, I take PRs! :DPermalink On twitter.com
❤️ 2 Favorites
Mood -1 🙁
-
And, in credit to this process, working in the open on this dev blog and thinking collaboratively led to multiple filed issues, at least two PRs on other projects, and two NPM packages: - npmjs.com/package/markdown-it-find-and-replace - npmjs.com/package/eleventy-plugin-dart-sassPermalink On twitter.com
❤️ 1 Favorite
Mood 0
-
My favorite part of this project was figuring out how to automatically create links from commit messages in text to the matching commit in the repository I was writing about: fightwithtools.dev/posts/projects/devblog/hello-day-37/#searching-for-git-commit-via-apiPermalink On twitter.com
❤️ 1 Favorite
Mood +4 🙂