liveBook · Manning

Framework

As explained in Think Like a CTO

A reusable software foundation that provides conventions and supporting components for building applications or automation systems.

A framework is a reusable set of libraries or standards built on a programming language to handle recurring tasks and establish development conventions. It usually covers more ground than the underlying language, making it productive but potentially restrictive. section 8.8

Assess a framework as both a technical choice and a long-term organizational commitment:

  • Account for existing investment in developers, deployment processes, support knowledge, and application code before switching. section 8.8
  • Evaluate its sponsor, maturity, community activity, educational presence, and hiring market rather than chasing novelty. section 8.8.2
  • Balance framework expertise with underlying language expertise, since specialists may find another framework in the same language difficult. section 8.8
  • Treat stability and client outcomes as more important than championing the newest technology. section 8.8.2

Framework choices in practice

Java Enterprise Standard and Spring provide frameworks on Java, while ReactJS supports JavaScript and Express.js supports Node.js. Each illustrates how a framework supplies broader conventions and reusable capabilities than its host language. section 8.8

How Think Like a CTO covers it

How deep it goes
Defines framework scope, explains migration consequences, and supplies selection criteria, but stops short of implementation detail.
Examples
Uses Java Enterprise Standard, Spring, ReactJS, and Express.js to illustrate framework relationships with Java, JavaScript, and Node.js.
What it assumes
Assumes familiarity with programming languages while distinguishing framework expertise from broader language expertise.
What you can do after
Evaluate frameworks against maturity, sponsorship, community, educational adoption, hiring availability, and switching costs.
How it connects
Connects frameworks with programming languages, libraries, standards, deployment, support, hiring, open source, and technology maturity.

Also explained in

Compare how 5 books explain framework →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.