FizzBuzzEnterpriseEdition

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

Fizz Buzz - Enterprise edition. https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

Vi's site is down from the onslaught. In the meantime, enjoy the ever-classic Fizz Buzz Enterprise Edition: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

This comes to mind: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

> software bloat This came up on another thread here from a blog/article titled "software disenfranchisement". I mentioned that I think a lot of it is an unhealthy obsession with writing re-usable code that results in abstractions on top of abstractions piled onto more abstractions to the point where we get the infamous FizzBuzz Enterprise Edition [0] that I'm sure nearly everyone at HN has seen. We also have a problem of people statically linking massive libraries when they only need a small fraction of its code. > user-hostile decisions that prioritize ads Definitely a problem in mobile web browsing. Ridiculous that on a data-limited connection, ad networks still try to push video ads or ridiculous JavaScript code. > But clock rate is truly meaningless as a performance measure when the underlying architecures are different... Defini

I put some of the blame on an unhealthy insistence of code reuseability and sticking to paradigms. The result is so much code that is just abstractions piled onto abstractions piled on to more abstractions until you get the famous FizzBuzz Enterprise Edition [0] that I'm sure we've all seen by now. Nobody wants to just write some god damn code anymore. They include entire frameworks instead of just writing a couple helper functions. [0] https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

The author simply has a grudge towards over-engineered code such as [FizzBuzz Enterprise Edition](https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...). Not all modern coding is like that, and you certainly cannot build complex software (at least maintainable complex software) without abstraction layers.

To all readers who've never experienced it, working on a large Java (and other) codebases where the original developers completely overused patterns, your life will be hell in my opinion, just as much as a codebase written totally without thought or patterns. Patterns can be useful but only in moderation and only with reason. They're spice. A contrived example, but: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... FizzBuzz Enterprise Edition. It's enterprisey!

I have no idea either, but those are "constants", and so it is only logical that they belong in com.seriouscompany.business.java.fizzbuzz.packagenamingpackage.impl.Constants (https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...).

> he seems prone to analysis paralysis and anxiety about raw ability/intelligence. This is what I also gained, and to me, it says that OP has the ability to solve these problems in much less time. I was a lot like OP when I started out. In college, I would get good marks but be one of the last people submitting a test. Whiteboard-style problems would take me forever to complete. I constantly felt that even though I could get it right, it took too long to be of any use. My problem was much of what you said: I was reinventing crude versions of the wheel while spending an inordinate amount of time comparing different ways to solve problems. I'm not some brilliant mind that's going to have a ubiquitous name in the annals of CS. I've just been really good at breaking down problems and tasks, and early on, I was writing things akin to FizzBuzz

Found it!! https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

Indeed, what's the point to ask someone to write a fizzbuzz when it's already been done to the highest of professional enterprise standards! [1] [1] https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

Leonid Bershidsky and a lot of other journalists laughing at Goldman Sachs' incorrect predictions seem to miss the point. The World Cup predictions from Goldman Sachs (and also UBS) are a form of recreation and entertainment with machine learning. It's an expression of quant nerd humor. Analogous intellectual games would be engineers devising ridiculous Rube Goldberg contraptions[1] or programmers building "enterprise" FizzBuzz[2]. (I think it would add to the fun if GS uploaded their raw data and models to Github for others to play with.) >It certainly didn't predict the final opposing France and Croatia on Sunday. True, but it did predict France having better chance winning overall but was handicapped by a tougher draw. It also predicted France beating Croatia in round 16 instead of the final. The pdf says: >While Germany is more lik

We have much work to do on https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... if we want to catch up.