All I’ve got is a nubby yubikey nano

To be fair, I’m not sure why firebase even has a public access option. That’s a recipe for issues.

Though if it’s anything like Google Cloud Store, they hopefully make it very clear that your bucket is public.

They all got $200M last week

But anything the US feds contracted them for, like building data centres, they have to comply or they face penalties and have to pay all the costs back.

10 days ago, a week before this was announced, they awarded $200M contracts each to Anthropic, OpenAI, Google and xAI

This doesn’t doom the public versions, but they now have a pretty strong incentive to save money and make them comply with the US governments new definition of truth.

And they sent this magnificent specimen to work the mines, where nobody can even see him.

What do they do with the daddy computers? All of mine only have female ports.

The first few iterations were good, when they went mass market they let quality go.

Yeah, sadly SpaceX and Tesla are both very promising companies primarily held back by Elon Musk.

That’s kind of just semantics and the frap the Trump admin is doing to say it doesn’t exist.

The FBI definitely has a file on this. They have the contents of his vault, his log books, etc.

Everyone on the Epstein list deserves to face open justice.

If he’s innocent he could have just released the list and proven it to the whole world.

I don’t think anyone would even trust that now.

Well it is owned by Oracle now

I don’t know rust, but for example in Swift the type system can make things way more difficult.

Before they added macros if you wanted to write ORM code on a SQL database it was brutal, and if you need to go into raw buffers it’s generally easier to just write C/objc code and a bridging header. The type system can make it harder to reason about performance too because you lose some visibility in what actually gets compiled.

The Swift type system has improved, but I’ve spent a lot of time fighting with it. I just try to avoid generics and type erasure now.

I’ve had similar experiences with Java and Scala.

That’s what I mean about it being nice to drop out of setting up some type hierarchy and interfaces and just working with a raw buffers or function pointers.

I actually do like that C/C++ let you do this stuff.

Sometimes it’s nice to acknowledge that I’m writing software for a computer and it’s all just bytes. Sometimes I don’t really want to wrestle with the ivory tower of abstract type theory mixed with vague compiler errors, I just want to allocate a block of memory and apply a minimal set rules on top.

Reminds me of java

I have Toolkit toolkit = Toolkit.getDefaultToolkit(); seared into my brain. Then there were the bean factories…

In defence of plants, it takes a highly evolved form of life to be able to do nothing all day and get away with it.

I tried following my cat and all he lead me to was his food bowl.

Batch process turning unstructured free form text data into structured outputs.

As a crappy example imagine if you wanted to download metadata about your albums but they’re all labelled “Various Artists”. You can use an LLM call to read the album description and fix the track artists for the tracks, now you can properly organize your collection.

I’m using the same idea, different domain and a complex set of inputs.

It can be much more cost effective than manually spending days tagging data and writing custom importers.

You can definitely go lighter than LLMs. You can use gensim to do category matching, you can use sentence transformers and nearest neighbours (this is basically what Semantle does), but LLM performed the best on more complex document input.

One built a bunch of local search tools with MCP and that’s where I get a lot of my value out of it

RAG workflows are incredibly useful and with modern agents and tool calls work very well.

They kind of went out of style but it’s a perfect use case.

The tool isn’t returning all code, but it is sending code.

I had discussions with my CTO and security team before integrating Claude code.

I have to use Gemini in one specific workflow and Gemini had a lot of landlines for how they use your data. Anthropic was easier to understand.

Anthropic also has some guidance for running Claude Code in a container with firewall and your specified dev tools, it works but that’s not my area of expertise.

The container doesn’t solve all the issues like using remote servers, but it does let you restrict what files and network requests Claude can access (so e.g. Claude can’t read your env vars or ssh key files).

I do try local LLMs but they’re not there yet on my machine for most use cases. Gemma 3n is decent if you need small model performance and tool calls, phi4 works but isn’t thinking (the thinking variants are awful), and I’m exploring dream coder and diffusion models. R1 is still one of the best local models but frequently overthinks, even the new release. Context window is the largest limiting factor I find locally.

Vibe coding you do end up spending a lot of time waiting for prompts, so I get the results of that study.

I fall pretty deep in the power user category for LLMs, so I don’t really feel that the study applies well to me, but also I acknowledge I can be biased there.

I have custom proprietary MCPs for semantic search over my code bases that lets AI do repeated graph searches on my code (imagine combining language server, ctags, networkx, and grep+fuzzy search). That is way faster than iteratively grepping and code scanning manually with a low chance of LLM errors. By the time I open GitHub code search or run ripgrep Claude has used already prioritized and listed my modules to investigate.

That tool alone with an LLM can save me half a day of research and debugging on complex tickets, which pays for an AI subscription alone. I have other internal tools to accelerate work too.

I use it to organize my JIRA tickets and plan my daily goals. I actually get Claude to do a lot of triage for me before I even start a task, which cuts the investigation phase to a few minutes on small tasks.

I use it to review all my PRs before I ask a human to look, it catches a lot of small things and can correct them, then the PR avoids the bike shedding nitpicks some reviewers love. Claude can do this, Copilot will only ever point out nitpicks, so the model makes a huge difference here. But regardless, 1 fewer review request cycle helps keep things moving.

It’s a huge boon to debugging — much faster than searching errors manually. Especially helpful on the types of errors you have to rabbit hole GitHub issue content chains to solve.

It’s very fast to get projects to MVP while following common structure/idioms, and can help write unit tests quickly for me. After the MVP stage it sucks and I go back to manually coding.

I use it to generate code snippets where documentation sucks. If you look at the ibis library in Python for example the docs are Byzantine and poorly organized. LLMs are better at finding the relevant docs than I am there. I mostly use LLM search instead of manual for doc search now.

I have a lot of custom scripts and calculators and apps that I made with it which keep me more focused on my actual work and accelerate things.

I regularly have the LLM help me write bash or python or jq scripts when I need to audit codebases for large refactors. That’s low maintenance one off work that can be easily verified but complex to write. I never remember the syntax for bash and jq even after using them for years.

I guess the short version is I tend to build tools for the AI, then let the LLM use those tools to improve and accelerate my workflows. That returns a lot of time back to me.

I do try vibe coding but end up in the same time sink traps as the study found. If the LLM is ever wrong, you save time forking the chat than trying to realign it, but it’s still likely to be slower. Repeat chats result in the same pitfalls for complex issues and bugs, so you have to abandon that state quickly.

Vibe coding small revisions can still be a bit faster and it’s great at helping me with documentation.