mgbmgb

There is also handy ripgrep-all, which wraps ripgrep and works with things like sqlite, docx, etc

from his wiki "now generally identifies himself as a composer rather than a software developer or engineer" - that's the goal!

Sys Admins -> DevOps -> SREs -> Platform engineers -> ?

What's next?

This is the way to go. With the recent push towards "more nimble teams" and high output / high velocity there is no place for QA teams to take days to review the releases, so you'd have to bake testability in.

Recent example how fairly small team in Meta built the Threads app https://engineering.fb.com/2023/09/07/culture/threads-inside...

I wouldn't dismiss the value of automated testing altogether, I think it really depends on the domain. I haven't seen a dedicated QA team in any of my recent companies and all the projects do just fine.

With that said, if I were to develop something high-profile I'd use a combination of both (and usually funding is not an issue for this types of projects)

Many teams are stuck in the outdated releases

You didn't have to call us out like that