Web Frameworks in a Nutshell
Post from January 24, 2015 (↻ November 22, 2017), filed under Web Development.
In the book, I share much of my experience architecting, developing, and maintaining web frameworks, as I’ve done for Google, Aperto, and GMX (though there we hadn’t called them frameworks). While frameworks come and go there are some principles that make them high quality, last longer, and easier to work with.
A recap taken from the book, which really is short and sweet for I didn’t set out to write an 800-page encyclopedia, as follows.
Professional web development is about quality. Quality is not easy to define, but one part of it is tailored code. External frameworks, if without customization options, are impossible to tailor for users and a pain to tailor for developers. Internal frameworks are much easier to handle and generally the way to go. Good frameworks aim for highest quality, are tailored, usable, and extensible. Framework users should follow the documentation and not overwrite framework code. Framework developers should have principles, a prototype, quality management tools, a maintenance plan, and healthy interest in documentation. And still, things can go wrong.
So much for a first impression.
I’ll keep you updated.
About the Author
Jens Oliver Meiert is a technical lead and author (sum.cumo, W3C, O’Reilly). He loves trying things, including in the realms of philosophy, art, and adventure. Here on meiert.com he shares and generalizes and exaggerates some of his thoughts and experiences.
If you have any thoughts or questions (or recommendations) about what he writes, leave a comment or a message.