Hacker News Reader

Comment by kardianos | Hacker News Reader

I would not recommend many of these patterns. A business application needs are specialized; create a framework for your needs, then define the application into being. Make your functions as large as makes sense, which is typically fairly large. Ignore most of these hot buzzwords.

Define the needs of the application, develop a framework to meet those needs, then define the application into being. Never write a business application screen by screen; define it into being screen by screen.

View on HN

If this post were called "We wrote a book about our approach to building DDD/CQRS business software using Go", I would be perfectly fine with it.

Feels like a clickbait, especially after your learn that the consultancy that wrote the book built their whole identity around being "DDD in Go" experts. Just don't push it on everyone. This kind of marketing is doing real harm to Go newbies, like that "standard Go project template" repo.

Hey, thanks for the comment. I hope this doesn't seem like we say it's the only valid way to build applications. We mention throughout the book where some patterns make sense, and where they're not needed. We also write about more patterns than just DDD and CQRS, so we don't include these in the book's title.

Book's title is fine with me, post's title isn't. Felt like clickbait once I realized its promoting patterns that aren't useful in most of "business applications built in Go". If you already decided to use CQRS/DDD for whatever reason - yeah, its a decent resource.

> I realized its promoting patterns that aren't useful in most of "business applications built in Go"

I don't really agree with this. I would say most of the patterns are quite useful in majority of business applications. Unless you're dealing with trivial domains, but I believe it's not that common.

Describing the book's content as DDD/CQRS is too specific, as we touch on many different patterns.

>Describing the book's content as DDD/CQRS is too specific (...)

We'll just have to disagree here. You can combine 10 guides into a "book" and if the whole thing ends up being about building an app using a certain approach, then in my eyes that's what the book is about.

Perhaps my standards are too high - still felt like clickbait. Especially considering that you're requiring signing up to a newsletter to get access to it.

> consultancy that wrote the book

I'm not really sure I know of a lot of people that are writing books for any other reason than furthering their own careers.

> Just don't push it on everyone

You're free to not read the content, or use the techniques and processes.

> This kind of marketing is doing real harm to Go newbies

Not sure I see the connection. But I imagine the people searching for "golang +ddd" will be happy this book exists.

Reply on news.ycombinator.com