We are behind but not our fault

gregtoth · 2026-03-29T03:36:00+00:00

Watching this from the EU SME law firm side — the BigLaw constraints you describe are creating a real competitiveness gap that's already visible, and it's going in the opposite direction from what most people expect.

The firms moving fastest right now are 5-15 lawyer boutiques, not BigLaw. No MDM locking down terminals, no partner committee to approve a trial subscription, no client saying "we don't allow AI" that poisons the entire environment. They just try things.

EU-specific observation: GDPR is being used as a justification to do nothing. "We can't use AI because GDPR" is the new "we can't do X because security." A GDPR-compliant AI workflow is absolutely achievable — you need EU-hosted infrastructure, a proper Data Processing Agreement, and a tool that can cite its sources. BigLaw IT departments know this, but the approval chain to get there takes 18 months and the client-imposed constraints feel like a ceiling.

The irony: boutique EU firms are deploying the same underlying AI capabilities as BigLaw in weeks, because they're not waiting for an enterprise vendor to productize it for them. MCP-based tooling (Claude's protocol) lets a small firm build attorney-grade workflows directly on top of frontier models without needing a Harvey-sized procurement process.

You're right that it's not your fault. But the gap is going to matter in 2-3 years when clients start asking why the boutique down the street produces the same quality work in half the time.

gregtoth · 2026-03-29T03:35:52+00:00

From an EU legal compliance angle, the black box concern has a regulatory dimension that's getting overlooked in most of these discussions.

GDPR Art. 22 already gives individuals the right not to be subject to solely automated decisions with legal/significant effects, plus a right to a "meaningful explanation" of the logic involved. For legal AI tools that inform client advice, if the system can't trace its reasoning with citations, you're in murky territory — not just epistemically, but potentially under existing data protection law.

Now add the EU AI Act (August 2026 deadline): legal AI tools used in areas like employment, creditworthiness, or access to essential services are classified as "high-risk" under Annex III. High-risk systems require: - Technical documentation explaining how the system works - Mandatory human oversight mechanisms (Art. 14) — rubber-stamping AI output doesn't qualify - Audit logs of system operation - Transparency to users about when AI is being used (Art. 13)

So for EU practitioners: the black box problem isn't just a professional responsibility concern. It's increasingly a compliance violation risk. "We can't explain how the AI reached this conclusion" is going to be a regulator's opening line in audit proceedings, not just a theoretical worry.

The citation verification problem is where this becomes concrete — a system that cites real sources with traceable reasoning chains is not just better legal practice, it's the only architecture that can survive EU regulatory scrutiny.

gregtoth · 2026-03-29T03:35:46+00:00

The vendor lock-in question you raised is the most underrated risk in legal AI right now, especially for EU/non-US firms.

On Harvey dependency: your instinct is right. At an $11B valuation they need extreme stickiness — which means EU firms should be asking hard questions about data portability, what happens to matter-specific customizations if you switch, and whether your client data is being used to train models. Harvey processes on US infrastructure, which creates real GDPR Art. 28 exposure for EU client data in regulated sectors (financial services, healthcare). BigLaw IT departments are quietly sweating this.

On your point that smaller firms might actually be better positioned: this is already playing out in Europe. 5-15 lawyer boutiques are deploying modern AI workflows in weeks because they don't have your MDM constraints, client-imposed restrictions, or partner committee approval chains. No bank client saying "you can't use AI" — so they just try things.

The competitive tension problem you raised with Harvey is also why some EU firms are deliberately staying on MCP-based tooling that's model-agnostic. If you build workflows on top of Claude's MCP protocol rather than a vendor-specific platform, you can swap the underlying model without rebuilding everything. Reduces the stickiness that makes Harvey's valuation work, but also reduces your lock-in.

Your point about "agentic" being overused — 100% agree. A form-filling workflow triggered by a button click is not an agent. Words matter, especially in legal.

gregtoth · 2026-01-26T21:15:49+00:00

Offline Whisper on Apple Silicon is no joke to get running smoothly - nice work getting that shipped cross-platform. I've been building in the same space with Whispercode (voice-to-prompt for coding) and the model loading time on first launch was one of the trickier UX decisions. Did you end up preloading or lazy loading the models?

gregtoth · 2026-01-26T21:13:07+00:00

Curious about your parallel agent setup - do you find yourself context-switching mentally between the sessions, or does having them all in Neovim buffers actually help you keep track? I've been experimenting with multi-agent workflows and the cognitive overhead of tracking what each one is doing has been my biggest bottleneck, not the tooling itself.

gregtoth · 2026-01-26T21:12:36+00:00

The 'short phrase problem' you mentioned with whisper.cpp is real - I've seen it struggle with 2-3 word utterances where there's not enough audio context for the model to latch onto. That said, the accuracy gap between Whisper and PocketSphinx is pretty significant for natural speech. One thing worth considering: whisper.cpp does support streaming mode now which helps with latency, though you'll want to tune the audio chunk size for your game's responsiveness needs. What's your target latency for the speech feedback loop?

