Awesome! yeah, there’s a variant where you can seal the jar, but for the most part exactly what you said is the norm. I’ve had mine for roughly 5 years now, but I added shrimp and trim it back about once a month or so . I don’t even feed the tank more than a few times a week.

You should look up “Walstad planted tank”. An all plants aquarium you don’t ever have to mess with (except to trim if you want to)

If you want to roll your own, I’ve had good luck with ASRock Rack motherboards.

A coworker once got an HR talking-to for printing this meme out and leaving it on all the dev’s desks.

I once tanked a production service by assuming it could handle at least as much load as my laptop on residential sub-gigabit Internet could produce.

I was wrong by at least an order of magnitude.

It took me a year but I broke my team of this habit. The trick was to remind them that the parking lot shouldn’t be scheduled. The whole point is that you continue conversations organically so that it’s more like the beginning of a working session instead of the end of a meeting.

It is, and it’s a valid complaint. Go and Rust have handled it differently than Python or JavaScript, and all of them have their faults and bonuses.

It’s a load bearing S.

There are so many more, and better!, options than testing in prod, but they take time, money, and talent and ain’t no company got time for that (for a business segment that “doesn’t generate revenue”)

The “Big Boys” use tests to gauge when code is production ready, they don’t rely on a typing system and call it a day. I’ve seen monoliths made out of bash serve their purpose for years without a glitch, thanks to tests.

I used to work at a place that required daily progress reports on tasks (this was before agile took off so ‘daily standup’ wasn’t a thing.). So I wrote a script to schedule my git commits throughout the week (so that I had at least one a day), and every afternoon it would pull my git history, generate a summary, and email it to my manager.

He knew it was automated and hated me for it but I had the most consistent and detailed reports. On the upside, it really trained me to make good commit messages. On the downside It really instilled me with a strong “burn the building down” kind of vibe that persists to this day.

The whitespace is not only required, but it must be tabs and spaces.

ಠ_ಠ

I know this answer is flippant and dickish, but:

python3 -m http.server 80

shadowsocks seems to be the best way for now.

bad habits are hard to break.