- code to an interface not an implementation
- segregate interfaces, don’t overload them with responsibilities
14,026 karma · joined July 2, 2012
Email: d@nblo.ws
Website: https://da.nblo.ws
- code to an interface not an implementation
- segregate interfaces, don’t overload them with responsibilities
> The text tries to introduce the idea of a “narrow waist” as an architecture pattern. But I don’t fully understand how the author distinguishes this concept from similar ones, and some of the examples even seem to contradict the principles.
Assuming:
- 5,250 can stand front to back
- 3,500 side-by-side
- 750 on top of each other
That's more than 13 billion humans you could fit in said cube.
> Any headline that ends in a question mark can be answered by the word no.
> https://en.wikipedia.org/wiki/Betteridge%27s_law_of_headline...
To take one example, 99% of monitors in 1997 were 1024x768 CRT with single pixel density, which freed designers to assume that's what their end user was on. No such standard exists today.
Claude or ChatGPT let me bash out my frustrations.
But, honestly, when I feel like that it's often best to get away from the computer entirely. Go for a walk, read a book, spend time with friends, do some old fashioned craft - whatever floats your boat.
Personally, I follow specific people who regularly submit interesting content, and pay less attention to the homepage.
Griff Rhys Jones (popular in the 80s - “Alas Smith and Jones”, “Not the Nine o Clock News”) lives nearby, and occasionally drives it.
His resignation four weeks later.