mceachen

gopher goes to 11

(archie and veronica are non-denumerable)

Oh man that's rough.

Your experience would make for excellent feedback for me if you're willing, email hello@ my domain name if you want complementary PLUS!

Just to clarify, I've open sourced a ton of PhotoStructure (exiftool-vendored, batch-cluster, fs-metadata, @photostructure/sqlite, sqlite-vec, and 10 more repos), but PhotoStructure's frontend and backend integrations are not open source. If PhotoStructure, Inc. ever closes, though, I will open source the repos powering the consumer product.

I've written open source for several decades, and certainly enjoyed the spoils of open source, but I've also seen a ton of bad behavior. Keeping it closed source certainly is not a guarantee that I avoid intellectual property theft or license violations, but at least I'm not just one agent prompt away from someone rebranding and reselling what I've worked full-time on for more than a decade.

You can switch to tgz which supports 50gb splits.

Don't rely on Google Takeouts for byte-perfect backups of your Google Photos library.

Depending on the device that uploaded the media and your country, they may have stripped GPS metadata from your media. I've also had captured-at times get changed randomly (!!) from your original media.

If possible, pull your media directly off your smartphone to make sure there are no shenanigans going on.

(These were painful discoveries made while trying to help support my PhotoStructure users)

I wrote the open source library that Immich (and PhotoStructure and several thousand other projects) use for metadata reads and writes.

PhotoStructure runs everywhere (laptops, desktops, macOS, Windows and Linux), libraries are portable across machines and OSes, there's a generous, usable free tier, and setup takes about three minutes. If you have any questions hop into our discord, we're a friendly bunch.

That's the combination to my HSM!

In almost every interview I gave at the last several companies I worked for, I'd start with "This may feel a bit odd, but with this coding problem, I'd appreciate if you spoke through your problem solving. If it helps, pretend like I am your intern. Good ideas, bad ideas, pros and cons of whatever you're considering, it's all valuable information for me to learn a bit about how you approach problems."

I feel like being explicit like this put candidates at a bit more ease than having them try to suss out what the interviewer is expecting from them implicitly (and I know there are many interviewers that will auto-veto any candidate with the audacity to suggest a possibly imperfect approach).

Yeah, took a look at your legacy codebase. Lots of deadwood, spaghetti, misalignments. I'd even say there was skeletal deformities in the architecture. If I was your uncle, I'd say it needed at least two full rewrites. Yeah, two, because the first rewrite will suffer from second system syndrome. You don't want that. Better to plan for both rewrites ahead of time.