@itsalexzajac.bsky.social
If you enjoyed this thread:
1. Follow me @itsalexzajac for more content on Software and AI
2. Check out Hungry Minds: newsletter.hungryminds.dev
3. RT the tweet below to share this thread with your audience
1. Follow me @itsalexzajac for more content on Software and AI
2. Check out Hungry Minds: newsletter.hungryminds.dev
3. RT the tweet below to share this thread with your audience
Subscribe to Hungry Minds
Get smarter about Software and AI in 5 minutes.
Save 50+ hours/week with deep dives, trends, and tools hand-picked from 100+ sources.
Join 50,000+ engineers from big tech to startups for 1 free email every Monday. Click to read Hungry Minds, by Alexandre Zajac, a Substack publication.
hungrymindsdev.substack.com
November 11, 2025 at 4:32 PM
If you enjoyed this thread:
1. Follow me @itsalexzajac for more content on Software and AI
2. Check out Hungry Minds: newsletter.hungryminds.dev
3. RT the tweet below to share this thread with your audience
1. Follow me @itsalexzajac for more content on Software and AI
2. Check out Hungry Minds: newsletter.hungryminds.dev
3. RT the tweet below to share this thread with your audience
What practices makes code easier to read?
November 11, 2025 at 4:32 PM
What practices makes code easier to read?
7. Avoid gotos:
↳ Use gotos only when absolutely necessary.
✅ They can make your code harder to follow and debug.
↳ Use gotos only when absolutely necessary.
✅ They can make your code harder to follow and debug.
November 11, 2025 at 4:32 PM
7. Avoid gotos:
↳ Use gotos only when absolutely necessary.
✅ They can make your code harder to follow and debug.
↳ Use gotos only when absolutely necessary.
✅ They can make your code harder to follow and debug.
6. Write smaller functions:
↳ Keep your functions small and focused on a single task.
✅ Smaller functions are easier to read, test, and reuse.
↳ Keep your functions small and focused on a single task.
✅ Smaller functions are easier to read, test, and reuse.
November 11, 2025 at 4:32 PM
6. Write smaller functions:
↳ Keep your functions small and focused on a single task.
✅ Smaller functions are easier to read, test, and reuse.
↳ Keep your functions small and focused on a single task.
✅ Smaller functions are easier to read, test, and reuse.
5. Keep variables short-lived:
↳ Declare variables as close to their usage as possible.
✅ This reduces the mental effort needed to track their values.
↳ Declare variables as close to their usage as possible.
✅ This reduces the mental effort needed to track their values.
November 11, 2025 at 4:32 PM
5. Keep variables short-lived:
↳ Declare variables as close to their usage as possible.
✅ This reduces the mental effort needed to track their values.
↳ Declare variables as close to their usage as possible.
✅ This reduces the mental effort needed to track their values.
4. Use distinct variable names:
↳ Choose descriptive and unique names for your variables.
✅ Avoid names that look similar, like `i` and `j`, to prevent confusion.
↳ Choose descriptive and unique names for your variables.
✅ Avoid names that look similar, like `i` and `j`, to prevent confusion.
November 11, 2025 at 4:32 PM
4. Use distinct variable names:
↳ Choose descriptive and unique names for your variables.
✅ Avoid names that look similar, like `i` and `j`, to prevent confusion.
↳ Choose descriptive and unique names for your variables.
✅ Avoid names that look similar, like `i` and `j`, to prevent confusion.
3. Group logic:
↳ Break long chains of functions or iterators into smaller steps.
✅ Use helper functions or intermediate variables to make the flow clearer.
↳ Break long chains of functions or iterators into smaller steps.
✅ Use helper functions or intermediate variables to make the flow clearer.
November 11, 2025 at 4:32 PM
3. Group logic:
↳ Break long chains of functions or iterators into smaller steps.
✅ Use helper functions or intermediate variables to make the flow clearer.
↳ Break long chains of functions or iterators into smaller steps.
✅ Use helper functions or intermediate variables to make the flow clearer.
2. Minimize nesting:
↳ Avoid deeply nested logic by breaking it into smaller functions.
✅ Flattening your code makes it easier to follow and debug.
↳ Avoid deeply nested logic by breaking it into smaller functions.
✅ Flattening your code makes it easier to follow and debug.
November 11, 2025 at 4:32 PM
2. Minimize nesting:
↳ Avoid deeply nested logic by breaking it into smaller functions.
✅ Flattening your code makes it easier to follow and debug.
↳ Avoid deeply nested logic by breaking it into smaller functions.
✅ Flattening your code makes it easier to follow and debug.
1. Simplify conditionals:
↳ Keep your conditional checks short and straightforward.
✅ Avoid mixing different logical operators like `&&` and `||` in the same condition.
↳ Keep your conditional checks short and straightforward.
✅ Avoid mixing different logical operators like `&&` and `||` in the same condition.
November 11, 2025 at 4:32 PM
1. Simplify conditionals:
↳ Keep your conditional checks short and straightforward.
✅ Avoid mixing different logical operators like `&&` and `||` in the same condition.
↳ Keep your conditional checks short and straightforward.
✅ Avoid mixing different logical operators like `&&` and `||` in the same condition.
0. Avoid novelty:
↳ Stick to familiar patterns instead of using new or complex constructs.
✅ This makes your code easier to understand because readers don’t have to learn new styles.
↳ Stick to familiar patterns instead of using new or complex constructs.
✅ This makes your code easier to understand because readers don’t have to learn new styles.
November 11, 2025 at 4:32 PM
0. Avoid novelty:
↳ Stick to familiar patterns instead of using new or complex constructs.
✅ This makes your code easier to understand because readers don’t have to learn new styles.
↳ Stick to familiar patterns instead of using new or complex constructs.
✅ This makes your code easier to understand because readers don’t have to learn new styles.
If you enjoyed this thread:
1. Follow me @itsalexzajac for more content on Software and AI
2. Check out Hungry Minds: newsletter.hungryminds.dev
3. RT the tweet below to share this thread with your audience
1. Follow me @itsalexzajac for more content on Software and AI
2. Check out Hungry Minds: newsletter.hungryminds.dev
3. RT the tweet below to share this thread with your audience
Subscribe to Hungry Minds
Get smarter about Software and AI in 5 minutes.
Save 50+ hours/week with deep dives, trends, and tools hand-picked from 100+ sources.
Join 50,000+ engineers from big tech to startups for 1 free email every Monday. Click to read Hungry Minds, by Alexandre Zajac, a Substack publication.
hungrymindsdev.substack.com
November 10, 2025 at 4:31 PM
If you enjoyed this thread:
1. Follow me @itsalexzajac for more content on Software and AI
2. Check out Hungry Minds: newsletter.hungryminds.dev
3. RT the tweet below to share this thread with your audience
1. Follow me @itsalexzajac for more content on Software and AI
2. Check out Hungry Minds: newsletter.hungryminds.dev
3. RT the tweet below to share this thread with your audience
What are you reading this week?
November 10, 2025 at 4:31 PM
What are you reading this week?
Join 50,001+ software engineers from big tech to startups here: newsletter.hungryminds.dev
Subscribe to Hungry Minds
Get smarter about Software and AI in 5 minutes.
Save 50+ hours/week with deep dives, trends, and tools hand-picked from 100+ sources.
Join 50,000+ engineers from big tech to startups for 1 free email every Monday. Click to read Hungry Minds, by Alexandre Zajac, a Substack publication.
hungrymindsdev.substack.com
November 10, 2025 at 4:31 PM
Join 50,001+ software engineers from big tech to startups here: newsletter.hungryminds.dev
I am packaging the other deep dives and trends in today's issue of Hungry Minds.
November 10, 2025 at 4:31 PM
I am packaging the other deep dives and trends in today's issue of Hungry Minds.
Absurd Workflows: Durable Execution With Just Postgres
Durable execution with just postgres.
lucumr.pocoo.org
November 10, 2025 at 4:31 PM
Architectural debt is not just technical debt
Frederick's delirious rants
frederickvanbrabant.com
November 10, 2025 at 4:31 PM
5. How to Become a Resourceful Engineer (by @gregorojstersek):
► newsletter.eng-leadership.com/p/how-to-be...
► newsletter.eng-leadership.com/p/how-to-be...
How to Become a Resourceful Engineer
Best engineers don't know everything off the top of their heads, but they can find essential information quickly. This is how to do it!
newsletter.eng-leadership.com
November 10, 2025 at 4:31 PM
5. How to Become a Resourceful Engineer (by @gregorojstersek):
► newsletter.eng-leadership.com/p/how-to-be...
► newsletter.eng-leadership.com/p/how-to-be...
3. Supercharging the ML and AI Development Experience at Netflix with Metaflow:
► netflixtechblog.com/superchargi...
► netflixtechblog.com/superchargi...
November 10, 2025 at 4:31 PM
3. Supercharging the ML and AI Development Experience at Netflix with Metaflow:
► netflixtechblog.com/superchargi...
► netflixtechblog.com/superchargi...
2. How Databricks Implemented Intelligent Kubernetes Load Balancing:
► blog.bytebytego.com/p/how-datab...
► blog.bytebytego.com/p/how-datab...
How Databricks Implemented Intelligent Kubernetes Load Balancing
The Databricks Engineering Team needed something smarter: a Layer 7, request-level load balancer that could react dynamically to real service conditions instead of relying on connection-level routing decisions.
blog.bytebytego.com
November 10, 2025 at 4:31 PM
2. How Databricks Implemented Intelligent Kubernetes Load Balancing:
► blog.bytebytego.com/p/how-datab...
► blog.bytebytego.com/p/how-datab...
1. 2x Performance, $300k Savings: A Case Study in Rewriting a Critical Service in Rust:
► wxiaoyun.com/blog/rust-r...
► wxiaoyun.com/blog/rust-r...
November 10, 2025 at 4:31 PM
1. 2x Performance, $300k Savings: A Case Study in Rewriting a Critical Service in Rust:
► wxiaoyun.com/blog/rust-r...
► wxiaoyun.com/blog/rust-r...
0. 1,500+ PRs Later: How Spotify Automated Code Changes with AI:
►engineering.atspotify.com/2025/11/spo...
►engineering.atspotify.com/2025/11/spo...
1,500+ PRs Later: Spotify’s Journey with Our Background Coding Agent (Part 1) | Spotify Engineering
1,500+ PRs Later: Spotify’s Journey with Our Background Coding Agent (Part 1) | Spotify Engineering
engineering.atspotify.com
November 10, 2025 at 4:31 PM
0. 1,500+ PRs Later: How Spotify Automated Code Changes with AI:
►engineering.atspotify.com/2025/11/spo...
►engineering.atspotify.com/2025/11/spo...