This is obviously bogus. Where are the XML configuration files?
Don't you know that auto-wiring dependencies changed everything? Look at how much more concise this is now without all that XML...
Fizz Buzz: Enterprise Edition
71–80 of 171 posts
Re: Fizz Buzz: Enterprise Edition
#72Earlier quoted context omitted.
Don't forget about the RESTful interface to the application.
first of all restful and json are not really welcome. do your JAX-WS first and then we can talk about these new silly things.
Good point.
Those fizzy SOAP requests need to be signed too. Enterprise Security and all.
Re: Fizz Buzz: Enterprise Edition
#73Please note that GitHub no longer supports Internet Explorer versions 7 or 8. How ironic. This covers so many enterprise programmers with locked down Windows PCs.
Twitter stopped supporting both a while ago as well.
Re: Fizz Buzz: Enterprise Edition
#74Startup edition: * provision one ec2 instance per number to check * assign numeric order based on uptime in msec using zookeeper * serve result via json * render it on the client.
Maybe they will use Heroku instead of EC2
It is done in node.js with the latest something.js fad that provides event-driven async MVC interfaces in Coffee script or something like that
Also, they will have 100% code coverage (thanks Uncle Bob) but will fail at launch since nobody bothered to test it for more than one user.
Re: Fizz Buzz: Enterprise Edition
#75This may be Enterprise Quality but without UML diagrams our Architects are not going to be able to understand or use the code.
Are you offering support contracts? MegaCorp Management requires that we have paid support, the more expensive the better.
Re: Fizz Buzz: Enterprise Edition
#76Earlier quoted context omitted.
The problem isn't random programmers, it is a culture and tool ecosystem which says that this is the right way to do things. If it were just one random programmer, there would be nothing to complain about. If some guy decides to write his website in his own dialect of Visual Basic, that isn't really being inflicted on anyone but his employees. The deeply-nested StrategyFactory stuff is an infection which worst affect…
So, you should be able to show me dozens of tools that are the default choice within these ecosystems, that make programmers build things in this way. Can you please name some tools and tell us how they say this is the right way to do things?
Why do JAVA, C# (and the like) IDE's have such complex feature sets? Is it not a reflection of the complexity that those ecosystems require for maintaining your code?
Re: Fizz Buzz: Enterprise Edition
#77Earlier quoted context omitted.
The problem isn't random programmers, it is a culture and tool ecosystem which says that this is the right way to do things. If it were just one random programmer, there would be nothing to complain about. If some guy decides to write his website in his own dialect of Visual Basic, that isn't really being inflicted on anyone but his employees. The deeply-nested StrategyFactory stuff is an infection which worst affect…
So, you should be able to show me dozens of tools that are the default choice within these ecosystems, that make programmers build things in this way. Can you please name some tools and tell us how they say this is the right way to do things?
Really?
Eclipse, Netbeans, Maven, JUnit, JLog
J2SE libraries - pretty much all of them
Apache libraries
Hibernate
J2EE libraries
The list is endless
Even Google App Engine manages to be way more convoluted in Java than in Python or Go, it's not even funny
Re: Fizz Buzz: Enterprise Edition
#78I've often wondered - is it the language that spawns this or the mindset of the developer (or both?) I see this primarily in Java or .NET shops - massive layer upon layer, code generation, factories, classes, etc. - when a simple architecture would be best. Why do we get these insane things to begin with? What's going on? It feels sort of like premature scaling (what if we have millions of programmers - we need more…
I wonder too. I write a very atypical brand of Java (I like to think of it as "unencumbered Java"). I sometimes even use public fields instead of accessors (o, the heresy). My best guess would be that you often need to refactor you code to include some of the patterns showcased in the repo (factories, for instance). So developers try to future-proof their project by using those patterns everywhere. This is obviously…
Because people who know the good side of java have jobs.
Re: Fizz Buzz: Enterprise Edition
#79I've often wondered - is it the language that spawns this or the mindset of the developer (or both?) I see this primarily in Java or .NET shops - massive layer upon layer, code generation, factories, classes, etc. - when a simple architecture would be best. Why do we get these insane things to begin with? What's going on? It feels sort of like premature scaling (what if we have millions of programmers - we need more…
Must be the mindset. I've seen plenty of straightforward, well written C# code with none of this garbage. I'm sure it's the same with Java. And you would see plenty of Ruby code written in this kind of style if Ruby was popular in enterprise software development.
Re: Fizz Buzz: Enterprise Edition
#80I've often wondered - is it the language that spawns this or the mindset of the developer (or both?) I see this primarily in Java or .NET shops - massive layer upon layer, code generation, factories, classes, etc. - when a simple architecture would be best. Why do we get these insane things to begin with? What's going on? It feels sort of like premature scaling (what if we have millions of programmers - we need more…
It's a blind insistence on caution.
There are thousands of things one might want to do in the future, and many managers "prepare" for each and every change they can conceive.