It looks like you're new here. If you want to get involved, click one of these buttons!

- All Categories 2.3K
- Chat 500
- Study Groups 19
- Petri Nets 9
- Epidemiology 4
- Leaf Modeling 1
- Review Sections 9
- MIT 2020: Programming with Categories 51
- MIT 2020: Lectures 20
- MIT 2020: Exercises 25
- MIT 2019: Applied Category Theory 339
- MIT 2019: Lectures 79
- MIT 2019: Exercises 149
- MIT 2019: Chat 50
- UCR ACT Seminar 4
- General 68
- Azimuth Code Project 110
- Statistical methods 4
- Drafts 2
- Math Syntax Demos 15
- Wiki - Latest Changes 3
- Strategy 113
- Azimuth Project 1.1K
- - Spam 1
- News and Information 147
- Azimuth Blog 149
- - Conventions and Policies 21
- - Questions 43
- Azimuth Wiki 713

Options

in Chat

Hi everyone,

I'm a software developer with a background in philosophy and computer science. I became interested in Category Theory a few years ago because I liked the elegant looking diagrams, but I really became hooked when I understood what a pullback was. My primary references have been Schanuel and Lawvere (2009) and Awodey (2006). My main goal with this course is to build a wider repertoire of examples that I can use to ground my intuitions that have been floating around since I began. I'm also really interested in toposes and categorical logic (I'm not sure if any of that will be covered in the course, but it's fascinating to me).

## Comments

Welcome to the course, Dennis! Where do you live or work, if it's not too nosy to ask?

We will definitely talk a bit about topos theory in the course. Chapter 3 of our textbook

Seven Sketchesis about databases, treating them as functors from a category to \(\mathbf{Set}\). The category of all functors from some category to \(\mathbf{Set}\), and natural transformations between these, is a very nice example of a topos.Chapter 7 is more explicitly about topos theory: it's titled "Sheaves, toposes and internal languages". This arises from David Spivak's use of topos theory to help redesign the air traffic control system - a project he did with NASA, which unfortunately has not been carried to completion.

(That is, nobody is currently planning to actually specify the behavior of the air traffic control system using the internal language of a topos, even though it could be a good idea.)

`Welcome to the course, Dennis! Where do you live or work, if it's not too nosy to ask? We will definitely talk a bit about topos theory in the course. Chapter 3 of our textbook _[Seven Sketches](http://math.mit.edu/~dspivak/teaching/sp18/7Sketches.pdf)_ is about databases, treating them as functors from a category to \\(\mathbf{Set}\\). The category of all functors from some category to \\(\mathbf{Set}\\), and natural transformations between these, is a very nice example of a topos. Chapter 7 is more explicitly about topos theory: it's titled "Sheaves, toposes and internal languages". This arises from David Spivak's use of topos theory to help redesign the air traffic control system - a project he did with NASA, which unfortunately has not been carried to completion. (That is, nobody is currently planning to actually specify the behavior of the air traffic control system using the internal language of a topos, even though it could be a good idea.)`

Thanks for the welcome John. I currently live and work in Austin (my BSc is from UT).

I'm excited to learn about the categoric perspective on databases! From what you've said, it sounds like a nice way to grasp what "representable" in representable functor means.

Also, the topos-theoretic air traffic control system sounds amazing.

`Thanks for the welcome John. I currently live and work in Austin (my BSc is from UT). I'm excited to learn about the categoric perspective on databases! From what you've said, it sounds like a nice way to grasp what "representable" in representable functor means. Also, the topos-theoretic air traffic control system sounds amazing.`