20.10.2026, 00:30
(This post was last modified: 20.10.2026, 00:31 by Stanley Durham.)
> devises and executes stress tests
That’s the big one. I always put “all possible edge cases” in there.
The other big one is reference. Major programming reference sources have recently disappeared.
I’m new to C. It took a few attempts to understand how I had to implement it., but over the last few days I built a complete lib for dynamic strings, wide strings, and string and number arrays for C. Not just dynamic but buffered. They allocate extra memory when memory is needed. Grow and shrink as needed. That also turns them into dynamic stacks.
Yesterday, I finished the string array. 222 edge tests. With one prompt, I had DS build a wide string array by just changing the logic. I refactored all the container files in the lib twice with one prompt each time. I added auto free to all containers.
So, I have dynamic strings and arrays that are automatically freed in C.
Also yesterday, I built a string hash table. I took my time, made a lot of enquiries before starting. 12 procedures and 161 edge tests. Then with one prompt, I have a wide string hash table along with edge test. I just told it to change the logic.
In one day, I finished the string array, built a wide string array, built a string and wide string hash table and refactored all files so that the automatically free memory when they go out of scope.
All containers in lib are handle-based. Essentially, they are objects without OPP. I added a handle array. The string arrays are string container handles in a handle array.
I already know how to build the containers. Took many years on PB.
Maybe in 3 years I might be competent enough to do that in C. Then it would take months to do it.
With AI, you have instant access to detailed knowledge. Anything you don’t understand, you keep asking.
On one hand, I quickly learned a lot about C because I got instantly corrected. On the other hand, I’m C stupid because I just tell AI to do some things. But, if you don’t need to know it, you don’t need to know it. If you want to print numbers, you must learn different symbols to use, and some have different symbols for different things. I just tell AI to build a lib that does it.
In the end, you tell AI to build an app to test the code. You can make it as complex as you want because you don’t have to write it. In a few seconds you have the results. If there are problems, it may automatically fix them.
You can’t fully trust it. You must keep an eye on it. Anything that’s tricky, I do one procedure at a time.
You have to plan the code and write it. Now you can focus on planning and have it do the tedious and boring stuff.
That’s the big one. I always put “all possible edge cases” in there.
The other big one is reference. Major programming reference sources have recently disappeared.
I’m new to C. It took a few attempts to understand how I had to implement it., but over the last few days I built a complete lib for dynamic strings, wide strings, and string and number arrays for C. Not just dynamic but buffered. They allocate extra memory when memory is needed. Grow and shrink as needed. That also turns them into dynamic stacks.
Yesterday, I finished the string array. 222 edge tests. With one prompt, I had DS build a wide string array by just changing the logic. I refactored all the container files in the lib twice with one prompt each time. I added auto free to all containers.
So, I have dynamic strings and arrays that are automatically freed in C.
Also yesterday, I built a string hash table. I took my time, made a lot of enquiries before starting. 12 procedures and 161 edge tests. Then with one prompt, I have a wide string hash table along with edge test. I just told it to change the logic.
In one day, I finished the string array, built a wide string array, built a string and wide string hash table and refactored all files so that the automatically free memory when they go out of scope.
All containers in lib are handle-based. Essentially, they are objects without OPP. I added a handle array. The string arrays are string container handles in a handle array.
I already know how to build the containers. Took many years on PB.
Maybe in 3 years I might be competent enough to do that in C. Then it would take months to do it.
With AI, you have instant access to detailed knowledge. Anything you don’t understand, you keep asking.
On one hand, I quickly learned a lot about C because I got instantly corrected. On the other hand, I’m C stupid because I just tell AI to do some things. But, if you don’t need to know it, you don’t need to know it. If you want to print numbers, you must learn different symbols to use, and some have different symbols for different things. I just tell AI to build a lib that does it.
In the end, you tell AI to build an app to test the code. You can make it as complex as you want because you don’t have to write it. In a few seconds you have the results. If there are problems, it may automatically fix them.
You can’t fully trust it. You must keep an eye on it. Anything that’s tricky, I do one procedure at a time.
You have to plan the code and write it. Now you can focus on planning and have it do the tedious and boring stuff.