The documentation is not Enterprise Ready™; it still contains a description of what the product actually does in an accessible location. For proper compliance, this description should be in a PDF whitepaper that will only be mailed to you after providing your e-mail address and phone number.
The Github issues list is the real gold mine: <a href="https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition/issues" rel="nofollow">https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...</a>
Looking at the problem statement, this should be built in a Reactive style of programming and more event based. What if we need to scale this to infinite numbers for millions of clients ?<p>Event based programming in technology like stack is more appropriate for this kind of problem domain...
I'm appalled that this piece of junk that has the audacity to call itself "enterprise grade" does not employ an industry standard dependency injection framework. 22 appearances of 'new' in the codebase - you gotta be kidding me! I cannot recommend to license this application for deployment at my company unless its code is thoroughly refactored to use Dagger or at the very least Google Guice.
Where/how does one learn to structure programs like this? Obviously I won't write fizzbuzz like this, but the point is it won't occur to me to structure a fizzbuzz solution like this. And if I can't produce such a structure for the dead simple case, then I can't trust myself to be able to architect an actual complex system where one <i>does</i> need to apply all these abstractions.<p>Are these skills only attainable from years of real-world experience?
Big fan of fizz buzz. Edited / wrote / collected a (free open source) book titled "FizzBuzz (1, 2, Fizz, 4, Buzz,...) by Example - There's More Than One Way To Do It" [1] in the Yuki & Moto Press incl. functional, object-oriented, code-golf, and many more styles / versions. Happy fizz buzzing.<p>[1] <a href="https://yukimotopress.github.io/fizzbuzz" rel="nofollow">https://yukimotopress.github.io/fizzbuzz</a>
On a more serious note.<p>What is the alternative to the OOP IOC SOLID multiple layers of abstraction way of doing things? Is this really the go to architecture for <i>enterpire</i> - or more appropriately, large projects? Why is it the go to architecture -- what are the alterntives? Suppose we're discussing a project in a non-typical OOP language (not Java/C#/C++), what is the architure of choice there?<p>Asking this as a junior developer
<a href="https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition/issues/340" rel="nofollow">https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...</a><p>Eh... this guy is right, ant is better.
Is there any technical paper on this somewhere on arxiv? I was trying to implement one of my own without all the enterprise abstractions and now I am stuck.