mathijs

I've used simpler agents like Copilot and Devin/Windsurf/Cascade/whateveritiscallednow, mainly in IntelliJ, and depending on the model, they starts showing behaviour that is at least remotely like this.

Example: put the agent in Ask mode (so it can't edit files) and you'll see it try to edit files anyway. The train of thought shows "something went wrong editing the file, let me try a different way" and it'll start spewing out bash files or Python scripts that try to edit a file. None of it works or can be executed, but still.

Cheaper models often ignore the available function calls to find and edit files in the IDE, and will start asking for permission to execute grep and sed commands, as well as trying to echo entire bash or Python scripts to file again.

It is not exactly like an agent autonomously trying to hack Huggingface, but it is a way of frantically looking for a solution because 'giving up' is not what LLMs are trained for.

Hey, this is my blog, thanks for sharing!

I've been finding myself increasingly annoyed by non-coding managers thinking AI is going to bring 190% reduction of cost, or will replace entire divisions of coders. It's a helpful tool, sometimes, but sometimes also a complete and utter tool. So I wrote this rant about it.

Exactly. A video on YouTube posted '1 month ago' is not the latest episode I'm looking for. Much quicker to interpret than a timestamp. Sometimes a fuzzy date is enough.

Especially being from Europe: it is never clear if 10/04/23 means October 4th or April 11th unless you know which date format is being used.

Android Studio offers this out of the box since the beginning of this year, I believe

The apps do, but the website does not. music.google.com used to have native support, but to cast music.youtube.com you have to cast the tab, which is far less than perfect. (Instead of streaming directly from the CDN to the chromecast, casting a tab will stream from your desktop to the chromecast. It works so poorly that sometimes even the pitch changes slightly, like an old timey recording.)

And still no Chromecast support.

Makes sense. The principle of 2FA is to combine 'something you know' (a password) with 'something you own' (your phone). I guess the biometric lock is 'something you are' on top of that.

That's a plastic 'Flippo'. Similar to cardboard milk caps but they came in bags of potato chips and are made of plastic.

Not necessarily dark though... as an app developer I'd actually really want to hear the feedback from the people who dislike my app. As in any business, oftentimes the most disgruntled customer is the one that can provide the most useful feedback.

An even smarter way (in my opinion) of getting 5 star reviews is by showing the dialog only after x hours of use. Users most likely to rate badly will have the app uninstalled before the dialog shows.

I've used Xamarin for several projects and I greatly regret that decision. Granted, most of my hatred is targeted towards Xamarin Studio and Xamarin.Forms so if you use Visual Studio and build only native UIs then maybe your experience will be better.

However, in my experience, both Xamarin Studio and the build system are buggy as hell. Random or inexplicable build errors, things that break during updates, incompatibilities with official Android support libraries... I find myself doing 'clean project and rebuild' to fix random errors, or switching between alpha, beta and 'stable' channels all the time depending on which one does not have the bugs that I'm running in to.

Xamarin.Forms is simply a disaster. Because it aims to unify the apis for the UIs for various platforms it boils down to only the most common denominator of those platforms. And then makes it worse. Not only is it buggy, it is also very slow and incredibly limited. In our office we're keeping a list of all of Xamarin's silliness we encounter, here is just one of those:

    "Clicking a Button changes its text alignment from center to left-aligned; it requires writing a custom Renderer to solve this."

I admit that Microsoft is usually quick to fix those bugs, but it doesn't instill much trust in the system if you're constantly running into issues. Many days I am literally working 50% of the time on my app and 50% working/fighting my way around Xamarins issues.

I'd love to hear from someone using Visual Studio if their experience is more positive, but my advise is: please stay away from Xamarin.Forms and Xamarin Studio as much as possible.

Thanks! I didn't know that, but I'll check it out. Thanks!