The hottest Engineering Culture Substack posts right now

And their main takeaways
Category
Top Technology Topics

Scrum is the Symptom, not the Problem

Rethinking Software • 77 HN points • 07 Aug 24
🕹 Technology Software Development Corporate Governance Agile Methodology Project management Engineering Culture
  1. Scrum is often seen as a bad tool for management, restricting developers' productivity and self-esteem. Many developers feel frustrated, yet companies keep using it because it controls people rather than empowers them.
  2. The main issue isn't Scrum itself, but a bigger problem of control in software companies. Developers often lack genuine power and are seen more as replaceable parts than valuable contributors.
  3. To truly change their working conditions, developers may need to start their own companies or work independently. This way, they can reclaim decision-making power and avoid micromanagement.

🗓 Your invitation to this week's CTO fellow discussion & CQRS stream

🔮 Crafting Tech Teams • 39 implied HN points • 22 Nov 23
🕹 Technology Engineering Culture
  1. The CTO Fellow discussion & CQRS stream is happening this week. Streams are scheduled on Wednesdays and Thursdays at 4pm CET.
  2. Crafting Tech Teams is a reader-supported publication. Consider becoming a free or paid subscriber to receive new posts and support the work.
  3. To access the full post archives, you can start a 7-day free trial by subscribing to Crafting Tech Teams.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

From Rockets to Roadmaps: An Engineer's Guide to Product Success

Dev Interrupted • 14 implied HN points • 03 Dec 24
🕹 Technology Software Development Engineering Culture AI Applications Product Management Team Dynamics
  1. Engineers can drive product vision, leading to faster and more innovative development. This shifts the focus from just coding to solving real business problems.
  2. With AI making coding easier, engineers who understand customer needs and market trends will stand out. Their blend of technical skills and business savvy is crucial for success.
  3. Collaboration and teamwork are key in software development. It's not just about individual contributions but how teams work together to create better solutions.

Zenful Estimates: Ditching Task Estimates to Build a Faster Team

Dev Interrupted • 51 implied HN points • 14 Mar 24
🕹 Technology Software Engineering Project management Agile methodologies Engineering Culture
  1. Engineering task estimates are often costly in time and resources, leading to inaccuracies and increased stress within the team.
  2. Distinguishing between task estimation and project estimation can help teams prioritize better and allocate resources more effectively.
  3. By adopting a 'Zenful' approach that focuses on project estimates rather than granular task estimates, teams can save time, reduce stress, and improve overall efficiency.

The Case for Nitpicking

David Reis on Software • 2 HN points • 18 Feb 24
🕹 Technology Software Development Code Quality Engineering Culture Best Practices Team Collaboration
  1. Nitpicking in code reviews can lead to better code quality and a stronger engineering culture. It's important to discuss style and best practices instead of ignoring them.
  2. Good taste in code exists and is based on collective standards among practitioners. Competent programmers can generally agree on what makes code better, like readability and consistency.
  3. Having a style guide helps streamline code reviews and makes discussions less personal. It sets clear expectations and allows for respectful and constructive feedback.

Weekly Notes

Rethinking Software • 0 implied HN points • 16 Sep 24
🕹 Technology Software Development Productivity Engineering Culture Project management Workplace dynamics
  1. Software engineering often feels like assembly-line work, where programmers are given tiny tasks with no time for deeper thinking or creativity. This can be frustrating for those who want to tackle bigger projects.
  2. There is a growing idea that people should focus on fewer tasks and prioritize quality over just being busy. This philosophy encourages a more balanced and thoughtful approach to work.
  3. Many people dislike strict management practices like Scrum, feeling they limit creativity and autonomy. They prefer a work environment where they can work freely on projects without constant oversight.

🐿️ Bypassing Technical Debt - The Insanely Profitable Tech Newsletter

Squirrel Squadron Substack • 0 implied HN points • 14 Jan 25
🕹 Technology Software Development Technical Debt System Design Engineering Culture
  1. Avoid doing a total rewrite of your software, as it often leads to mistakes. Instead, make small, incremental changes to improve what you have.
  2. Technical debt is a common issue in tech. Learning to manage and refactor it can lead to better software over time.
  3. Just as our bodies have remnants of evolution, software can have old parts that still serve a purpose. It's important to understand their history before trying to remove them.