4 ms·
If you really want to experiment, give Cursor a try. It’s free up to a limit, so maybe it’ll be enough for your example use case. It handles even more complex
by yunohn 3y ago
If you really want to experiment, give Cursor a try. It’s free up to a limit, so maybe it’ll be enough for your example use case.
It handles even more complex use cases and will automatically include/patch code for you via the inbuilt LLM framework. This helps with iteration and modifications as you massage it to what you need. Plus, it’ll scan your code and find the languages/frameworks automatically.
Finally, keep in mind that the goal should not be perfect production code - that’s just Twitter AI hype. It’s about saving time and energy for you (the human) to achieve more than possible before.
https://cursor.sh/ https://cursor.sh/
- jpc0 3y agoTo give some feedback. I tried your prompt and the above approach and it took me about 45 minutes of putsing around to get a result I am happy to begin iteration on. Effectively: I have an 80bit byte array representing a timestamp struct consisting of a 48 bit unsigned integer for seconds and a 32 bit unsigned integer representing nanoseconds. The byte array is big endian and the host systen is little endian. I gave it full signatures for all functions and relevant structs and instructions on how I would want the parsing done regarding algorithmic complexity and yet it still took multiple iterations to get anything useful. At this point it is converting to little endian during the decode then doing a check if host the system is big endian and converting back to big endian if that is true. There is likely some easy optimisations to be done where there and I would have definitely have gotten to this point quicker had I just written the 10 lines of code this needed and would have done the optimisations where I'm pretty sure that entire operation can happen in a few instructions.