Responsible Engineering Prevents Costly Failures In A Scaling World
- Dr. Panos Patros tl;dr: Dr. Panos Patros, VP of Engineering at Raygun and a seasoned expert in the engineering field, recently wrote an article about the importance of building robust, scalable software by prioritizing quality.featured in #554
The Life-Changing Magic Of Tidying Up Code
- Kent Beck tl;dr: “Tidying up works through a series of small, safe steps. In fact, Rule #1 is If it’s hard, don’t do it. I used to do crossword puzzles at night. If I got stuck and went to sleep, the next night those same clues were often easy. Instead of stressing about the big effects I want to create, I am better off just stopping when I encounter resistance.” Kent shares his approach.featured in #551
On Over-Engineering; Finding The Right Balance
- Eliran Turgeman tl;dr: “A big debate among developers is whether to write code for today’s problem or to build a general-purpose solution for future needs. Both approaches have their pros and cons. Specific-purpose code can quickly become messy. But overly general code can add unnecessary complexity. This post, obviously opinionated, argues for a middle ground. That’s the sweet spot, as always.”featured in #548
Best Practices for Setting Up an Observability Framework
tl;dr: This playbook outlines the specific steps an organization should take when setting up a sustainable observability framework from scratch. Establishing a repeatable observability framework prevents critical visibility gaps, improves availability, reduces operational costs, and streamlines incident management - among other key business outcomes.featured in #548
Write Change-Resilient Code With Domain Objects
- Amy Fu tl;dr: “Although a product's requirements can change often, its fundamental ideas usually change slowly. This leads to an interesting insight: if we write code that matches the fundamental ideas of the product, it will be more likely to survive future product changes.”featured in #547
Less Is More: Principles For Simple Comments
- David Bendory tl;dr: (1) Adopt the mindset of someone unfamiliar with the project to ensure simplicity. (2) Use self-contained comments to clearly convey intent without relying on the surrounding code for context. (3) Include only essential information in the comments and leverage external references to reduce cognitive load on the reader. (4) Avoid extensive implementation details in function-level comments.featured in #543
Speed Up Your App By Caching Database Queries
- Jon Harrell tl;dr: Users demand speed and efficiency. Caching database queries can significantly improve your app's performance. Discover how to use caching to get lightning-fast load times and a smooth user experience for all of your users globally, no matter where your database lives.featured in #541
How To (And How Not To) Design REST APIs
- Jeff Schnitzer tl;dr: "In my career, I have consumed hundreds of REST APIs and produced dozens. Since I often see the same mistakes repeated in API design, I thought it might be nice to write down a set of best practices. And poke fun at a couple widely-used APIs. Much of this may be "duh", but there might be a few rules you haven't considered yet."featured in #537
How To (And How Not To) Design REST APIs
- Jeff Schnitzer tl;dr: "In my career, I have consumed hundreds of REST APIs and produced dozens. Since I often see the same mistakes repeated in API design, I thought it might be nice to write down a set of best practices. And poke fun at a couple widely-used APIs. Much of this may be "duh", but there might be a few rules you haven't considered yet."featured in #536
featured in #536