FizzBuzzEnterpriseEdition

They rejected my pull request to migrate their markdown docs to docbook. https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

I love that there is a commit to 'remove redundant import'. https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... Being enterprise software, the last thing they need in the codebase is clutter.

TL;DR: Java as a language is not bad. The problem with Java is its bloatware ecosystem. Endemic to the Java world are uninstallability, Rube Goldberg machine code, and such heights of over-engineering that they're easily parodied: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... I think the over-engineering is an unintended side effect of Java's most attractive features: incredibly stable standard ABIs, portable byte code, fantastic tooling, and a language that makes byzantine abstractions relatively easy to implement without the instability you get in C++ or the unmaintainability you get in dynamic languages. Sometimes you actually do need very high level complex abstractions, so this makes Java a fantastic language for those cases. But those cases are rare. Java makes it easy to build towers of babel that stand up, so the

Here is a parody of what they're terrified of https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

Ahh Enterprise. Protip for anyone applying for an enterprise job: just copy-paste https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... when they do the mandatory fizzbuzz test in the job interview. And then complain in the github issue tracker if you didn't get the job.

I think this code truly represents the essence of this article: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

Have you seen https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...? It's a well-known parody, but one could also say it's "obviously written to a high standard", for some definitions of "standard".

[3] is broken, should be https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

The actual Java implementation: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... A non-programmer’s solution to “Fizz Buzz” https://news.ycombinator.com/item?id=4853509 FizzBuzz Still Works http://www.globalnerdy.com/2012/11/15/fizzbuzz-still-works/ FizzBuzz with CSS http://dabblet.com/gist/2628265

New York City Tired of the startup goose chase? Change the world for real in 2014. Work on projects involving solar power, hardware controller software, data science, and mobile apps which really are life-changing[1] at the Sustainable Engineering Lab[2] at Columbia University in NYC. You'll be joining a like-minded peer group of hackers working in python, R, go, mongodb, nodejs, and other interesting technologies, focused on making the world suck less. There are no sales/MBA types, no scrum masters, and we strongly disapprove of code written in Enterprise FizzBuzz style[3]. Deets[4] here: https://github.com/SEL-Columbia/jobs [1] Data-driven planning projects in Nigeria, Myanmar, Indonesia; Android apps for rural nurses in India [2] http://sel.columbia.edu/ [3] https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... [4] Somewhat o

> It's also quite the mystery how this culture happened Maybe the language didn't have powerful tools in its core? What if getters/setters weren't mandatory, like in Scala, wouldn't we write more tiny expressive classes to hold intermediate values? Think about this example of Dependency Injection: Why did we have to use DI? Because using statics as a dependency injector (like in Play) prevents from unit testing. How could we have solved it? By allowing inheritance override on statics. We don't have it, therefore we have Spring. Even the Servlet API is criticized for being inexpressive [1]. They've done it so wrong that every single framework reimplements url routing (Struts, Spring MVC...) resulting in those horrible /myserviceaction.do patterns. In turn, those patterns deny RESTful apis, prompting for yet-another-framework for REST resou

Tired of the startup goose chase? Change the world for real in 2014. Work on projects involving solar power, hardware controller software, data science, and mobile apps which really are life-changing [1] at the Sustainable Engineering Lab at Columbia [2]. You'll be joining a like-minded peer group of hackers working in python, R, go, mongodb, nodejs, and other technologies. There are no sales/MBA types, no scrum masters, and we strongly disapprove of code written in Enterprise FizzBuzz style[3]. Deets here: https://github.com/SEL-Columbia/jobs [1] Three current projects: data-driven local planning project in Nigeria, infrastructure planning project for Myanmar and remote islands in Indonesia, building an Android app for rural nurses in India. [2] http://modi.mech.columbia.edu/ [3] https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpr