I have been reading Spivak’s book ‘Category Theory for the Sciences’ on-and-off for the last 18 months during vacations as some of my ‘holiday reading.’ I’ve wanted to learn something about category theory for a while, mainly because I feel it’s something that looks fun and different enough to my day-to-day activity not to feel like work. I found Spivak’s book on one of my rather-too-regular bookshop trips a couple of years ago, and since it seemed like a more applied introduction, I thought I’d give it a try. This blog post combines my views on the strengths of this book from the perspective of a mathematically-minded engineer, together with a set of notes on the topic which might be useful for me – and maybe other readers – to refer back to in the future.

The book has a well-defined structure. The first few chapters cover topics that should be familiar to applied mathematicians and engineers: sets, monoids, graphs, orders, etc., but often presented in an unusual way. This sets us up for the middle section of the book which presents basic category theory, showing how the structures previously discussed can be viewed as special cases within a more general framework. The final chapters of the book discuss some topics like monads that can then be explored using the machinery of this framework.

**Set**

Chapter 3 covers the category of sets.

One of the definitions here that’s less common in engineering is that of coproduct. The *coproduct* of sets and , denoted is defined as the disjoint union of and . I first came across disjoint union as a concept when doing some earlier holiday reading on topology. We also here get the first experience of the author’s use of informal ‘slogans’ to capture the ideas present in more formal definitions and theorems: “any time behavior is determined by cases, there is a coproduct involved.” I really like this approach – it’s the kind of marginalia I usually write in books myself, but pre-digested by the author!

The notation is used for the set of functions from to , which we are encouraged to refer to as morphisms, all without really explaining why at this stage – it of course all becomes clear later in the book.

To give a flavour of the kind of exercises provided, we are asked to prove an isomorphism . This reminds me of digital circuit construction: the former corresponds to a time-multiplexed circuit capable of producing outputs from with inputs from either or , together with an identifier for which (to feed a multiplexer select line); the latter corresponds to two circuits producing both the outputs rather than just the selected one.

The *fibre product*, , given functions and is defined as the set . Any set isomorphic to this fibre product is called a *pullback* of the diagram .

The *fibre sum,* , given functions and is the quotient of by the equivalence relation generated by and for all . A *pushout* of and over is any set which is isomorphic to .

A good intuitive description in the text is to think of the fibre sum of and as gluing the two sets together, with as the glue. A nice example from one of the exercises is , , a singleton set, defined by . Then we’re left with , where is an element corresponding to the collapsing of all negative elements in to a single point.

The familiar notions of surjective and injective functions are recast as monomorphisms and epimorphisms, respectively. A function is a *monomorphism* if for all sets and pairs of functions , if then . A function is an *epimorphism* if for all sets and pairs of functions , if then . By this time in the book, we get the hint that we’re learning this new language as it will generalise later beyond functions from sets to sets – the chapter ends with various slightly more structured concepts, like set-indexed functions, where the idea is always to define the object and the type of morphism that might make sense for that object.

**Monoids, Groups, Graphs, Orders & Databases**

In Chapter 4, the reader is introduced to several other structures. With the exception of the databases part, this was familiar material to me, but with slightly unfamiliar presentation.

We learn the classical definition of a monoid and group, and also discuss the *free monoid* generated by a set as being the monoid consisting of set of lists of elements of , with the empty list as the identity and list concatenation as the operation. We discuss the idea of a monoid action on a set , i.e. a function associated with the monoid having the properties for any , where is the identity, and , where and are any elements of , is any element of , and is the monoid operation. The discussion of monoids is nice and detailed, and I enjoyed the exercises, especially those leading up to one of the author’s slogans: “A finite state machine is an action of a free monoid on a finite set.”

Graphs are dealt with in a slightly unusual way (for me) as quadruples of a set of vertices , a set of arrows , a functions , mapping each arrow into its source and destination vertex. This corresponds then to what I would call a *multigraph*, as parallel edges can exist, though it is called a graph in the book.

For each of the structures discussed, we finish by looking at their morphisms.

As an example, let and be monoids (the tuple is of the set, identity element, and operation). Then a monoid homomorphism is a function preserving identity and operation, i.e. (i) and for all .

Similarly, for graphs, graph homomorphisms for and are defined as pairs of functions and preserving the endpoints of arrows, i.e. such that the diagrams below commute.

Order morphisms are similarly defined, this time as those preserving order.

Thus we are introduced to several different (somewhat) familiar mathematical structures, and in each case we’re learning about how to describe morphisms on these structures that somehow *preserve the structure*.

**Categories, Functors, and Natural Transformations**

Things really heat up in Chapter 5, where we actually begin to cover the meat of category theory. This is exciting and kept me hooked by the pool. The unusual presentation of certain aspects in previous chapters (e.g. the graphs) all made sense during this chapter.

A category is defined as a collection of various things: a set of objects , a set of morphisms for every pair of objects and , a specified identity morphism for every object , and compositions . To qualify as a category, such things must satisfy identity laws and also associativity of composition.

Examples of the category of Monoids, of Groups, of Sets, of Graphs, of Pre-Orders, etc., are explored. Isomorphisms between objects in a category are carefully defined.

*Functors* are introduced as transformations from one category to another, via a function transforming objects and a function transforming morphisms, such that identities and composition and preserved. Functors are then used to rigorously explore the connections between preorders, graphs, and categories, and I finally understood why the author had focused so much on preorders in the previous chapters!

