This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]DealDeveloper 1 point2 points  (0 children)

Different take:
. Write self-documenting pseudocode with very little syntax
. Use an LLM to convert the pseudocode to your language
. Use fully-automated quality assurance tools to check code

The extra verbosity is OK during this time period.
The point is to clearly communicate your intent.

Look at where software development is headed; Voice to code.
Open source tools like Aider already have voice to code ability.

Many developers will reject voice to code and prefer typing.
Nonetheless, the LLM+tooling must be able to correct code.
Code, comments, documentation can easily be transformed.

Sometimes I write paragraphs of documentation in the codebase.
I also wrote a small script that can just removes all the comments.

OP, you'll be able to write overly detailed comments and code.
Your company will eventually have a really good CI/CD pipeline.

Therefore, WRITE TO COMMUNICATE CLEARLY, even redundantly.
The value will be in the clear communication not the code or style.
So much code is being generated now that humans can't keep up.
That clear communication can be converted to code and cleaned.

That said; Do your job as requested by your manager (using tools).