Software Standards from overseas, Outsourcing and Contracting - Jonathan Blow

Here are detailed notes from the transcript:

Main Topics Discussed:

• Global Influence in Software Development: The observable dominance of the USA in setting the tone and practices for global software development.
• Approaches to Software Development: A comparison between a perceived "Western" model (US/UK) emphasizing creativity and resources, versus an "outsourcing" model (e.g., India, Vietnam) characterized by low-skilled labor and low-cost production.
• Software Quality Trends: A discussion on the suspected decline in software quality over time, both domestically and internationally.
• Challenges of Outsourcing and Contracting: Issues related to visibility into outsourced projects, misaligned incentives, and the impact on quality.
• Incentives and Developer Behavior: How personal and financial incentives influence decision-making in software development, often prioritizing speed or profit over thoughtful, high-quality solutions.

Key Points and Arguments:

• US Hegemony in Software: The USA has predominantly set the global standard and tone for software development, with other nations largely copying or attempting to replicate its models (e.g., "local Silicon Valley") rather than developing independent approaches.
• Divergent Development Models:
  • Western (US/UK) Ideal: An idealized approach involves small teams of "imaginative, creative people" given "lots of resources" and a "luxurious environment" to produce "concise, accurate code." This is presented as how "Western companies sell their software expertise."
  • Outsourced (e.g., India, Vietnam) Reality: This model is characterized by employing "lots of people who are low skilled," with "very low expectations," minimal training, and limited resources, leading to "low quality but low-priced code."
• Historical Context of Outsourcing: Software outsourcing has been a practice since at least the 1980s, implying that the described dynamic is not new.
• General Decline in Quality: One speaker suspects that overall software quality has "gone down both here and overseas as quantity has gone up." An analogy is drawn that the quality from an "average Twitter programmer today is probably what you got from an outsourced programmer in the '90s."
• Lack of Visibility in Outsourced Projects: It's difficult for clients to observe the true skill level or number of people working on outsourced projects. The outsourcing company's management often handles internal issues (e.g., "fighting fires," managing "too low skilled" individuals), making the actual process opaque to the client.
• Misaligned Incentives in Contracting:
  • Even when contracting with smaller, theoretically "high-quality" US or European companies, results are often not high quality.
  • Reasons include: contractors not having personal ownership ("not their project"), lacking full context, juggling multiple projects, and potentially "over billing" without commensurate effort.
  • The core issue is that contractors' "personal incentive" is to be "paid and gone long before the results of our decision is discovered." This encourages handing in code quickly rather than spending time "sit and think about the problem, make the right decision," because "thinking time" is hard to bill.

Important Facts or Data Mentioned:

• The USA is identified as the primary tone-setter for global software.
• Outsourcing of software has been observed "since the '80s at least."
• Specific regions mentioned for outsourcing: India, Vietnam.
• Specific regions mentioned for theoretical "high quality" contracting: US, Europe.

Conclusions or Recommendations (Implicit):

• Critique of Current Models: The current global software landscape, particularly regarding outsourcing and contracting, often prioritizes cost and quantity over thoughtful design and quality, leading to a general degradation of software standards.
• Need for Aligned Incentives: For higher quality software, there's an implicit recommendation to align incentives between clients and contractors. When developers (or contracting companies) are personally invested in the long-term quality and outcome of the code they produce, they are more likely to take the time for proper design and implementation.
• Value of Context and Ownership: Software quality benefits significantly when developers have full project context and a sense of ownership, which is often diminished in outsourced or short-term contract work.