
Charles O'Farrell retweeted
New blog post by @EdskoDeVries on falsify, his new Haskell property-based testing library with Hypothesis-inspired shrinking well-typed.com/blog/2023/04/…
I must be crazy, but I can't find another way to get strict unsealed pattern matching errors without using the typelevel scala compiler. Is there an easier way? How are people not finding this annoying?
github.com/typelevel/scala/b…
Charles O'Farrell retweeted
As I've been saying, the producers of news need to not only debunk, but actively #decenterTrump.
Last night, Anderson Cooper did a monologue about this very subject. It got surprisingly emotional. Watch:
As much as I love code review I have come to believe the private sector has embraced the wrong parts from open sourcr, especially it being a mandatory gate. Post merge reviews should be the default where there should be more trust.
giladpeleg.com/blog/better-c…
Charles O'Farrell retweeted
Just a reminder that life's too short to reject someone's PR just because they did things differently than you would have done.
Charles O'Farrell retweeted
I noticed today that the originator of gitflow has added a note at the top of his gitflow page cautioning that it's a bad idea to use gitflow if you're building web apps.
Again, for those in the back: IT'S A BAD IDEA TO USE GITFLOW FOR WEB APPS
nvie.com/posts/a-successful-…
Charles O'Farrell retweeted
This morning I decided to use @hedgehogqa for the property-based testing chapter of my Scala book. Tonight I created my first pull request for the project. That escalated quickly.
Charles O'Farrell retweeted
Shape Up is a new book published on the web that describes how we build software at Basecamp. The 6-week cycles, scoping the work, budgets instead of estimates, assigning projects not tasks, and forgoing the dreaded backlog. It's all here. basecamp.com/shapeup/
Charles O'Farrell retweeted
Fantastic article on the Dropbox tech blog on designing for reliability, the actor model, the "error kernel", testing the error kernel, property based testing and measuring the risk profile of software when deciding and prioritizing feature development. dropbox.tech/application/bui…
Charles O'Farrell retweeted
Some levity during these times: Krazam released one of the funniest sketches they’ve done so far.
Microservices accurately depicts how all PM meetings go 👇
youtu.be/y8OnoxKotPQ
Charles O'Farrell retweeted
I feel like "technical debt" is the wrong metaphor, because with debt you can control the payment schedule. "Technical land mines" would be more accurate, because the poor technical choices blow up in your face with little advance warning
Charles O'Farrell retweeted
Continuing to use model checking with Hedgehog to verify some in-production code, and continuing to find very subtle design flaws. I thought this code was solid, it's far from it.
This technique is a must to have in your toolbox!
Charles O'Farrell retweeted
If you've ever tried to test a stateful app in QuickCheck, Hedgehog or any other property-based testing library you'll know it can be seriously difficult!
Check out this tutorial for a simple way to test stateful apps using Hedgehog.
jacobstanley.io/how-to-use-h…
Charles O'Farrell retweeted
I guarantee there's at least one thing on this list which you don't know about.
jacobstanley.io/5-tips-for-b…
Charles O'Farrell retweeted
“My boss invited me for a one-on-one chat where they politely asked me to revert my change. I was aghast. The old code was a mess, and mine was clean!
I begrudginly complied, but it took me years to see they were right.” overreacted.io/goodbye-clean…



















