Right. Given the option I will always choose to work with a decent programmer who can communicate well and documents their code, over a very strong programmer that doesn’t think they should waste time with documentation

As long as “cleaner than you found it” also includes “better documented.” I’ve worked with people who think that “the code should speak for itself” to the point that they will make biased decisions with no explanation or documentation and then if you ask them about it after their response is “look at the PR for how that decision was made.” I’m not going to git blame and find your PR to find an outcome from an argument between two people that after scrolling just says “sometimes the API returns a JSON string here instead of nested JSON so we have this conditional” when that could be a comment

I mean, it depends on how pure your ketamine is

It’s generally become my opinion that unless I’m eating unsweetened muesli with a splash of milk pretty much every cereal except unsweetened cheerios is bad for me

LOL to your family 😂😂😂

I think MS like other big tech companies has started to run out of “senior” positions without paying more so many people just end up as “senior” principal engineers which is basically “this is as far as you can go if you don’t want to get involved in management”

Yeah that sounds way more enjoyable, but first you need the 250k and up salary that a principal engineer at MS makes for 20 years, then you have plenty of equity to focus on whatever your hobby is

DRAGULA

Then volunteer to phone bank for someone in a swing state where a vote may make the difference, and write other representatives. It’s not illegal to tell other reps that you feel under-represented and the issues you are concerned about

If only cyber trucks had a little red button

Well, any game that basically releases the same game with changed rosters every year with only minor improvements, or COD would work too

North Korea, you know folks say, folks say, oh North Korea, but let me tell you folks Kim is lovely, and he’s a big fan so we love him. And people are saying North Korea, folks let me tell you, let me just say, the North Korean people are lovely. Beautiful country, nobody even needs to vote folks, how nice is that

In many ways you’re correct, the “modern” js toolkit can be a nightmare. I work for a SaaS company that makes emergency management software. I’m pretty proud of our setup. It’s Vue 3, it’s incredibly optimized. We have tree shaking and code splitting, e.g. there’s hundreds of potential JS files you might load using our software, but they will only load when you need them, over a brotli compressed HTTP/2 connection so it really is efficient.

With the amount of data we process through our API and how it’s presented to the client it would be a nightmare to not have Vue for state management and routing, axios for API calls, etc. But many SaaS products certainly aren’t optimized like ours

Many of the things that jQuery made easy back in the day are now pretty easy with pure js (Ajax calls, improved selectors, programmatic DOM manipulation, etc), and browser support for most JS features is way more standardized.

Granted, your pure JS is likely to be way more verbose to write, making it look more intimidating than jQuery.

That being said. jQuery is performant in modern browsers, and when being delivered compressed and minified is tiny, so if you want to use it, go for it. Anybody who criticizes you or tells you “you should use [x]” for your online store or website is a JS elitist.

jQuery is really only a “bad” choice for big interactive web apps, where frameworks that handle state and routing independently of the DOM are a much better choice.

Username checks out

Star Wars?

We landed on the moon!

https://www.youtube.com/watch?v=X9FGRkqUdf8