This is terrifying. 30+ minutes! 😳 The point of a stand-up is, if you’re a team that’s working effectively using scatter/gather, at least you’ll have a few minutes to coordinate before the day starts. If that takes more than a few minutes, you’re in deep deep trouble. Among other things, it tells me you’re not communicating at all over the course of the day.
@_swanson But in essence I tend to lean towards something like Events.register that hides the Event.create. End result is usually similar but does not require hooks. I do love the look of the more 37signals style. But haven’t worked in a code base that had the constitution to keep it clean
Yep! Or ish. I’ve been in enough situations where backfilling will be needed, someone does something they shouldn’t in prod console or ship code without thinking about the implicit side effects that I think the extra layer of explicit calls are worth it.
separation of concerns should be about isolating units of behavior, not technologies. we should focus on what a system does—not what it's made of—and colocate areas of a system that will depend on one another when a change is made. the goal is to be able to understand as much as possible about the behavior of a specific part of a system when looking at a cohesive unit.
My biggest gripe with @TypeScript is that while it should follow API design, it often drives it. The beauty of JS is that it enables highly dynamic, flexible APIs that can provide great ergonomics, but TS tends to do very poorly with them so they’re often ruled out.
The priority of constituencies¹ is end-users > authors² > implementors > theoretical purity.
When designing development tools (whether that is a JS library, a browser, or a web technology), our convenience is lower priority than our users’ convenience², and their convenience is lower priority than their end-users’ convenience.
API design decisions should be driven by user needs, not tooling limitations.
¹ https://t.co/2dIgtKc4L9
² Users of the tool, called "authors" here to distinguish from their own end-users
I think I figured out how to create responsive type scales with composable CSS utilities, thet lets you scale linearly between exact pixel values (this is important if you want to align exactly with a type scale, rather than just scale type on a case-by-case basis) 🧵