Didn’t know that one before, I didn’t even consider the dependency issue!
Didn’t know that one before, I didn’t even consider the dependency issue!
But, yes. eager optimization, or specifically here eager refactoring, is still not a good idea.
Beware premature optimization, indeed! Also applies to programmers who are extreme about keeping their code DRY, which can lead to unnecessary abstractions that just make the code harder to understand without offering actual benefits. IME some languages suffer from this more than others, e.g. Ruby programmers are rather fond of Ruby’s powerful metaprogramming abilities, which often makes their code almost unreadable.


A language’s packages need to be in lockstep with the language’s version, and they usually depend on each other, too (to a much higher degree than they depend on programs/libraries from other languages, not counting stuff like C that many higher-level languages are built on).


LLMs also enables managers and businesses who want to make money with shitty products, which is probably a higher detriment to code quality than the low-level difficulties of programming ever was.
Either way, IMO the prime use of AI, including LLMs, is mass surveillance. And no, that’s not a good thing.


Aww, did the serial copyright violator get copyright violated?


I’d say it still counts as diurnal, unless you’re actually sitting completely in the dark (and yes, the screen counts as a light source) Ü
Also, as someone who also is awake most nights, I get the impression that it’s not particular healthy, i.e. is in conflict with our biology.


All other things being equal, eyes specialized on daylight activity will just be better at the kinds of intricacies needed for shaping the tools, collecting the right materials etc., mostly because night vision is pretty much greyscale for mammals. And would humans even be as likely to start using fire if they could see in the dark? It’s obviously still useful for preparing food, but IDK that I’d choose to place a beacon of light and smoke (smell) in the night if I could see without it.
I’d assume that humans used tools long before they started using fire, because making fire is far more involved than using simple tools. Though this might actually be worth looking up.


Tool use and being nocturnal are kind of a bad fit, so it’s hard to believe that humans would have evolved in a recognizable form if they had been nocturnal.


You can do that, but fediverse and threadiverse (Mastodon and Piefed/Lemmy/Mbin) are very different kinds of websites and it will lead to unexpected weirdness. Best to make a separate account for each type of thing (i.e. one for the twitter-like experience, one for the reddit-like, one for the instagram-like etc.).
Whether you use the same identity (e.g. same username on Mastodon and Piefed, linking your Mastodon profile in your Piefed profile etc.) for the whole fediverse is a matter of taste.
Ah. Fair, I guess I forgot about it because I didn’t make that mistake in a while.
Is that a combo you often hit on accident? Ctrl+Shift+C seems way too specific for that …
Neat feature, though. Nice to see that they still do features that aren’t about AI.


If Cursor doesn’t help with that, but you constantly have several devs on “putting out fire”-duty, you have a pretty strong case for taking the time to make the software not be constantly on fire. i.e. it’s probably going to save you time (man-hours) to write some proper code, and time is money.
Not that I expect your superiors to care about that.


Does Cursor actually help with any of that?


Do your customers ever complain about your software? If so, what does your team do when it happens? Is this what “something is always on fire” refers to?


This kind of thing was a huge problem when Germany tried to ban the NPD (a neo-nazi party) in the 2010s. Too many police/secret service infiltrators in way too high positions. In the end, they failed to ban the party.
TBF, if your parents did the stock investment themselves, it’s pretty likely that they would have lost most of it, too. Still better chances than the lottery, though.
On one hand, (for the big types of lotteries) the odds are known and they will pretty much always pay if you win, unless you forget that you even bought a ticket or something like that. Both of those are different for most other types of gambling.
On the other hand, most people don’t really understand these kinds of odds and lotteries make no effort to educate people on it, even though they’re often state-owned. They’re pretty much deliberately designed to prey on cognitive biases and lack of education.
I think the demographic for lemmy (and lemmy.ml in particular) is so niche and so biased towards privacy that even with a bigger sample, it’s next to impossible to get really good data. Probably good enough to say that it’s very likely that there’s a significantly skewed gender distribution, though. The user polls that were done on my instance showed similar results IIRC.
How could that possibly lead to a bias? /s
I do have formal education in the field, but that doesn’t mean that I’m easily capable of e.g. writing a module for Nginx or even most website frameworks or knowledgable enough about administration to feel comfortable exposing a dynamic website (as opposed to static HTML+CSS) to the internet.
A lot of it is learning by doing, though, and for a lot of things books are a great resource (some stuff is outdated as soon as it’s published, but general system administration or programming knowledge doesn’t get outdated that fast).