strife25
Joined 14 years ago
Karma
218
Submissions
82
Member since
May 10
Recent submissions
Comment · 4 months ago
Comment · 5 months ago
Generally agree with this approach. We need to make sure that friction exists in our kids' lives.
I have a toddler, and screen time is something that is on top of my mind, Balancing the trade-offs of when to use it while also minimizing it as much as possible.
Something that made me really sick to the stomach was learning how Cocomelon was doing AB testing to make sure that children don't look away from the show[1]. In response to that, I default to showing my kids shows from the 90s that didn't use cuts, aggressive cuts, to keep attention going. Things like Sesame Street, Mr. Rogers Neighborhood, etc.
Heck, I remember trying out one Disney show focused on Minnie Mouse and barely allowed the show to run for three minutes after I realized that there were multiple cuts happening every three seconds.
[1] https://www.nytimes.com/2022/05/05/arts/television/cocomelon...
Comment · 6 months ago
Marginal costs matter in this world.
Comment · 6 months ago
I like this angle. I didn't read much of the article, but I do think this is a topic that people should consider, at least when it comes to estimating software projects. I don't think we really think enough about the monetary costs of our projects. When I raise the topic in my discussions, it really changes and focuses people, particularly when folks are advocating for tech debt projects that don't really have a return because they're not a focus for the company at this time. When we say that it's going to be a $60,000 project, it quickly becomes deprioritized in the conversation.
Comment · 3 years ago
Does anyone know of good building science websites? I'd love to better understand best practices.
The only one I've found is https://inspectapedia.com
There's great stuff on YouTube too (e.g. Matt Risinger's channel), but soooo much conflicting information.
Comment · 3 years ago
> Sometimes making the cinematics wasn't a core competence of the studio working on the game, so VFX or animation studios would be contracted to do this.
That explains why FFX's cinematics had different character models compared to in-game designs.
Comment · 3 years ago
What I've been annoyed with for years: Drying Racks.
What do people do instead of using these? I'm guess just hand drying them. I do have a lot of air-tight container lids that are super annoying to hand dry.
I like the convenience of the drying rack, but hate the countertop clutter and space it takes.
Comment · 3 years ago
Labor wasn't the issue, it was UX.
Users wanted responsive UIs and Gmail showed the power of AJAX in the browser. In the mid-2000s, server power, network latency, and maintaining state were the challenges. The UX was more powerful when the client tracked state, only requested the data it needed, etc.
Things have flipped. SPAs became bloated as abstractions were introduced. Network latency and server power is not an issue anymore. Rendering a bunch of HTML is as quick as rendering JSON.
As a vet of the IE7 days, I love this trend. Leveraging the best of server compute and browsers is going to simplify web app development a LOT.
Comment · 4 years ago
_hums the rhythm of wisdom_
Comment · 4 years ago
+1
SPAs were a workaround to slow CPU servers serving millions of requests in the mind-2000s. Client computers were faster, so it made sense to push UX logic there.
We've flipped things around. Servers are fast as hell for rendering HTMl. We can leverage that and re-focus the client on UI code that only it can do.
Comment · 4 years ago
I switched from Paprika to Plan to Eat this year and love it.
Https://plantoeat.com
It has the same features as Paprika but Generates a shopping list from your meal plan. Saves a ton of time when shopping.
The one thing I don’t like about PtE is you can’t mark off ingredients as you prep them. Paprika has this and I miss it.
Comment · 4 years ago
Exactly! It’s a crazy diverse user base too.
The needs of designers creating a marketing site and engineers working on a real web app are different, but they all work with web tech.
A key point is understanding the business (or personal) goal of the system.
Is this a mission-critical system that is core to how the company makes money? Then make sure its robust.
Are you a startup figuring out product-market fit? Then thorough and robust systems matter less. The goal is figuring out how to get users and customers, not stabilize.
I actually wrote more about this a while back: https://www.buildthestage.com/when-should-you-over-engineer-...