Things started to take a surprising and exciting turn for me when the author shows, via the use of functors, that a monoid is a category with one object (the set of the monoid becomes the morphisms in the category), and that groups can therefore be understood as categories with one object for which each morphism is an isomorphism. This leads to a playful discussion, out of which pops groupoids, amongst other things. Similar gymnastics lead to preorders reconstituted as categories in which hom-sets have one or fewer elements, and graphs reconstituted as functors from a certain two-object category to . Propositional logic is re-examined from a categorical perspective, though I suspect this is just scratching the surface of the interplay between category theory and logic, and I’d love to read more about this. For me, this was a highlight – that by playing with these definitions and trying things out, all these wonderful familiar structures arise.

The final part of this chapter deals with natural transformations. Just as functors transform categories to categories, natural transformations transform functors to functors. Specifically, a natural transformation between functor and is defined as a morphism (in ) for each object in , such that the diagram below commutes for every morphism in .

I think this section on natural transformations is where the huge number of exercises in the book really came into its own; I doubt very much I would’ve grasped some of the subtleties of natural transformations without them.

We learn about two kinds of composition of natural transformations. The first combines two natural transformations on functors , say one and one to obtain a natural transformation . The other combines a natural transformation between functors with one between functors , to produce one, .

An equivalence relation – weaker than isomorphism – is introduced on categories as a functor such that there exists a functor and natural isomorphisms and . This seemed odd to me — the lack of insistence on isomorphism for equivalence — but the examples all make sense. More importantly it is shown that this requirement is sufficient for the on-homomorphism part of the functor to be bijective for every fixed pair of objects in , which feels right. I think my understanding could benefit from further interesting examples of *usefully* equivalent but non-isomorphic categories though – suggestions welcome!

**Limits and Colimits**

Chapter 6 is primarily given over to the definitions and discussion of limits and colimits, generalising the ideas in to other categories. The chapter begins by looking again at product and coproduct. As an example, for a category , with objects , a *span* is defined as a triple where is an object in and and are morphisms in . A *product* is then defined as as span on and such that for any other span on and , there exists a unique morphism such that the following diagram commutes. Again, I rather like the author’s slogan for this: “none shall map to and except through me!”

The chapter then further generalises these ideas to the the ideas of limit and colimit. This section was a step up in abstraction and also one of the least “applied” parts of the book. It has certainly piqued my interest – what are limits and colimits in various structures I might use / encounter in my work? – but I found the examples here fairly limited and abstract compared to the copious ones in previous chapters. It’s in this chapter that universal properties begin to rear their head in a major way, and again I’m still not totally intuitively comfortable with this idea – I can crank the handle and answer the exercises, but I don’t feel like I’m yet at home with the idea of universal properties.

**Categories at Work**

In the final section of the book, we first study adjunctions. Given categories and , an *adjunction* is defined as a pair of functors and together with a natural isomorphism whose component for , is . Several preceding results and examples can then be re-expressed in this framework, and understood as examples of adjunctions. Adjuctions are also revisited later in the chapter to show a close link with monads.

Categories of functors are discussed, leading up to a discussion of the Yoneda lemma. This is really interesting stuff, as it seems to cross huge boundaries of abstraction. Consider a category . Spivak first defines a functor sending objects in to the set and similarly for morphisms. This is then used in the following theorem:

Let be a category, be an object, and be a set-valued functor. There is a natural bijection .

This looks super weird: the right-hand side is just a plain old set and yet the left hand-side seems to be some tower of abstraction. I worked through a couple of examples I dreamt up, namely (the category with one object) with mapping that object to an arbitrary set, and with and convinced myself this works just fine for those two examples. Unfortunately, the general proof is not covered in the book – readers are referred to Mac Lane – and while some discussion is provided regarding links to databases, I felt like I need a proof to properly grasp what’s going on here under the hood.

Monads are then covered. I’ve briefly seen monads in a very practical context of functional programming, specifically for dealing with I/O in Haskell, but I’ve never looked at them from a theoretical perspective before.

A *monad* on (monads are only defined in the book on , for reasons not totally apparent to me) is defined as a triple consisting of a functor , a natural transformation , and natural transformation such that the following diagrams commute:

I found this discussion enlightening and relatively straight-forward. Firstly, exception monads are discussed, like `Maybe`

in Haskell, and a nice example of wrapping sets and their functions into power sets and their functions, for which I again enjoyed the exercises. Kleisli categories of monads are defined, and it then becomes apparent why this is such a powerful formalism to think about concepts like program state and I/O.

The *Kleisli category * of a monad on is defined as a category with objects and morphisms . Identity is in is exactly in Â and composition of morphisms and in is given by in . You can intuitively see the ‘baggage’ of being carried through in yet hidden from view in .

Finally, the book ends with a (very) brief discussion of operads. I’ve not come across operads before, and from this brief discussion I’m not really sure what they ‘buy’ me beyond monoidal categories.

**General**

The exercises are copious and great, especially in the earlier chapters. They kept me engaged throughout and helped me to really understand what I was reading, rather than just think I had. In the later exercises there are many special cases that turn out to be more familiar things. This is both enlightening “oh, an X is just a Y!” and frustrating “yeah, but I want to see Xs that aren’t Ys, otherwise what’s this all heavyweight general machinery for?” I guess this comes from trying to cover a lot of ground in one textbook.

I am struck by just how much mental gymnastics I feel I had to go through to see mathematical structures from the “outside in” as well as from the “inside out”, and how category theory helped me do that. This is a pleasing feeling.

The slogans are great and often amusing, e.g. when describing a functor from the category of Monoids to the category of Sets, “you can use a smartphone as a paperweight.”

The book ends rather abruptly after the brief discussion of operads, with no conclusion. I felt it would be nice to have a summary discussion, and perhaps point out the current directions the field of applied category theory is taking.

Overall, this book has been an enlightening read. It has helped me to see the commonality behind several disparate mathematical structures, and has encouraged me to look for such commonality and relationships in my own future work. Recommended!