As if needing to be able to understand code quickly wasn’t already a problem before LLMs.

It is almost always that.

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.

Can you share your nix config to get cachyOS kernel + proton?

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.

Doesn’t happen to me on the web app.

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.

There should be some balanced path in the middle somewhere, but I haven’t stumbled across a formal version of it after all these decades.

This is where experience is so valuable. It helps you know how much planning to do before you start building. Or sometimes if you need to build something before you can start planning (i.e. prototyping). You need to identify the most critical problems to solve for your given use case, and make sure you do just enough planning to solve those problems. Often that means anticipating future requirements and making sure your plan doesn’t put you on a path that’s incompatible with future requirements. But don’t completely solve the future problems yet; do just enough to convince yourself that you aren’t painting yourself into a corner.

I can’t take this seriously if MATLAB is near the top of the scoreboard.