This is just one of several places where I tinker with ideas, burn the midnight oil, fix bugs and inadvertently end up creating more of them in the end, but alas… c'est la vie d'un développeur.
| 👔 | I’m currently employed at Carevoyance at Definitive Healthcare. |
| 📚 | I’m currently learning Svelte, SvelteKit, D3, LayerCake, PostGreSQL. |
| 👯 | I’m looking to collaborate on a new idea surrounding git versioning. |
| 🤝 | I’m looking for help maintaining and growing TypedCSS. |
| 👨💻 | Explore some of my tinkering on CodePen. |
| 💬 | Ask me about CSS, SCSS, Tailwind, JavaScript, React, or Svelte. |
| 📫 | You can reach me on Twitter or via email. |
| 📄 | Learn more about my professional experience on LinkedIn or download my resume. |
| ⚡ | When I'm not flushing out lines of code faster than Eminem raps (or occasionally staring at my screen blankly), I enjoy traveling 🏔, photography 📸, playing sports 🏓, hiking 🥾, and spending time with friends and family 👨👩👧👦. |
- Answer by Brandon McConnell for Performance of Array.flat() vs spread operator to flatten multiple arrays into one
- Answer by Brandon McConnell for JavaScript map & find at the same time: findMap?
- Boolean truthiness narrowing not working in Typescript
- Answer by Brandon McConnell for Adding tabindex dynamically
- Prevent merging of branch conditionally based on label
- @nikitabier with so many people getting thousands of dollars in their payouts, i’m pretty confused how this one generated less than $70 👀
- i went from mcp hater to power user. mcp is actually really good now. connecting specialized agents unlocks an absurd amount of capability. everything can control everything. but i can’t help but feel orchestration is still grossly lacking, especially when it comes to mcp use.
- we have: – tools + agents w/ mcp – shared interfaces – cross-app control but no real coordination layer. (more than just agent orchestration) agents don’t share context well. dependencies aren’t understood. work isn’t sequenced intelligently.
- draft a spec and upon approval: – plan created → project + issues – agents per task – shared context across deps – code written – code reviewed + ready for final approval – dashboards spun up – team updates posted end-to-end. no babysitting. seems like the natural next step.
- fantastic read on the state of oss contribution and where It's headed
