Sunny

← All weeks

What I’ve been reading (W3, 2023)

Software has diseconomies of scale · 2023 AI Players and Predictions by Neeva

Software has diseconomies of scale

  • Small teams frequently outperform large teams, five people working as a tight team will be far more productive per person than a team of 50 or even 15. (The Quattro Pro development team in the early 1990s is probably the best-documented example of this.)
  • The more lines of code a piece of software has, the more difficult it is to add an enhancement or fix a bug. Putting a fix into a system with 1 million lines can easily be more than 10 times harder than fixing a system with 100,000 lines.
  • Projects which set out to be BIG have far higher costs and lower productivity (per unit of deliverable) than small systems. (Capers Jones’ 2008 book contains some tables of productivity per function point which illustrate this. It is worth noting that the biggest systems are usually military, and they have an atrocious productivity rate – an F35 or A400 anyone?)
  • Waiting longer – and probably writing more code – before you ask for feedback or user validation causes more problems than asking for it sooner when the product is more minor.
  • Take each and every opportunity to go small. Get good at working in the small, and optimise your processes, tools, and approaches to do many small things rather than a few big things.

2023 AI Players and Predictions by Neeva

  • AI applications to our daily lives are going to explode in 2023
  • Over the next year, we expect multiple battles, consolidation, and splintering across these categories.
  • Compute clouds and foundation model players will collide. Microsoft already has its OpenAI investment. Google will join the rungs of the foundation model providers by exposing an LLM API via GCP.
  • The CoPilot for X companies will compete with AI frontend companies that use foundation model APIs to beat them to market.
  • OpenAI will try to be both an API provider and a “CoPilot for X” company for many use cases.
  • Traditional enterprise companies like SalesForce, ServiceNow, and UIPath will find themselves at the end of an onslaught of the likes they haven’t seen before. They will react by acquiring “CoPilot for X” companies.

Be different, not better.

  • If the last era rewarded conformity and competition, the next rewarded differentiation and cooperation.
  • The things that are going to be valuable are the things you can’t teach or copy. As the value of things you can teach or copy trends towards zero, the value of fresh new ideas increases.
  • It’s so tantalizingly easy to copy others, to create undifferentiated products or ideas in the pursuit of doing something, that it’s become the default. Just as AI doesn’t improve with stale, rehashed data, the world doesn’t progress based on stale, rehashed ideas. We progress as we evolve based on mutations.
  • We seek constancy in heredity – and find its opposite: variation. Mutants are necessary to maintain the essence of ourselves.
  • Being different beats being better, and differentiation’s lead will only widen from here.

List of questions that devs need to answer before a service deployment

  • How and why would the service fail?
  • Do we use appropriate logging levels depending on the environment? (Trace and DEBUG should not go to production)
  • What kind of metrics are you exposing? (No of requests per second, No of errors per second) and time each request takes)
  • How does the data flow through the service? (PII/Sensitive, data captured in logs)
  • What is the testing coverage for this service?

Others