Hi,
I'm part of the team that built Sai. If you are curious about the tech, feel free to ask.
We are still limiting signups to keep our costs under control, but you can use the code "SIMULAR" to register. The first 1,000 users get access to Sai for $20/month (regular $200/month).
I find the Swift tooling very lacking. There's no way to lint dead code, there no way to auto format the files exactly as Xcode would do it and tell the linter those rules so that it doesn't lint your auto formatted code. Xcode project files are impossible to edit except with Xcode and Xcode often has issues and I need to manually empty the build folder. These are just some of the issues I remember
Now that some bikes have electronic shifting, you can attack the bike itself. I wrote two blog post about how to downgrade the Shimano Di2 shifters and do a replay attack to remotely shift it. You can find them here:
I think an important factor is also how long you had the same number. I switch numbers every couple of years because I get a new contract and moving the number to the new company is such a hassle. Over time you share your number with more and more companies and people who sell it or get breached.
My parents had their number for ~30 years. I never get spam calls or texts. They get one once a week or so (this is in Germany, we get a lot fewer of these calls).
In theory you cannot even say for all programs and all inputs if the program will finish the calculation [0]. In practice you often can break it down but the number of combinations of input is what makes it impossible to test everything. Most developers try to keep individual functions as small as possible to understand them easier. You can use math to do formal verification, but that gets difficult with real programs too.
UPDATE: Two people from Anthropic recommended me internally and their HR department already rejected the application. They recommended me for jobs where you need more experience with AI, so I agree that I wasn't a good fit for those positions. Thank you for your recommendations anyways. That was very kind.
A number of other people contacted me with offers so it looks like there will be a happy end to the story :-)
Correct, you cannot remove a version or the whole crate unless very specific criteria are fulfilled. You can "yank" versions. That prevents people from adding the version as a new dependency, but if you relied on it before it got yanked, your build will succeed.
I wouldn't delete old versions even if I could though. My goal is to publish a rock solid library that everyone can depend on and build awesome projects with
I don't know. I have no comparison but it is common for crates to be released under MIT. I took over the maintainership from the original author so the license was already there. I rewrote pretty much everything so I guess I could try changing the license now but that's not something I wanna think about.
I do the work because I see it as payback for all the great open source software I use all the time.
Right now it is just a hobby and there are still a number of bugs remaining. Since I don't have an income from it, I can't dedicate more time to it. Hiring me would allow me to work on fixing them full time and make the progress much faster
Hey, I'm the author of the blog post. Thank you for submitting this. If you have any questions feel free to ask and please let me know how the writing was. It's one of my first posts so I'd like to improve
https://www.emilydamstra.com/please-enough-dead-butterflies/