|
Friday 5th July’s issue is presented by Statsig |
|
![](https://mcusercontent.com/e9492ff27d760c578a39d0675/images/ced41add-5681-6588-84f8-8baac1e05298.png) |
|
|
|
Numbers To Know For Managing (Software Teams)
tl;dr: “Based on philosophy, experience, and analysis; we hope they’ll be of some use.” The authors cover topics such as: (1) Minimum number of direct reports anyone should ever have. (2) Minimum number of candidates you should interview before making a decision. (3) Number of days before a new hire should have merged a pull request, (4) Number of days before a small support issue becomes a large support issue. And more.
Leadership Management |
|
|
Eponymous Laws — Mike Fisher
tl;dr: “I’m a big fan of eponymous laws such as Conway’s law, that software reflects the organizational structure that produced it, named after Melving Conway” Mike discusses his own laws: (1) The more you deny, the more you implicate. (2) If you hire a skill, you will get more of that skill demonstrated. (3) Everyone thinks they can improve on others' works. (4) The complexity of a system increases with each new feature. (5) Change becomes harder as organizations grow.
Leadership Management |
|
|
|
|
How I Plan My Week As A Senior Engineer In Big Tech — Jordan Cutler tl;dr: Today, I’ll share the system that has allowed me to: (1) Finish nearly everything I set out to achieve each day. (2) Plan the most important work to accomplish my goals. (3) Have a record of what I accomplished to reflect, update my manager, and add to a brag doc.
CareerAdvice |
|
|
|
“You don’t win a race by trying not to lose."
— Chad Fowler
|
|
|
|
How We Build Experiments In-House — Vincey Au
tl;dr: “Experimentation is an invaluable decision-making tool, and at Canva, it’s a pivotal step in our product development process to quickly test ideas, measure impact, and safeguard the customer experience of over 100 million monthly active users. We split our experimentation platforms into 2 core components: (1) Experiment setup: Creating feature flags and assignments. (2) Experiment analysis: Measuring the impact of the change. In this blog post, we will dive into how the second component, experiment analysis.”
Architecture |
|
|
6 Hard Lessons We Learned About Automated Testing For GenAI Apps — John Gluck tl;dr: Testing LLMs is not simple. The probabilistic output makes failures hard to identify while running the models repeatedly tends to become very expensive quickly. In this blog post, QA Wolf engineer John Gluck covers 6 things the team learned about building automated black-box regression tests for genAI applications.
Promoted by QA Wolf Tests |
|
|
My Programming Beliefs As Of July 2024 — Evan Hahn tl;dr: This is a collection of things I believe about computer programming as of today. It’s based on my own experience. Evan discusses: (1) How to approach tasks. (2) How to design software. (3) Nitty-gritty coding details. (4) Interpersonal dynamics. (6) High level / career topics.
CareerAdvice |
|
|
Reasons To Use Your Shell's Job Control — Julia Evans tl;dr: “Job control” is a set of commands for seeing which processes are running in a terminal and moving processes between 3 states: jobs in the foreground, in the background and jobs stopped. Julia asked her network for reasons people use job control, sharing responses here.
Shell |
|
|
|
|
Most Popular From Last Issue |
|
|
|
Burn: Dynamic deep learning framework.
Doggo: Command-line DNS client for humans.
MindsDB: Platform for building AI from enterprise data.
OmniParse: Ingest, parse, and optimize any data format.
Semantic Kernel: Integrate LLM technology into your apps.
|
|
|
Click the below and shoot me an email! 1 = Didn't enjoy it all // 5 = Really enjoyed it
1 … 2 … 3 … 4 … 5 |
|
|
|
|