Colorado, USA
Joined July 2010
- Tweets10K
- Following692
- Followers10.9K
- Likes5.7K
Same for me now too. Single Rex main thread with instructions to keep the main chat always available by always running tasks in other side worker threads that report back to the main thread.
It's been absolutely *thrilling* to team up with with Michael and the Remix team lately. Contributing by introducing new tooling and api's based on the level of quality we're achieving around the software we're building with it has unlocked a whole new level of excitement.
Getting so much amazing feedback on this already. Thanks so much to Ridd and the dive team for having me back again ❤️
If you want to hear more around how we're approaching the next generation of interface innovation at @Shopify, check it out:
this week's episode with @PixelJanitor is all about scaling craft + impact as an IC
just wait until you see some of the design details he screen-shares 😍
youtube.com/watch?v=r4IW73e6…
This is why you use motiondev. Because Matt thinks about all the things so that you don’t have to.
Highly recommend. Did this recently with shop.com and made font assets 74% smaller and 80% fewer font requests. Easy improvement with easy gains.
Tell your agent to optimize your site’s web fonts. I’m seeing a huge difference on my blog.
Full prompt:
Make this site's web fonts load faster without changing how anything looks. Shrink font bytes as far as possible, keep rendering identical, and prove it with before/after pixel diffs. Treat any visual change as a regression unless I approve it. If an optimization would change rendering, tell me what it saves and what it changes, and keep the site looking the same by default. Keep the current loading behavior: don't touch font-display or fallback fonts. Don't add font processing to the build; write a script I run by hand, commit its output, and note when it needs rerunning. First measure the current state: each font file's size, glyph count, variable axes, OpenType features and hinting, plus font bytes per page and what each page preloads. Then find out what the site actually uses, checking inline component styles as well as stylesheets: which characters appear in the content, which axis values and weights each font needs (including one-off overrides and bold inside italics), which OpenType features are turned on, and CSS side effects like `hyphens: auto` using the U+2010 hyphen. Cut each font down to that. Keep the used characters plus Latin-1 and Latin Extended-A, and leave CJK to system fonts if that's how it renders today. Limit variable axes to the ranges in use, and only fix an axis at one value if nothing overrides it. Drop unused OpenType features and hinting. Split each font into two files. A small core with ASCII and the punctuation most pages use (curly quotes, dashes, ellipsis) gets preloaded. An extended file behind `unicode-range` only downloads when a page needs one of its characters. Each file's `unicode-range` should list only characters it actually contains. Watch out for a few things. A generated fallback face between the core and extended files will draw the extended characters before the real font does. Fonts with a Reserved Font Name under the OFL must be renamed internally once subset. Check the generated files, since font tools have quirks. Before calling it done, build a baseline from the same content and pixel-diff before and after on pages with code, italics, accented characters, components with their own font settings, and CJK. Explain every visible difference: content change, regression to fix, or harmless sub-pixel rounding. Re-measure bytes per page and confirm the extended files only load where needed. When you're done, tell me the bytes before and after per font and per page, the pixel-diff results, anywhere you deviated from what I asked and what it cost, and how to rerun the script. Later, it may be worth embedding the core font in the global stylesheet and precaching the extended files after idle.
Working on a little image gallery glow up for shop.com's web experience using @motiondotdev's gallery component. Check it out:
If you're browsing this with chrome, press the ~ key.
🤯
The new Edition drops today.
It’s a magical time to build. Hope this Edition shows how much fun we’re having.
shopify.com/editions/fall202…
Got to play around with this recently and it's super slick. Give it a try!
(The website is freakin awesome too!)
I built a notes app inspired by the 80s, when software felt simple and snappy. It launches in 2.6ms.
I've taken notes for 10+ years, first in VS Code, then Obsidian. Sometimes I just want to jot down a thought and get back to work.
Here's Noted: noted.computer 🧵
The homies got back together for another amazing chat 👀
👀 @jamesm is one of my favorite visual designers on the planet
but now he's transitioned into a full-blown builder with Claude
so this week's episode is a behind-the-scenes of how he builds stunning websites👇
youtube.com/watch?v=IStiszvY…
When we can ship substantial improvements in days instead of months, we should ask more around “how great can this be?” rather than “when will this get done?”
Stop treating a pursuit of excellence as a threat to speed. Moving fast should raise standards instead of lowering them.
Today marks 1 year of joining Shopify. The shift from startups to a large public company has been a thrilling learning adventure, but exciting as hell.
- Things move slow
- Bureaucratic process everywhere
- Decisions take forever
That's what I was warned it would be like. But here's how it actually is:
- Things move as fast as how great something can be
- Process is constantly questioned and trimmed
- Decisions are simply a DM away
Big things are happening and I'm excited about what's to come. This morning I joined @ridd_design for another dive club episode to talk about my experience in all this, and I'm so stoked to share our chat when it comes out in a few weeks.
Happy 1 year, Shopify. Thanks for having me around.
The team behind @inflight has been working on feedback for prototypes for a while, excited it's finally out!
Missed opportunity for the agent bot apps to use the accelerometer to have the cute little eyes move around toward the user as the device tilts.
Headed back to SF for Vercel Ship. Last trip ended with this tech fam dinner hang, and I’m so excited to see all the homies again who will be around 🖤
Found out why $NKE is down.
Even the brand guidelines should say not to do that with the logo.
This week was one of the best of my career. Shopify is going through quite a moment and this week felt transformative. The excitement in the quality and velocity is palpable.
Someone said: "This week has felt like working at the company I've always wished I could work at."