_jesse

I think they realized that a large portion of their community would have just gone elsewhere if they didn't. I was not impressed with how they handled the initial criticism--after they backpedaled after realizing that deprecating basically the entire current api wasn't popular (surprising... lol), they then started saying they never intended to deprecate it. It was strange.

I'm still not a huge fan of the composition api. It's like a weird version of React function components with different quirks. Maybe I just need to use them more and I'll eventually get it.

I think it's because the people that like tailwind really like tailwind, and they will take any opportunity to tell you how amazing it is. The evangelism gets really old after a while.

I also thought it was going to be for publishing writings online. They're reusing the lingo from storybook, which is going to be familiar to a lot of people in the frontend space these days.

It does look like a great tool, I would definitely give it a try first before going to storybook.

You can dynamically import using import(): https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe.... Works basically the same as a static import, just returns a promise that resolves with the module that you're importing.

I think it's easier to get away with not having someone who specializes in front end and so a lot of companies just don't prioritize it. I think a lot of them also don't realize how much they're missing either, but I'm maybe a little biased because I specialize in front end, haha. I do think that this is a contributing factor to why so many websites and web apps work and run so poorly.

Nope, hate sprints. Continuous planning works much better in my experience because it is _actually_ agile. It lets you constantly reset what your current priorities are. It lets you plan out projects and think about the projects and what it's going to take to get them over the finish line, without the constraint of "well, what do we think will fit into the next two weeks"? Also, sprints totally strip autonomy from engineers, I don't know why anyone would argue that they give engineers more autonomy.

Honestly, I just really hate the arbitrary timebox and all the problems it brings. You totally don't need sprints to do anything that's a part of the scrum process. Want to be more introspective as a team? Schedule a meeting every few weeks to talk about problems you're facing as a team and how to solve them. Want to plan out your work in advance? Cool, do that for every project you're going to be tackling.

It's not moving as fast as CSS has been, but they have been adding new elements to HTML. <summary> and <details> for accordions, <dialog> for modals, and I've heard murmurs of a <selectmenu> element that does everything <select> does while allowing the developer full control over the look.

When did this change? I interviewed in fall 2021 and got a decent offer but ultimately took a higher offer elsewhere.