Principal Engineer for Accumulate
When yarn/react/next.js/amplify breaks in some new and idiotic way, Claude is helpful more often than not. Why spend hours googling and sifting through github/stack overflow/etc when Claude can tell me what option to tweak to fix it in a fraction of the time?
Boring, tedious shit that doesn’t require brainpower, just time, when fixing whatever comes out of the LLM is less annoying than doing it myself.
If every possible action is going to piss off a large portion of the user base, doing nothing is the sanest option IMO.
They weren’t looking for universal approval. They were looking for widespread/majority approval.
So you think they should have picked a solution that pissed off a large portion of the user base, just so they could say they “solved” it? The entire problem is that they tried, repeatedly, and none of their proposals had wide support.
How is that relevant to “That’s on you for using Java”?
You need to understand how code actually works. If you’ve only worked with highly abstracted languages like Python, Ruby, JavaScript, etc then you should probably start by learning lower level languages like C or C++. Or maybe Rust and Go but they’re kind of low level and abstracted at the same time. If you already know C/C++ then buy yourself an Arduino (or equivalent) and start screwing around. If you’re in school and interested in this as a career, take some electrical engineering or digital circuit design classes.
It is possible to sign a flatpak, but yeah distributors need to actually do that and flathub should require published flatpaks to be signed.
VSCode is the first development environment I’ve used that doesn’t make me feel like this. It’s not perfect but the base application is rock solid and the full DE experience is the more reliable than any other DE I’ve used.
P.S. I specifically said DE for those people who say VSCode isn’t an IDE. Personally I don’t see the point in differentiating.
P.P.S. Sublime is not a DE in my opinion. It’s an excellent text editor with syntax highlighting. The plugins were an afterthought and it was never intended to provide the full experience. Granted I haven’t used it in years.
There was this one time where I took down the accounting department by accidentally DDOSing the SQL server. MS Dynamics is such a piece of garbage that it will crash if the database takes more than a minute to respond.
I thought you were saying to literally use def main(): pass, that’s why I was confused
What is the point of this?
Saying “front end is not proper software engineering” is bullshit but at the same time if you hire someone to write code and then ask them to write CSS I can understand being frustrated.
I’m not saying it doesn’t happen. This thread started because I said I’ve never understood why people talk like tar is some indecipherable black magic. Common tasks are easy and there’s a man page for everything else.
Literally the only time I’ve ever run into that is when I was trying to manipulate the path it extracted to. In 99% of cases I’m doing tf, xf, or cf plus flags for the compression type, etc, and those differences are irrelevant.
I almost never create a tarball, so I have to look up the syntax for that. Which is as simple as man tar. But as far as extracting it almost couldn’t be easier, tar xf <tarball> and call it a day. Or if you want to list the contents without extracting, tar tf <tarball>. Unless you’re using an ancient version of tar, it will detect and handle whatever compression format you’re using without you having to remember if you need z or J or whatever.
I’ve never understood why people are so intimidated by tar
I thoroughly agree, you should always have CI tools to ensure it builds, passes tests, and meets whatever formatting and/or linting standards the team sets. I was specifically responding to “Rust makes it harder for a ‘contributor’ to sneak in LLM-generated crap”. If I get a contribution from an untrusted party, I will start with the assumption that it’s utter garbage, buggy, broken, and malicious and review it until I’m convinced it’s not. Not because I assume the dev is bad but because it’s safer to assume the code is garbage. If I get a contribution from a trusted party (e.g. a member of the dev team/employee/whatever) I will review the code carefully though not with as much paranoia. I don’t particularly care if my teammates are using LLMs, but if they’re submitting code they don’t understand that’s a great way to get ejected from the “trusted contributors” group, and if they’re an employee it’s a good way to get fired if they keep doing it after being warned not to.
That does sound unpleasant and I can understand why you prefer Windows. Personally, I rarely have problems with Linux that aren’t self inflicted and IMO Windows is an absolute garbage fire of an OS so there’s no way I’d ever daily drive it.
Your options are:
AFAIK there are no other options