Julio Biason
5 years ago
3 changed files with 37 additions and 1 deletions
@ -0,0 +1,35 @@ |
|||||||
|
+++ |
||||||
|
title = "Things I Learnt The Hard Way - Blogging About Your Stupid Solution Is Still Better Than Being Quiet" |
||||||
|
date = 2019-07-25 |
||||||
|
|
||||||
|
[taxonomies] |
||||||
|
tags = ["en-au", "books", "things i learnt", "personal", "solutions"] |
||||||
|
+++ |
||||||
|
|
||||||
|
You may think "This project is so small and so focused on whatever I needed, I |
||||||
|
should never post it on Github. What would people think?" Github is not for |
||||||
|
that. |
||||||
|
|
||||||
|
<!-- more --> |
||||||
|
|
||||||
|
Github is not a repository for "cool, almost perfect" projects. You're free to |
||||||
|
show that, at some point, you were a beginner[^1]. |
||||||
|
|
||||||
|
You can always come back, review what you did and fix it. It will, as your |
||||||
|
[blog](/books/things-i-learnt/blogging), show that you're improving. |
||||||
|
|
||||||
|
... or maybe you'll let your project there just to rot. I still have some |
||||||
|
Python projects that I wrote when I was learning the language that, although |
||||||
|
they work, they don't look like Python projects. |
||||||
|
|
||||||
|
But who knows? Maybe the code you wrote to solve your small problem can help |
||||||
|
someone else to fix their problem, which was not exactly the same, but pretty |
||||||
|
close. Or even you could get a code review that would teach you something new |
||||||
|
about the language/design you used. |
||||||
|
|
||||||
|
[^1]: Whoever see the first projects I did in |
||||||
|
[Rust](https://www.rust-lang.org/) wouldn't think I have 30 years of |
||||||
|
experience in the field. Everybody is a beginner at some point. |
||||||
|
|
||||||
|
{{ chapters(prev_chapter_link="/books/things-i-learnt/blogging", prev_chapter_title="Blogging About Your Stupid Solution Is Still Better Than Being Quiet") }} |
||||||
|
|
Loading…
Reference in new issue