While i agree with the principal statement, this also requires two things to work:

First: The scope should be defined properly, so people can contextualize what they are actually doing and reviewing.

Second: If the scope is subject to change, or parts of it are unclear, there needs to be room to consider, develop and try different variants

This is were good management is crucial, which includes giving breathing room at the start. What we tend to experience is the expectation of already good detailed results, that can be finalized but still work if things change significantly.

Please excuse my ignorance, but what is grep, what are the do’s and dont’s of logging and why are people here talking about having an entire team maintain some pipeline just to handle logs?

Friendly reminder to every CEO that this could have been a situation where a disgruntled employee accidentally fucks up the off site backup too.

You can brute force most of higher education with memorization learning still. If you work twice as hard on your thesis for the six month or so you have to write it, you can make it seem like you understood most of it, even if you didn’t. If in doubt you can always try to make a literature research thesis and just write down what most authors talked about, even if you don’t understand what it is.

How do you know that what you consider “literal monkey could do it” is not something many other people struggle with?

As a kid i struggled a lot understanding, why people didn’t get the math we dealt with in high school, but i lacked behind in languages, not getting that you have to study for them and can’t just “get” them like with math.