its easy:
- Udssr did something wrong its very useful to this day for the us.
- Fukushima was done by an "western orientated" country.
- The fact that people say that chernobyl was worse then Fukushima is them not thinking. Fukushima was build in a area were this kind of accidents happen all the time.
- If Fukushima happened in China you would have more netflix tv shows about it how bad it was handled.
- Remember western media is going through an American lens. Just watch any main stream holy wood movie about war and think of it as US propaganda and you will see it everywhere
The USSR made several key decisions which made Chernobyl a far more dangerous and deadly situation and it's important that the decision making process is studied and understood to stop it from being repeated. As far as I'm aware Fukushima was a series of unlikely events when brought together ended in a disaster. The decision making process was fairly open to the public and open to international scrutiny and criticism.
Oh I have seen this story and was the one who caused this story when I was younger.
In a lot of cases the "new guy" thinks its an easy software and does it on his free time and thinks he did a great job.
In reality the specs are never 100% done correctly. The "new guy" misses some edge cases everybody but him knew because its just company knowledge. A lot of info in the specs was missing since they are not complete and so on.
This over the weekend never works in the long run. The ORM worked for all the happy path and written down cases but then you have cases were the ORM just is not good enough or fast. So you start to add strange code to work around the ORM. The same for the web framework or the validation lib.
To me the author of this comment sounds like the typical "Freelancer" coming in into a company knowing everything better then all the people and then leaving after a few months and now everybody else has to deal with his code.
It swings both ways though. I've seen plenty of older engineers dismiss the "new guys" effort and claim that everything had to be custom written, because there's no way a common framework like Django could cover their use case. The same type of engineer has never once worked with a common framework though, so they don't know what's included nowadays.
Turns out it's a lot easier to build on top of a common framework than do everything from scratch.
I think it's safe to say that ORM in Django is, in fact, better in all possible ways than an ORM someone at some company just wrote. Including speed and handling edge cases.
We only know what OP wrote and he doesn't sell himself as a genius but as someone who was competing with really, really bad ideas.
When building larger projects you should consider using a MVP (model-view-controller) pattern to separate your view code from the business logic. This way you can keep the view code simple, and the model code out from view-specific abstractions. This is called separation of concerns and is the primary way to build scaleable applications. I'll tackle this topic in detail along with a more complex demo application when Nue MVC project is released: https://nuejs.org/tools/#nue-mvc
Nue will be absolutely fantastic for scaling large applications and teams!
I'm starting to become a fan of your motivation (although count = 0 is still not ES6 classes variables). Good luck scaling it! Are you creating this framework out of your own necessity or just because it can be done? Any medium/large app using it to showcase?
reply