brandonmcconnell.com
Find me on 𝕏 @ https://x.com/branmcconnell Software Engineer ⚡️ Crafting some of the most popular Tailwind CSS plugins around. Bugs are my own. Dev-tooling & spec-reading fanatic 💻 #codeinpublic
👤 Joined on 02 June 2023
Followers
Following
Total Posts
@brandonmcconnell.bsky.social@brandonmcconnell.bsky.social → @branmcconnell.bsky.social@branmcconnell.bsky.social → @brandonmcconnell.bsky.social@brandonmcconnell.bsky.social → @brandonmcconnell.comTotally this...this is why I love building slides with @joyofcode.xyz animotion... I get to just write fun super interactive whimsical Svelte components here and there! 🧡
Show PostMy talk for @zurichjs.com was running long during my dry runs, so spent this morning trying to tighten it up. I removed a few demos that didn't really contribute, and in doing that I managed to go from 90 slides to 60 slides. So of course my next dry run was 6 minutes longer than before 😅
Show PostI know it's cutting things a little close to the event, but @farisaziz.com, I'm sure with a little bit of effort you could find a way to give me ~2 hours instead of 30min, right? 🤣
Show Posteven if you're not literally porting the code i think it's good to have a written-down model of each cohesive part of the system. it's just design discipline. but you can also try things "in spec" and see how they affect everything else. like constraints on API design. so that excites me
Show Postyou can also pin it with ports of integration tests that look close to original tests but are actually a Lean DSL that is also just typechecking theorems under the hood. so you get more assurance you're pinning the right objects. and if your code is FP-lite or C-lite, it translates pretty closely
Show Post