Earlier quoted context omitted.
While Enterprise is always the go to for things like this, I think any time non technical people get involved in technical decisions the fun time begins. Just today I was told that I wasn't allowed to implement something in python just because it's "a scripting language"
If theoretically a developer chose to develop something in Python in my company that would be an automatic no. There are multiple reasons: You would add an another language to support from the development to the operational support like monthly security updates. And that's a major risk and most companies won't take it. If you leave the company then the company may have potentially unsupported app with noone capable o…
FizzBuzz Enterprise Edition
41–50 of 72 posts
Re: FizzBuzz Enterprise Edition
#42Re: FizzBuzz Enterprise Edition
#43Re: FizzBuzz Enterprise Edition
#44Where/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 does need to apply all these abstractions. Are these skills only attainable from year…
Re: FizzBuzz Enterprise Edition
#45Re: FizzBuzz Enterprise Edition
#46Event based programming in technology like stack is more appropriate for this kind of problem domain...
Re: FizzBuzz Enterprise Edition
#47Re: FizzBuzz Enterprise Edition
#48Re: FizzBuzz Enterprise Edition
#49The 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.
Re: FizzBuzz Enterprise Edition
#50On a more serious note. 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 enterpire - 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? Asking this as a juni…
You have to understand that the context in which this kind of architecture is needed is high-turnovers environments. Basically, in the 90's, managers at big corps - IBM, ATOS, etc... asked the question : "how can we fire a whole team, hire a whole another team and put them in front of the fired team's code and have them be productive in a few days ?".
The answer to this is to heavily compartimentalize everything. Your manager tells you that you must implement a very particular behaviour in a very particular class ; you aren't meant to know what's happenning in other parts of the system.