Canadians do tip as well, and you can’t blame Trumpets for that 😁

Not my experience. I’ve had the displeasure of having to use Rider at work, and it’s much slower than VSCode, if only for boot times which are a pain in the butt for large projects. You gotta pay for that bloat and feature creep somehow.

And that’s on a Xeon machine.

As for refactoring, yes, Rider has lots of options that don’t work and do half the job. So much so, that I don’t use them at all, because they’re unreliable.

The requirement for Copilot to qualify an IDE is a bit funny. First, VSCode has some support for it, and, secondly, this is super recent, so unless IDEs didn’t exist since last year, I’d say this is not core to the definition of IDE.

I’d go easy with the recommendation to couple components loosely. If you make things that belong together loosely coupled, you’ve created obfuscation, and added complexity to your codebase. Loose coupling makes sense, but not everywhere.

And it will “surely” be assisisting a genocide should Trump be elected. He never hid it or denied it.

Even if that was true, how is that better than having fascism today, given than genocide will happen no matter what? You seem to imply people will have more willingness to resist if it happens tomorrow (and I doubt it). But are you really willing to take the chance on actual fascism? It really seems like you want it to happen…

You guys have a twisted sense of priorities. You’re willing to trade a maybe for a surely.

It really seems like my options are Fascist Now Party or Fascist Later Party. If the Democrats don’t listen when I vote and don’t listen when I abstain, why should I vote?

The answer is in your question. Fascism later is the better option because it buys you time to do something else. Fascism now means the game is over today. Nothing about that is difficult to understand.

You’ll have ample time (and freedom) to oppose Harris after November, but now’s not the time.

If higher-ups complain about intempestive code refactoring, it’s always a good idea to stop for a moment and to start becoming less trigger-happy with refactors. It’s OK to take some time to determine what actual value refactors bring to the project in tangible terms - intuition is not enough. Convincing a critical manager is a good start, because their tolerance for programmer bullshit is low if they don’t actually write code.

Very often, and this is especially prevalent among junior programmers who care about what they do, the reasoning for refactoring turns out to be something along the lines of “I don’t like this” or “I read some cool blog article saying things should be done that way”, without any care about whether or not the change in question is actually improving anything, or, if it does, if the improvement is worth the degradation in terms of quality (new bugs)/maintainability (added genericity making the code more difficult to understand, cryptic features of the language being used that make it hard to understand what’s going on, I’m sure there’s other examples…)

The problem is you often get in cases where the developer cannot back their intuition that something is actually harmful with facts. When it’s not just pure bikeshedding about code they don’t like and falsely claim to be a ticking timebomb, they fail to weigh the risks of leaving slightly offputting code in the codebase against the risks associated with significant code changes in general, which, even with tests, will still inevitably break.

Developers of all sorts tend to vastly overestimate how dangerous a piece of code may be.

To be clear, while I’ve seen it with other developers, I’m still guilty of this myself to this day. I’m not saying I’m any better than anybody.

It’s just that I’ve seen how disruptive refactoring can be, and, while it is often necessary, I thought it would be important to mention that I think it should be done with care.

If you can convince a manager with rational arguments in terms of product quality, it can be a good way to make the case for a refactor, because your manager probably won’t be impressed by arguments about unimportant nuances we developers obsess about.

Async is weird, and the generics salad stuff is clunky.

Just my gut feeling as well.

Dude. That’s Bambi 😬

At the end of the day, it’s a bit like a good editor setup. Sure, your crazy neovim skills might save you a minute or two here and there. But I’ve met excellent programmers that can code in anything, and be just as efficient as the Neovim nerds.

Programming is not just about writing code, you spend a lot of time thinking about it, which is a huge part of the work.

Oh sweet irony… I remember butting heads with techbros on this very platform about their misguided intuition that people criticizing LLMs were going to be left out (assuming I or others had never tried them).

Yeah, I write enough bugs on my own, I’ll pass on the 41% more, thank you very much.

Sure, I know this study needs to be replicated and should not be considered to be a holy truth… But the issues with the tech do pile up, and they’re not just ethical concerns about resource usage. There’s a new study like this one every week.

Yeah, you might not be applying to the same jobs a random stranger on the Internet is applying to. Fair assumption.

Now that this is out of the way, I do also have a family to feed, and am employed. I’ve never not had a job since I left school (and before that, too). But the job searching experience is unnecessarily soul-crushing, because some people in the recruitement chain aren’t displaying the level of professionalism they expect new hires to show. These people are scum, and I’ve had more luck recently sidestepping them outright (they were pissed, and I don’t care). I landed my current gig because I knew someone that helped me bypass all the bullshit, and talk to the real adults in the room directly.

HR drones are really demanding, and it’s fair to be demanding in return. They don’t get to treat people like shit and get respect just because some people are desperate.

I’m not telling you what to believe or how to behave. You’re entitled to your opinion.

Exactly what I was about to reply. Try copying a crazy multi-column Word document into text, and you’ll get similar results.

Copy-pasting parts of your PDF document is not any more difficult than doing the same thing for a Word document.

We don’t care, it’s their job. I get that they’re busy, but it’s their problem, not mine. No excuses for these scumbags.

You can extract text from PDFs without using OCR, they aren’t all images embedded in a file.

I’m sure you’ve opened PDF documents before and selected text in it, or searched for something. That works because the text is embedded in the document, I’m sure.

You can also create PDF documents with the text converted as images, but those are usually larger in size.

Oh, I understand. You’re trying to make people Google online pornography of Putin, by inventing a story around the Web’s famous rule number 34. Very clever!

Don’t feed the troll. This one is obvious.

I had to switch recently because I wanted to try out font ligatures and it turns out Alacritty refuse to implement support for that 😬

Bubbles joined the chat.