vekker

This is awesome! Does it work in EU as well?

Does this also recognize peaks as well as PeakFinder does?

Doesn't this suit a prepush hook or CI job better?

I personally want to keep my commits light & fast, so it's not an impediment to commit often. I've always found even a simple reformatter on commit can be a bit annoying. Ideally for every micro-task done I commit, even if it's messy and even if I decide to revert the work later. It becomes kind of like a reasoning trace. Only when the task is completed, must the code comply to all the necessary checks, and then it becomes a PR and CI jobs run to validate

You can use any (Anthropic API-compatible) provider and any model with Claude Code, it's just a matter of changing the env vars in the settings json...

Can confirm this is a really excellent piece of OSS for local STT, I use it in both English and Dutch.

The only thing it has trouble with are brand/product/tooling/person names. You can add custom vocabulary, but then it tends to over-correct and insert those custom words when I never said them. However this isn't unique to local STT, frontier cloud models also struggle with this.

Hm, the main headache I have with .env files is simply that I lose them (switching between machines etc...), or the trouble of sharing secrets with team mates, etc... The headache of keeping them up to date and synced across environments & machines.

Not affiliated but those troubles are now finally solved with Infisical for me. It's open source so I happily give them a plug.

I feel like these days it's more like managing a team of seniors who are technically very competent, but may not always have the full domain context of the problem they're solving. And/or they forget parts, if that context is too large. And/or they have a poor temporal dimension (deprecated badly maintained information polluting the context).

They also tend to overengineer solutions if not guided well.

If you think about it, in that respect it's not that different from managing actual human senior engineers.

I think this is why focussing one's limited human attention more the input (defining clear requirements) as well as on validating the output (good CI/CD including end-to-end automated tests) is far more important than manual code reviews and micro-managing the development process.

What does "scanning" mean though?

Does this mean every parent has to now make sure not to take pictures of their children playing in bath for instance, in order not to trip these scans for false positives?

For ages I've been looking for a way to easily share & sync a simple knowledgebase (HTML/MD and other files in folders) with my team (= including non-technical people), using Git as the sync/versioning layer, without it being too technical, and without getting vendor lock-in with expensive & unnecessarily complex cloud-based platforms.

Having built-in AI integration without relying on sketchy plugins would be the cherry on top (although, seriously missing the option to connect with any openai-compatible LLM provider like someone else mentioned here).

Seems like this might almost offer exactly that? I'll have to try it out...

I literally wrote how I measure this in the post you are replying to: #commits which is admittedly a worthless proxy for productivity, so, more importantly, number of finished production-ready features delivered.

That number is at least tenfold of what it was before, simply because I can run a lot of gruntwork in parallel now without wasting brainpower and focus on that stuff.

> Seriously, what value are tokens providing other than justifying layoffs

Like the OP said, it's incredible how polarizing this debate is. When I read comments like yours, I feel like a significant part of the global workforce in IT must be living on another planet? Or they never really used Claude Code, Codex, OpenCode, ... intensively before because of company policies?

I legitimately am at least 10x more productive than a year ago, and I can prove it in number of commits and finished monetizable features developed per day. Obviously my workflows still very much require an active, constantly context-switching human-in-the-loop, but to me there's absolutely no question both output volume & quality have skyrocketed.

Isn't this just an artifact of their chain-of-thought reasoning? If they are verbose in their output, it's more likely the next word predicted is actually correct.

Also, I see this more as a feature than a bug. In many projects I inherited in the past, I wish the original devs were a bit more verbose. Then again, with every developer using LLMs now, probably the opposite applies now.

You could also use plain markdown files, any free Markdown editor/IDE, and git, and sync with a remote Git repo using gcrypt for encryption (git-remote-gcrypt).

It's just a bit of a pain to set up, and also, not mobile-friendly.

The 2% of cases when you need the commit log (or more importantly: someone else who inherits your code...) justifies writing good messages imho.

If you make a change to your codebase, normally you know what you want to achieve and why (otherwise... what are you even doing?). A commit message is just putting that in writing... that only takes a few seconds, often less than it takes to write the code.

So it's just a good habit to have. It forces you to think more about the changes you do & why, so it makes you a better software developer. Creating any new habit always takes some energy initially, but it's worth it.

Cool, but I wonder... is this really a feasible workflow?

The way I use LLMs is, I enter a very specific query, and then I check the output, meticulously reviewing both the visual output and the code before I proceed. Component by component, piece by piece.

Otherwise, if you just "let it rip", I find that errors compound, and what you get isn't reliable, isn't what you intended, increases technical debt, or is just straight up dangerous.

So how can you do this from a smartphone? Don't you need your editor, and a way to run your code to review it carefully, before you can provide further input to Claude Code? Basically, how can you iterate from a phone?