This is the Dropbox problem. People are willing to pay for convenience, and tech folks tend to underestimate how much convenience comes from seemingly simple solutions
It may not be their duty to filter it out, but it should definitely be their duty to not take money to bump it to the top of their results. Let the algorithm dump random unlinked medium posts on the 5th page where they belong
Yeah Telegram only has 1:1 opt-in E2EE, that you can't use across your devices, so either you or your buddy quickly gets tired of whipping out their phone when they're sitting at their laptop, and just replies you through Telegram's non-E2EE cloud chats, and that's the backdoor. The user activated it. It's "their fault".
I'm not going to promote Telegram, just wanted to highlight that Whatsapp is not considered trustworthy by a geopolitical enemy of US. I don't think that Telegram is bad, and when your life depends on it, you can click "Secret Chat" button, it's not a big deal.
It's a bit vague, but the idea is right. If your SaaS is built with AI, then any customer you have can also build it with AI, and whatever they build is going to be better suited to their needs and will run cheaper because they aren't paying your margin. AI skews the build vs buy curve massively, because it makes building so much easier
How are those "bugs" not immediately disqualifying? "Move fast and break things" is not an acceptable strategy for controlling 2 tonne bricks hurtling down the freeway
Homebrew's built a package manager on top of git. I'm talking about platforms that generate built artifacts and have package managers with dependency resolution to fetch them.
Anecdotally, Claude Bug Bot has actually been super impressive in understanding non trivial changes. Like, today, it noted a race condition in a ~1000 line go change that go test -race didnt pick up. There are definitely issues though. For one, it's non deterministic, so you end up with half a dozen commits, with each run noting different issues. For a second, it tends to be quite in favour of premature optimisation. But over all, well worth it in my experience
I haven't used the bug bot, but I like asking claude code to just review my PR in the command line. Yesterday it found a bug in a data structure I was implementing (it didn't support ZSTs properly). Of course, the fix it suggested was completely wrong, but what are ya gonna do. Still saved me from embarrassing myself before asking for a review
Pinning certs has generally been discouraged for a while afaik. It's pretty trivial to bypass, at least on Android where you can side load easy, and it's a pain in the ass to manage with a huge potential to just take down your app if you mess it up
reply