Conor MahoodDec 28, 2022

Teach me something useful about a subject you know very well.

Doesn't have to be a detailed lesson, in fact ideally just a few words or a single post.

Boosts appreciated, 2023 is coming and I'd like to get smarter. Maybe we can all get a bit smarter.

I'll start:

My job is voiceovers and I can tell you with absolute confidence that reading your writing out loud is like a magic trick for better proofreading.

The mouth stumbles on mistakes the eyes glide over.

Show threadKaren Lopez šŸŒŽšŸ‘©ā€šŸ’»šŸ”’Dec 29, 2022
@ConorMahood @doalty Always assume data presented to you has an error of some point. Verify everything.
Show threadsmells of bikes
@DataChick @ConorMahood @doalty Extrapolated compliments of an ex-manager: the most dangerous data is when you take a measurement and get what you expected, so you don't bother to check your signal integrity/dataflow path. Make sure that you're measuring what you think you are, by forcing faults, so you know you're not just getting lucky but not actually correct results.
Dec 29, 2022 at 10:51pmWeb
Show threadGwyntaglawDec 31, 2022
@smellsofbikes @ConorMahood @doalty @DataChick This sounds a bit like a software maxim I have heard (and trust in): always be suspicious if code seems to run perfectly the first time.
Show threadTomDec 31, 2022

@ConorMahood @doalty @smellsofbikes @Gwyntaglaw @DataChick After 20 years, I can remember only a few times code ran perfectly the first time.

In each case, it was because Iā€™d spent a great deal of time examining the problem first.

Show threadKaren Lopez šŸŒŽšŸ‘©ā€šŸ’»šŸ”’Dec 31, 2022
@alttag @ConorMahood @doalty @smellsofbikes @Gwyntaglaw Iā€™m a typo queen. No chances here.