Think of egoism like a single-threaded algorithm assuming all actions optimize for self. Altruism suggests a multi-threaded model where some processes prioritize others’ well-being. Data from user behavior (empathy-driven actions) and system design (evolutionary efficiency) supports a hybrid model—humans aren’t just “selfish” codebases.
Debated since Hobbes, it’s challenged by:
- Butler’s Stone: Pleasure is a byproduct, not the goal.
- Science: Biology (altruism aids survival), neuroscience (motivation ≠ pleasure), and psychology (empathy drives genuine care) suggest mixed motives.
- Analogy: Egoism is a single-threaded “selfish” algorithm; altruism adds threads for others’ benefit. Data leans toward a hybrid model.
Whenever I dive into a creative project, whether it’s freelancing for a client or tinkering on my own stuff, I know exactly what’s coming. The dopamine hit from shipping code is unreal, like a high from solving a puzzle that’s been nagging me for days. The rep boost, the financial payoff (or potential for my own projects).But deep down, it’s not just about me. Crafting something that users love or that makes their lives easier? That’s the real magic. It’s a mix of selfish thrill and selfless impact, like a perfectly balanced commit.
As I designer I was trying to skate to where the puck was going technically. We’d get some insight on what was coming from the model side and we’d try to build UI around that future before it arrived. The labs team at Google has done a solid job of trying to build with that mentality.
We were in a mad dash for 1.5 years launching early and listening to user feedback then iterating our way to where the product landed. As I mentioned, those close to me knew how all consuming this process became. It was an amazing time taking a new product from 0 to 1 inside Google.
I Definitely never expected my portfolio site to make the rounds like this!
> As A designer I was trying to skate to where the puck was going technically.
Resonates big time! At the end of the day, this isn't a full-proof science - it's an art. Req-con-fin(Requires continuous finessing).
I also assume, the project revolved around many roles and as you mentioned, the project was iteratively built around user feedback.
NLM disrupted the space and I know just like with the early days of bard/gemini this will only get insanely better; UI/UX especially.
Dey Well
Anybody else?
2 small requests that (I think) would help with the UX: consider moving (or duplicating) the play button - maybe directly in the middle below the editor, or on that panel itself. It took me a few confusing seconds to realise where it was. Also, could you consider making each fourth (or first) column a very slightly lighter grey? So if I want my kick on 1, 3, 10 and 11 it's really easy to see where to click without counting?
This could be a component logic; a row of drop downs for customizing the UI and a good examples are color and grid count. This could even be a toml/json config file that can be imported/exported.
My own addition is ability to import samples from my own device.