pfm

joined 9 months ago
[–] pfm@scribe.disroot.org 15 points 4 days ago (1 children)

If you enjoyed it, I've collected a couple of others:

https://untalkative.one/reading:2019:good-stories

[–] pfm@scribe.disroot.org 72 points 4 days ago (5 children)

Reminds me this great story from a different era:

https://www.ee.ryerson.ca/~elf/hack/recovery.html

[–] pfm@scribe.disroot.org 1 points 1 week ago

On a serious note, I really enjoy yerba mate-based (or should I write flavoured) elixirs. Or even yerba mate itself. Just saying! 🤷

[–] pfm@scribe.disroot.org 5 points 1 week ago

That's like... Your opinion, sis...

[–] pfm@scribe.disroot.org 18 points 2 weeks ago (3 children)

Do you eat them too? Asking for a friend!

[–] pfm@scribe.disroot.org 13 points 2 weeks ago (1 children)

Your body? You mean body of knowledge?

[–] pfm@scribe.disroot.org 9 points 3 weeks ago (9 children)

Could someone explain how they're going to drive 407 km/h in traffic jam? Or in a city, in general?

[–] pfm@scribe.disroot.org 1 points 3 weeks ago

I definitely agree that too many comments is often a bad sign, esp. when large part of them is obviously generated.

[–] pfm@scribe.disroot.org 2 points 3 weeks ago (2 children)

As mentioned in my other comment, names will rarely explain the reasons why a given solution was chosen. These reasons are important from maintenance perspective and should be recorded next to the relevant code.

[–] pfm@scribe.disroot.org 8 points 3 weeks ago (1 children)

You're definitely not the only one.

In my opinion the important information we should record in comments is WHY, because the code can only explain HOW, maybe WHEN, but never WHY. If we don't know WHY, any refactoring done in the future could break the logic by ignoring assumptions made by the authors.

[–] pfm@scribe.disroot.org 10 points 3 weeks ago

Thanks for making me aware 🙇

view more: next ›