Comment by calrain

2 days ago

Unfortunately not, but ensuring the final code quality will be well written is a challenge I am putting off for now.

I'm leaning into the future growth of AI capabilities to help me here, otherwise I'll have to do it myself.

That is a tomorrow problem, too much project structure/functionality to get right first.

4 comments

calrain

Reply
KodeNinjaDev  2 days ago

So you are more productive, as long as you don't have to consider code quality.

  • calrain  2 days ago

    Possibly, but not really.

    With most projects where innovation is a key requirement, the goal isn't to write textbook quality code, it's to prove your ideas work and quickly evolve the project.

    Once you have an idea of how it's going to work, you can then choose to start over from scratch or continue on and clean up all the bits you skipped over.

    Right now I'm in the innovation cycle, and having AI able to pick up whole API path strategies and pivot them, is incredibly amazing.

    How many times have you used large API's and seen clear hands of different developers and URI strategies, with an AI, you just pivot.

    Code quality and pen tests are critical, but they can come later.

    • skydhash  2 days ago

      > Code quality and pen tests are critical, but they can come later.

      In my experience, no.

      These kind of shortcuts taken at the beginning of the project is why velocity have a sharp descent after some times. Because you’re either spending time undoing all of it (unlikely to be allowed) or you’re fighting in the code jungle trying to get some feature out.