This article was originally posted on HBCUvc’s website. This article was generated by Hadiyah Mujhid in collaboration with ChatGPT, based on a thoughtful conversation about race and identity in venture capital talent evaluation. You can read the full conversation with prompts and responses by clicking here. In venture capital, where relationships, networks, and access are […]

Fuzz testing is a technique for automatically uncovering bugs in software. The problem is that it’s a pain to set up. Read any fuzz testing tutorial, and the first task is an hour of building tools from source and chasing down dependencies upon dependencies. I recently found that Nix eliminates a lot of the gruntwork from fuzz testing. I created a Nix configuration that kicks off a fuzz testing workflow with a single command.

This is the second half of a post about using Nix to automate a fuzz testing workflow. At this point, I can run honggfuzz against pdftotext, but it takes a bit of manual effort to get things started. I promised in part one that I’d get all of the installation and fuzzing down to a single command. Downloading tricky PDFs In my ad-hoc fuzzing, I manually downloaded a PDF from the IRS website.

Last week, I saw an interesting article on the /r/legaladvice subreddit. An e-commerce business owner was complaining that a customer was suing because the merchant had been sending the customer promotional emails for years that the customer never agreed to. The author deleted the post a few days later, but I found a copy of the text. The merchant was indignant and felt like it was a shakedown, but I was 100% on the customer’s side.

Plan 9 clustering at home