andrewzeno

Thank you! Cloud backups means you can sync the profiles to the cloud. Cookie bot hours mean that your profile will get launched in the cloud and a bot will go onto different websites to build your browser cookies, like opening a website that uses Google Tag Manager on schedule. Will think about the wording in the tooltips, thanks!

lol thankfully no. My GitHub is in bio

My email is filled with junk from cybersecurity "experts" telling me that my open source project is "very compromised" and that they will gladly reveal to me what the issue is, if I commit to paying them a bug bounty. I get at least a few every week. I hate them, but I feel like we are well past the point where in any place where there is money to be made, the majority of cold outreach will be from semi-personalized AI agents. You just have to accept that most of the time your get contacted by someone, it is likely not a human.

This is the way. Hopefully they learned from IKEA which instead of firing 8,500 support agents retrained them into interior designers.

Companies still need to verify your competence. You should be prepared to answer LeetCode mediums and ensure that your soft skills are strong. What you did at your previous company and how likeable you are are more important than ever.

I think this is an interesting idea, but I don't see a reason to use it in the current state. Claude Code can already create memories and those work similarly, except Claude "reflects" and "validates" memories only when you tell it that they are wrong.

If you are missing business context, update CLAUDE.md yourself. In a project where Claude makes few mistakes (like a web app) you don't need any form of memory. If it is something complex, it will not help. I work on an anti-detect Chromium fork and tried creating memories for every iteration of changes, recording what worked and what didn't. At some point it just made things worse by Claude confidently doing some nonsense while refernsing test results from a previous Chromium version.

I think this article is great, but it doesn't focus on the open source aspect. GitHub still has effective monopoly on open source, simply because of how much free resources they provide, let alone higher chances of getting your project discovered and fewer barriers for people reporting issues.