901 karma · joined June 28, 2023
/s
AI can help crank out commits & PRs at breakneck speed. But if you're unable to spot logical inconsistencies or inaccuracies within it, you're introducing bugs that will require subsequent PRs & reviews to fix them, when customers discover what you missed.
I am sorry for breaking trust, especially when the whole aim of Basilisk as a tool is to build trust. We have an absolute commitment to building the trust of the Python community so requesting this removal is a necessary step until we can work through the issues."
Though unfortunate that this happened, it's commendable the Basilisk author proactively identified and raised the problem & took responsibility for missing it. It's really easy to miss problems that AI introduces, and that's something I suspect most programmers are just learning how to deal with -- myself included.
I still say "Google it", but I don't use Google for search anymore -- haven't for almost two years, ever since I started subscribing to Kagi. If you're busting my ass about how I use "Google" as a verb, and you're still actually using Google to search, you can help yourself to a heaping serving of Shut The ** Up.
People would likely juggle the use of two stores if the value proposition was great enough. But it isn't, which is why Steam dominates and all their competitors operate in comparatively tiny fiefdoms.
As you already said, Azure is awful and only in second place behind AWS because of how much worse Google Cloud Platform is. Windows is back to sucking again, this time so hard that I'm seriously considering learning Linux and/or switching to macOS on my home system, & playing games on SteamOS instead. I almost never use Microsoft Office anymore, outside of household budgeting spreadsheets that I could easily work with LibreOffice instead.
Hackatons are commonly used as a way to take credit for & reap the benefits of another person or team's work, without attribution or compensation. And oftentimes, a promising hackathon idea will be "improved" by management & added to the creator's workload with tight deadlines (because the hard part is already done!) -- even if they don't necessarily agree with the "improvements".
I don't really care all that much, because my employer is the one paying for Copilot & wants us all using it. Personally, I think it sucks: the tooling is inconsistent across VSCode and Visual Studio, Microsoft caps the context window of Sonnet 4.6 at 200k even though it's capable of 1M, & at this price point there's almost certainly better ways of getting the same results from other models via other CLIs or plugins.
Even when I was building stuff in Kotlin, I couldn't figure out how to make async -- coroutines? RX? I forget already -- work, either. But that was all in the last few months before I left & moved back to the .NET stack.
idk who the hell would ever use a product that did that.
So it's going to be an internal implementation change -- that is, it generates the MSIL code that's generate when a developer writes async/await code, and won't require changes to how a developer writes async/await code?
I also find serialization/deserialization to be weak in .NET. Third-party Newtonsoft was king for years, then Microsoft released System.Text.Json. Years later, it lacks feature parity, including an easy way to debug like Newtonsoft did.