5 ms·

This seems to be implemented in a single programming language without any dependencies on legacy systems. A truly enterprise-grade system talks to PL/SQL stored

This seems to be implemented in a single programming language without any dependencies on legacy systems. A truly enterprise-grade system talks to PL/SQL stored procedures. Or it would, if the DBAs had written the stored procedures. But they haven't responded to your ticket request yet. And when they do, it will be with a mostly irrelevant question delaying actual work for another week. by which time their manager will be offsite at OracleWorld and won't be able to approve the changes.

Shorel 14y ago
At the very least we can have a FizzBuzz table with a FizzBuzz field and the following records: 3 5
- serverascode 14y ago
  Awesome! :)
- dansari 14y ago
  And access it using Hibernate.
xntrk 14y ago
There should also be other applications that do almost exactly the same thing but display the information in a slightly way but use a completly different code bases.
- logn 14y ago
  Interesting. I see a need for an adapter library and maybe some runtime configuration settings to choose your preferred, underlying fizz-buzz library.
logn 14y ago
Also it would be nice to configure the strategies with XML. Plus it would be super helpful to have jar plugins for new strategies. And seriously, there's no SOAP interface? This is hardly usable then. Also how the heck am I supposed to build this without Ant and batch and shell scripts to call Ant? Plus once you get ant files you can integrate it with Hudson. And package this as an EAR and add some user authentication too, probably single sign on. Also needs some log4j. And there are probably all sorts of unforeseen bugs and style issues, so it needs Findbugs and Checkstyle integrated.
- podperson 14y ago
  If it were truly Enterprise worthy it wouldn't be in github, but im perforce or, better yet, ClearCase.
- ivanmaeder 14y ago
  You're right. There are so many issues with this, on top of the ones mentioned. No serious enterprise-grade software today would do without leveraging Maven, annotations, IoC, AOP... And why isn't the UI decoupled from the business logic? What happens if one day another team in the organization needs access to Fizz Buzz? Writing their own Fizz Buzz would be extremely redundant (even dangerous), and if anybody changed the logic of Fizz Buzz it would have to be changed in multiple places at the same time: a simple change like making "Fizz" print every fourth time instead of every third time would make every Fizz Buzz team go through architecture, various change management meetings and at least one weekend deployment. And all of this would have to be coordinated to make sure it all happens within a single change window (assuming this could even be rolled out in a "big bang" situation). No problem. IT solves this problem easily with the seamless integration of EJBs, or SOA (as mentioned), or a modern plug and play ESB. There are multiple ESB vendors, each with their own advantages and disadvantages, so best practice advises organizations to create a working group comprised of all the stakeholders of the organization with the aim of reaching a consensus on the best product to use and the best way to move forward with this (it's more than likely the whole company will want to move to an ESB platform quickly because everybody likes to leverage and everybody likes things that are seamless). The team does not have to be very technical (the brochures and online PDFs explain things very well). Plus anybody inside the organization who thinks they need to participate should be involved. On another note, the programmer who decided to take the initiative and write this needs to have a one-on-one with his or her manager immediately. Even organizations that value proactivity will find problems with this: there is a strict violation of at least one of the basic principles of enterprise software. I don't see any constants defined and everybody knows that "the enterprisocity of an application is directly proportionate to the number of constants defined." http://thedailywtf.com/Articles/Enterprise_SQL.aspx http://thedailywtf.com/Articles/Enterprise_SQL.aspx This would never get promoted through change management. Why hasn't anyone in-house written an Eclipse plug-in for this yet?

Shorel 14y ago

At the very least we can have a FizzBuzz table with a FizzBuzz field and the following records: 3 5

serverascode 14y ago
Awesome! :)
dansari 14y ago
And access it using Hibernate.

xntrk 14y ago

There should also be other applications that do almost exactly the same thing but display the information in a slightly way but use a completly different code bases.

logn 14y ago
Interesting. I see a need for an adapter library and maybe some runtime configuration settings to choose your preferred, underlying fizz-buzz library.

logn 14y ago

Also it would be nice to configure the strategies with XML. Plus it would be super helpful to have jar plugins for new strategies. And seriously, there's no SOAP interface? This is hardly usable then. Also how the heck am I supposed to build this without Ant and batch and shell scripts to call Ant? Plus once you get ant files you can integrate it with Hudson. And package this as an EAR and add some user authentication too, probably single sign on. Also needs some log4j. And there are probably all sorts of unforeseen bugs and style issues, so it needs Findbugs and Checkstyle integrated.

podperson 14y ago
If it were truly Enterprise worthy it wouldn't be in github, but im perforce or, better yet, ClearCase.
ivanmaeder 14y ago
You're right. There are so many issues with this, on top of the ones mentioned. No serious enterprise-grade software today would do without leveraging Maven, annotations, IoC, AOP... And why isn't the UI decoupled from the business logic? What happens if one day another team in the organization needs access to Fizz Buzz? Writing their own Fizz Buzz would be extremely redundant (even dangerous), and if anybody changed the logic of Fizz Buzz it would have to be changed in multiple places at the same time: a simple change like making "Fizz" print every fourth time instead of every third time would make every Fizz Buzz team go through architecture, various change management meetings and at least one weekend deployment. And all of this would have to be coordinated to make sure it all happens within a single change window (assuming this could even be rolled out in a "big bang" situation). No problem. IT solves this problem easily with the seamless integration of EJBs, or SOA (as mentioned), or a modern plug and play ESB. There are multiple ESB vendors, each with their own advantages and disadvantages, so best practice advises organizations to create a working group comprised of all the stakeholders of the organization with the aim of reaching a consensus on the best product to use and the best way to move forward with this (it's more than likely the whole company will want to move to an ESB platform quickly because everybody likes to leverage and everybody likes things that are seamless). The team does not have to be very technical (the brochures and online PDFs explain things very well). Plus anybody inside the organization who thinks they need to participate should be involved. On another note, the programmer who decided to take the initiative and write this needs to have a one-on-one with his or her manager immediately. Even organizations that value proactivity will find problems with this: there is a strict violation of at least one of the basic principles of enterprise software. I don't see any constants defined and everybody knows that "the enterprisocity of an application is directly proportionate to the number of constants defined." http://thedailywtf.com/Articles/Enterprise_SQL.aspx http://thedailywtf.com/Articles/Enterprise_SQL.aspx This would never get promoted through change management. Why hasn't anyone in-house written an Eclipse plug-in for this yet?