Skip to main content

Stay Updated As Software Engineer

Are you a software engineer looking to stay updated and grow in your field? We've got you covered with over 50 valuable resources to keep you on the cutting edge of technology. From newsletters to books, we've curated a diverse list just for you. 

Newsletters: 


  • Pragmatic Engineer: Link 

  • TLDR: Link 

  • Level-up software engineering: Link 

  • Coding challenges: Link 

  • Engineers Codex: Link 

  • Techlead Mentor: Link 

  • Saiyan Growth letter: Link 

  • Wes Kao: Link 

  • Addy Osmani: Link 

  • And many more (see link below) 

Books: 

Engineering: 

  • A Philosophy of Software Design Link 

  • Clean Code Link 

Communication & Soft Skills: 

  • Smart Brevity Link 

  • Connect: Building Exceptional Relationships Link 

  • Crucial Conversations Link 

  • Engineers Survival Guide Link 

Leadership: 

  • The Manager's Path Link 

  • Staff Engineer: Leadership Beyond the Management Track Link 

  • The Coaching Habit: Say Less, Ask More Link 

While we can't list all 50+ resources here, this is a fantastic starting point to fuel your growth as a software engineer. For the complete list of meticulously categorized resources, be sure to check out our latest High Growth Engineer article. 

Comments

Post a Comment

Popular posts from this blog

Mastering Java Logging: A Guide to Debug, Info, Warn, and Error Levels

Comprehensive Guide to Java Logging Levels: Trace, Debug, Info, Warn, Error, and Fatal Comprehensive Guide to Java Logging Levels: Trace, Debug, Info, Warn, Error, and Fatal Logging is an essential aspect of application development and maintenance. It helps developers track application behavior and troubleshoot issues effectively. Java provides various logging levels to categorize messages based on their severity and purpose. This article covers all major logging levels: Trace , Debug , Info , Warn , Error , and Fatal , along with how these levels impact log printing. 1. Trace The Trace level is the most detailed logging level. It is typically used for granular debugging, such as tracking every method call or step in a complex computation. Use this level sparingly, as it ...
Post a Comment
Read more

Advanced Kafka Resilience: Dead-Letter Queues, Circuit Breakers, and Exactly-Once Delivery

Introduction In distributed systems, failures are inevitable—network partitions, broker crashes, or consumer lag can disrupt data flow. While retries help recover from transient issues, you need stronger guarantees for mission-critical systems. This guide covers three advanced Kafka resilience patterns: Dead-Letter Queues (DLQs) – Handle poison pills and unprocessable messages. Circuit Breakers – Prevent cascading failures when Kafka is unhealthy. Exactly-Once Delivery – Avoid duplicates in financial/transactional systems. Let's dive in! 1. Dead-Letter Queues (DLQs) in Kafka What is a DLQ? A dedicated Kafka topic where "failed" messages are sent after max retries (e.g., malformed payloads, unrecoverable errors). ...
Post a Comment
Read more