Tag

#refactoring

653 posts38 followers

Explore Hashnode

Alternatives

Clean Code & Design Patterns: Writing Code Other People (and Future You) Can Read

Write code other people can read and change: naming, small functions, safe refactoring, SOLID without the dogma, and the design patterns that actually show up in AI apps.

28 min readblog.zyvop.com

PowerduckOct 26

The agent extracted a shared helper and merged two callers' error paths

Two routes shared an upstream call, so the agent lifted the block into one helper. The callers differed only on fault: one rethrew for a 500, the other served a cached fallback. The helper picked one exit, the harder caller silently degraded, and green tests missed it.

4 min readblogs.powerduck.com

PowerduckOct 21

The Agent Renamed the Symbol but Left the Old Name in the Error String

The agent renamed the class, updated every reference, and CI went green. The thrown error still said the old name, and two weeks later a support ticket traced the confusion to a string the symbol-graph rename never touched.

5 min readblogs.powerduck.com

PowerduckOct 20

The agent split the giant PR into three smaller PRs — and the bug that lived between them stayed invisible

Splitting a 3000-line PR feels like rigor. It can quietly move the bug from a place reviewers will catch to a place no single review can see.

5 min readblogs.powerduck.com

PowerduckOct 20

The Agent Added a Cache Layer Because the Comment Said This Function Was Slow

A stale comment claimed the function was slow, so the agent built a TTL cache around it. The function had been milliseconds fast for two years. The cache just made invalidity the default.

4 min readblogs.powerduck.com

PowerduckOct 17

The Agent Converted the If/Else Chain to a Lookup Map and Dropped the Side Effect

An agent converts an if/else chain to a lookup map for cleanliness. TypeScript is green, tests pass, but one branch's logging and metrics call quietly disappears.

3 min readblogs.powerduck.com

2

PowerduckOct 16

The Agent Added an Await to a Synchronous Function. The Caller Didn't Notice.

An agent 'modernized' a sync function by marking it async. TypeScript was happy. The production caller that destructured the return value synchronously started crashing at runtime.

3 min readblogs.powerduck.com

PowerduckOct 16

The Agent Flattened Your Custom Error Type Into a Generic Error

A refactor that looks like a cleanup — until callers that matched on your specific error type start silently falling through to a different branch.

3 min readblogs.powerduck.com

PowerduckOct 16

The Agent Deleted the Comment That Explained Why the Code Looks Weird

The function looked ugly on purpose. The comment said why. The agent "cleaned it up" and now the next engineer has to rediscover the workaround the hard way.

4 min readblogs.powerduck.com

1

PowerduckOct 16

The agent refactored that tiny function for clarity. It doubled the runtime.

A clean-looking diff passed every test. The function was called 40k times per request. We didn't notice until p95 spiked.

3 min readblogs.powerduck.com

Search Hashnode

Explore Hashnode

Trending tags this week

Clean Code & Design Patterns: Writing Code Other People (and Future You) Can Read

The agent extracted a shared helper and merged two callers' error paths

The Agent Renamed the Symbol but Left the Old Name in the Error String

The agent split the giant PR into three smaller PRs — and the bug that lived between them stayed invisible

The Agent Added a Cache Layer Because the Comment Said This Function Was Slow

The Agent Converted the If/Else Chain to a Lookup Map and Dropped the Side Effect

The Agent Added an Await to a Synchronous Function. The Caller Didn't Notice.

The Agent Flattened Your Custom Error Type Into a Generic Error

The Agent Deleted the Comment That Explained Why the Code Looks Weird

The agent refactored that tiny function for clarity. It doubled the runtime.