And these days, with all the social networks, how is it that there wasn't a specialized space for getting to know people through co-working on something. It's either classroom or workplace, which had monopolized the most interesting thing about making relationships -- doing something exciting and potentially useful together!
Is Intel poaching TSMC senior engineers in Arizona ( https://tinyurl.com/duvfkrm2 ) related? Cause, I would be really pissed off, if I we'd agreed to build a factory in foreign land out of desire to build good long-term relationships, and then, that country's strategically important corporation would decide take away our key engineers.
What's normalized in context of free opportunistic market can be seen as treacherous in context of politics and in the behaviors of strategically important enterprises of countries.
So, CEOs are thieves of the letter "E" from employees, if they delegate so much that the employees cannot meaningfully participate in the higher strategic decisions together?
Task delegation can be cooperative or abusive, as the article points out. It might be called theft if there is something owed and taken away from, but for that, it has to be that participation in executive decision was a right of employee or contractor to begin with (for that, they have to investigate under what agreement they work, what type of organization and expectations were set). Some contractors are happy to deliver a part or component to specifications, get paid and not participate in strategic decision making, others want to be part of the mission, and decide higher level goals together. It depends on the type of social contracts we enter into!
Btw., the "Executive Function Theft" as defined in the article, is an important social issue in the area of abuse of power, but reading plainly, it can be confused with good illegal leadership takeover without abuse of power, and with positive social outcomes.
Normalizing Unix seconds by the number of seconds in a day, results in Unix day, which has convenient properties, such as 5th digit after decimal point corresponding to decimal second (0.864 length of traditional second).
So, dividing UNIX_SECOND by 86400, we get a decimal Unix day.
For example, if UNIX_SECOND = 1688897360, then UNIX DAY = 19547.42315, Displaying this number with time formatting, makes it extremely easy for our time-trained eyes to interpret:
19,547 4:23:15, meaning:
19th Unix decimal year
547th day of the year (5-dmonth, 4-dweek, 7-dweekday)
4:23:15 decimal time (4-dhour, 23-dminute, 15-dsecond)
Unix days make for a good decimal calendar. Simply divide Unix seconds by 86400, and you're done. While there are several decimal calendar attempts available online, this approach follows Occam's Razor principle by relying on basic division and digit grouping without the need for additional inventions, and yet, has pretty much all the benefits one would want.
To explain "tech" to non-techies, somebody comes along with a term "cogs" to explain their importance to a clockwork, which user only sees the dial ("frontend") of.