The tradie app space is ripe for deep customisation. Appaca might fill that. Each trade has specific requirements that vendors lack deep domain knowledge of.
A fairer way would be requiring all excess profits be invested in hard assets like factories, infrastructure etc. capital should be forced into competition and create excess capacity.
The web revolution is to Windows UI what vibe coding is to programming today. It brought in a massive group of people who didn't need to understand message pumps, or handles or non-blocking api calls. On top of that, it delivered incrementally more capable result each year. View source taught millions how to build modals, blurred overlay. Meanwhile, the old group of programmers were still worrying about how to protect the knowhow behind compiled languages.
I read a story about Dreame. The founder worked in aerospace, but wanted to make a mass-produced motor with aerospace standards. So he modelled air flow using aerospace tools, built the motor to tight tolerances. Conventional vacuum motors run at 30k rpm, his runs at 100k rpm. Then he standardises on a single motor, for all his devices, robovacs, stick vacs etc, so he gets scale.
If hybrid seeds provide economic and material benefit then the laws should be written to prevent counterfeits, not specifically banning people from replanting.
Don’t you think if we understand why energy, the fundamental unit of economics is lower in China we can gain much insight into the rest of the economy? Economists have often praised an energy tax for its non distortionary effect.
why does this arbitrage exist? Why is the cost of energy, the fundamental input into every economy, cheaper in Asia? Tractors consume fuel, fertilisers do too. Human labour is the least efficient at converting fuel into energy. When you dig a little deeper, you'd find an economy structured around keeping rentiers away from the basics: housing, energy and food.
SOAP started life as XmlRpc. It was a simple model used in Python. It was a simple serialisation format. It was a micro format and could be implemented in a day. It didn’t cover encryption, signing , routing, cyclic references. But it could be implemented in a day. It’s all text and easy for implementers to fix. Since these were early days of the web, there were no openidconnect, no jwt, no encryption standards. If you used Ruby you couldn’t easily interoperate if there were standards calling for all these things. The SOAP specs were big documents.
LLMs’ design is around novelty and creativity. It was the missing left brain of computation. We should stick to traditional styles of computation for compilation.
I’ve often wondered about PPP and why China is cheaper. Deepseek provided interesting answers, and it’s nothing to do with pollution or cheap labour. Turns out socialist policies, investing in free markets, cheap education, open competition, public infrastructure result in competitive manufacturing.
Queues have several problems
- if the caller is http it may timeout and retry, leading to more jobs being queued
- the caller may no longer care because it took so long and the work is wasted
- if the caller is called from a queue it can cause cascades
- you can fill a disk up and crash the system
In any large orgs the more people involved the more deadlocks you have and it can become a policy quagmire. Both meta and twitter achieved more velocity once cuts are in place.