Articles

  • Sep 29, 2024 | gog.com | Angus Morrison |James Sterling |Hayden Dingman

    Created with Sketch. Created with Sketch. Created with Sketch. Created with Sketch. Created with Sketch. Created with Sketch. Created with Sketch. Created with Sketch.

  • Aug 25, 2024 | howtocodeit.com | Angus Morrison

    Are you overwhelmed by the amount of choice Rust gives us for handling errors? Confused about when to return a structured error type or a Box<dyn Error>? Intimidated by Box<dyn Error + Send + Sync + 'static>'s beefy type signature? Whether you're building an application or library, this guide will help you make the right decision. I love error handling. I'm obsessed. I work in the finance and space industries, and things go wrong a lot. Failure cases vastly outnumber success cases.

  • Sep 10, 2023 | nzherald.co.nz | Angus Morrison

    OPINIONIt’s the hope that kills you. The hope that the players will forget everything they were told in the shed and just play some rugby like we know they can play. But it doesn’t happen. Not under this coach. We knew Saturday’s performance against France was coming. We knew it was coming and we couldn’t do a damn thing about it. We knew it because we’ve spent four years watching the All Blacks get gradually worse and Ian Foster have less of a clue every time he sends a team out there.

  • Jun 26, 2023 | betterprogramming.pub | Angus Morrison

    How enum-specific compiler optimizations keep our programs performantRecently, while touring the std::io::Result source code, I found something that challenged my understanding of Rust’s enum types. On 64-bit systems, std::io::Error is a wrapper around a bit-packed internal representation, Repr:pub struct Error { repr: Repr,}struct Repr(NonNull<()>, PhantomData<ErrorData<Box<Custom>>>)The definition of Repr looks spooky, but the details aren’t important.

  • May 23, 2023 | betterprogramming.pub | Angus Morrison

    Log anything with confidence by making your secrets unloggableHow many countless hours have you wasted trying to find the cause of bugs in code without proper instrumentation? Bugs that would be trivial if only someone had logged the inputs, outputs and errors of the right function at the right time? I’m over it. I’d rather build things than spend my day chasing heisenbugs. That’s why I log everything.

Contact details

Socials & Sites

Try JournoFinder For Free

Search and contact over 1M+ journalist profiles, browse 100M+ articles, and unlock powerful PR tools.

Start Your 7-Day Free Trial →