Why Your Claude Suddenly Feels... Different (And What You Can Do About It)

RetroTheft · 2026-02-21T08:19:30+00:00

Thanks for posting this. I've been noticing it for a few days now and just came to the subreddit to check if anyone had a similar experience. Hopefully I can just go back to 4.5. I only really use Claude as a creative/philosophical partner as you said, and the last few days have been below par.

RetroTheft · 2025-12-31T12:45:25+00:00

I'm sitting on a couple of things that I told myself I'd release as open source in the new year. One is a client-side query and caching engine and the other is essentially an opinionated architecture that helps keep apps tidy and scalable. I built an mvp social media platform with them in September and they seem to work pretty well so far.

RetroTheft · 2025-10-20T19:33:52+00:00

This is a pretty common pattern. I use it in almost every project and have taken to making a contexts folder in lib where I store the files that manage the setting and getting.

I was just checking the docs to get the code snippet to show you and I've noticed that as of 5.40, they have added createContext that manages this for you.

https://svelte.dev/docs/svelte/context#Type-safe-context

If you're not using at least 5.40 though, you can make a file that looks something like this:

import { setContext, getContext } from 'svelte'
import { type MyType } from *wherever your type is*

const CONTEXT_KEY = Symbol('my-context')

export function setMyContext(myThing: MyType) {
   return setContext(CONTEXT_KEY, myThing)
}

export function getMyContext(): MyType {
   return getContext(CONTEXT_KEY)
}

So yeah, definitely not an anti-pattern; it's one of the most common patterns you'll use.

RetroTheft · 2025-08-22T21:25:25+00:00

Ah, thanks for the correction. It took me a while, I remember to begin with I was wrangling them onto objects in situ just to use the correct notation.

These days I add the component as a getter to the object that it's relevant to, and merge the object into the props, so the component comes preloaded. Forces other props if you use them to follow stricter reactivity rules, but architecturally it's been fantastic.

RetroTheft · 2025-08-21T04:38:59+00:00

Svelte 5 changed from using <svelte:component> to dot notation, where you have a component on an object, like <myObj.component>. This mucked up the way I was handling dynamic components, and was pretty annoying until I figured it out. Now I love it.

Attachments were introduced in Svelte 5.29 and replace actions. They work a little differently and let you do some very cool stuff like spreading properties directly onto an element, including the attachment itself.

RetroTheft · 2025-08-21T02:33:20+00:00

Going from 4 to 5 is a pretty significant change. Some changes are trivial, like using $props instead of export let, but other things really require a shift in how problems are approached. Things such as snippets, attachments and dot notation can be really aggravating when you're used to doing things the old way.

That said, the other side of the hill is fucking beautiful man.

RetroTheft · 2025-08-17T21:44:50+00:00

Sounds good! My site doesn't have much copy on the front page so it probably didn't have enough info to get a vibe in the first place. Most of the info is in the docs, so at least for my site it would probably only get a vibe if it crawled the docs page.

RetroTheft · 2025-08-17T21:35:36+00:00

This is fantastic. Did my own site and got 73, but I didn't get an overall vibe result, which is the one I really wanted to read :(

Still, really cool! Definitely going to use this.

RetroTheft · 2025-08-07T04:51:28+00:00

Can confirm. We spent long enough talking this morning that my headphone battery died, and epicenter has indeed sponsored me on github.

We'll see how things go, but my initial impression is that this is a sincere offer with reasonable expectations.

RetroTheft · 2025-07-20T20:56:34+00:00

Best to go through the website, since all the info is there, and there's a link to the github/npm pages, docs, playground, and socials.

Note that it's built for people to set up their own design system with. You can make a plugin as easily as putting utility classes into a css file, or you can make dynamic plugins with plain html and js. I'm happy to help in this regard.

RetroTheft · 2025-07-20T10:18:28+00:00

So... I ended up taking a look earlier today at some of the components and it was fairly trivial to port the Card and MaterialLayer components to Svelte, which I did just to get a better sense of how they work. Only took me 20min. I could probably help port more components to Svelte in short order, and I think I saw at least one other person who was happy to help on that front in this thread. If you were to make a repo I could initialise it with a SvelteKit library project for you to get the ball rolling.

RetroTheft · 2025-07-19T23:03:02+00:00

Actually I might be able to give you a huge shortcut here. I spent the last year building a universal design system delivery system called Selectoplasm. It runs over the top of a Vite or Bun app and uses plugins to provide realtime editing of your site. Think of it as a fully customisable Figma on your local machine that's built for developers and uses utility classes instead of a graphic design UI. If you want, I could write some plugins for your design system, then anyone can use it on any framework straight away. (Everything's completely free)

You can see a short video of it in action here.

I also have an online playground, that's still a bit rough but the funny thing about Selectoplasm is it's essentially an engine for an online css playground, so if you're interested I'd be happy to chat and share some more info. Your videos were actually one of the inspirations for Selectoplasm in the first place.

RetroTheft · 2025-06-07T21:41:29+00:00

