multiple times a day for me

idk what to tell you, because I just tried it and it works

ah, this puts it together and it’s exactly what I was looking for, thanks

ah yes, I stopped watching the guy because of that and the clickbait, but he does make some interesting content sometimes.

so you haven’t tried it recently

maybe last you tried it was over 6 months ago, maybe you’re using the old google assistant, or idk, but it definitely works for me

yeah, that’s what I’m looking for. Do you know of a way to integrate ollama with HA?

1. They can and do; 2. LLMs can do tool calling just fine, even self-hosted ones.

yeah, I really don’t get maintainers that try to put human hours to review PRs that are potentially AI generated. This equation will never balance out. There needs to be a first triaging layer that is automated, only then bring a human in the loop if it’s worth continuing.

Keeping tokens in plaintext on the client is really common. The alternative would require the user to enter a decryption password on every system start, like some wallets do, which is a bit of a hassle. If at least there was “one obvious way of doing this” across platforms, that’d make things better, but in reality, some tools can’t even put their configs and cache in a sensible location.

I’ve been using more https://cheat.sh/ or --help on specific commands and subcommands.

It’s usually less noise than in a man page, and no need to install a specific man page for each command you want.

I don’t quite get what this is supposed to do. Is it basically a software to allow jellyfin/plex users to request media without needing a radarr/sonarr account?

ugh, no way. It might do a fine job with typesetting, but the user experience is utterly awful and that’s very unlikely to change because of design choices over 40+ years. If you don’t think so, give typst a real try.

It seems your team is not ditching AI anytime soon, but you can still use it to tame technical debt. In fact, with the higher rate of code generation, I’d consider trying to write the best possible code when using AI a requirement.

Look into “skills” (as in the Anthropic’s standard) and how to use them in Cursor. Use custom prompts to your advantage - the fact you’re still getting code with lots of comments as if it was a tutorial, tells me that this can be improved. Push for rules to be applied at the project level, so your colleagues’ agents also follow them.

Make heavy use of AI to write regression tests for covering current application behavior: they’ll serve as regression warnings for future changes, and are a great tool to overcome the limits of AI context window (e.g. most times your agent won’t know you fixed a bug last week, and the changes it’s suggesting now break that again . The test will protect you there). Occasionally use AI to refactor a small function that’s somewhat related to your changes, if that improves the codebase.

Stepping away from AI, try introducing pre-commit hooks for code quality checks. See if the tools of your choice support “baseline” so you don’t need to fix 1000s of warnings when introducing that hook.

AI can write code that’s good enough, but it needs a little push to minimize tech debt and follow best practices despite the rest of the codebase not being at an ideal quality.

I find it really hard to replace maps, because half of the times I use it it’s because of photos, reviews, or traffic information that’s just not available in other places.

Maybe there’s a technical difference, but at least in Brazil, publicidade and propaganda are widely used as synonyms

• https://www.dicio.com.br/publicidade/
• https://pt.wikipedia.org/wiki/Escola_Superior_de_Propaganda_e_Marketing

It is uncommon to call propaganda (in the political sense) publicidade, so maybe in popular conversations this makes publicidade a kind of propaganda, and not the other way around.

Often “silent” fails are a good thing

Silent fails have caused me to waste many hours of my time trying to figure out what the fuck was happening with a simple script. I’ve been using -e on nearly all bash code I’ve written for years - with the exception of sourced ones - and wouldn’t go back.

If an unhandled error happened, I want my program to crash so I can evaluate whether I need to ignore it, or actually handle it.

Exactly, if an unhandled error happened I want my program to terminate. -e is a better default.

cool, does that mean it runs in the same event loop as the asgi server?

idk about other languages, but in Portuguese it’s literally the same word