The hottest Substack posts of Engineering Open Societies

And their main takeaways
58 implied HN points 19 Mar 23
  1. Governments struggle to build good software for citizens, with outdated technology and convoluted processes.
  2. Governments lack good product and software development practices, often using outdated methods and facing bureaucratic challenges.
  3. Governments have inadequate API and data access, causing issues for engineers and entrepreneurs trying to integrate with government systems.
58 implied HN points 12 Mar 23
  1. Design documents are essential for software engineers to communicate ideas and solutions with others.
  2. Design documents should be treated as ephemeral artifacts used to drive a collaborative process and then discarded.
  3. In design documents, focus on presenting the problem, provide solution-independent correctness conditions, and offer a solution with trade-offs and decisions.
39 implied HN points 24 Mar 23
  1. Define a clear business vision that is achievable and aligns with overarching goals
  2. Strive to balance idealistic mission with pragmatic solutions for open societies
  3. Adopt a broad perspective in shaping solutions to address diverse needs and requirements
19 implied HN points 01 Apr 23
  1. Government as a Service aims to address unique challenges governments face with tailored software solutions.
  2. The product strategy focuses on aligning incentives with government partners to create mutual value and revenue streams.
  3. The technical architecture emphasizes common infrastructure, modularity, and security for efficient development and deployment.
Get a weekly roundup of the best Substack posts, by hacker news affinity: