liveBook · Manning

Hardware

As explained in Think Like a CTO

Physical computing equipment and connected electronic devices that support or participate in software and network operations.

Hardware is the physical equipment that supports an organization’s systems, including servers, network equipment, and connected devices. Managing it means planning capacity, maintaining components, and accounting for security. Responsibilities vary: an organization may run servers in its office or in a remote data center, while devices such as printers may sit outside the CTO’s usual remit but still need IT attention. section 8.3.2 section 13.1 section 12.1.3

Owning servers makes capacity a purchasing decision. Too little hardware can strain systems during busy periods; too much can sit unused. Buying, delivering, provisioning, and installing servers can take weeks and requires capital approval. A private cloud can reallocate existing capacity more quickly, but it cannot create capacity beyond the hardware available. section 8.3.2

Preparing for a promotion

An online promotion is expected to increase demand. If spare capacity exists in a private cloud, internal servers could be turned off temporarily and that capacity assigned to frontline servers. Before relying on the plan, check what the internal systems can give up and whether the total hardware pool is large enough for the spike. section 8.3.2

For hardware under your control, make maintenance a routine rather than a response to failure:

  • Keep an inventory of each asset’s manufacturer, model, purchase and installation dates, next service date, support details, maintenance log, location, and login details. A spreadsheet may be enough. section 13.1
  • Use expected component lifetimes to schedule servicing and source replacements early. Fans and drives can fail sooner than expected, while parts for older equipment can become difficult to find. section 13.1 section 13.6
  • Check that support contracts cover the help you need, and monitor both the client’s experience and internal system performance for early signs of trouble. section 13.6

Hosting adds physical requirements: servers need power, cooling, and a network connection whether they sit in an office or a data center. Security extends beyond servers. Printers, scanners, TVs, routers, and switches may need update checks, even when some other devices update automatically. Treat every network-connected device as a potential entry point: manage its passwords and security updates, record checks in the asset log, and keep the production network isolated from back-office devices. section 8.3.2 section 12.1.3

A useful first check is practical: Which equipment is under your control, where is it, when is it due for service, and can you obtain a replacement before it fails? Then ask whether current capacity and support arrangements are adequate for the next period of demand. section 8.3.2 section 13.1 section 13.6

How Think Like a CTO covers it

How deep it goes
Develops operational decisions and maintenance checks, without descending into component repair or hardware configuration instructions.
Examples
Uses a promotion-driven capacity spike, office and data-center hosting, aging replacement parts, and network-connected office devices.
What it assumes
Defines on-premises provisioning while assuming familiarity with servers, network equipment, and organizational IT duties.
What you can do after
Operate/configure it by inventorying equipment, planning service and replacements, checking support coverage, and reviewing connected-device security.
How it connects
Links hardware to on-premises hosting, private clouds, asset inventory, preventive maintenance, monitoring, and network security.

Also explained in

Compare how 3 books explain hardware →

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.