1,043 karma · joined February 1, 2017
Source: I am an employee
Imagine waking from a coma after 10 or 20 years and reading this in the news.
In other words: an introvert. There seems to be a widespread misconception that introversion means being "shy" and not talking to people, when in reality it is more about where you draw energy from. The result is tons of people self-identifying as "extroverted introverts"[1], presumably in an attempt to signal that they are not totally devoid of social skills, when in reality introversion has nothing to do with that.
[1] When I was single I saw this surprisingly often in online dating profiles. Interestingly, for all the many people I've seen identify this way, I've never seen a single person self-identify as the opposite: an "introverted extrovert".
> a willingness to abide by the rules and procedures of a complex organization, even when they don't make much sense or directly contribute to the core competency. It shows a willingness to submit to authority, a willingness to get often arbitrary work done on schedule with acceptable quality, and other traits and experiences that matter a great deal for becoming a functional employee in a corporate workplace.
This is one of the main theses of the book "Disciplined Minds" by Jeff Schmidt. I highly recommend it if you're interested in following this line of thought further.
I wonder if this is a case for emphasizing that "one size fits all" doesn't work in dieting, either. It seems likely that satiety for various food sources might vary based on biology and lifestyle too.
After one year of moderate effort I too got the promotion, with almost no pay raise. The problem of giving everyone a certain title is you basically completely dilute any meaning or status it conveys.
I soon went on to FANG and am now a regular ol' Software Engineer again. But I'd much rather be bottom rung at a top company than a "Senior" whatever at a company where it means nothing.
Amen. This seems to be one of the primary problems with the tech industry today. Is building another convenience app for X really a good use of time for bright and talented individuals when there are so many pressing problems to solve? But I guess as long as the money is flowing there will be people willing to do these things.
I'd love to figure out how I can apply my software engineering skills toward something more "worthwhile", while also making decent money. It's hard when at this point many of the real pressing problems for humanity to me don't seem to really involve software as a primary component. I feel like we've reached diminishing returns with software. But maybe I'm just not looking in the right places.
The problem IMO is that at least in English, "god" is simply too widely-used and inexactly-defined. Certain religions don't have any exclusive claim to the word; it isn't unique enough. So I'm not convinced of this argument. I'll spell it how I want, because in my mind the concept of "god" is intractable and has no well-defined meaning to begin with, so it can't be a proper noun.
So true. I feel like a large portion of all the conflict that arises between parents and children stems from a failure to understand this.
> Homophily is discrimination
I think you are onto an interesting point here. I do not dispute the importance of diversity/inclusiveness/fairness, but there is an uncomfortable truth that these things directly conflict with the factors that facilitate close bonding in groups. When you force an environment to be absolutely non-exclusive in every possible way, it becomes rather sterile somehow. I don't doubt that the homogeneity of my old company was one of the reasons we were able to become so close. I'm not necessarily suggesting companies should become more exclusionary, just reflecting on the tradeoffs involved.
"It is the time you have spent on your system that makes it so important", the man added, "and when you lost sight of why it made sense to spend time on it, when it became a game of pride, it caused more grief than relief.
"Developers have often forgotten this truth; If you lose sight of things, working on your system becomes its own problem, and the most effective solution is to get rid of the system, given it's the problem."
This story is easily one of the best depictions of the software engineering profession I've ever come across. I originally got hooked on programming because of the thrill of solving "intricate problems"... but the fleeting nature of that thrill only becomes more and more apparent as time goes on. Fundamentally I think it's necessary to have a deeper motivation, a bigger "why" behind what you do, in order to sustain your satisfaction from day to day.