It's not meant to be super in-depth, more so aimed at understanding the high-level details and motivations of k8s. I figured that the best way to do that was to pose each chapter as an evolution of a startup experiencing a problem, and showing how k8s solves that problem, by treating the reader like the technical manager in the situation.
I'm not a k8s expert, so I can't definitively say it's "my course" but I will say, we're at an interesting time where you can contribute authorship to something and learn it at the same time. I'm spending more time steering the output the more I learn things, so it's not just slop.
Sure, but you can build an agentic system which verifies outputs and fact corrects, with probably better accuracy than a human would.
As well, if people were a bit less anti-AI then maybe we can get disclaimers that things are written by AI that don't immediately torpedo any value the writing has.
This is what I'm grappling with myself. I'm building out a bunch of materials for things I'm learning and feel like others can benefit from my trudging through and correcting or getting AI clarification.
I think we're quickly getting to a point where AI is going to be able to do a better job teaching things than humans can (especially stuff with heavy associations with paper/screens, like programming and math). AI can augment for personal styles and spin up whole entire educational widgets on demand. Human's can't scale like that.
I don't think there is educational worth in an novice publishing the outputs from their chats.
I think there is some worth in having someone knowledgeable using AI to generate educational material, although it will be in my opinion, of less use than if that knowledgeable person wrote the material by hand.
For example, many professors in universities have started generating slides or even assignments using AI. A knowledgeable teacher who cares about their students outcomes can generate better material.
Well, it's pretty obviously slopped together, which I think the commenter makes clear with "it's nonsensical."
The problems are obvious. The OP is not even toning down the 100 window height's worth of battle tabular data, it's pretty clear that OP just pulled the output from a simple claude code output without any taste or editorialization.
So I think it's pretty constructive. This is a cool map, I thought of doing something similar myself (for Alexander's conquest). It just needs to be de-slopped.
It's not meant to be super in-depth, more so aimed at understanding the high-level details and motivations of k8s. I figured that the best way to do that was to pose each chapter as an evolution of a startup experiencing a problem, and showing how k8s solves that problem, by treating the reader like the technical manager in the situation.
I'm not a k8s expert, so I can't definitively say it's "my course" but I will say, we're at an interesting time where you can contribute authorship to something and learn it at the same time. I'm spending more time steering the output the more I learn things, so it's not just slop.
reply