3 ms·

Pretty archaic. It stops just after version control, code builds and testing. Nothing on devops - deployments, kebernetes, containers, monitoring, release manag

by zkmon 10mo ago

Pretty archaic. It stops just after version control, code builds and testing. Nothing on devops - deployments, kebernetes, containers, monitoring, release management, environments (prod, non-prod) etc. All this should be part of "development tooling".

badatlife 10mo ago
this is meant for freshman/sophomore cs students i think its a reasonable start
adornKey 10mo ago
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...
znpy 10mo ago
> All this should be part of "development tooling". that's not really development, that's operations.
- zkmon 10mo ago
  The article is not about "development". It is about "development tooling".
- bitwize 10mo ago
  You're not really a professional in 2025 if you do not approach development with a devops mentality, with due consideration given to concerns like deployment, scaling, and observability.
  - znpy 10mo ago
    i've been in the industry long enough to know that the devops promise that developers can do operation is essentially fantasy. i mean don't get me wrong, some statistical outliars certainly can, or they can as long as they outsource a lot of the actual work (look at heroku/vercel and similar platforms). or if they have an infinite budget. but at the end of the day software development and system administration are two very different skillsets in the practical side of the field of computer science. particularly nowadays, you'd be surprised how many engineers don't know shit about what's outside their favourite language runtime. i see developers reinventing the wheel almost every month because they're unfamiliar with many of the underlying linux/unix systems capabilities.
deleted 10mo ago
[deleted]
tekknolagi 10mo ago
It's a "teach people how to teach themselves to fish" class

by zkmon 10mo ago

badatlife 10mo ago

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

adornKey 10mo ago

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...

znpy 10mo ago

> All this should be part of "development tooling". that's not really development, that's operations.

zkmon 10mo ago
The article is not about "development". It is about "development tooling".
bitwize 10mo ago
You're not really a professional in 2025 if you do not approach development with a devops mentality, with due consideration given to concerns like deployment, scaling, and observability.
- znpy 10mo ago
  i've been in the industry long enough to know that the devops promise that developers can do operation is essentially fantasy. i mean don't get me wrong, some statistical outliars certainly can, or they can as long as they outsource a lot of the actual work (look at heroku/vercel and similar platforms). or if they have an infinite budget. but at the end of the day software development and system administration are two very different skillsets in the practical side of the field of computer science. particularly nowadays, you'd be surprised how many engineers don't know shit about what's outside their favourite language runtime. i see developers reinventing the wheel almost every month because they're unfamiliar with many of the underlying linux/unix systems capabilities.

deleted 10mo ago

[deleted]

tekknolagi 10mo ago

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