pdelgallego

Author here. Two comments:

1/ As you mentioned, this is not a good approach for start-ups. The single-threaded model keeps teams autonomous and focused by eliminating alignment in big companies. It tries to replicate the nimbleness of start-ups within business units and teams. A startup should already be focused on finding a market fit as fast as possible.

2/ Not everything should be run as single-threaded. For example, AWS sales and support teams run as functional teams because otherwise, it will impact the customer's experience.

A better approach for start-ups and small businesses is using something similar to the Directly Responsible Individuals approach. Its focus is on decision-making ownership and speed. [1]

Thanks for the feedback. I will try to incorporate it into the post.

[1] https://about.gitlab.com/handbook/people-group/directly-resp...

And if I recall correctly, AWS needed to develop Nitro before offering Graviton.

AWS Glue Data catalog is Hive, and as you mentioned, Athena is a wrapper of Presto

anything big enough that connecting it using wifi might be challenging. E.g. Port, factories, airports, ...

Nation states -> wealthy bigco -> billionare's pet project -> hobbyist (e.g. Copenhagen Suborbitals) -> normal people.

That is what I like (at least in theory) of AWS CodeGuru. It helps you to detect bugs and common bad practices automatically in the code review.

I help often customers understanding technical debt, and code quality. Most people focus of code metrics, but they tend to forget organizational metrics, and how that impact the software. There are several studies on this. I particularly like one from Microsoft [1].

One of the metrics that I use address your point:

Number of Ex-Engineers (NOEE): This is the total number of unique engineers who have touched a code and have left the company as of the release date of the software system

Implications: This measure deals with knowledge transfer. If the employee(s) who worked on a piece of code leaves the company then there is a likelihood that the new person taking over might not be familiar with the design rationale, the reasoning behind certain bug fixes, and information about other stake holders in the code.

A large loss of team members affects the knowledge retention and thus quality.

[1] https://www.microsoft.com/en-us/research/wp-content/uploads/...

Project Kuiper?

as a new grad there, it wasn't your fault. There should be guardrails to protect you.

The Jevons paradox applies to compute. In economics, the Jevons paradox occurs when technological progress increases the efficiency with which a resource is used, but the rate of consumption of that resource rises due to increasing demand. The more efficient (or cheaper) compute gets the more uses we find for it, rising the consumption of it.

People think about pricing as a zero sum game. In reality, there are very few things in the world that are zero sum games.

It is quite common to get communication wrong, even inside Amazon. It leads to design by committee, slow decision making, and increase team dependencies.

I would love to hear your experience adopting Amazon mechanisms.

Disclaimer: I work at Amazon. I help customers to adopt some of those mechanisms.

Music is a winner-take-all markets. It makes it really hard for new musicians to break in. It also tend to be a sticky market, so those that have several hits remain relevant for a long time. Winner-take-all markets are reinforced by feedback loops.

The Two-pizza team concept is a very small part on how Amazon works. A few others on top of my head.

- Enable high-velocity decision making: Defining clear tenets that act as the north start for decision making at team level, and two-way doors thinking.

- Establish how you measure success, and how does relate to the goals of the organisation.

- Achieve team independency is a key factor, and having strong mechanisms such as the "away teams" concept, "communication is terrible" mental model and reducing cognitive overload by relying on platform teams

- Nominating a single-threaded owner for programs and business outcomes.

- Articulate how the organisation works across teams using mechanisms such as bar raisers, OP1/OP2, PR/FAQs, CoEs, WBRs, experiment-driven teams, ...

AI algorithmic progress is outpacing Moore’s Law at it best.

Compared to 2012, it now takes 44 times less compute to train a neural network to the level of AlexNet.

How that affect self-driven car is still to be determine, but progress is very real

https://openai.com/blog/ai-and-efficiency/

If workers unionize right now, then it will probably put the general public opinion against the workers. Specially as the pandemic get its way into the US, and more and more people self quarantine, and start relying in delivery services for all their shopping

The return of JEDI

For a AWS product manager, pricing is a one-way door once you cross it there is no way back from it you.

"You can't legislate against failure, but you can focus on fast detection and response"

-- Chris Pinkham

They are also hiring lots of MS and AWS sales AMs, SAs, and ProServe people

As a Danish resident, I would 100% use this too

That is basically Amazon scale playbook 101 (aka flywheel), if there is an efficiency that can benefit the customer (e.g. lowering prices), they will chase it.

It doesn't matter if that means designing Graviton2 or challenging Fedex by trying to build the biggest delivery network in the USA.

Not OP, but I remember Al Jazeera reporting about it in 2014. E.g:

https://www.youtube.com/watch?v=rvkEpstd9os

https://www.aljazeera.com/investigations/boeing787/2014/09/i...

Use DynamoDB TTL, streams and AWS Lambda as a dynamic task scheduling mechanism

AWS > Azure > GCP

Oracle is not a real competitor yet

   You load sixteen tons, what do you get?
   Another day older and deeper in debt

https://www.youtube.com/watch?v=zUpTJg2EBpw

I found a copy in another website.

https://trulytimes.com/basecamps-cofounder-explains-why-it-d...

Sound Interesting, but its behind a paywall

What if we don't destroy Greenland ecosystem?

>> if you'd rather define the infrastructure side as code vs YAML

Or AWS CDK

https://aws.amazon.com/cdk/