I wouldn’t say “correct” as this implies all alternatives should be discarded. As we have the commo, decentralized protocol everyone can use the software which fits their needs / subjective preferences.

For example Misskey / Sarkey are intersting alternatives to Mastodon as they offer neat features. And Piefed is currently gaining a lot of users (also from Lemmy).

• punctual
• like giving helpful advise even if not asked
• can discuss the definitions of single words

I tried TDD in a personal project recently and it got annoying pretty fast. It was also a project where I tried a new Framework so writing test when one doesn’t know how things behave exactly results in adjusting the tests afterwards anyway.
Thinkimg how I want to designe my API upfront while discovering the details as I go served me well in the past (still in context of personal projects).

It also doesn’t help when my tests have more bugs than the tested code…

Multi layer debugging is still better than multi layer marketing.

I’m new to Go and wanted to copy some text-data from a stream into the outputstream of the HTTP response. I was copying the data to and from a []byte with a single Read() and Write() call and expexted everything to be copied as the buffer is always the size of the while data. Turns out Read() sometimes fills the whole buffer and sometimes don’t.
Now I’m using io.Copy().

Turned out that the bug ocurred randomly. The first tries I just had the “luck” that it only happened when the breakpoints were on.
Fixed it by now btw.