I develop embedded software. I use make all the time.

I don't want to .. but people keep using it because it's simpler than other build systems.

Many UI tools based on eclipse use make under the hood.

Many recipes used by Yocto just use make to build the software and then install the output somewhere.

It all depends what you're trying to build and where you work.

You'll never guess what we talk about later on in the unit. Spoiler: exactly that!

It notionally focuses on make but the concepts apply much more broadly than the one specific tool

makefiles and shellscripts are still knocking around in systems programming world, which i think is the world OP comes from

The schedule is generated from a Python script, but doesn't involve YAML

looks sweet. gonna look into this.

It seems to be an introduction, so just covering the basics is ok. We're still very close to the IT stone age and the IT industry is still quite archaic, so teaching archaic basics isn't that bad. In a lot of areas it's still best to just write your own tools from scratch...

It's a "teach people how to teach themselves to fish" class

this is meant for freshman/sophomore cs students i think its a reasonable start

> All this should be part of "development tooling".

that's not really development, that's operations.