|
|
|
|
|
|
by PaulHoule
660 days ago
|
|
|
Taking your statement at face value I'd be tempted to say it's fair to ask an LLM how to do small things at the "few lines of code" level. For instance if you're not sure how to get the length of a string in language X or don't know off the top of your head how to use CSS to move an object a few px higher up without changing the layout of everything else it might be quicker than asking Google, looking at the docs. I do it a lot these days. My first instinct though is that struggling people often have poor insight into their problem. When I was teaching physics I heard "I understand the concepts but can't solve the problem" a lot. Invariably when I'd help the student debug the problem solving process I found that they didn't understand the concepts. |
|
|
I have an array of bytes (u8’s) (let’s just say integers for now). The first 8 bytes is the signature of that particular sequence of bytes. I compare and check that signature (if it’s not there or doesn’t match the signature I am comparing it too) then we exit the reading operation.
The array of bytes / integers insist to communicate information through 4 byte sequences. So after reading the signature, I would collect the next 4 bytes. I take those bytes and read them, these 4 bytes indicate the length of the upcoming data segment, the next 4 bytes after that contain the data segment type. I read this to determine the type of data segment I am dealing with.
The next read operation is preformed using the length I gathered early. Let’s assume the length said 15, so after reading the data segment type, I read +15 bytes, and store them in some data structure (A Vector). After this, the next 4 bytes mark the end of the data segment. Rinse and Repeat.