Oscar Luis Jiménez

nickname: nai 🐱
Person who loves solve complex things in a simple way :)

[Oscar Luis Jiménez @oljimenez]

@tannerlinsley @AnuragShar74342 Does Tanstack have islands like, for example RSC first?

[Oscar Luis Jiménez @oljimenez]

@dillon_mulroy Also model based testing using state machines.

[Oscar Luis Jiménez @oljimenez]

@FabianHiller @RyanCarniato I think it's better to ask the React team why they think React doesn't need Signals.

I'm on with the React team, I don't think React needs it.

@rickyfm

[Oscar Luis Jiménez @oljimenez]

@FabianHiller @reactjs Why would React need Signals?

[Oscar Luis Jiménez @oljimenez]

@mattpocockuk Also long skills in md are harder to test, so you should always avoid it.

If you need long workflows with logic and real conditionals i think you should move that to a state machine 200%.

[Oscar Luis Jiménez @oljimenez]

@cnakazawa @rickyfm @amadeus @fat Goat 🐐

[Oscar Luis Jiménez @oljimenez]

@mattpocockuk @hhg2288 But that won't make skills like a little useless?

Why not use commands (because they aren't opt in by the agent, only humans can call them) + rules for forcing the agent to follow the codebase patterns.

I don't understand why I should let my agent opt in a skill.

[Devon Govett @devongovett]

Creating your own slop forks of battle tested libraries to make them smaller is a great way to introduce subtle bugs for edge cases you didn’t know you had, create accessibility issues you didn’t know to look for, security problems, etc. The reason we use libraries has never been just to avoid the cost of writing the code ourselves. It’s to start from a baseline level of quality instead of discovering all those edge cases in production.

[Oscar Luis Jiménez @oljimenez]

@jarredsumner @tanavtwt How bun achieve adding more features without increasing size?

[Oscar Luis Jiménez @oljimenez]

@mattpocockuk Yeah, but using dev containers + /sandbox https://t.co/oFmxeNt6UA should make it secure enough.

This way we can use subscription instead of the API key.

What am I missing?

[Oscar Luis Jiménez @oljimenez]

@mattpocockuk i really love all your work with skills and sandcastle. And most important remember developers that fundamentals and architecture are still important.

One question though:

Why build sandcastle instead of using native CC sandbox features?

[Oscar Luis Jiménez @oljimenez]

@anthonysheww goat

[Oscar Luis Jiménez @oljimenez]

@webdevcody The tool doesn't matter that much when comparing codex to claude, there are many reasons why it works on one and not the other.

Improve your workflow and it will work on both.

[Oscar Luis Jiménez @oljimenez]

@fortysevenfx @aurorascharff @valentinprgnd @nextjs @tan_stack @timneutkens any plan on adding this to Next.js devtools itself?

[François Best @fortysevenfx]

Remember @aurorascharff's RSC / "use client" boundary visualiser ?

@valentinprgnd packaged it for @nextjs, with @tan_stack support coming soon 👀

https://t.co/f4Y5pHaIvV

[Oscar Luis Jiménez @oljimenez]

@mattpocockuk It looks really good i will give it a try.

One question, do you commit CONTEXT.md and adrs.md to the repo? Or are these only for the local context?

[Oscar Luis Jiménez @oljimenez]

@FabianHiller I'm implementing a lot of server focused apps.

Using Context first APIs is the better approach because it can lead to using more of the Donut pattern, so we can reduce hydration cost because we can make more components server components.

[Oscar Luis Jiménez @oljimenez]

@FabianHiller Yeah, i will try first to implement my context hook abstraction of Formisch first.

But in my current experience i have with this kind of libraries, when using Context + Signal + React Compiler it starts to have rerenders problems.

Even that i will try Formisch :).

[Oscar Luis Jiménez @oljimenez]

@crutchcorn @FabianHiller Thanks, i will checkout again and tell you if I find something.

[Oscar Luis Jiménez @oljimenez]

@crutchcorn @FabianHiller When using Context patterns?