Developer @ Masabi. TDD zealot, cyclist, bassist and recent convert to the joys of woodworking
Yorkshire
Joined November 2012
- Tweets2K
- Following118
- Followers345
- Likes198
For obvious reasons, I too am jumping ship to bsky.app/profile/tddmonkey.b…. If you're interested in my yearly post, follow me over there.
Colin Vipurs retweeted
any time a jr DMs me with a question I always ask them to re-ask in the team channel so that it's searchable for future ref, and for others to see - maybe others have the same prob or they have the answer and will get to it faster than I can
I was told this is rude and makes them anxious. is that so wrong??????
Looking at some modern, clean Java today. As much as it is better than it used to be, it's still light years away from Kotlin. The ceremony around everything leaves too much code describing the "how", not the "what"
Colin Vipurs retweeted
If it's flaky and you know it, fix your test 🎶🎶
If it's flaky and you know it, fix your test 🎶🎶
If it's flaky and you know it, and you really wanna show it
If it's flaky and you know it, fix your test 🎶🎶
I'm seeing a lot of noise about monoliths lately. Neither monoliths or microservices are always "right", but if we go down this road I fully predict that in the future I'll be reading about huge, complex codebase that cannot scale.
Everything in tech comes round again.
Colin Vipurs retweeted
#TechnicalWriting: Prefer the active voice over the passive voice. For example:
❌ “The XYZ object is returned by this API.”
✅ “This API returns the XYZ object.”
Colin Vipurs retweeted
If you give your code to a competent programmer who's never seen it and they ask any questions, you've failed. Every question is a defect. Fix it.
Colin Vipurs retweeted
Great to see so many of the @Masabi_com crowd at our London office party last night, including music from one of our in-house bands featuring @cdpjenkins, @iamkenloh, Andrey and Doug, and also amazing double-decker bus cake from the positivity legend that is Jason Parmar.
Colin Vipurs retweeted
"Kotlin is now the recommended programming language for server-side JVM usage at Google, set to replace Java while still providing access to a large existing Java ecosystem."
youtu.be/o14wGByBRAQ
I’ve put together a simple list of rules to determine when you need to use a DI framework:
1 - You don’t.
You’re welcome.
There was a point in my software career where I could write programs that were functional but messy. Once done I could rewrite them to also be tidy.
I’m now at that point in my woodworking journey- it’s just much more time consuming and expensive to start from scratch!
So out of 4 tests:
2 tests were wrong (using direct class comparison rather than "is" check)
1 piece of production code was wrong (invalid default value hardcoded)
1 test was correct and the production code was right.
I can code, honest
I had written 4 tests before I spotted my error. Turns out that _none_ of them work.
Issue is using powerassert for Kotlin but wasn't registered in IDEA so the assertions were just ignored.
Oops.
Writing some tests after the code has been done (don't judge me). Test passed first time, moved on.
Hang on - aren't I the one that said you shouldn't trust a test you haven't seen fail?
Went back to check the test itself - turns out it passed _no matter what_ value I assert
Opener twitter app for the first time in a long time. Took me a good 2 minutes to figure out how to write a new tweet. Am I old or is it just a poor UX?
Colin Vipurs retweeted
idea: a gameshow called Imposter Syndrome where you take 10 senior developers and tell them that one of them is actually just a sales guy who's been taught to say DevOps buzzwords. to win, they have to figure out who the fake dev is. the trick: there is no sales guy
Does writing Hello World in a language you've not used before ever get old?
Finally got around to trying Erlang this week and seeing "Hello World" pop up - genuinely exciting