Ethan

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.

How is that relevant to “That’s on you for using Java”?

It sounds like you already know how to do embedded programming, at least at the hobby level. For someone who’s new to that, Arduino IDE is the easiest learning curve I know of. As far as which boards to use, I have no specific feelings which is why I said Arduino or equivalent.

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.

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.

There’s no difference between SSA and ASS in that context so it’s pointless to punish a student for that

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

Really? Huh, TIL. I guess I’ve just never run into a situation where that was the bottleneck.

It’s safe to assume that any non-trivial program written in Go is multithreaded

I have to strongly disagree with you. I’ve used WSL 2 with VSCode, and I experienced waaaaaaaay more weird broken shit than I ever have running Linux. And even if it weren’t for that, it’s still not at all worth it IMO because using WSL 2 means every interaction I have with my development environment has to go through a Linux-to-Windows translation layer. I will never use Windows again for anything beyond testing unless I’m forced to.