2,170 karma · joined January 19, 2010
For example "balls to the wall" comes from aviation (https://en.wiktionary.org/wiki/balls_to_the_wall) and not from human anatomy. Even when the source of that expression is well attributed, later on the list goes on to call out "rule of thumb" even though it says it is unable to attribute the source of that expression (and, yes, maybe there is a violent past to it, but also: a person's thumb is about an inch, a useful way of measuring things of that size scale). And of course, they suggest instead of rule of thumb "standard rule," even though the etymology of "standard" involved "stand" - which elsewhere seems something the list would consider ableist.
Man in some context means an adult human male, but sometimes it just means any human (see https://www.merriam-webster.com/dictionary/man). When Neal Armstrong said "... one giant leap for mankind," he was not speaking on behalf of the species. Some groups of Christians have a prayer that reads in part "for us men..." which is prayed equally by the female members of the congregation. There are plenty of cases where the word "men" is equally clear that we're referring to all members of the human species.
And the word "guys" is routinely used to refer to a group that is not just men. People use it all the time, everyone knows what we mean, it does not cause offense, and in using it to refer to a group you are no more implying that the group is all male as you are implying that the group is composed of clones of Guy Fawkes (from whom the term originated).
Besides ones where just facts are getting in the way, there are also many that just seem ineffectual. For example, "the use of person-first language" - In English, adjectives come first. Sometimes English makes use of substantives, either directly or as lone words from other languages. When you put the word "person" first, you aren't magically changing how people construe that sentence - if someone wants to be uncharitable and define someone entirely by a characteristic, they probably will, and the rest of us will go on understanding that each of us can be described in multiple ways depending on the context.
The "Latinx" also needs to go. Every poll I've seen indicates that the people whom it was meant to describe don't care for it, and find it disrespectful of their linguistic heritage.
In the real world (outside of programming competitions, that is), programmers don't get clear instructions for what we're doing, and what instructions we get deal with messy aspects of the real world. For just one example I tried: if you ask Codex how to calculate taxes on US products, it misses the point of the ask. I know that you have a tax rate and a price and you multiple them together - but what tax rate is applicable? Figuring that out is a thorny problem.
In programming, a lot of the inherent complexity is in understanding the weird bits of ambiguity and the corner cases. Whether that specification is through natural language or some other thing, we're a ways of from a computer capable of replacing us on that.
> People talk shit about office politics
Right... there are good ways to go about politics, and not-good ways. I think many of us see the not-good ways.
Just write out sentences with the period at the end so you don't sound condescending.
In any case, 5% is a lot for any salaried employee. It's been a few years since I've been at a startup, but employee share pools used to be 15% or 20% - you wouldn't give a third or a quarter of your pool to one person.
1. There's been a big difference between mostly hiring generalists, and only hiring generalists. When you only hire generalists, all those generalists are trying to figure out the tech from scratch, which can be messy. If you have a specialist in a tech stack and then otherwise hire mostly generalists, you pair people who can learn quickly with someone who is capable of teaching them - this is a great mix.
2. Your hiring should reflect your goals. Sometimes startups really do just need to get a prototype out as soon as possible. But, sometimes, startups need help figuring out what kind of thing they should build in the first place. Those are two different skill sets, and not all engineers are great at helping shape product decisions.
3. While you need to consider the good and bad in all people, and recognize there is no perfect candidate, hiring someone who isn't a good fit for the role is often worse than not hiring someone at a startup. If you have 12 months of runway and you're burning 2-3 months being distracted by a Smart Jerk, then you might be jeopardizing your whole company.
4. So-called soft skills should be taken into consideration. It's not just someone's coding skills. Are they good at giving feedback? Are they effective at working with others? Do they demonstrate the ability to project plan?
1. When asked about a particular thing from a particular non-fiction book (or lecture, or podcast), one might not remember the text itself, but one may have internalized the point without remember where it's from. I know somewhere along the way I learned how to write a structured program, and there might be certain sources I remember being useful, but a lot of what I learned I couldn't off the top of my head point to a specific reference.
2. In a large amount of my reading, I don't read to absorb knowledge, I read to remember the reference for later. I don't need to try to absorb a lot of knowledge if I can easily pull up a book, web page, or document on my computer later.
3. Most facts I can recall off the top of my head are usually not things I read in a book, they are things I read in multiple books (or read in a book and later heard in a lecture or podcast). That doesn't mean that books don't work.
4. The style of the author can also come into play. Some authors are capable writers - they do their research and put together a coherent book - but some authors just excel at writing scenes that are memorable. David Mccullough was one such writer - compared to other non-fiction books I've read, I feel like I am able to remember more details from his writings than other similar writings. I think St. Augustine is also in this category - he spent a large portion of his life studying rhetoric, how to just keep people interested in what he was saying. Whether one agrees with Augustine, anecdotally most people I've talked to about his Confessions don't have the same problem as the author has in his discussions about The Selfish Gene. But I think writers that can write at that level are rare.
Another thing one can do is, instead of picking a school, pick professors. Consider what majors the student might study, look at what professors are there, and look at things like what books they've written, have they written any interesting blog posts about their teaching, and that sort of thing.
Both of these approaches take more time than scanning a rankings, but it actually resembles much more closely how other decisions we make in life operate.
> some arbitrary evaluation function...
I think "wanting an Ivy" is a bit arbitrary, but wanting a small vs. a large school, or a school a certain distance from home, can lead to a very different experience over the course of 4 years.
> a lot of colleagues don't know how to give good situation reports.
Another thing that can help, both written and in face-to-face communication, is using the Inverted Pyramid. Let's say the person in your 1-1 has an emergency and you have to cut it short after 5 minutes. In those first 5 minutes you want to get the most important information across. In the next 10 minutes, you give supporting details, and in the final 15 you can geek-out on the nitty-gritty.
I think if you expect you'll only need a small group of people to know the name (the "Shelob" example at a startup), or you expect a large group but only are adding one name to learn ("Vue"), it's fine.
The cute naming gets hard on larger projects. If you have to write a status or design document covering many teams, all with multiple cute names, that document will be impenetrable. It will be as hard as learning a new language - which in a sense it is, because your team will have created a new language that outsiders will need to understand in order to work with your team.
On my first team, we managed internal tools. Our customers were other people at Amazon, they submitted tickets to us directly.
For some teams at Amazon, there is at least a filter through some sort of customer support to handle certain kinds of issues. You are still on-call, but it's not like you are interacting with customers directly.
Also, since teams at Amazon tend to be small, the amount of things you are on-call for tends to be however much your team handles on its own. I know of other companies in which the oncall covers areas in other team's code bases - this is not the typical setup at Amazon.
Generally, we don't have SREs. Software engineers usually understand best how their software works, so we get faster mitigations, and they are also incentivized better to not write buggy software.
I mean, I don't make it that hard for people to figure out who I am if that's a thing they care to do.
But I think you're right about the larger part - it's hard to trust Corporations. As I said in my case, and what I advise others to do, is rather than trusting a company (big or small), try to find individuals there you can trust (either, early in your time there, or ideally find someone that you already trust that happens to be there).
Capital-P-Policies get followed. But there are a lot of lower-case-p-policies, more what you might call guidelines, that are not. Sometimes, for good reasons! There are examples of things Amazon does that try to encourage individual judgement, trusting the people in place. But there are also examples where we think we know what the right process is, but for whatever reason (prioritization, we haven't figured out the right way to enforce it, scaling challenges) it's not as strictly followed as outsiders might assume.
That seems excessive, but I don't know what area you work in. Does your team need to spend that long? I have heard of that happening within Amazon, but then people vote with their feet and move to a team that doesn't spend four hours in sprint planning.
> Many many folks inside Amazon say it has a startup culture.
I've spent roughly as much of my career at startups as I have at Amazon. It's a bit of a mix bag. Having worked at start-ups that had to spend time doing undifferentiated work (just getting automated deployments, for example), it's in some ways nice not to deal with that, and yes, you have to follow The Process for that to be easy. I sometimes see people taking chances and acting quickly on new opportunities. But yes, I also see people not taking chances when the cost of doing so would have been small. Then again, I once worked for a start-up where you had to use a particular template for a design document, and you had to produce a project plan that 6-month long projects that was accurate to the hour. So... I think it's hard to make generalizations.
I've heard of many writers - fiction, non-fiction, poets, all types - who do rewrite things again and again. I don't see why that wouldn't make them a writer.
If anything, it seems the desire to improve a piece is a desirable trait.
Different pockets of the company have different trade-offs and incentives. The on-call burden on some teams is higher. When I've seen this happen under good management, the managers work to do different things to relieve the burden (such as spending time working on tech debt, improving test automation, and so on).
Some of the aspects of Amazon's culture that I hear criticized often come with unfair comparisons. No one likes getting paged at 1:00 AM, and that's a thing that can happen to you at Amazon. In my personal experience though, I got paged at weird hours much more often working at start-ups. Amazon at least (again, generally, in the parts of the company I've worked) has a healthy culture around continuing to improve operations, preparing people for on-call, and to address any page events so that particular reason for getting paged doesn't happen again.
(I'm just offering my own opinion, I don't speak for Amazon in any official capacity.)
Now, sometimes systems diverge from the design, and sometimes threat models are incomplete. But the exercise of generating a threat model makes understanding who manages data more manageable.
This is a false dichotomy. I had the good fortune to study Math and Computer Science at a liberal arts school. During the course of my undergraduate degree, I had to spend a fair amount of time writing about STEM, in addition to actually doing STEM things. I've found, for example, reading and critiquing a paper on some ML research and asking "Is this true?" uses many of the same skills as asking "Is this true?" in other areas. And I was able to take plenty of Humanities classes as an undergrad as well. It is possible to get both a liberal arts education and a STEM education at the same time.
> Humanities specialists argue that these majors open up higher-earning opportunities later in life because they don’t lock students into a narrow programming language, certification or career path.
While I actually am a fan of liberal arts generally, this is an uninformed argument. Most CS programs I know of do not teach anything all that specific to the moment. At least when I was in school, and soon after, many programs included at least some course work in Lisp, ML (the programming language: https://en.wikipedia.org/wiki/ML_(programming_language)), or Haskell, with the idea that they would teach a lot of programming language precisely so that you can learn how to pick up things later. No programs I'm aware of prepare students for a particular certificate. And, if they did, outside of consulting these certificates seem to not be particularly popular in computer science or software engineering fields. I suppose if an education in Humanities had prepared these particular people to make such a crummy argument, that would be a reason not to pursue a degree in the Humanities.
One possible reason: no one whose job it is to write Python scripts was ever promoted for making an Excel spreadsheet when that is the simpler and more practical approach. And no manager of people who write Python scripts is going to be able to use that Excel spreadsheet to sell "I need more responsibility and head count." People tend to follow incentives, rather than focusing on making wise decisions.