Re:Why I No Longer Use MVC Frameworks
by ryanSrich on Tuesday February 16, 2016 @03:04AM
(#11108484)
Designers coding is fine. Designers programming is not.
[ Parent
| on HN ]
Careful on that line as some of us become programmers and are quite apt at playing both roles when needed.
In reality separation of concerns is a luxury only afforded to larger teams and orgs.
If you have the people, do it. If you don't, you're in for a bad time concerning yourself with it.
Granted the html in Java is just straight idiocy, and my point refers to far less insidious mixings.
Re:Why I No Longer Use MVC Frameworks
by bryanrasmussen on Tuesday February 16, 2016 @05:16AM
(#11108923)
separation of concerns in your organization is a luxury.
separation of concerns in your codebase is a necessity.
I was about to write the same thing, so true. Even if you are working alone at the moment, doesn't mean that you should glue everything together and end up with spaghetti code.
I was more of referring to the level of separation.
I feel like a designer would have the opposite sentiment.
Re:Why I No Longer Use MVC Frameworks
by rawTruthHurts on Tuesday February 16, 2016 @04:37AM
(#11108789)
*Take with a pinch of salt