this is a “soft delete”. as the author notes, depending on the nature of the data being stored a soft delete does not meet the requirements of many data privacy laws and compliance regulations (like GDPR’s right to erasure).
I've had cases where the rows in question absolutely could not be hard deleted, because of legacy foreign key relations. But the PII in those rows had to go. So we did a kind of "firm delete" by setting all columns (except the PK and a few necessary flags) to their default values and/or null.
if this was just to improve SEO, why not just slap in pre-rendering middleware and forgo SSR? like prerender.io or some headless chrome variant w/ cache? honest question, I’m not as experienced with the nuances of frontend dev
You mean in 2023? So many of my favorite SF dives closed during or as a result of covid: lucky 13, hemlock, whiskey thieves, bachus kirk just to name a few
a former employer of mine insisted we use phabricator (self-hosted) instead of github. while I initially fought it because of vpn requirement and UI/UX differences after years of github, I grew to quite like it. in particular the comment organization, handling of back-merges to trunk, and workflow standardization. not sure if it’s still maintained or not though
Hi, I'm Alex - a Bay Area software engineer with 13 years of experience, primarily in gaming and live events & ticketing industries. Most recently led engineering as Director then Principal Engineer for a small, interactive livestreaming startup.
Looking for a full-time position as staff-level IC or EM, either remote or hybrid. Contact me over email or linkedin (link can be found on my website above) with serious inquiries only.
