Mark Seemann
@ploeh
Followers
17K
Following
133
Media
411
Statuses
27K
Danish software design
Copenhagen
Joined May 2009
@ploeh I also found this article: https://t.co/rJgUWSM14k by Vladimir Khorikov essential in explaining the supposed dichotomy of DAMP vs DRY.
enterprisecraftsmanship.com
In this post, we’ll make a deep dive into the DRY and DAMP principles and will talk about the false dichotomy around them.
1
1
6
Other readers are showing their appreciation of ploeh blog by supporting it. You, too, can do that.
blog.ploeh.dk
Ploeh blog is free, and always has been. Keep it free.
0
1
1
@ploeh I'd even go as far saying that the test code is more important than production code, thus needs to be cleaner. After all, with a good test suite, you can always clean up your production code. But cleaning up tests without losing coverage can be surprisingly challenging.
1
5
8
New article: Treat test code like production code.
blog.ploeh.dk
You have to read and maintain test code, too.
2
2
17
#repostfriday TDD improves reusability.
blog.ploeh.dk
The unit tests are the first client of the production API. Production code is reuse.
0
1
9
New article: Result is the most boring sum type.
blog.ploeh.dk
If you don't see the point, you may be looking in the wrong place.
3
2
11
#repostfriday Modelling versus shaping reality.
blog.ploeh.dk
How does software development relate to reality?
0
1
3
0
1
0
New article: Empirical software prototyping.
blog.ploeh.dk
How do you add tests to a proof-of-concept? Should you?
1
1
11
New article: 100% coverage is not that trivial.
blog.ploeh.dk
Dispelling a myth I helped propagate.
1
0
7
'Paratechnical power user'. Nice phrase coinage. Well done, 2023-me! #repostfriday
blog.ploeh.dk
Persistence concerns second.
0
0
6
Other readers are showing their appreciation of ploeh blog by supporting it. You, too, can do that.
blog.ploeh.dk
Ploeh blog is free, and always has been. Keep it free.
0
0
2
New article: Empirical Characterization Testing.
blog.ploeh.dk
Gathering empirical evidence while adding tests to legacy code.
0
3
5
I'm almost afraid to jinx it, but I've been writing non-trivial Haskell in @code all week, and been impressed with how stable and useful it's become of late 👍👌
marketplace.visualstudio.com
Extension for Visual Studio Code - Haskell language support powered by the Haskell Language Server
1
1
13
#repostfriday When to refactor:
blog.ploeh.dk
FAQ: How do I convince my manager to let me refactor?
0
0
5
0
2
2
Here @ploeh discusses how much of this applies to property-based testing https://t.co/H2Hukxni4X
blog.ploeh.dk
Including an example of property-based testing without much partitioning.
0
2
3