洪民憙 (Hong Minhee): For my library and CLI projects, I've been writing documentation before writing any code. It helps me imagine the final interface early on, which usually leads to better design. Sure, sometimes I miss implementation details and have to revise later, but hey—it's just docs. Docs are easy to change. This tiny habit has surprisingly big payoffs. When I focus on how things will be used rather than how they'll be built, I end up with interfaces that actually make sense. Anyone else do this? Curious about your experience with documentation-first approaches. RE: https://hollo.social/@hongminhee/01964c76-ef1e-7994-b3f0-57f967742566

Hackers’ Pub

Syntax	Description	Examples
`"` keyword `"`	Finds the string within quotes, including spaces. Case-insensitive. (Escape quotes inside with `\"`)	`"Hackers' Pub"`
`from:` handle	Finds content written by the specified user.	`from:hongminhee` `from:hongminhee@hollo.social`
`lang:` ISO 639-1	Finds content written in the specified language.	`lang:en`
`#` tag	Finds content with the specified tag. Case-insensitive.	`#HackersPub`
condition condition	Finds content that satisfies both conditions on either side of the space (logical AND).	`"Hackers' Pub" lang:en`
condition `OR` condition	Finds content that satisfies at least one of the conditions on either side of the OR operator (logical OR).	`#HackersPub OR "Hackers' Pub" lang:en`
`(` condition `)`	Combines the operators within the parentheses first.	`(#HackersPub OR "Hackers' Pub" OR "Hackers Pub") lang:en`

洪民憙 (Hong Minhee) @hongminhee@hackers.pub

4/19/2025, 5:19:47 AM

Public

For my library and CLI projects, I've been writing documentation before writing any code. It helps me imagine the final interface early on, which usually leads to better design. Sure, sometimes I miss implementation details and have to revise later, but hey—it's just docs. Docs are easy to change.

This tiny habit has surprisingly big payoffs. When I focus on how things will be used rather than how they'll be built, I end up with interfaces that actually make sense.

Anyone else do this? Curious about your experience with documentation-first approaches.

RE: https://hollo.social/@hongminhee/01964c76-ef1e-7994-b3f0-57f967742566

If you have a fediverse account, you can reply to this note from your own instance. Search https://hackers.pub/ap/notes/01964c7d-1295-70f7-b7ea-c74e47436f27 on your instance and reply to it.

ayo @ayo@ayco.io

4/19/2025, 5:24:45 AM

Public

@hongminhee洪民憙 (Hong Minhee) I half-joked about this some time ago, “docs driven development”. 😄 Happy to see it is working in reality for someone!

I think @sarah11918Sarah Rainsberger might know if others do it too 🤔

박준규 @curry@hackers.pub

4/19/2025, 5:42:38 AM

Public

@hongminhee洪民憙 (Hong Minhee) Document Driven Development!

Tak! @Tak@glitch.taks.garden

4/19/2025, 6:08:42 AM

Quiet public

@hongminhee洪民憙 (Hong Minhee) back in the day, we used to call this a "specification"

도막도 @domatdo@hackers.pub

4/19/2025, 6:59:12 AM

Public

@hongminhee洪民憙 (Hong Minhee) I never start writing code before I gather enough context for the problem. Listening to possible customer's voices and collecting prior arts are one of the most important part of designing solutions.