183 karma · joined October 13, 2020
I still don't understand what the benefit of those standard text blocks is.
If people are excluded from services, there should be rational reasons for it and these reasons should be social consensus.
That's your style of argumentation and I doubt it brings us far.
It's tempting to just linearly project the status quo into the future but looking at this graph here (https://cdn.howmuch.net/articles/61-c98f-5e41.jpg) it is highly possible that IT/Tech will play a less dominant role in 2067 than today including that the next big corporations potentially grow and rise in completely different areas than SF and Silicon Valley.
Let's say a software engineer writes a C++ application that stores documents in an inverted index and he also takes care that the program is stored in a docker container and deployed to Elastic Kubernetes Service via Jenkins. Good luck understanding your IDE, C++, Tries/Radix trees, docker, Jenkins and EKS "all the way down to the metal".
It may be possible for a small subset of those but if the expectation for great engineers really is to deeply understand "all that they touch", I wonder how many can keep up with this standard.
How are those number of any help if I can just arbitrarily select those that are in my favor and ignore the rest?
> Increased user engagement 27% by refactoring our front-end experience in React.
Was it really your refactoring that caused those 27% or something else? Did your refactoring had any negative side effects that you are not talking about? How do I know it was really 27 and not just 2%?
Numbers are useless without context and contexts are often company-specific or purely a matter of opinion.