The hottest Engineering Practices Substack posts right now

And their main takeaways
Category
Top Technology Topics

Fruits & Roots

Software Design: Tidy First? • 2187 implied HN points • 15 Nov 24
🕹 Technology Software Design Development Team Dynamics Project management Engineering Practices
  1. The Forest represents a way of working where teams can deliver value quickly and effectively, highlighting benefits like fewer bugs and delivering good news often.
  2. Achieving the success of The Forest requires commitment to its roots, which involve working together, learning actively, and not over-planning.
  3. Communicating a shared purpose and fostering a strong community are crucial for maintaining the balance between roots and fruits in a productive team environment.

Forest & Desert

Software Design: Tidy First? • 1900 implied HN points • 11 Nov 24
🕹 Technology Software Design System Architecture Engineering Practices Project management
  1. In software development, there are two environments: a challenging 'desert' where mistakes are costly, and a supportive 'forest' where teams can work collaboratively and learn from their errors.
  2. Strategies that work in a desert, like detailed planning and strict reviews, won't help in a forest, which thrives on testing, incremental growth, and collaboration.
  3. To shift from a desert to a forest, teams need to understand why their current situation exists and take small steps toward creating a more supportive and effective work environment.

Software Quality

Engineering Enablement • 21 implied HN points • 12 Feb 25
🕹 Technology Software Development Engineering Practices Product Management Developer Productivity Quality Assurance
  1. Software quality has four main types: process quality, code quality, system quality, and product quality. Each type affects the others, so improving one can help improve the rest.
  2. Process quality is crucial because a good development process leads to better code quality. This means having proper testing and code reviews can help avoid defects later on.
  3. Product quality is what customers experience and it includes a product's usability and reliability. Engineers need to team up with product managers to ensure that products meet customer needs.

The value of grunge work

Wednesday Wisdom • 113 implied HN points • 15 Jan 25
🕹 Technology Software Development Agile Methodology Tech Debt Work Culture Engineering Practices
  1. Tech debt happens when we make bad decisions in software development. It can pile up, making fixing problems a big task for teams.
  2. Doing hands-on work, or 'grunge work,' helps deepen understanding of the tech systems. It’s crucial for maintaining and improving technology.
  3. To tackle tech debt effectively, it should be part of official job expectations. This way, everyone contributes and helps keep things running smoothly.

Why sprints are taking the joy out of building software

Leading Developers • 147 implied HN points • 29 Oct 24
🕹 Technology Software Development Agile Methodology Product Management Team Dynamics Engineering Practices
  1. Sprints can make software development feel rushed and stressful. Teams often end up prioritizing completing tasks over enjoying the process of creating.
  2. Agile isn't just about following the sprint process; it's more about flexibility and responding to change. Focusing too much on the sprint leads to sticking to the rules instead of adapting to needs.
  3. Instead of traditional sprints, teams might benefit from cycles where they take their time, release when ready, and allow some room for creativity and quality work. This can create a more enjoyable work environment.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

Build Software Like a Home

Tech Ramblings • 39 implied HN points • 11 Aug 24
🕹 Technology Software Development System Design Architecture Project management Engineering Practices
  1. Designing software is like laying the foundation of a house. A good structure makes it easier to build and change things later.
  2. Planning your work is crucial. Just like you wouldn't install plumbing before your walls are up, you shouldn't write code before having a solid plan.
  3. Create a clear process to develop your software. Start with architecture, build the basics, and then refine. This helps you deliver updates quickly and efficiently.

Software code reviews, and other empty rituals that waste time

Respectful Leadership • 54 implied HN points • 30 Nov 24
🕹 Technology Software Development Code Review Engineering Practices Team Management
  1. Code reviews take up too much time and energy without giving enough value back. Instead of focusing on comments from reviews, teams should focus on writing tests to catch real problems.
  2. It's better to trust the skills of experienced engineers rather than rely on code reviews. If engineers are good, they won’t need to second-guess each other's work.
  3. Instead of worrying about all possible issues, focus on real problems that can be tested and fixed. Don't waste time on imaginary problems that are unlikely to happen.

