Etienne

@etienneburdet.com

173 Followers 738 Following

Dev, Snowboarding, Parenting & Tea 😱

Les calculs sont pas bons Kevin !
Mistral vibe code session where LLM asks questions about how to perform a task.
Terminal showing command "gh repo claude path/to/repo" and error.
Couverture d'Asterix aux jeux Olympiques
Terminal running zellij, one large pane for coding agent, stacked panes for common project commands, smaller pane bottom right.
Graph with 0% at everything but disruption and privilege blindness
Orchestre et dessin abstrait rouge à la philharmonie de Paris
Une boîte de lentille marquée LR
Kaamelott: c'est systématiquement débile, mais toujours inattendu. Et ça, c'est très important pour la santé du… Du cigare.
Gaiwan with leaves and a packet of Tea Habitat 2013 Lao Xian Weng
Dates drying in a date plam oasis
Claude Code output in the terminal: 1. Legacy vs. Current: .command might be the old naming convention and .skills is the current one, but both are still supported for backwards compatibility 2. Different mechanisms: They could potentially serve slightly different purposes (though from my perspective, I interact with both through the Skill tool)
Code showing use of useTransition in an handleApply callback
.svelte-kit/output/client/_app/immutable/chunks/C87uAaWo.js 22.60 kB │ gzip: 8.84 kB .svelte-kit/output/client/_app/immutable/chunks/BFD65KVX.js 26.20 kB │ gzip: 10.31 kB
file client.ts starts with "use server"
Kyushu, tea cup and a paquet on Tobetto tea.
Gitlab commit showing 4000 lines added and removed over 200 files.
Claude code thinking it found a bug but then realizing nope, and again.
Computer with solid js code, bottle of whiskey from Domaine des Hautes glace, white porcelain cup.
A very basic interface and a second tab with API result.
Friends meme: Phoebe tells Joey that users, companies, and the internet don't care about his frontend framework. Joey only smiles when she mentions Palestinians getting food and land if he switches to HTMX.
quicksort with typed complexity and binarySearch with typed algorithm correctness.
Cons of Moving to Form-Level Autosave ❌ Change Detection Complexity - Form level needs to track which specific fields changed ❌ Performance Risk - Might trigger more frequent saves without granular change tracking ❌ Validation Coordination - Current system elegantly combines validation + autosave per field ❌ React Aria Integration - Your current approach works seamlessly with React Aria components ❌ Loss of Granular Control - Each field currently decides when it has "meaningfully" changed Verdict Your current component-level approach is well-architected. The useLiveForm hook provides excellent abstraction with smart change tracking (hasChanged.current) that prevents unnecessary saves. Moving to form-level would require significant refactoring for marginal benefits, given your React Aria-based architecture already handles this elegantly. Recommendation: Keep the current approach unless you're experiencing specific pain points with the component-level implementation
State of html final board and score
Elon Musk Tweet: You can cut & paste your entire source code file into the query entry box on http://grok.com and @Grok 4 will fix it for you! This is what everyone @xAI does. Works better than Cursor.
Storybook running a test with "expect" and "userEvent"
Snowy mountains