Rootless docker exists now. Not sure why people still don’t use it.

Sorry but you will never get me to enjoy writing or even reading code on a tiny display.

Judgement call. When it’s something prone to change that’s hard to get right, duplicating it just creates more maintenance burden.

People who’ve never used Rust or only used it once and couldn’t grok it like to meme that Rust is bad to cope.

and it happens exactly as the people whose claim is being denied with “slippery slope” fallacy said

But this is the crux of the fallacy. What evidence is anyone providing that there is indeed an insidious chain of events we are enabling by adding the birthdate field? Are there examples of cases similar to this in history?

EDIT: I can tell people are getting emotional about this because I’m being down voted for just asking a question that elaborates the point someone is making.

I’m thinking seriously about using something like a Daylight tablet as a thin client for a more powerful machine at home. Obviously doing real coding by hand would still suck, but LLM-based coding might actually be viable.

This just makes me realize that my TI Nspire calculator probably violates this law.

Slop points aside, I found 5.4 to be pretty ass compared to 5.3 codex. Took way longer and wasted more tokens.

1000 lines isn’t that unreasonable for a PR. Commit size matters more.

Or idk maybe people have a job where it’s useful to hone your tools? This meme doesn’t make any sense.

That’s why I quit coffee. Tea doesn’t do that to me for whatever reason, probably just less caffeine total.

But I assume it also had something to do with high blood pressure.

Same as demon. Because my research indicates that this usage was originally a reference to Maxwell’s demon.

https://www.takeourword.com/TOW146/page4.html

I thought it was a reference to Maxwell’s demon.

Daemons in computing, generally processes that run on servers to respond to users, are named for Maxwell’s demon.

I have used OOP design patterns many times, but that doesn’t mean I use inheritance a lot. I almost always reach for interfaces instead.

It was actually typed. Python had type annotations at the time.

I only wrote C++ very early in my career so I don’t remember much, but I’m sure I at least tried some inheritance in toy games I would write. All of that code was trash though by my standards today.

Some legacy Python code that already used inheritance. I had to extend it, and it was pretty infeasible to refactor the whole thing to not use inheritance. Not sure if I technically regretted that decision, but it was definitely painful, since Python inheritance makes it really hard to follow program control flow.

No because those are different things.

In over ten years of professional programming, I have never used inheritance without regretting it.

Not a senior dev thing, just a bad dev thing.

These days with language services, code should be compiling after nearly every edit.