@dillon_mulroy@justine_mulroy C’mon now, you can’t take credit for your courthouse wedding when you also had a regular wedding AND literally snuck into a rich people paradise for your pictures 😂😂
@LinusEkenstam@FedEx FedEx has reliably been the worst shipping company for years. Everyone else has no problem delivering to my door (you know, the address I paid to have it delivered to). FedEx is a coin toss for the street, some random lobby on the property… anywhere but my actual doorstep!
@shuddupmeg@polyfraggrenade Web dev here — basically all of this is correct except for “anything” at the beginning. There are tons of uses for query parameters, only one of which is tracking and analytics! When in doubt, you can just remove the stuff after the question mark and see if the link still works.
@ceccon_me@thorstenball Reddit had the right idea with `/r/subreddit` and `/u/user` — as soon as the root route parameter could be a username, team slug, blog slug, static page, etc you’re just creating an eternal well of pain for yourself.
@ceccon_me@thorstenball Working at Vercel, I hate our URL structure. We leaned into the GitHub “pretty URLs” thing early on and it’s caused so much pain over time. My biggest piece of advice for me building sites in the future: Never place a dynamic slug as the first path parameter in your site.
It’s amazing how much the 80/20 rule applies to library/framework development. AI has helped me a lot with both the 80 and the 20, but much less with the 20: The last bits of refinement just require tremendous taste, judgment, and trial and error.
This is spot on, and not just for visual design, for API design, too.
We often get feature requests for Svelte where if we would just implement them the framework would become worse over time.
You gotta understand the problem behind it, find overlaps, and then design a solution
@jlongster I think this depends on the domain. There are a lot of very edge-case-y bugs in Svelte that require regression tests and won’t really be covered by a “more cohesive” approach. The blast radius of something like that regressing is, in our case, millions and millions of devs.
@dillon_mulroy I’ve had a lot of times lately where I skim something, think I’ve got it, set an agent on it, realize the agent’s solution sucks, realize I didn’t fully understand the problem, and end up writing it mostly by hand 🙄
DO NOT WORRY ABOUT PEOPLE TO YOUR RIGHT
DON’T STOP IN THE TRAFFIC CIRCLE
The only additional quirks are:
- if there are crosswalks, don’t hit pedestrians (don’t hit them if there aren’t crosswalks either)
- some places require you to yield unconditionally to buses/18 wheelers
I feel like a huge number of people in the US have no mental model on how to approach a traffic circle, so here you go:
As you approach, look left. Is someone going to hit you?:
- no: go into the traffic circle and DON’T STOP
- yes: stop until no one will hit you from the left
@MakJoris@RhysSullivan GitHub has a lot of surface area. Pushing commits rarely goes down, but things like Actions not working, commit statuses never updating, random 404s on pages that definitely exist, etc. all occur pretty regularly, especially if you use the site all day every day.