Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

HTML, css, JS (jquery) have stable APIs, when new developers come they don't have to learn something new.

If your code degrade over time, sorry to tell you, a framework won't solve the problem.

If you have coders that don't care about maintainability of code correction, code organization in whatever technology, they won't care about what you wish.

As usual, they won't take the time to learn the frameworks, will diverge, and you are back to square one with no code that can be salvaged or reused. (at least with vanilla techs you may salvage stuffs)

I think you use frameworks to solve the wrong problems here: you are probably the problem by trying to ditch the lack of real engineering skills in IT (not the letter of engineering. The spirit: making things that are correctly built and are reliable over time... like a plane).



Well I think we'll just have to disagree here. I think you are patently wrong if you really believe you can keep up maintainability of a largish codebase by appealing to craftmanship in a real-world company.

This is all nice and well in academics and start-ups but some years down the road, your code is going to be a mess. Frameworks, especially opinionated frameworks are a tremendous help. Coding in jQuery or native JS without some prodding is at best an accident waiting to happen.


In my experience, the only reason the code is going to be a mess is because the company hired a bunch of junior developers and gave them "Architect" titles. I can show time and time again that with a team of seasoned engineers the code not only isn't a mess but in fact there is less code that does more, and does it more efficiently.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: