- "Write the CMake file"
- "Write a GitHub CI yml"
- "Write tests for this class"
- "Update this function with X"
It really shines if you can give it a straightforward task with a narrow scope.
- "Write the CMake file"
- "Write a GitHub CI yml"
- "Write tests for this class"
- "Update this function with X"
It really shines if you can give it a straightforward task with a narrow scope.
I.e. most of the design work falls to you, but the implementation is done by the LLM.
I've also found that the model matters a lot. The paid versions of ChatGPT and Claude are necessary for bigger projects.
I.e. most of the design work falls to you, but the implementation is done by the LLM.
I've also found that the model matters a lot. The paid versions of ChatGPT and Claude are necessary for bigger projects.
For the second question it's complicated because I didn't know what I was doing.
I click a button in blender which uploads the .blend file to S3. The render farm downloads and renders that file.
It sounds like a universal scene description file would be less error prone.
For the second question it's complicated because I didn't know what I was doing.
I click a button in blender which uploads the .blend file to S3. The render farm downloads and renders that file.
It sounds like a universal scene description file would be less error prone.
Toddlers develop a symbol for "thing exists but is not present" around age 2.
It's not a far jump to "thing does not exist but maybe could".
Those two symbols are the basis for human planning.
Early humans probably benefited a lot from cooperative manipulation of imagined scenarios.
Toddlers develop a symbol for "thing exists but is not present" around age 2.
It's not a far jump to "thing does not exist but maybe could".
Those two symbols are the basis for human planning.
Early humans probably benefited a lot from cooperative manipulation of imagined scenarios.
My main issue is that the RFCs are 8.5x11 by default. That page size makes an unpleasant book.
They probably have them printed out somewhere.
My main issue is that the RFCs are 8.5x11 by default. That page size makes an unpleasant book.
They probably have them printed out somewhere.
The conversion process needs a little more work before I'd feel comfortable selling them.
That said, I'm not sure which RFCs to focus on. Let me know if you have any suggestions for specific RFCs.
The conversion process needs a little more work before I'd feel comfortable selling them.
That said, I'm not sure which RFCs to focus on. Let me know if you have any suggestions for specific RFCs.
An RFC is a document specifying a protocol.
These documents are provided in a digital-only format. I am converting them into hardcover books.
So far I've converted these RFCs:
OSPFv2
SIP
RTP
BGP-4
X.509 PKI
SMTP
NTPv4
TLSv1.3
An RFC is a document specifying a protocol.
These documents are provided in a digital-only format. I am converting them into hardcover books.
So far I've converted these RFCs:
OSPFv2
SIP
RTP
BGP-4
X.509 PKI
SMTP
NTPv4
TLSv1.3
Do you have plans to use this as a component in a larger project?
Do you have plans to use this as a component in a larger project?
There's a fun trick to find the function prologue by parsing the bytecode of the instruction before the saved LR.
github.com/torvalds/lin...
There's a fun trick to find the function prologue by parsing the bytecode of the instruction before the saved LR.
github.com/torvalds/lin...