4 ms·

The point of the article is one I align with: You're writing it for yourself, 99% of the time. The other 1% is the future you. I blog for work. I don't discuss

by ggm 2y ago

The point of the article is one I align with: You're writing it for yourself, 99% of the time. The other 1% is the future you. I blog for work. I don't discuss it with family. I think I'd find it very stressful answering the "why did you say that" questions. The corollary of this, is that I write notes by hand in almost every meeting I attend, and never ever read them again -But for things like IETF I do a mixture of .org and meetecho (markdown) because there is at least some possibility others may get value from the shared log in meetecho, and I know I will use the .org to .. write the blog.

matrix87 2y ago
> You're writing it for yourself, 99% of the time. The other 1% is the future you. Or alternatively it could be a place for educational stuff like the more detailed answers on stackoverflow. Except the middleman gets removed
- crngefest 2y ago
  [flagged]
- fullspectrumdev 2y ago
  In the past I’ve used a blog literally to make small notes on very simple things that I always ended up having to look up, or for notes on the “right way” to do something. For example: for years I was using Pythons requests library incorrectly. The way I was doing it worked - but it wasn’t correct. Once I published a short blog on the correct way - the correct way seemed to stick better in my mind!
  - matrix87 2y ago
    > For example: for years I was using Pythons requests library incorrectly. The way I was doing it worked - but it wasn’t correct. Usually I prefer a git repo for this kind of thing
    - ggm 2y ago
      You mean.. you're blogging in git, right?
      - matrix87 2y ago
        Kind of, idk if you can call it that. Git frontends like gitea already have markdown rendering so idk what the point is of having a separate thing for blog writing
vasco 2y ago
I take many handwritten notes throughout the day like you, but found that reviewing them for 2 minutes at the start of the next day has high return on investment.

by ggm 2y ago

matrix87 2y ago

> You're writing it for yourself, 99% of the time. The other 1% is the future you. Or alternatively it could be a place for educational stuff like the more detailed answers on stackoverflow. Except the middleman gets removed

crngefest 2y ago
[flagged]
fullspectrumdev 2y ago
In the past I’ve used a blog literally to make small notes on very simple things that I always ended up having to look up, or for notes on the “right way” to do something. For example: for years I was using Pythons requests library incorrectly. The way I was doing it worked - but it wasn’t correct. Once I published a short blog on the correct way - the correct way seemed to stick better in my mind!
- matrix87 2y ago
  > For example: for years I was using Pythons requests library incorrectly. The way I was doing it worked - but it wasn’t correct. Usually I prefer a git repo for this kind of thing
  - ggm 2y ago
    You mean.. you're blogging in git, right?
    - matrix87 2y ago
      Kind of, idk if you can call it that. Git frontends like gitea already have markdown rendering so idk what the point is of having a separate thing for blog writing

vasco 2y ago

I take many handwritten notes throughout the day like you, but found that reviewing them for 2 minutes at the start of the next day has high return on investment.