korrents
Hynek Schlawack

What Hynek Schlawack thinks about software quality

@hynek-schlawack · 16 positions · On ppll ↗

Software engineer and open-source maintainer of attrs and structlog; writes about Python, software design and career growth at hynek.me.

Hynek Schlawack did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

Filter software quality · Newest first
Topic
All 16software quality 7developer tools 4Python 4design 2JavaScript 1Microsoft 1software performance 1
Sort
NewestOldest

Only Hynek Schlawack on software quality. See everyone on software quality

7 dated positions, 2021 to 2022, in their own words. Our reading of what Hynek Schlawack has said — not written or endorsed by them.

  1. Our readingThe principle 'Don't Mock What You Don't Own' means that mock objects should be used to substitute one's own objects rather than third-party ones.

    Their wordsThe principle Don't Mock What You Don't Own means that whenever you employ mock objects, you should use them to substitute your own objects and not third-party ones2.

    ↗“Don’t Mock What You Don’t Own” in 5 Minuteshynek.me 1st of 3 in this piece

  3. Our readingUsing nested mocks to mimic third-party APIs can make tests brittle, unidiomatic, and difficult to debug.

    Their wordsThis is a business logic test and the purpose of the test is drowning in boilerplate necessary to mimic the API of an HTTP client that can change at any time. That makes the test brittle and unidiomatic.

    ↗“Don’t Mock What You Don’t Own” in 5 Minuteshynek.me 2nd of 3 in this piece

  5. Our readingTo keep business code testable and idiomatic, one should avoid directly using third-party dependencies in it.

    Their wordsCorollary: To keep your business code testable and idiomatic, avoid directly using third-party dependencies in it.

    ↗“Don’t Mock What You Don’t Own” in 5 Minuteshynek.me 3rd of 3 in this piece

  6. 7 months earlier

  7. Our readingCodecov has become very flaky.

    Their wordsUnfortunately, Codecov has grown very flaky. I have lost any confidence in the fact when it fails a build and my first reaction is always to restart the build and only then investigate.

    ↗How to Ditch Codecov for Python Projectshynek.me

  8. 5 months earlier

  9. Our readingCode sharing via subclassing is an ineffective way to customize more than one behavioral aspect of a class.

    Their wordsIf you want to customize more than one behavioral aspect of a class, code sharing via subclassing won't work. It leads to subclass explosion.

    ↗Subclassing in Python Reduxhynek.me 1st of 2 in this piece

  11. Our readingProperly implemented composition provides better reading clarity than inheritance.

    Their wordsWhen it comes to reading clarity, properly-done composition is superior to inheritance.

    ↗Subclassing in Python Reduxhynek.me 2nd of 2 in this piece

  12. 4 months earlier

  13. Our readingThe amount of unintentional breakage through updates outweighs the amount of intentional breakage.

    Their wordsIn almost 20 years of professional software development, I have observed that the amount of unintentional breakage through updates outweighs the amount of intentional breakage by far.

    ↗Semantic Versioning Will Not Save Youhynek.me 1st of 3 in this piece