@shreyas Well described. Happens in engineering too. Tech projects that please internal audiences without making cust/biz impact. I think about cultures that are internally-driven (perceptions, promotions, etc) vs externally-driven (customer, competition).
@kamilkazani Israelis need to recognise that they’re not optimising for peace, they’re optimising for territorial expansion within geopolitically acceptable norms.
@Noahpinion The measure became the target because of a myopic focus on equity as a goal. Equity alone is a horrible goal without something to balance it that channels resource to the people that are not receiving equitable outcomes
@HarrisonObiorah@shreyas I think they are. Where this is pervasive, it works as a massive constraint on vision and expectations. I’ve seen it drive PMs to focus less on customers and more on these internal challenges.
@tastapod Hard agree. The sophistication of infrastructure sucks up so much money and time. It becomes the problem space in a lot of developers eyes, and the business/customer problem falls well down the list
@davidfowl That’s the challenge with applying generic solutions to specific problems. Something like clean architecture rarely matches the problem space perfectly. Generic solution patterns aren’t bad but often they’re used to bypass critical thinking and overcome gaps in domain knowledge
Code is holding back business productivity. Why we ever thought giving a machine instructions for every condition it faces was scalable is beyond me https://t.co/HPj8mmZxDo
@THINK_Lyndon@RogerLMartin@chriscfox You’ve just described the problem with building business software as well. The codification of knowledge breaks down without base elements from which to extend using taxonomic rank.
@Noahpinion Completely agree. Software was always about solving problems, mostly business problems. Those problems will still be there to solve but more people will have the tools to solve them. It probably won’t be with code though, given the advances in natural language interfaces
Love a good demo fail as much as the next person but some people are raging on Google for disinformation. When you make things, sometimes they don’t work perfectly the first time. It happens
Great 🧵 about scaling. Interesting frame for thinking about software as well. Code is customisation and scales poorly. Metadata systems on the other hand can be the app factories of the future
1. A short thread on a fundamental trend in economics of physical stuff that's highly relevant to the conversation about nuclear & renewables:
A. Manufacturing things gets cheaper with scale.
B. Constructing things in the field gets more expensive with time.
@a16z Fantastic article!! I also think that in late stage growth SAAS, the “flexibility tax” compounds due to the behavioural changes that come with abundant resources. It’s no coincidence that resource intensive patterns such as micro services have gained popularity in the cloud era
@jbogard Hard agree. I don’t get why the industry moves infrastructure from data to code. When I’m solving real-word problems I want to spend 0% of my time on infrastructure, data is a path to do that, code makes me focus on amazing stuff like indenting.
Watching Jack Ryan is a flashback to the 90s, but not in a good way. Lots of action, little comprehensible plot, and tone deaf to the current geopolitical situation