Not

Hacker News!

Beta
Home
Jobs
Q&A
Startups
Trends
Users
Live
AI companion for Hacker News

Not

Hacker News!

Beta
Home
Jobs
Q&A
Startups
Trends
Users
Live
AI companion for Hacker News
  1. Home
  2. /Story
  3. /We stopped roadmap work for a week and fixed 189 bugs
  1. Home
  2. /Story
  3. /We stopped roadmap work for a week and fixed 189 bugs
Nov 23, 2025 at 11:06 AM EST

We stopped roadmap work for a week and fixed 189 bugs

lalitmaganti
2 points
2 comments

Mood

calm

Sentiment

neutral

Category

other

Key topics

General

Discussion Activity

Light discussion

First comment

43m

Peak period

1

Hour 1

Avg / period

1

Comment distribution2 data points
Loading chart...

Based on 2 loaded comments

Key moments

  1. 01Story posted

    Nov 23, 2025 at 11:06 AM EST

    15h ago

    Step 01
  2. 02First comment

    Nov 23, 2025 at 11:49 AM EST

    43m after posting

    Step 02
  3. 03Peak activity

    1 comments in Hour 1

    Hottest window of the conversation

    Step 03
  4. 04Latest activity

    Nov 23, 2025 at 12:10 PM EST

    14h ago

    Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (2 comments)
Showing 2 comments
inhumantsar
14h ago
1 reply
I firmly believe that this sort of fixit week is as much of an anti-pattern as all-features-all-the-time. Ensuring engineers have the agency and the space to fix things and refactor as part of the normal process pays serious dividends in the long run.

eg: My last company's system was layer after layer built on top of the semi-technical founder's MVP. The total focus on features meant engineers worked solo most of the time and gave them few opportunities to coordinate and standardize. The result was a mess. Logic smeared across every layer, modules or microservices with overlapping responsibilities writing to the same tables and columns. Mass logging all at the error or info level. It was difficult to understand, harder to trace, and nearly every new feature started off with "well first we need to get out of this corner we find ourselves painted into".

When I compare that experience with some other environments I've been in where engineering had more autonomy at the day-to-day level, it's clear to me that this company should have been able to move at least as quickly with half the engineers if they were given the space to coordinate ahead of a new feature and occasionally take the time to refactor things that got spaghettified over time.

lalitmaganti
14h ago
As I pointed out in the "criticisms" section, I don't see fixits weeks as a replacement for good technical hygiene.

To be clear, engineers have a lot of autonomy in my team to do what they want. People can and do fix things as they come up and are encouraged to refactor and pay down technical debt as part of their day to day work.

It's more that even with this autonomy fixits bugs are underappreciated by everyone, even engineers. Having a week where we can address the balance does wonders.

View full discussion on Hacker News
ID: 46024541Type: storyLast synced: 11/23/2025, 6:49:40 PM

Want the full context?

Jump to the original sources

Read the primary article or dive into the live Hacker News thread when you're ready.

Read ArticleView on HN

Not

Hacker News!

AI-observed conversations & context

Daily AI-observed summaries, trends, and audience signals pulled from Hacker News so you can see the conversation before it hits your feed.

LiveBeta

Explore

  • Home
  • Jobs radar
  • Tech pulse
  • Startups
  • Trends

Resources

  • Visit Hacker News
  • HN API
  • Modal cronjobs
  • Meta Llama

Briefings

Inbox recaps on the loudest debates & under-the-radar launches.

Connect

© 2025 Not Hacker News! — independent Hacker News companion.

Not affiliated with Hacker News or Y Combinator. We simply enrich the public API with analytics.