The hottest Development Process Substack posts right now

And their main takeaways
Category
Top Technology Topics

Slow down to speed up

The Engineering Manager • 41 implied HN points • 13 Mar 26
🕹 Technology Development Process
  1. When execution gets cheap and fast, getting requirements and design right matters more; slow down to clarify the problem, success criteria, and constraints before you build.
  2. Fast AI-generated work can look finished but still be solving the wrong problem, creating technical debt and costly rework; only unleash speed once you’re confident the direction is correct.
  3. Make deliberate slowness practical: timebox a clarification phase, run pre-mortems and inverted questions (even using AI), build throwaway prototypes, and share artifacts so you catch mistakes cheaply and make later execution faster.

How Snyk fails

Frankly Speaking • 355 implied HN points • 16 Aug 23
🕹 Technology Development Process
  1. Snyk is a developer-focused application security product that integrates security into the development process.
  2. Snyk's core product is a software composition analysis (SCA) tool that quickly detects vulnerabilities in dependencies.
  3. Despite success, all startups, including Snyk, still have the possibility of failure.

Why hire Technical Program Managers when we have Product Managers

Building Rome(s) • 7 implied HN points • 13 Feb 23
🕹 Technology Development Process
  1. Hiring Technical Program Managers can add value by keeping track of complex project schedules and dependencies.
  2. Product Managers can sometimes handle the work of TPMs, especially in early stage startups.
  3. As organizations grow, there may be opportunity costs in not hiring TPMs to ensure effective communication, alignment, and risk mitigation.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

Black Box Programming

Tribal Knowledge • 0 implied HN points • 06 Apr 23
🕹 Technology Development Process
  1. When programming, focus on zooming in rather than zooming out to improve productivity and solve problems efficiently.
  2. Treat certain parts of your work as 'black boxes' where you focus solely on inputs and outputs, allowing you to tackle complex tasks one step at a time.
  3. Address unknowns in your project by compartmentalizing them as black boxes, enabling you to focus on what you do know and make progress without feeling overwhelmed.

Quality Engineering Basics: Bug Reporting

QUALITY BOSS • 0 implied HN points • 19 Dec 23
🕹 Technology Development Process
  1. A good bug report should have a clear title that describes the issue. This helps others understand the problem quickly without needing to read everything.
  2. Including steps to reproduce the bug is essential. This allows developers to see the issue themselves and figure out how to fix it.
  3. Adding relevant details like environment information, expected vs. actual results, and visual aids like screenshots makes the report more useful and helps prioritize the fix.