You're reading the public-facing archive of the Category Theory Zulip server.
To join the server you need an invite. Anybody can get an invite by contacting Matteo Capucci at name dot surname at gmail dot com.
For all things related to this archive refer to the same person.
I was reading this article this morning: https://www.defensenews.com/breaking-news/2020/09/15/the-us-air-force-has-built-and-flown-a-mysterious-full-scale-prototype-of-its-future-fighter-jet/
I was really impressed with this claim:
The importance, Roper said, is that just a year after the service completed an analysis of alternatives, the Air Force has proven it can use cutting-edge advanced manufacturing techniques to build and test a virtual version of its next fighter — and then move to constructing a full-scale prototype and flying it with mission systems onboard.
“This is not just something that you can apply to things that are simple systems” like Boeing’s T-7 Red Hawk trainer jet, the first Air Force aircraft to be built using the “holy trinity” of digital engineering, agile software development and open architecture, Roper said.
“We’re going after the most complicated systems that have ever been built, and checked all the boxes with this digital technology. In fact, [we’ve] not just checked the boxes, [we’ve] demonstrated something that’s truly magical.”
The reason why I was surprised is that I thought this is what ACT is going after, more or less, and I didn't think it existed yet, at least to such a degree (assuming the claims are true). What do you think?
(Sorry for the bad formatting, I'm on mobile)
I don't know what kinds of techniques they used, but defense acquisitions is pretty messed up from an engineering process point of view, so you could definitely make 10X improvements by just having strong leadership and changing the incentives. You wouldn't need ACT to get 10X improvement, but you would probably need ACT to get 100X or 1000X improvements in process.
“I can’t make both ends of the life cycle go away; industry has to make a profit somewhere,” Roper said. “And I’m arguing in the paper that if you get to choose what color of money you use for future air superiority, make it research, development and production because it’s the sharp point of the spear, not the geriatric side that consumes so much of our resources today.”
if the AF program managers take this attitude, that spending money on R&D is more effective than spending it on sustainment and retrofitting, then it makes sense that they could build a new plane 10X faster.
This is very interesting. Maybe it's total bs military-industrial complex propaganda. Or maybe they really have done something magic, I'm totally open to that possibility
Matteo Capucci said:
built using the “holy trinity” of digital engineering, agile software development and open architecture
My usual thing when explaining ACT to everybody else is basically "take the approximate methodology and successes of the software industry and try to apply it to things that aren't software". The actual technical content of category theory is in service of that. So to me this is the most interesting line
(In particular ACT neighbours functional programming, but I always use analogies with OOP rather than FP)
Yeah I think that FP is "the application of CT to the study of programming languages" in FP you model programs as Homs in a category and denotational semantics are functors into Set. ACT is, to me, "the application of CT to ". Since CT is all about finding the right abstractions to make the math easy (ie. once you understand the definitions, the theorems are obvious), ACT should be about finding the right abstractions to make science easy. For example, monoidal categories are the right abstraction for modeling processes, and hypergraph categories are the right abstraction for modeling systems.
It seems that the magic wand for them was to br able to simulate the whole plane before construction (I believe this is the meaning of the expression 'digital engineering'). Then I don't know what open architecture is. Maybe a principle in software engineering? Thereby they managed to decompose the task by having the right approach to the overall software development task.
I think that open architecture means something like avoiding vendor lock in and using generic parts instead of specialized ones whenever possible.