News for hackers. Stuff that matters.
Re:How the AWS team will contribute to Rust’s success by leprechaun1066 on Wednesday March 03, 2021 @12:44PM (#26331853)
> People use tenets for everything at AWS

What is with all the cult/religious/military terminology turning up in software development these days? Squad, ritual, tenet; one day management will be asking us to remember to bring in our robes for the Thursday morning sacrifice...

Re:How the AWS team will contribute to Rust’s success by eitland on Wednesday March 03, 2021 @12:50PM (#26331942)
I remember one consultant in 2009 describing how they had a toy chicken that they used to sacrifice by chopping off its head before VMware upgrades back when VMWare was new.

(They would then sew the head back on so the sacrificial chicken would be ready for next time.)

My point is: I guess this is nothing new.

Re:How the AWS team will contribute to Rust’s success by TheGrassyKnoll on Wednesday March 03, 2021 @01:49PM (#26332694)
Up one for the toy chicken (I'm thinking rubber chicken).
Re:How the AWS team will contribute to Rust’s success by pygy_ on Wednesday March 03, 2021 @02:44PM (#26333347)
... with a pulley in the middle? High voodoo you’re playing with here...
Re:How the AWS team will contribute to Rust’s success by sgift on Wednesday March 03, 2021 @12:56PM (#26332018)
Maybe it's because English is my second language, but tenet is to me just another word for principle or axiom? Nothing cult/religious/military about it?
Re:How the AWS team will contribute to Rust’s success by EamonnMR on Wednesday March 03, 2021 @01:03PM (#26332148)
Native English speaker, no extra connotations that I recognize.
Re:How the AWS team will contribute to Rust’s success by karmakaze on Wednesday March 03, 2021 @02:08PM (#26332928)
Google'd:

  ten·et /ˈtenət/

  noun
  a principle or belief, especially one of the main principles of a religion or philosophy.
  "the tenets of a democratic society"
Re:How the AWS team will contribute to Rust’s success by geodel on Wednesday March 03, 2021 @12:56PM (#26332039)
Indeed. As person suffering from endless agile bullshitery scrums, stories, sprints, and crap. I now have to keep a lookup table for normal names in my mind as every fucking thing has a "code/cool" name. So QA/UAT/Prod environment are now "Audi/BMW/Tesla" environment at work.
Re:How the AWS team will contribute to Rust’s success by whateveracct on Wednesday March 03, 2021 @12:50PM (#26331933)
Corporations are inherently stupid. The social & political mechanisms within make the employees stupid as well (while acting as employees), so they turn to rules & folksy truisms as a heuristic to wrangle that stupidity and get the mob to advance the corporation's interests.
Re:How the AWS team will contribute to Rust’s success by yikesshescute on Wednesday March 03, 2021 @01:34PM (#26332527)
> Corporations are inherently stupid.

Is it that groups of people are inherently stupid, or is there some facet of corporations that makes them in particular stupid?

Re:How the AWS team will contribute to Rust’s success by whatshisface on Wednesday March 03, 2021 @01:50PM (#26332718)
An individual person will act to the best of their ability. A group of people at bare minimum has to pay communication costs, and so will act to less than the best of the ability of its members.

Furthermore, since dysfunctional organizations aren't quickly removed, the reality is usually a lot worse than the ideal. Depending on how much slack there is in the arena of competition there can be almost no limit on how dysfunctional small pockets, or even large slices, of the organization can become without leading to the death of the host.

Re:How the AWS team will contribute to Rust’s success by enioarda on Wednesday March 03, 2021 @02:07PM (#26332917)
Does that not leave out synergetic effects? While communication costs, it could also reward?
Re:How the AWS team will contribute to Rust’s success by whatshisface on Wednesday March 03, 2021 @02:20PM (#26333070)
The organization might "know" more about subject A and subject B together than expert A or B, but it will "know" less about subject A than expert A and subject B than expert B.
Re:How the AWS team will contribute to Rust’s success by yikesshescute on Wednesday March 03, 2021 @02:33PM (#26333201)
What about subjects like “building rockets that are moon-capable”? All experts know negligible amounts about this subject, but organizations have “sufficient” knowledge.
Re:How the AWS team will contribute to Rust’s success by whatshisface on Wednesday March 03, 2021 @02:45PM (#26333368)
That's essentially half my point. The organization might be passable at "building rockets that are moon-capable," but it's going to be worse at each individual specialized task than the individual experts that make it up. One of the C programmers is likely to look at the architecture of the control system and think "that's a dumb way to architect a control system," and he'll probably be right. The same will be true for every subsystem, and even the integrated assembly. However unless someone figures out how to reduce communication costs, that's the best anyone can do; the alternative would be to have a great control system with no rocket.
Re:How the AWS team will contribute to Rust’s success by yikesshescute on Wednesday March 03, 2021 @04:49PM (#26335145)
Is the implication that a company can spend more time and money to get each subsystem to subsystem-expert-acceptance level, or is there something about current organizational practice that makes even this impossible?
Re:How the AWS team will contribute to Rust’s success by whatshisface on Wednesday March 03, 2021 @05:01PM (#26335281)
Imagine two experts advising a leader. They're not going to fully communicate all of their expertise to him, so his decisions on topic A will probably be worse than expert A, and likewise for topic/expert B. He's going to make better decisions on joint A+B tasks that require combined and balanced knowledge, but both experts will (not incorrectly) see him as "not knowing as much about A/B as I do."

You can substitute the individual leader for a group whose consensus must be obtained and get another parable illustrating the same principle.

Re:How the AWS team will contribute to Rust’s success by yikesshescute on Wednesday March 03, 2021 @06:52PM (#26336604)
So, the leader is an expert on “joint A+B tasks”? Then provided he, the leader, can identify, A tasks, B tasks and A+B tasks and correctly defer on the first two sets, won’t we get optimal decision making?

And are we sure that there really are A+B tasks?

Re:How the AWS team will contribute to Rust’s success by whateveracct on Wednesday March 03, 2021 @02:39PM (#26333293)
Not all groups, but corporations are groups with

* hierarchy

* competition between people in the same tier of the hierarchy

* opposing incentives throughout the hierarchy (company aims to maximize employee labor and minimize employee compensation and; employees minimize their labor and maximize their compensation)

Left alone, this results in a lot of the stupidity, and that's why "building culture" is so important - a good company culture transcends this perverse base nature.

Re:How the AWS team will contribute to Rust’s success by yikesshescute on Wednesday March 03, 2021 @04:53PM (#26335194)
What are the specifics of a culture that transcends these organizational hazards? How does it work?
Re:How the AWS team will contribute to Rust’s success by zwieback on Wednesday March 03, 2021 @01:11PM (#26332252)
Where I work our internal code names are all Star Wars/Trek or Hitchhiker through the Galaxy. I always push for something like "flowers" or "trees" to no avail.

Be interesting to collect data on how these trends change over time.

Re:How the AWS team will contribute to Rust’s success by cle on Wednesday March 03, 2021 @01:10PM (#26332246)
Groups of people can communicate more effectively if they agree upon common terminologies and definitions.