taberiand

6 ms·

1.
by taberiand 15d ago
Seems to me it's a reasonable position that runs face first into the irrational market. Like they're digging a gigantic hole and Ed's up the top saying if you keep digging the hole will collapse (+ a whole lot of unnecessary
2.
by taberiand 15d ago
Most of us just shovel CRUD, we really should be honest with ourselves.
3.
by taberiand 17d ago
I remember reading an article years ago about how a company was running rings around its competition because they were releasing features faster and more effectively, due to their choice to use Lisp as their language. Of course a competitor
4.
by taberiand 17d ago
That's my belief as well: modular architecture and separation of concerns is orthogonal to monolith <-> microservice infrastructure axis. And Service Oriented Architecture is the nice middle ground of that infrastructure axis
5.
by taberiand 1mo ago
Then you mow side to side
6.
by taberiand 2mo ago
The models are good enough these days that I see it like managing a team of juniors. The LLMs need guidance and oversight, and about the same amount of time I'd spend reviewing code from a junior I spend on the LLM output. I think gene
7.
by taberiand 3mo ago
You could probably get Claude to build the plugin for you
8.
by taberiand 4mo ago
We used fast.com to speed test our new office internet connection and the next day got an irate email from corporate (who had argued we didn't need the new connection) about "watching Netflix all day". I imagine some C-level
9.
by taberiand 4mo ago
Well sure - that's essentially the same as wrapping the whole workflow in a version check for each version; copy-paste the whole lot and change the code wherever. It's still surfacing an issue that would otherwise be less visible
10.
by taberiand 4mo ago
> Depending on how your code is written, modifying code baked into workflows becomes complex, as anything that modifies the history event ordering breaks determinism in already-deployed workers. I see this as Temporal surfacing inherent
11.
by taberiand 4mo ago
Discrimination of sexual orientation, for example, depending on how it's asked. Just one of those areas best left alone in an interview
12.
by taberiand 5mo ago
Don't rewrite shared public history It's ok to force-push a branch that only you have worked on (and even in the case of others working on the same branch it can be fine as long as you communicate with them)
13.
by taberiand 5mo ago
How does the megamerge handle the case where two included branches overlap in changes and a new commit is made that applies to the overlap?
14.
by taberiand 5mo ago
This is true but I don't think the downvotes are "fake" though. There's just a whole lot of people who truly believe they are Making the World a Better Place Through Capitalism
15.
by taberiand 5mo ago
At least until they actually tried selling them
16.
by taberiand 6mo ago
On the face of it, "10k lines of code per hour" sounds like a ridiculous metric to the point of parody.
17.
by taberiand 6mo ago
The generation that's going to enter adulthood in the age of unchecked climate change and AI taking over their careers? I say let them enjoy themselves while they still can.
18.
by taberiand 7mo ago
The sensor isn't in the main compartment, it's in the back reading the water (not a specific bowl or other item)
19.
by taberiand 7mo ago
Why not just wrap the tool so that when the LLM uses it, the wrapper enforces the OTP? The LLM doesn't even need to know that the tool is protected. What is the benefit of having the LLM enter the OTP?
20.
by taberiand 7mo ago
Is that cheating, or is that just working smarter not harder?
21.
by taberiand 8mo ago
Other comments suggest that the Agents.md is read into the system prompt and never leaves the context. But it's better to avoid excessive context regardless
22.
by taberiand 8mo ago
Getting the context full to the point of compaction probably means you're already dealing with a severely degraded model, the more effective approach is to work in chunks that don't come close to filling the context window
23.
by taberiand 8mo ago
That's what I'm getting at - the nixos learning curve is flattened out completely with LLMs to the point that I do recommend it as a starter distro for anyone technically competent (as it's still crucial to actually read and
24.
by taberiand 8mo ago
If you're a developer, try NixOS. The code based configuration can be daunting but LLMs are very good at writing it.
25.
by taberiand 8mo ago
Sure, and the people who live near oceans can just sell their houses and move as sea levels rise. People forced to migrate due to fresh water scarcity will migrate to where fresh water can be found, which is likely where other people alread
26.
by taberiand 8mo ago
Savvy move by cloudflare, once they have enough sites behind their service they can charge the AI companies to access their cached copies on a back channel
27.
by taberiand 8mo ago
It's not just the grammar; it's the tone of voice. The result? A post that reads like nails on a chalkboard.
28.
by taberiand 9mo ago
He does lots of different voices, it's very good
29.
by taberiand 9mo ago
This blog post smells of LLM, both in the language style and the muddled explanations / bad technical justifications. I wouldn't be surprised if their code is also vibe coded slop.
30.
by taberiand 9mo ago
Overengineering is building a bridge that will stand 1000 years when 100 will do; it's excess rigor for marginal benefit. Juicero wasn't overengineering, it was building a crappy bridge to nowhere with a bunch of gaudy bells and w

More ›