4 ms·
My team at work has been studying CT. Every week we read one chapter of Category Theory for Programmers. Then every Thursday we discuss the chapter and our prob
by adamch 8y ago
My team at work has been studying CT. Every week we read one chapter of Category Theory for Programmers. Then every Thursday we discuss the chapter and our problem solutions together.
It's been very fun. Our discussions help forge links between the category world and our day-to-day programming. We're only 3 chapters in, so I can't say it's given me some huge insight into programming. But as we move from Go to Rust/Typescript, it gives us a useful way to think about the correctness of our programs and a useful shared vocabulary for talking about types in a language-agnostic way.
- kgc 8y agoWhy are you moving from Go to Rust/Typescript?
- stuxnet79 8y agoThis is fascinating. I would love to set up something like this at my current workplace. How much time do you allocate during Thursdays to review?
- crimsonalucard 8y agoMy workplace is the exact opposite. They scoff at types let alone categories. One guy literally told me, and I kid you not, that he doesn't need type checking, all he needs is to be "careful." We don't learn things together, instead what happens is if I present something new, another person stays silent looks it up at home on google and comes to work the next day pretending he's an expert on the topic. It's toxic.
- zmix 8y agoWow, that's must be some real uncompetitional place. Nobody likes to be called out on anything!