Yeah, I understand the surface-level reasoning. But to me the risk-to-reward ratio is a bit off. Resumes have very personal info on them. It’s also well known that engineers are wealthy. I could see something like this being used to generate a portfolio of high-quality, high-income targets for scams.
Cool thread/idea, but kind of weird in the age of LLMs and data scraping. If I wanted to build a database of engineers with really sensitive data, this is how I’d do part of that collection.
I don’t know if replacing Elixir is even one of the top 10 reasons Gleam exists. People don’t usually pick a platform and then pick a language.
Many times a language develops into an option by bundling features. In Gleam’s case, they bundled a certain type system, extreme developer convenience, and optionally features from BEAM.
Wow, the amount of work here and technical solutioning is insane. I don’t have any context here; so I wonder if this is a team or solo. If latter, how do you achieve so much with so many different technologies?
I’ve read probably 100 comments before I stopped. It’s really sad how negative HN has become. I wonder how many of those comments are from people that are really into coffee.
Super cool product. Especially interested in the grinder. I recently purchased a Niche Duo and was not very impressed in the upgrade from a Zero. Kind of wished I would have gone a different direction entirely. Maybe something like yours.
Regarding the website, I was on mobile and it seemed fine. I like the very Apple-y product showcasing. I think it’s fun.
Regarding the espresso machine, I think people are being very silly about the plastic and external heating source.
A tube going into kettle? Like, people are consuming 10x as much plastic eating beans out of a can or getting a coffee to go from their local shop.
The external heating source is also exactly how Modbar works. I think it’s cool you don’t double or triple the price by basically doing what Modbar does. A nice kettle can hold temps to approximate levels pretty well.
I think people should see this for what it is: a specialty espresso machine. It could be a statement piece, or perhaps a really interesting option for great espresso depending on how it performs. Have you tried to get it in front of daddy Hoffmann?
Very interested in stuff like this. I think similar “make an interactive bit to embed in an otherwise static site” things are being done in the Gleam ecosystem.
Amazing write up as usual, Erika. Your blog is an inspiration and model of what a tech blog should look like: high-quality info, plain and clear language, and extreme focus.
I want to know what they think. I also stylistically like the directness of “I” and “you”. Not everything needs to be written abstractly, academically, or in business-speak.
Not sure how secure erase works, but I’ve run into this a few times after “erasing”. I think it has something to do with boot records or partition tables. So there’s a piece of some drives (usually at the front) that contains this data. You can overwrite it properly with the appropriate tools. I always just used `dd` on the raw drive ref in Linux to blow it up.
We did do some encryption with LUKS, and I’d try to write over boot records, keys, and headers, but I was pessimistic that was enough. Not an encryption expert myself. Always felt that any given encryption tech (be it hardware or software) has possibility of vulnerability later found or backdoors.
So it made sense to me that a physical erasure prior to recommission would be good. There’s also regulatory/compliance checkboxes (be them effective or not).
Super interested in this and would love to hear about some techniques. Used to work at a HealthTech co. We had an “appliance” that we’d send to doctor offices to integrate with other diagnostic machines on the network.
Sometimes we would send out new ones to replace the old. When we got the old ones back, it was always unclear how to purge and recommission SSD/NVME drives.
My best attempt was using GNU shred, but it wasn’t recommended for flash-based storage back then.
It always amazes me how compact and readable Elixir code can be. I know the examples in article use a high-quality library that takes care of some of the ETS and Plug piping, but the business-level rules seem compact and readable too! :)