Sounds very similar to NASA C programming guidelines. Each module during the initialization period would allocate its static memory size. Every loop had a upper bound's max iteration to prevent infinite loops.
I think they posted the guidelines and it was a wonderful read about how they developed real time systems.
Part of finding yourself, and not appealing to people is you take the next step and foster a better understanding of social interactions in groups. You use a bit of cynical implementation to be part of groups and team's. You're not doing to prove anything to you, but other than being singled out and isolated.
I understand being self actualize is great, but part of growing is what is more valuable to you isn't what you know but it's what other people know. If your not integrating yourself part of social circles you miss out on leads and adventures you wouldn't of otherwise found if you're sitting by yourself because no one want's to interact with yourself because you haven't developed yourself more than yourself.
Do you mean selfishness or low self-wroth? Selfishness is that you're doing it because you only care about yourself and not the other person (In that case you would be talking about yourself). Low self-worth is where you believe you're view point and genuine experiences are lesser than the other person.
Vast majority of people are ego invested in themselves, and typically love to criticize other people well hating being criticized themselves. You run into a problem is they're easy to manipulate, as you play to their ego and criticize the people they hate.
There is a fine line as most people don't have very good conversation skill's and will use you as a surrogate to a psychologist. You have to pull them in line with eye contact and silence and then giving them the benefit of the doubt, and finally have to say they're in a conversation/discussion. If that all else fails then you leave the conversation.
Only smug i could tell was in regards to their free app offering, and considering it costs money and resources to maintain those free services their viewpoint is understandable. The feature was removed, they thank them for the feedback for being upset that the feature was removed.
There was two competing viewpoints of OO. A object is nothing more than an animated data structure, and the opposing view saw objects as behaviors and you didn't map them explicitly to your data model.
As most people viewed object's as simple extension over the data, it's not surprising to see most developer opt out for more basic form of data representation and that doesn't need object's at all.
Big reason why most tech people I know leave Australia, go over to the states make their million and then come back home. Then the ATO has the audacity to want to tax them for their over-seas income well not residing in Australia.
Vitamin K - Mk7, Vitamin V, and Magnesium seem to help with the removal of calcifications of the artillery. Though I couldn't really find referees other than reports on `Vitamin K intake and calcifications in breast arteries Angela`
I found when I disconnected from the news and politic in my own country that the people around me didn't really have well developed retention of the new's they where talking about. For example, news event A occurs on day, and everyone in the office talks about A, and how it made them feel. Then news event B occurs the next day, and there doesn't seem to be any cognitive awareness how A connects to B, instead A is forgotten and everyone emotes about B.
I've had to use the analogy to people how weird it appears. It's like everyone talks about a blue cat one day, and the next day talk about a red cat. Everywhere you go everyone talks about the same colored cat's.
It's open source you could spend your time fixing the issues and collaborating with other source project's to bring a better unified experience for users for Linux.
Yeah..... you've got `more` important things to do.
Linux have all-ways been a hobbiest project. It your mindset when going into it.
Give them benefit of a doubt, you have no prior knowledge of the time/pressure constraint's and organization structure at the time they wrote the code.
I would say they probably made the decision like we all do when development work, that solving this n+1 or bubble sort, or api package doesn't have time in the budget.
Getting to market sometimes is more important to managers than optimal `correct` code, when the market isn't willing to pay for the services of `correct`.