Home
Welcome to my wiki, where I keep track of things that I found relevant at some point in my past. Some people call this my knowledge archive, or Manager Readme. Are these things relevant today, who knows /shrung
Here are some metrics I claim to care about. I track these as best as I can: engineer happiness, ambition to innovate, spare capacity, number of issues sourced from package updates/vulnerabilities/features delivered, positive customer experience feedback.
Everyone cares about something, first and foremost I care about:
- Transparency
- Accountability
- Adaptability
- Sustainability
These are the important metrics: engineer happiness, ambition to innovate, spare capacity, number of issues sourced from package updates/vulnerabilities/features delivered, positive customer experience feedback. The deep dive on these is expanded in this article.
While they are not easy to measure, you get what you measure. So measure what you want.
Warren's Recommended Reading List
- Building your AWS account strategy
- Connecting to RDS using SSM (Alternate instructions)
- Debugging a container in Fargate -
aws ssm start-session --target="ecs:${ClusterName}_${TaskId}_${ContainerRuntimeId}" - Data transfer costs
- Log in to ECR repo:
aws ecr get-login-password | docker login --username AWS --password-stdin $ACCOUNT_ID_HERE.dkr.ecr.us-west-2.amazonaws.com - Enabling SSM on EC2
- How much memory to allow to AWS Lambda
- There is zero reason to EKS, but if you were going to, please set it up like this - What I do instead is make the Service a type: NodePort, which doesn't tell the cloud controller to create a load balancer, configure some static ports that end up being opened on the nodes, then point a target group at those ports outside of Kubernetes.
- Lambda Example payloads for every service
- Should I use Lambda Graviton ARM?
- AWS Lambda cold start continuous analysis
-
You won't be punished for a Good Culture
-
Bad engineers are promoted, but it isn't their fault Details here
-
How tech debt costs a company millions automated trading fail
-
Developers don't know security - If you want I will store the password encrypted
-
Dedicating time to engineering effectiveness is critical for success of a larger organization: http://www.gigamonkeys.com/flowers/
-
Don't say hey in Slack async chat - No Hello.com
-
Employee's deciding their own salaries Morningstar tomatoes and Buurtzorg
-
Why receiving positive feedback is challenging - (Hint: It's not your fault)
-
How to lose a lot of money in 45 minutes - The automated stock trading disaster.
- Scrum isn't effective
- Why estimation is always wrong
- And Relative estimation size is irrelevant
- And even if you do estimate and plan, you deliver more by delivering better
- Why estimates are off, California San Francisco to LA trip from Quora.
- Breaking up EM, PM, and architect responsibilities
- How to interview
- Conditions for improvement
- 1-1 Questions
- How to the coding interview
- Even the DoD has better agile practices than your team - DIB Guide -Detecting Agile BS
- How to give a compliment is a skill
- The Culture Map - Country Spectrum
- Great example of a Manager ReadMe
- Why takers have to be fired -The dark side of generosity: Employees with a reputation for giving are selectively targeted for exploitation
- How to actively sabotage productivity
- What Google Learned From Its Quest to Build the Perfect Team. PDF
- What makes Ted Lasso a great leader
- Be selective about glue work - See Metcalfe’s law, Reed’s law and Amdahl’s law for the technical reasons why large companies are inefficient.
- AWS: Fairness in multi-tenant systems
- All progress bars are wrong
- Extreme programming practices and recommendations on conventions
- It's important to spend X% of your time improving effectiveness
- Curated list of falsehoods that programmers believe
- HTTP/3 + QUIC
- Polymorphism is literally the worst and so are most clean code related suggestions
- Foreign keys are bad
- Why software programming class inheritance is wrong
- Building complex queries in REST is hard
- How to communicate at the right level for your audience
- Maybe don't use graphQL
- Evaluating and improving code readability
- Postal's Law: or why "be liberal in what you accept" is wrong