dig VS FizzBuzz Enterprise Edition

Ironically given Spring’s history, you do have dependency injection in Go. But you don’t need to use it unless there’s a clear benefit. Most code reviewers would be appalled if you pulled in dig into a project that didn’t need it.

Interesting, one of my friends works at a big tech company and they said they passed on Wire and ultimately decided on Uber Dig https://github.com/uber-go/dig. But looking at that lib it seems a bit anti-paradigm of the goal of the Golang language (no magic/obfuscated code running in the background, what you see is what you get style coding)

It's a library to help with DI, by Uber: https://github.com/uber-go/dig

That "Hello World Enterprise Edition" looks dangerously under-engineered - I could understand it! Far better to follow the best practices demonstrated in the Fizz Buzz Enterprise Edition...

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

Clean code is a balancing act - you’ll want to make sure you don’t turn your codebase into something like this.

Bu hocam https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition

amidoingitright

It seems to me that all large software projects eventually grow into "Enterprise" code. What I mean by this is something like FizzBuzz Enterprise Edition; large codebases with many layers where Design Patterns and SOLID principles are applied vigorously.

???

I'll answer your question with a question: Have you seen https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... ? :)

I'm guess that to those of us who remember when Java came out, "FizzBuzz: EE" is what we think of when we think of Java. :P

In Java I have to type a bazillion characters to get anything done! And make all these useless directories and files and InterfaceClassFactoryProtocolStreamingSerializer BS. And worry about how that executes.

C++? No bloat*, just speed

*Yes, there's some _optional_ bloat. But compared to Java? no contest.