Where? I feel Google has gone way downhill but the Bing based search engines haven’t seemed any better.

Why was this written like this? It makes no sense. I’ll git blame it and ask them what’s going on. Oh it’s me…

I just peeked at the docs and right off the bat I don’t like how they have conflicting attributes like hx-get and hx-post. What happens if both are set at the same time? Why not just have hx-method?

It will be questioned, but you have a good explanation. The tricky part is explaining it elegantly. Hiring managers kinda glance at resumes so you should add a sentence at the end explaining that you were let off due to internal company reasons. You should also try and get a letter from the company explaining that it wasn’t for performance reasons. Even better would be to get letters of recommendation from your coworkers and manager. Hopefully they’ll be extra nice to you due to your situation, but you need to be proactive about it.

By the end of the meeting you have 10 more questions and no answers and more meetings to discuss the new questions

But they’re both Walt Disney, so does this say that he did character voices while masturbating?

I think you’re misunderstanding what I mean. Early Access is a newer term for getting paid access to a game early. Open beta is an older term but was used for free access to a game early for testing purposes. They used to have different meanings which is why early access was created as a new term to distinguish it from a beta. Calling paid early access a beta is intentionally misleading.

In that case you will love typescript. I’m not sure what other imperative languages have both type inference and structural typing.

My opinion is you should use it when it’s useful, but not when it’s unnecessary. Their main use case is when you need to couple the functionality of functions to a shared state, and it’s particularly useful when you have multiple interdependent functions that need to be tied to multiple codependent states.

I find it relatively rare when I really need to use a class. Between first class functions and closures and modules and other features, I find JavaScript has a lot of tools to avoid needing classes. Classes add complexity so I only use them when the complexity they add is less than the complexity of the task they’re needed for.

It used to be called early access. At least it wasn’t a misleading term.

Agreed. I’m not defending phones in class, just pointing out that there’s more work that can be done with lesson plans as well.

I fully support kicking kids off their phones in class, I don’t think any lesson no matter how engaging can compete with that. I’m not supposed to be on my phone during meetings, I think it’s perfectly reasonable to ban phones from class. I was just commenting that work can be done to make lessons more engaging when phones aren’t involved. There’s of course a limit to what you can do, and some subjects are just inherently harder to get kids into, like statistics. But seriously good on you for doing that. I’m sure that while it didn’t have perfect engagement, it was far better than just teaching it to the book.

Just curious, is there a place you can share that lesson plan to other teachers? It’d be a shame for all that work you did to not get to be used in other classrooms as well.

You can increase motivation to learn by making lessons more engaging even if it’s a subject they’re not personally interested in. But making lessons more interesting and engaging is not easy and we can’t expect all teachers to have the skills and resources to do the research and development needed to produce lesson plans that are really interesting. I think it could be improved by putting more money into developing interesting lesson plans centrally and distributing the materials to teachers to follow instead of just producing dry curriculums. Teachers need support.

Have you people never heard of a phone book? Phone numbers aren’t sensitive information. If they want to scrape your phone number they can legally and trivially do so through public data sources. Google does plenty of sketchy things around privacy, but this isn’t one of them, it’s just about security.

Like many shitty things in the world it appears to be incited by Russians https://www.google.com/amp/s/amp.theguardian.com/world/2023/jan/27/burning-of-quran-in-stockholm-funded-by-journalist-with-kremlin-ties-sweden-nato-russia

Hear me out, a good portion of Reddit posts are reposts anyways so what if we did a one time import of Reddit community top posts of all time to seed communities so there’s a place people feel more encouraged to post to? I don’t like bot posts generally, but if it’s a one time thing I think I’d like it if the communities here had some extra seed content to browse so you wouldn’t reach the end so quickly like you do now.

Also helps to come out with a game so popular you can bank on it for the next decade

After experiencing ad hoc inline scripts, frameworkless jQuery spaghetti code, inflexible monoliths like angular, and overly simplistic micro frameworks like backbone, I’m super happy with where we’re at with react and react like frameworks. I really do feel like we’ve hit the sweet spot between power, simplicity, flexibility, and ease of use which is why I’m confident that things aren’t going to be as volatile as the past. React is already 10 years old now and still going strong with no new trends looking to usurp it. I think those old trends were necessary experiments to get to where we are now, and I think the old meme of web dev changing every week is no longer true.

I’ve had a good time with react SSR and SSG particularly when using next.js which does a great job optimizing out of the box, but really SSR and SSG are functionally just glorified string interpolators so anything will do. What matters is ease of use and with the strong community and toolset available to react I’ve had no trouble setting up react for SSR/SSG.

Where things still need improvement is with hybrid apps that take SSR/SSG pages and hydrate them to be ready for the client to take over, but that’s always been a pain point, and while we’re still not where we need to be I do think it’s better than it’s ever been and we’re on the right track to cracking it.

Maybe it’s because I’ve seen how bad things can get that I’m appreciative of what we have. After experiencing frameworkless jQuery spaghetti code, overly complicated monoliths like angular, and overly simplified micro frameworks like backbone, I’m really happy with the frameworks and toolsets we have now, and react’s ecosystem is very mature.

I would say that react is overkill for SSR, but pure SSR is pretty simple so react is also able to handle it just fine and elegantly as react is even easier to use when you’re not dealing with dynamic state, and if you find the need to introduce some hybrid client side functionally, which pretty much always happens eventually, it’s a good thing to be on react.

Here’s my hot take as a dev who’s been making websites since before JavaScript and css were invented: modern web development is leaps and bounds better than how it was and the rapidly changing best practices had a big part for how we got there in the time we did. I think the industry is in a great place now and now that it is things have slowed down and the focus is now on stability rather than changing development patterns.