ploeh Profile Banner
Mark Seemann Profile
Mark Seemann

@ploeh

Followers
17K
Following
133
Media
411
Statuses
27K

Danish software design

Copenhagen
Joined May 2009
Don't wanna be here? Send us removal request.
@ploeh
Mark Seemann
2 days
TIL that it's possible to yield from within #fsharp lists: > [yield 1; yield! [2;3]; yield 4];; val it: int list = [1; 2; 3; 4]
2
0
4
@ploeh
Mark Seemann
4 days
New article: Pattern guards for a protocol.
Tweet card summary image
blog.ploeh.dk
A Haskell example.
0
1
6
@ploeh
Mark Seemann
7 days
#repostfriday Decouple to delete.
Tweet card summary image
blog.ploeh.dk
Don't try to predict the future.
0
1
5
@GGalezowski
Grzegorz Galezowski
10 days
@ploeh I also found this article: https://t.co/rJgUWSM14k by Vladimir Khorikov essential in explaining the supposed dichotomy of DAMP vs DRY.
Tweet card summary image
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
@ploeh
Mark Seemann
10 days
Other readers are showing their appreciation of ploeh blog by supporting it. You, too, can do that.
Tweet card summary image
blog.ploeh.dk
Ploeh blog is free, and always has been. Keep it free.
0
1
1
@VasiliyZukanov
Vasiliy Zukanov
11 days
@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
@ploeh
Mark Seemann
11 days
New article: Treat test code like production code.
Tweet card summary image
blog.ploeh.dk
You have to read and maintain test code, too.
2
2
17
@ploeh
Mark Seemann
18 days
New article: Result is the most boring sum type.
Tweet card summary image
blog.ploeh.dk
If you don't see the point, you may be looking in the wrong place.
3
2
11
@ploeh
Mark Seemann
21 days
#repostfriday Modelling versus shaping reality.
Tweet card summary image
blog.ploeh.dk
How does software development relate to reality?
0
1
3
@nikosbaxevanis
Nikos Baxevanis
23 days
@URozmej I think this post by @ploeh is relevant here.
0
1
0
@ploeh
Mark Seemann
25 days
New article: Empirical software prototyping.
Tweet card summary image
blog.ploeh.dk
How do you add tests to a proof-of-concept? Should you?
1
1
11
@ploeh
Mark Seemann
1 month
New article: 100% coverage is not that trivial.
Tweet card summary image
blog.ploeh.dk
Dispelling a myth I helped propagate.
1
0
7
@ploeh
Mark Seemann
1 month
'Paratechnical power user'. Nice phrase coinage. Well done, 2023-me! #repostfriday
Tweet card summary image
blog.ploeh.dk
Persistence concerns second.
0
0
6
@ploeh
Mark Seemann
1 month
Other readers are showing their appreciation of ploeh blog by supporting it. You, too, can do that.
Tweet card summary image
blog.ploeh.dk
Ploeh blog is free, and always has been. Keep it free.
0
0
2
@ploeh
Mark Seemann
1 month
New article: Empirical Characterization Testing.
Tweet card summary image
blog.ploeh.dk
Gathering empirical evidence while adding tests to legacy code.
0
3
5
@ploeh
Mark Seemann
1 month
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 👍👌
Tweet card summary image
marketplace.visualstudio.com
Extension for Visual Studio Code - Haskell language support powered by the Haskell Language Server
1
1
13
@mikemoorhouse
Mike Moorhouse
1 month
@yacineMTB https://t.co/NN3JfrXVV8 from the man who wrote the book on DI @ploeh
0
2
2
@MaineFrameworks
Chase Saunders
1 month
Here @ploeh discusses how much of this applies to property-based testing https://t.co/H2Hukxni4X
Tweet card summary image
blog.ploeh.dk
Including an example of property-based testing without much partitioning.
0
2
3