Question 1

Engineers who obsess over being a "10x engineer" are often not aware of the technical debt they create for their team.

Accepted Answer

Engineers who obsess over being a "10x engineer" are often not aware of the technical debt they create for their team. — from "Why The 10x Engineer Is A Dangerous Myth"

Question 2

While truly prolific engineers exist, aiming to be a "10x engineer" is a misguided target.

Accepted Answer

While truly prolific engineers exist, aiming to be a "10x engineer" is a misguided target. — from "Why The 10x Engineer Is A Dangerous Myth"

Question 3

Excellence in engineering can be defined in many ways, from writing a lot of code to writing a few lines that save a company millions.

Accepted Answer

Excellence in engineering can be defined in many ways, from writing a lot of code to writing a few lines that save a company millions. — from "Why The 10x Engineer Is A Dangerous Myth"

Question 4

Coding, design, and architecture are not distinct but rather a continuum with blurry boundaries.

Accepted Answer

Coding, design, and architecture are not distinct but rather a continuum with blurry boundaries. — from "This Changes How You See Software Architecture"

Question 5

The speaker and Gregor Hope often express similar ideas, with the speaker using terms like 'software engineers' and Gregor using 'architects.'

Accepted Answer

The speaker and Gregor Hope often express similar ideas, with the speaker using terms like 'software engineers' and Gregor using 'architects.' — from "This Changes How You See Software Architecture"

Question 6

Both software engineering and architecture involve more than just technical aspects.

Accepted Answer

Both software engineering and architecture involve more than just technical aspects. — from "This Changes How You See Software Architecture"

Question 7

The term "clean code" has several origins, including Robert C. Martin's 2008 book, Kent Beck's "tidy first" series, and Richard Gabriel's earlier concept of "habitability."

Accepted Answer

The term "clean code" has several origins, including Robert C. Martin's 2008 book, Kent Beck's "tidy first" series, and Richard Gabriel's earlier concept of "habitability." — from "Clean Code: Timeless Truth or Myth?"

Question 8

Habitable code is characterized by being comfortable to navigate and confident to change, focusing on the developer's experience rather than just static code properties.

Accepted Answer

Habitable code is characterized by being comfortable to navigate and confident to change, focusing on the developer's experience rather than just static code properties. — from "Clean Code: Timeless Truth or Myth?"

Question 9

There's a distinction between "Clean Code" (the specific, sometimes dogmatic practices associated with Robert C. Martin's book) and "clean code" as a general, suggestive description of good code hygiene.

Accepted Answer

There's a distinction between "Clean Code" (the specific, sometimes dogmatic practices associated with Robert C. Martin's book) and "clean code" as a general, suggestive description of good code hygiene. — from "Clean Code: Timeless Truth or Myth?"

Question 10

The traditional focus on memorizing syntax and API details for developers is becoming less important, as AI can generate code.

Accepted Answer

The traditional focus on memorizing syntax and API details for developers is becoming less important, as AI can generate code. — from "What Skills Do Developers NEED In An AI Future?"

Engineering Leadership

What You'll Learn

Why The 10x Engineer Is A Dangerous Myth

This Changes How You See Software Architecture

Clean Code: Timeless Truth or Myth?

What Skills Do Developers NEED In An AI Future?

How Expert Programmers ACTUALLY Practice Coding

Tech lead to manager: A blueprint for successful transition

The altitude slider: Knowing when to dive into code vs. drive the strategy

The twin mandate