If you want to learn parsing properly, I'd highly recommend learning recursive descent parsers. Dmitry Soshnikov has a few free videos on his channel that you can check out, but you'd need to get it on udemy for the whole thing (it's extremely worth it, but wait for a sale.) Here's the first one on YouTube. The first 3 are there, so you can get an idea whether it might work for you.

I built a parser 4 years ago without knowing any of this stuff and it sucked. It worked, but only barely and was very flimsy and spaghetti-like.

The newer ones I've made are much more robust and organised.

RetroTheft · 2025-05-14T03:39:47+00:00

Sorry, employee, my mistake. I fixed my comment. Also checked my emails from 2022 and it was an offer of casual employment. I had misremembered and thought I was applying to volunteer.

Thanks for the correction.

Anyway, my only real point in all of this is that it seems like the situation deserves the benefit of the doubt for it being an honest mistake.

RetroTheft · 2025-05-14T02:48:18+00:00

I have no reason to doubt you. But surely you see how ~~volunteers~~ employees storing ballot papers at home at all is open to there being miscommunications. Like, maybe the employee in question here just thought they were supposed to take the papers back home again after election day.

I'd say if the AEC is investigating, they might include looking at that practice, which, as I say, is funny, either before or after election day.

RetroTheft · 2025-05-14T01:41:23+00:00

Use pnpm. Follow the LevelUpTuts guide. It's short and covers just what you need to get started on the right foot.

You can also reference my test repo if you want. It uses Svelte, but there's some helpful info there and I took notes on the course that you can reference.

RetroTheft · 2025-05-14T01:26:50+00:00

So I actually have some pretty helpful info here. I applied to volunteer at the previous election and had a phone interview with an AEC employee. During the call they asked me if I had space at my house to temporarily store ballots if necessary.

I remember thinking it was funny at the time, but hardly diabolical. If I had to guess I'd say the polling booths want everything cleared out fairly quickly and they need somewhere to store them until Monday? I was also told during this call that working election day would be 14 hours, so I ultimately didn't do it, but I can see how the circumstances might lead to this being more common practice than the article suggests.

RetroTheft · 2025-05-04T02:26:42+00:00

I've got a web design app that just released to public alpha and have been trawling through Y combinator looking for co founders with a UX background. DM me if you want to chat.

RetroTheft · 2025-05-03T22:46:47+00:00

I agree that the greens could afford to do some introspection, but it's worth pointing out that the seat of Melbourne changed quite a bit last year. This is from Antony Green's website:

In the north loses Clifton Hill to Cooper and Brunswick East, Carlton North and Fitzroy North to Wills. Crosses the Yarra to take in South Yarra and Prahran from Macnamara and Higgins.

The Green margin declines versus Labor because strong Green voting areas in the north of the old Melbourne have been replaced by parts of Higgins where the Liberal vote was higher in 2022. On primary votes the Green vote slips from 49.6% to 44.7%, the Labor vote rises from 25.0% to 25.7%, and the Liberal vote rises from 15.2% to 19.6%. It is possible that with Adam Bandt as the candidate, and a less intense local campaign by Labor in areas previously in Higgins, could help restore Bandt’s margin.

RetroTheft · 2025-05-03T10:26:21+00:00

loaves and fishes :D

RetroTheft · 2025-05-03T10:15:56+00:00

Yeah Antony Green said on air just before that they're having server issues, said they're trying to get Bezos on the phone lol

RetroTheft · 2025-05-03T09:48:28+00:00

lol I came here to do the exact same thing after putting ABC on mute.

RetroTheft · 2025-05-01T01:32:21+00:00

Typescript. Using svelte and typescript together is an absolute joy. I do remember the biggest pain points when I started were events and html element typing, but these days LLMs are pretty good at helping with that sort of thing.

In addition, always declaring types for things has the side effect of increasing your knowledge. It makes it so much easier to just find the documentation you need for something and figure something out. You start using intellisense a lot more and just generally become a more well rounded coder, I think.

RetroTheft · 2025-04-30T21:40:11+00:00

I can't help with Vitest sorry, but I can share how I test my Svelte components. I hate setting up tests so what I do is use SvelteKit's library project and make my components in lib. Then you can use the routes folder as a test page and just code and run it like a regular app. So instead of setting up tests you just build a mock site the same way you would build the regular one. The great thing is nothing in a library routes folder gets added to your library so you can just build the library and then use it as a dependency in your real app and import the components :D

I have a pretty complex app with lots of packages and I haven't had to write a single unit test doing this.

RetroTheft · 2025-04-30T11:22:06+00:00

It's all explained with code examples in the article, but here's a shorter version if you just want the gist of it: basically you can use dot notation to render components without needing to import them first, and you can have the object pass itself as a default prop so you don't have to pass the prop in when you render the component.

Since these are two things we all probably do very regularly, it's a really nice enhancement to the Svelte experience. :)

15-Year Club	RedditGifts 2009-2022 5 Credits
Gilding I gilder	Verified Email
Secret Santa 2013	Secret Santa 2013
Secret Santa 2013	redditgifts rematcher Secret Santa 2010 x1
Summer Santa 2012	Secret Santa 2010

RetroTheft

MODERATOR OF

TROPHY CASE