Ty Terdan

This week I shipped two micro-frontends from prototype to production as part of Upwork's platform decomposition into composable smart surfaces. The job search browser went from zero to merged with real pagination, sidebar filtering, accessible scroll-to-top, and reactive search state. The membership manager was the heavier lift: 4 parallel GraphQL queries with graceful degradation, a full API transform layer normalizing raw schema into clean store state, reworked modals, alerts, tracking, and i18n — roughly 1,750 lines across 36 files. Both run as independent SPAs injected into the platform shell, each with its own Pinia store, error boundaries, and analytics instrumentation. What I keep learning at this scale is that the hard part isn't building the feature — it's designing the boundary. Where does the microapp end and the shell begin? Which queries are critical enough to block render, and which degrade silently? How do you instrument analytics without coupling to the host? These are the decisions that determine whether a micro-frontend architecture actually scales or just moves the monolith into smaller boxes.

3

It feels so weird that just a few years ago I was in debates about whether or not to start adopting typescript, and now I’m in debates about how much permission we should give to our autonomous code robots. Life does come at you fast.

13

2 Comments

A small real-world problem: my son had 200+ Roblox friends, and Roblox doesn’t offer a bulk removal option. My latest blog post walks through a simple, browser-based approach using dev tools and JavaScript. Nothing fancy - just practical, repeatable steps for anyone who hasn’t done this sort of thing before. 🔗 https://lnkd.in/gQhsUCdW #webdev #parenting #javascript #automation

18

You might have a functional website, but that doesn't mean it works. Today I learned about a unique California alert system and went to the CHP website to discover more about it. Only I didn't Instead I got a big old no response in my browser. Confused I double checked the availability of the website and quickly confirmed that there was something there that triggered my DNS level ad filtering. This isn't surprising as I maintain a lot of rules and prefer more blocking to less, but I was certain this had to be a mistake likely triggered by a bad filter. Turns out I was wrong, the filter was in fact working correctly, only the CHP seems to have chosen a specific hoster that has a reputation for being a source of trackers. Feel how you will about their choice of hoster, but there's an interesting problem here. What's the right way to solve picking a bad host? While lifting and migrating to a new hoster is definitely an option, what's the likelihood it will happen? Until then the CHP website is down for anyone who uses the Peter Lowe adlist and if they are non technical there's essentially no solution for them. Problems like this aren't going to go away and everyone should be taking notice. California is in a very good spot and they should be taking note. Ironically California has already made some AMAZING plays that lay the ground work for this. Californians stop screaming, this might be one of the only compliments ever given to your state government. In 2023 California announced their intention to partner with a generic medicine manufacturer to produce insulin for 10 years. 3 years later they were shipping insulin to the market with copays 1/10th of the federally maintained copay. The program has been a resounding success. How can I say this so surely? I'm a type 1 diabetic and the production of Californian insulin has created one of the only markets in the USA where a Type 1 can actually have a hope at the pharmacy. California is also the only state in the Union now that has a chance of negotiating with ANY insulin producer (it's not easy to negotiate when playing hardball kills the people you are fighting for). The model from 2023 should be at play in states like California (or Washington), or any state looking to gain an economic advantage into the future. States need to build their own cloud competitor.

Anyone can create software now. This is incredible. The barrier to entry has collapsed. Ideas are coming to life faster than ever. But there is still a missing step between something that works and something that is production ready. Getting across that gap requires a different mindset. It also requires a different language when prompting and structuring AI assisted workflows. How you ask matters. How you organize the work matters. To help bridge that gap, Avrum Laurie, Tucker Schreiber, and I are building → https://lnkd.in/ebmFQ24Y Builder Patterns is a curated collection of resources designed to help builders get production grade results from AI assisted coding. These are patterns we actually use when building real systems in production. The goal is simple: Build an open library of Builder Patterns. For now this includes prompts, language patterns that improve output, visual style references, developer terminology, and other practical resources. Over time we will expand this further with skills, hooks, and even full SaaS level prompts. If you're building with AI, we'd love your feedback and ideas. We'll be launching a contribution model soon as well.

35

3 Comments

Anthropic released Claude 4.6 to their mid-tier Sonnet model after Opus. Be prepared to frequently hear these assertions: - EVERYTHING has changed!!! - Anyone using a prior model doesn't know what they're talking about. - Your experience is invalid because 4.6 is exponentially better than 4.5.

5

1 Comment

What does a Build team do, exactly? I wrote my first ever blog post to try to answer that question: https://lnkd.in/gXV4Cn5S

19

1 Comment