crackinmalackin

The front end is not less risky to hand to the agent. There are a thousand different ways the agent could bork the UI and say it's good. And knowing how to babysit the AI/Agents doing the UI is more important than ever. Yeah I agree that developer education in the front end space seems to be diminishing, but let's not pretend like non of that matters anymore.

Absolutely. News like this is so hard to ignore. Nervous as hell to drop big money on things the family needs right now. Grateful to have a job, but life overall was just better in almost every sense before AI became part of our daily vocabulary and layoffs occurring every couple of weeks.

Awesome work getting this updated with Svelte 5!

Worms Armageddon. Enough randomness to maintain replayability. Deep strategy elements for those players dedicated enough.

I know it's not a apples to apples comparison, but the same parent company nonetheless. Not a good look after closing the deal on 69 billion for activision blizzard. Couldn't have set aside one of those billions to keep people employed a while longer MSFT?

I see these changes as net positive in the long run. Especially since it sounds like performance is getting a boost as well. The $props rune isn't something I realized I needed, but it definitely clears up code clarity. The $effect runes makes people think we are going down the React useEffect route... but I didn't see a dependency array attached there waiting to obliterate performance? I'm all for removing a tiny piece of Svelte magic to improve code clarity and performance gains. Seems like a big win to me. Thanks Rich and team!

I don't see how it can hurt adoption? Svelte/Sveltekit are already stable. This is simply an update from the Svelte team about how performance is getting even better. If anything, this inspires confidence from me about how the team is constantly looking to improve the product. Svelte 3 to Svelte 4 was pretty much a painless transition too.

A lot of panic in here about how people think this is a Angular v1 to v2 transition all over again. Svelte version updates are largely behind the scenes so there's really not much to upgrade if your app is already built in Sveltekit.

People who haven't tried Svelte/Sveltekit yet are seriously missing out. It's a breath of fresh air in today's UI landscape. The constant performance gains are the cherry on top.

Love this! Thanks for sharing

Location: Salt Lake City, UT

Remote: Yes, or onsite if in UT

Willing to relocate: No,

Technologies: JavaScript/TypeScript, HTML/CSS, React, Svelte, Angular, Node.js, Deno, MongoDB

Resume/CV: Available on request

Website: zbar.dev

Email: zneibaur [at] gmail.com

Hello everyone, hoping to make a few connections here. I'm a software engineer with 6+ years of highly focused work on UI and Front End related projects. React.js is my main UI framework currently, but have used Svelte and would love to more work in that area. I've also dabbled in some Back End technologies and I aspire to do more full stack eventually. Ideally looking for full time roles only, no contracts at this point. Thank you!

I'm also looking for a frontend position. I don't see it listed on the hiring page though.

I've had a M1 mac mini for about a year now. It's been a really great machine, dead silent (never heard the fan), super fast and responsive. No complaints really, software mostly seems to have caught up to the new architecture. I do most of my work in JS/TS, React, etc. Don't know if I'd buy a M1 mac mini right now though, feels like a M2 refresh is due soon.

People grind leetcode problems for weeks or months ahead of time though.

Most take assignments are throwaway code, but once in a while they are things you can add to a portfolio and expand on. Also if you finish and need to reaapply to another position you’re already done.

Definitely a time consuming practice, but i like knowing what I’m getting into versus the mystery of leetcode. Short and sweet is the key though. Someone else mentioned live pair coding on some revelant feature , I think those are ideal

100% agree on the 1 hour maximum live challenge. As long as the challenge is relevant to the role being applied for, this is the way to go. This is enough time for the company to see some code and for both parties to ask questions about the tech, role, etc.

That hiring process doesn't sound too bad to me. I know some people are iffy on the take home portion though. I'm looking for work at the moment, 5+ years as a Frontend web dev. React.js, Typescript and lot's of good CSS skills if anyone is in need send me a message.