0x696C6961

4 ms·

91.
by 0x696C6961 7mo ago
The example with the dash in it confused me as well.
92.
by 0x696C6961 7mo ago
Printing RC toys gets expensive fast. Before you know it you're buying castle motors and a flysky remote.
93.
by 0x696C6961 7mo ago
If all/most QA people were like this then no one would be complaining.
94.
by 0x696C6961 7mo ago
You can do this with i3
95.
by 0x696C6961 7mo ago
Would be nice to have a polars version of this.
96.
by 0x696C6961 7mo ago
If you lost access to AI would you be able to continue development on your app?
97.
by 0x696C6961 7mo ago
The //go:xyz comments are an established pattern in the Go tooling.
98.
by 0x696C6961 7mo ago
You're absolutely right!
99.
by 0x696C6961 8mo ago
My work involves fixing/adding stuff in legacy systems. Most of the solutions AI comes up with are horrible. I've reverted back to putting problems on my whiteboard and just letting it percolate. I still let AI write most of the c
100.
by 0x696C6961 8mo ago
Yes
101.
by 0x696C6961 8mo ago
The problem here is a lack of namespaces. A problem the cargo bozos decided to duplicate
102.
by 0x696C6961 8mo ago
Man... I spent the last 6 months writing code using voice chat with multiple concurrent Claude code agents using an orchestration system because I felt like that was the new required skill set. In the past few weeks I've started openin
103.
by 0x696C6961 8mo ago
It begs the question, why don't these languages put out a v2 stdlib?
104.
by 0x696C6961 8mo ago
There's nothing special about using http other than most corporate firewalls allow it. It's just the pragmatic choice.
105.
by 0x696C6961 8mo ago
Alternative take: don't put draft RFCs into prod
106.
by 0x696C6961 8mo ago
I get a kick out of publishing libs with no external deps. Regardless of reasoning, this change makes that easier.
107.
by 0x696C6961 8mo ago
No man, that's called an oligarchy.
108.
by 0x696C6961 8mo ago
I doesn't matter how it "should" work. In the real world you need to interact with external systems which don't have granular enough permission schemes. People out here letting Claude code run CLIs using their own user p
109.
by 0x696C6961 8mo ago
Or just extract the certificate from the hardware you own.
110.
by 0x696C6961 8mo ago
You burn a lot of money on tokens for a solution that you throw away.
111.
by 0x696C6961 8mo ago
This is exactly what I do. I assume most people avoid this approach due to cost.
112.
by 0x696C6961 8mo ago
Those functions usually already exist, you just write light wrappers around them for the LLM.
113.
by 0x696C6961 8mo ago
Try ast-grep
114.
by 0x696C6961 8mo ago
That's basically all it is. It's a readme file that is guaranteed to be read. So the agent doesn't spend 10 minutes trying to re-configure the toolchain because the first command it guessed didn't work.
115.
by 0x696C6961 8mo ago
In what world is this simpler than just giving the agent a list of functions it can call?
116.
by 0x696C6961 8mo ago
I usually have a long running note per-project and whenever I need to context switch, I add a "Next Step: ..." line at the bottom of the doc. So I can jump right back in when I come back.
117.
by 0x696C6961 8mo ago
That doesn't make the tool bad.
118.
by 0x696C6961 8mo ago
I use a very similar setup. I initially used nix to manage dev tools, but have since switched to mise and can't recommend it enough https://mise.jdx.dev/
119.
by 0x696C6961 9mo ago
It's not an analogy.
120.
by 0x696C6961 9mo ago
You're free to use whatever tools you like.

More ›