The Over-Engineering Trap

Tech Ramblings • 39 implied HN points • 28 Jul 24
🕹 Technology Software Development Engineering Practices Cost management Product Design Systems Architecture
  1. Simplicity and maintainability are more important than performance and complexity in software design. Focus on creating code that's easy for others to understand and work with.
  2. Avoid over-complicated platforms like microservices, especially if your application doesn't need them. Start with basic tools and scale only when necessary.
  3. Your goal as a software engineer should be to deliver a product that customers can use easily. Keeping things simple helps with maintenance and helps new team members get up to speed faster.

Learning from the Best

Permit.io’s Substack • 79 implied HN points • 14 Mar 24
🕹 Technology Software Development Engineering Practices Open Source DevOps
  1. Learning from bigger companies can help solve problems effectively. They often share their insights which can be adapted to smaller projects.
  2. Not reinventing the wheel is smart. Using existing solutions like policy engines can save time and effort while ensuring reliability.
  3. Engaging with the community and resources available online can provide valuable knowledge and support for developers looking to improve their work.

The DX Core 4 Framework

Fish Food for Thought • 11 implied HN points • 11 Dec 24
🕹 Technology Software Development Productivity Metrics Engineering Practices Data Analysis
  1. The DX Core 4 Framework helps companies measure developer productivity by looking at four main areas: Speed, Effectiveness, Quality, and Impact. This balanced approach provides a complete picture of how well teams are performing.
  2. It includes a Developer Experience Index (DXI) that shows how developers feel about their work, helping identify areas for improvement. This means companies can catch issues before they become bigger problems.
  3. The framework focuses on connecting developer productivity to business goals, making it easier for all levels of the organization to understand how engineering work impacts the company's success.

Tech Talks Weekly #7 ⭐️

Tech Talks Weekly • 39 implied HN points • 21 Mar 24
🕹 Technology Software Development Tech Conferences Engineering Practices Open Source
  1. There are new talks available from different tech conferences, so you can catch up on the latest insights and trends.
  2. Sharing Tech Talks Weekly with your friends or coworkers can help grow the community and bring more interesting discussions.
  3. You can fill out a Google form to share what topics you're interested in, which will help improve the content shared every week.

Scrum's "Product Owner" Problem

Rethinking Software • 14 HN points • 03 Oct 24
🕹 Technology Software Development Agile Methodology Product Management Engineering Practices Team Dynamics
  1. Product Owners should provide information, not direct decisions. Engineers need real-time data to make informed choices, rather than just waiting for orders.
  2. Engineering teams should ask deeper questions to understand their customers and competitors better. This helps them create better solutions instead of just following a checklist.
  3. The relationship between Product Owners and Engineers should resemble a restaurant. Product Owners gather customer insights while Engineers create the dishes, allowing for better quality and innovation.

Context matters

Sunday Letters • 59 implied HN points • 24 Oct 21
🕹 Technology Software Development Product Management Design principles Engineering Practices
  1. Finding the right balance between short-term and long-term focus is important in building complex software. You need to address immediate issues without losing sight of broader goals.
  2. Metrics should reflect real business goals, not just vanity numbers. It's better to watch user engagement than just sales figures.
  3. Being able to switch between different contexts and focus on what's most important is a key skill for engineers and business people. Understanding where to concentrate your efforts can greatly impact success.

Curious Devs Corner

Curious Devs Corner • 0 implied HN points • 07 Jul 24
🕹 Technology Software Development Cloud Computing DevOps Artificial Intelligence Engineering Practices
  1. Curious Devs Corner is a publication for IT professionals looking to learn more about technology. It covers various topics like Spring Boot, Cloud, and AI to help developers grow their skills.
  2. The publication offers easy-to-follow tutorials and hands-on experiences. This makes it a great resource for those who enjoy practical learning when exploring new technologies.
  3. It's designed especially for developers who are curious and want to stay updated on the latest trends in the tech world. This could be a valuable tool for anyone wanting to advance their knowledge.