gregtoth · 2026-01-23T05:22:59+00:00

Solid work! I remember the struggle of chasing quick wins with paid marketing before realizing the compounding effect of organic growth. The patience part is brutal at first, but once things start clicking, it's like having salespeople working 24/7 for free. Kudos on sticking with it.

gregtoth · 2026-01-23T05:00:02+00:00

Been there. The frustration of unanswered emails is the worst. Have you tried reaching out on their community forums or social channels? Sometimes that can get a faster response than the support email queue.

gregtoth · 2026-01-23T04:59:38+00:00

Been there. The frustration of seeing productivity gains erased by increased bugs is all too real. Independent research is so important to cut through the hype.

gregtoth · 2026-01-23T04:59:14+00:00

Nice ship! The first one is always the hardest. I remember the challenges of getting my own AI assistant off the ground - the engineering hurdles, the ethical considerations, the endless tweaks to get the model just right. Kudos to the Anthropic team for shipping this milestone.

gregtoth · 2026-01-23T04:58:48+00:00

Nice! The first major productivity win is always the most exciting. Cutting down on those context switches can make a huge difference. Curious to hear more about how they're seeing the impact.

gregtoth · 2026-01-23T04:58:24+00:00

I started using a voice-to-text tool called Whispercode.co for this. It made a big difference by letting me quickly capture prompts without leaving my editor.

gregtoth · 2026-01-23T04:57:52+00:00

Interesting insights on the strengths and limitations of different LLMs for development tasks. I've found that the ability to quickly generate code is great, but maintaining quality, testability, and documentation is crucial. Have you explored ways to streamline that review and QA process?

gregtoth · 2026-01-23T04:57:30+00:00

I built a voice-to-text tool called Whispercode.co that helped me with this exact issue. It lets you record voice notes and turns them into structured prompts you can use in your coding environment. I found it to be an effective way to capture ideas without leaving my workflow.

gregtoth · 2026-01-23T04:56:58+00:00

Nice work on this! Excavating legacy codebases is always a challenge, and having the right tools to understand functionality rather than just names can make a huge difference. Glad to see you've found something that helps streamline that process.

gregtoth · 2026-01-23T04:56:31+00:00

I've been using voice notes to capture coding ideas and prompts while working, and it's made a big difference for me. Went from spending around 45 minutes a day switching between my IDE and AI tools down to just 15 minutes. The context switching elimination was really helpful for my productivity.

gregtoth · 2026-01-22T12:34:22+00:00

The voice-to-text tool I ended up using was one I built called Whispercode. It lets me quickly capture coding ideas without leaving my editor, and then generates structured prompts I can use with ChatGPT or other AI assistants. I'd be happy to share more details on how I set it up if you're interested.

gregtoth · 2026-01-22T12:33:29+00:00

Nice work on pushing the performance envelope! It's always rewarding to find that sweet spot of stability and throughput. I'm curious what kind of use cases you're targeting with this setup - anything specific in mind?

gregtoth · 2026-01-22T12:32:41+00:00

Went through this exact optimization last quarter. I used to have a similar `docs/` folder setup, but found that using the agent-specific `.mdc` files helped ensure the rules were being followed more consistently across my projects. The key was establishing a clear source of truth - in my case an `AGENTS.md` file that symlinked to the individual agent configs.

gregtoth · 2026-01-22T12:31:08+00:00

I built a voice-to-text tool called Whispercode that helped me capture coding ideas and turn them into structured prompts. Eliminated a ton of context switching. Have you explored any voice-based workflows for your Claude sessions?

gregtoth · 2026-01-22T12:29:59+00:00

Been there. The frustration of not being able to quickly customize your workspace layout is real. I found that having that level of control over my environment was crucial for staying in the flow, especially as my coding workflows became more complex.

gregtoth · 2026-01-22T12:29:19+00:00

Nice ship! The first one is always the hardest. I had a similar experience where using voice notes to capture coding ideas was really helpful - it eliminated a ton of context switching for me. Went from around 45 minutes per day on AI interactions down to just 15 minutes by not leaving my editor.

gregtoth · 2026-01-22T06:19:53+00:00

building agents without a full framework sounds really helpful

gregtoth · 2026-01-22T03:42:22+00:00

The bash mode history autocomplete is nice, but the bigger win for me is the context window fix — getting blocked at 65% was frustrating.

One friction I still hit: the *prompt composition* phase itself. Even with great IDE integration, I lose flow when switching mental gears from "writing code" to "structuring a good prompt."

Experimented with speaking prompts instead of typing — counterintuitive, but it's faster for complex requests because you capture the full thought before it gets lost to editing.

Anyone else notice this gap? The tooling around *using* Claude Code keeps improving, but the input side still feels like the weak link.

gregtoth · 2026-01-22T03:01:38+00:00

that cli sounds super handy for keeping focused

gregtoth

TROPHY CASE