Doing too much work on one's own before looping in others

Re:Doing too much work on one's own before looping in others by baby on Tuesday January 25, 2022 @07:53PM (#30080283)

> Writing code as a team is almost like writing a novel with a few dozen other people, all of which have differing ideas on how the book should be written, or even what it should be about. It's hard to feel the joy in creating something when you're only a small cog in the development machine, and every decision needs a dozen voices of input.

I believe this is why books most often have a single author. A solution to this, is to agree on the global design, and then have different developers own different "modules" of the design. These modules should be treated like third-party libraries (and should act like third-party libraries vis-a-vis of their documentation and API).

Basically, microservices can exist within your code if you know how to modularize well.

[ Parent | on HN ]

Re:Doing too much work on one's own before looping in others by lolc on Wednesday January 26, 2022 @06:56AM (#30084460)

I don't like the analogy to writing a novel because in a novel you do want suspense, drama, surprises and generally a non-ordinary flow of the story. With source-code, you want none of that. The whole process is geared to remove it. And we should not deplore that but embrace it. Maybe there will be non-conventional things, because you have non-conventional requirements, or you're trying something new, but that should be the exception.

[ Parent | on HN ]

Re:Doing too much work on one's own before looping in others by e12e on Wednesday January 26, 2022 @05:12AM (#30083716)

> I believe this is why books most often have a single author.

... And at least one editor, no?

[ Parent | on HN ]

Re:Doing too much work on one's own before looping in others by baby on Wednesday January 26, 2022 @05:00PM (#30092597)

I see the editor as the code reviewer :p

[ Parent | on HN ]