2,170 karma · joined January 19, 2010
In some ways, it can look bad for someone in leadership, like a CTO, to get called out for not doing things the right way. At the same time though, if you and the leadership in your company have hired the right engineers working with you, even if you are the CTO hopefully people working with you know more about specific areas than you do, and as CTO you can help make sure that things fit together. So what if you get feedback on how to do things better? You as CTO have a chance to set an example to others on the team for how to receive feedback constructively.
I think this was a common way of doing it 10+ years ago, but what I've seen work the best is to have your CI/CD process apply the updates. Assuming the migration scripts follow the same process as all your other code (code reviewed, tested, and are runnable), automatically applying these scripts is much less error prone than having a person apply them. Humans are pretty terrible at following a script, which is one of the things computers are great at.
Some objections I've seen to relying on automatic deployments:
- "But we should have a person run them to make sure they do they right thing!" Agreed, you should, but that should happen at test time, or maybe code review time, not right before you are about to apply something into production the Shift Left [1] principle applies to database changes as well as code changes
- "What if something goes wrong?" Well, what if something goes wrong with any of your deployments? Usually, you can roll back (either literally rolling back, or rolling forward, or rolling in some other direction that leaves your system in an ok state), look at the logs to see what went wrong, and try again.
- "But data can get messed up!" Data can get messed up by code changes. You should have a backup/disaster recovery process.
Well-defined UIs can help by making discoverability of features simpler, but more often than not, but I'm not convinced the industry understands the difference between "the UI is easy to navigate and discover" and "the UI has soft colors and rounded corners on everything."
Also, it took me two passes through to notice the tooth brush in step 16.
These posts raise some interesting points I hadn't thought about (I don't see any problem with Next-in accounting). But it seems that lack of inventory isn't the only problem, throughput at ports is also an issue, and the ports themselves are limited at what changes they can make to fix these issues, partly due to profits (no one will want to operate a huge port that's profitable 5% of the time), but also partly due to limits put on ports and shipping by the government.
Epistemology is simply the study of "the nature, origin, and scope of knowledge, epistemic justification, the rationality of belief, and various related issues." [1] We all do epistemology, all the time, whether we choose to think about it or not. In sports, we have minor leagues, where the stakes are lower. As the political climate (and the unfortunate affect of things like QAnon) demonstrates, the stakes aren't always lower just because epistemology is done poorly.
Something similar can be said of rhetoric. I applaud this article for not falling a trap we have also seen too often recently, the Appeal to Authority [2]. The author judges someone else's argument solely on the merits, rather than that person's background. To steal the original authors metaphor: Babe Ruth still had to go up to the plate and take a swing. Babe Ruth was an expert baseball player because he hit a lot of home runs. It would bizarre if the opposite were true - that is, if Babe Ruth was given a lot of home runs because he was an expert. And yet, we have experts that try to dismiss plausible (perhaps likely, perhaps unlikely, but nevertheless plausible) scenarios without any explanation as to why they choose to do that. [3][4] And it is incumbent of all of us in a free society to be able to read something presented to us and realize, though we may not be experts, even if the conclusion is right, the argument along the way isn't.
> My point is we're all engaged in this kind of desperate project of trying to feel like we're having new important insights, in a world full of people who are much smarter than we are... Partly this is all for the greater good... I would argue "intellectual exercise" is a better term.
I've come to the conclusion that even if it's not read by many people, public professions are still valuable. As an American who is generally more "conservative" but also finds Trump abhorrent, I wish I had written more random internet posts in the summer of 2015 about how, even from a traditional conservative perspective, Trump is terrible, for the World, for the US, and for Conservatism. Perhaps it would have changed a few people's minds. Maybe it wouldn't have changed anyone's minds, but planted a seed of doubt in people's blind faith for that man. I'm a complete amateur when it comes to all the relevant subjects. Yet, it still seems like it would have been a good thing to do.
1. https://en.wikipedia.org/wiki/Epistemology 2. https://en.wikipedia.org/wiki/Argument_from_authority 3. https://apnews.com/article/who-report-animals-source-covid-1... 4. https://apnews.com/article/joe-biden-world-news-health-scien...
I have been lucky, in that I had worked with my first team's director at a previous company and so I knew he was a good boss, and I had known the manager for my second team prior to joining. It's important as part of the interview process (at Amazon, or anywhere else) to treat the interview as a two-way process, as you're vetting the company, the team, and your boss as much as they're vetting you, and if you don't get all your questions answered as part of the interview (interviewers are supposed to save time for you to ask questions!), feel free to relay them to your recruiter.
The problem with this way of thinking is: we've already spent this amount of money on ending homelessness. California plans on spending $4.8 billion next year [1]. HUD has a budget of around $2.7 billion [2]. In 2019, the City of New York spent $3.2 billion [3]. I haven't bothered to do a full accounting of how much we've spent on homelessness over the past 5 years, but from those three data points it seems safe to extrapolate we've spent over $20 billion. This is also in the context of the larger War on Poverty, which has spent an estimated $15 trillion since the program started in the 1960's [4]. It seems that simply throwing money at problems is insufficient.
> "The options are stark reminders of public good we forsake in refusing to redistribute wealth." - Newsweek
One could just as easily make a game that did something similar with the US government's budget. The overall budget is something like $4 Trillion. Just the annual interest payments are on the order of $250 Billion. If we had a more fiscally responsible approach to budgeting and therefore didn't have to make interest payments, according to that game we could "repair Puerto Rico," "hire 100,000 new teachers," and "end homeless in the United States." We already redistribute wealth on a grand scale.
It's also not like the wealth of billionaires is just in a Scrooge McDuck-style money vault that they swim in all day, nor are they like Smaug, holed up in a cave sitting on vast amounts of gold and precious stones. The wealth is invested in various things, which in turn serve the public good.
1. https://www.latimes.com/california/story/2021-07-16/californ... 2. https://endhomelessness.org/ending-homelessness/policy/feder... 3. https://datalab.usaspending.gov/homelessness-analysis/ 4. https://en.wikipedia.org/wiki/War_on_poverty
First of all, I work at Amazon (and posting this under our social media policy, this is just my experience, and I don't speak for the company), and Scrum is pervasive at Amazon. The article is right that many big projects start with a 6 pager, but once teams start executing, many teams run some form of Scrum (Kanban is also popular).
The second thing I found strange in this article was the idea of Scrum being heavy-weight. Early in my career I worked at a small company where our process guru was a big fan of the Unified Process. The point of Scrum is that it is lightweight (without being zero process). There really isn't a lot to it. You sync with your teammates daily, to make sure you're all focused on the most important thing today. You check in every 1-4 weeks by (a) demoing your software to figure out where you are, (b) you do a retrospective to look at what can be done better, (c) you figure out what is the most important thing to be doing the next N weeks. The teams that I've been on that have tried to not do these things either in actuality, did these things, but did them subconsciously, and therefore unintentionally. When I hear people say "Oh, I don't like Scrum because my old team did Scrum and I didn't like how we..." what follows is almost inevitably something that if you asked a professional scrum coach "Should we do that?" the answer would be no.
> Competent, autonomous people need less structure to produce reliable, high-quality output. Big Tech is able to attract, afford and hire these people.
I don't like this way of thinking. Start-ups have lots of competent, autonomous people. Big Tech companies have lots of people early in their careers that are still learning to be autonomous. In fact, when I was at start-ups I often heard the opposite (and equally untrue) claim: that start-ups required people with more autonomy, because the product is new and the team is involved in discovering the product, whereas in larger companies the products are more defined, so people needed less autonomy.
I appreciate the author surveying people and trying to make sense of the results, but in this case I think he just over-simplified a much more complex reality in a way that isn't particularly helpful.
This is a silly comparison. The engineers I've worked with in my career that stand out don't stand out because they can write for-loops faster than others or public-class-Foo-public-static-void-main-string-args-System.out.println-hello faster than others. They are much more productive because they are better at ensuring they understand the problems they're trying to solve, and solving the problem with the least amount of superfluous work.
> No one talked about the fact that this particular developer had been developing the same system for the past 15 years, the first five almost alone. He relished being “the best." Wrote hard-to-understand procedural code to 5000-line files. Did not actively share knowledge with his peers. Over the years, some capable developers had joined the company. Most of them decided to move on. The ones left were happy to coast along and leave all the heroics to the “10x engineer.” As a result, the company had great difficulties in trying to scale its development efforts.
This example seems like a counter-example to me. It's important to separate out one's (potentially flawed) judgement vs the actual value an engineer brings. This engineer made everyone else less productive. Simply calling someone a "10x engineer" does not make it so.
> The best strategy for most companies is not a relentless focus on trying to hire “the best” in hopes of finding 10x unicorn engineers.
The rest of the article is a distraction from this generally good piece of advice. For many things, finding a competent programmer familiar with your tools and stack who can write the CRUD operations you need should be acceptable. A lot of software engineering interviewing distracts from this, with gotcha trivia questions about whether one can recite from memory algorithms from a text book that are not relevant to the work.
In my current company, teams are left to come up with their own policy, but most teams I know of have the "every commit needs 2 reviewers" policy (the ones that don't have a "1 reviewer policy"). I am a Principal Engineer at a big-tech company, and when I want to commit code, I must get it reviewed by 2 engineers, same as an engineer who graduated in May. It's not because my team doesn't trust me (I think...), but rather I earn my team's trust by showing that my seniority doesn't put me above the rules. My seniority also doesn't put me above getting better either.
Prior to my current company, most places I've worked generally had all code reviews optional. It was usually the better engineers that were more likely to ask for a review.
> The reason you’re reliant on a lot of “Asking” might be that you have trust issue.
I'd flip this on the head - the reason many teams are reliant on skipping code reviews is that they have a problem doing code reviews. As engineers, reviewing each other's work is part of our job. We should be prioritizing it as such. On the team's that I've been on that prioritize doing code reviews, waiting for a review has hardly ever been a problem.
At most of the companies I've worked for, there is a bunch of up front ramp up before someone can complete even a simple task. You have to become familiar with a team's frameworks, the business context, and the structure of the code base. To do one real task then requires all that ramp up first (or else, you'd need to simplify it so it's not a real task).
How big a task? If you are interviewing new college grads, it might not matter, but people who already have industry experience either have to use a large chunk of vacation time or leave their current job if the task is non-trivial (taking, say, a sprint or two to do).
How much do you pay? Do you have a fixed bounty? Do you pay senior engineers more?
I get how you want to see someone do this for real, but I've already built something like this 20 times. If a company trying to recruit me asked me to build this, I could spend a few hours building it again, or I could just tell you about the times I did something like that (and the challenges I ran into), which would take 30 minutes.
> The only problem is, I'm all out of chores.
The author could try cleaning up the melted gelato that's all over the pretzels on the middle shelf and the almonds on the lower shelf. Who puts gelato in a cabinet?
A little more seriously though, I find it hard to relate to an author who puts working and playing video games on the same shelf, and who also puts chores and interacting with people on the same shelf. As far as I can tell, the ranking of things into "shelves" mostly has to do with how digital they are (assuming "work" here is done on a computer). Is that a common sentiment? For me, even as a relatively introverted person, I would rather be outside, spending time with family, or reading a book then working (even as much as I do enjoy my relatively cushy work as a software engineer).
The last 2 VPs I've been under have had similar takes on meeting attendance: don't feel obliged to continue in a meeting if it's not providing value to you and you aren't providing value to it. This is, admittedly, way easier in COVID, where you can just drop off without much notice. But there's a polite way to do this in person (send an IM message to the meeting organizer politely saying you have other commitment/need to work on a near term delivery, and excuse yourself from the room).
Depending on the situation, I've found your-mileage-may-vary with trying no meeting days. Currently, as a principal engineer at a big tech company, it pretty much doesn't work. At smaller companies (or in smaller teams) I've found it works better.
Also, the claim "In the historical Dark Ages, religion put down science" is simplistic. If by "Dark Ages," the author means the time between the fall of Rome in the west and the Carolingian Renaissance in 800, there was no institution maintaining science, but there happened to be institutions maintaining religion. During this time, what scientific knowledge that was preserved in the west was preserved by monks copying manuscripts. If the author means to refer to the whole Medieval period, then many of the most famous scientists were clergy, and many scientific institutions grew out of religious institutions, so again the claim is confusing.
It's unfortunate that the author chose to distract from a good point by using a problematic metaphor.
> In this study, we confirmed the use of human ACE2 as receptor of two novel SARSr-CoVs by using chimeric viruses with the WIV1 backbone replaced with the S gene of the newly identified SARSr-CoVs. Rs7327’s S protein varied from that of WIV1 and WIV16 at three aa residues in the receptor-binding motif, including one contact residue (aa 484) with human ACE2. This difference did not seem to affect its entry and replication efficiency in human ACE2-expressing cells. A previous study using the SARS-CoV infectious clone showed that the RsSHC014 S protein could efficiently utilize human ACE2 [33], despite being distinct from SARS-CoV and WIV1 in the RBD (S1 Fig). We examined the infectivity of Rs4231, which shared similar RBD sequence with RsSHC014 but had a distinct NTD sequence, and found the chimeric virus WIV1-Rs4231S also readily replicated in HeLa cells expressing human ACE2 molecule. The novel live SARSr-CoV we isolated in the current study (Rs4874) has an S gene almost identical to that of WIV16. As expected, it is also capable of utilizing human ACE2. These results indicate that diverse variants of SARSr-CoV S protein without deletions in their RBD are able to use human ACE2.
So, I'm not a biologist but I have read biology papers before. The way I read that is that they are doing local changes to binding sites, not simply taking spike proteins and putting them on an experimental backbone.
All the opinions and politics aside: is that the right reading of this passage from the article? Seems like that should be an objective-to-answer question, and for my own education I'd appreciate someone explaining to me.
Otherwise, what you've cited disagrees with the WHO timeline, which says pretty definitively that the first COVID-19 cases were in Wuhan (https://www.who.int/emergencies/diseases/novel-coronavirus-2...). Whatever disagreements one might have with the WHO, this timeline seems pretty well documented and supported by cross-referenced citations.
But, yeah, if you put in the work, it shouldn't hurt to list your side projects. But also, keep them in perspective: don't bring them up simply because they would be "interesting to discuss." By their nature, side projects don't deal with a lot of challenges of professional projects: there's usually no deadline, there's no disagreements with other engineers, they deal with a smaller scale audience so don't deal with bugs and maintenance.
So... the party that holds the presidency and both chambers of Congress is the "opposition?" That's an interesting take on things.
Perhaps he means "opposition to authoritarianism," but the party of "I have a pen and a phone" and "We need to pass the bill to find what's in it" has it's own authoritarian tendencies. I'm NOT a fan of Trump, but the idea that this is a problem only with the Republicans is silly.
So is the idea that the dissolving of "mutual toleration" mentioned in the article is a one way street. There are plenty of interviews like this one https://www.nationalreview.com/2021/07/ive-never-felt-this-s... that express how norms on the left have also changed pretty drastically over the past few years. The government has been in multiple law suits with a group of nuns, called the "Little Sisters of the Poor," all of whom are celibate and most of whom are elderly, trying to force them to buy health insurance that includes birth control. Maybe that group of nuns is misguided, but how does the left demonstrate mutual respect? How do situations like that demonstrate "restraint in using their institutional powers?"
Keyboard short cuts would make it a bit better.