john borland

Depending on how many tokens you want to use here are other things you can ask AI about a PR. Will this PR require the cppcheck manual to change? if yes which sections. What unit test cover these changes? if no unit test is found can please write one. What do you think the intent of this PR is?

To me this talk has lived rent free in my brain since 2012 https://youtu.be/5wwKjdvPxa8 its about how CI can be used as a code reviewer. Most CI systems are pass fail. But there tea leaves that often go unnoticed. I think in the age of AI its probably a good idea to use AI as a first pass aproach to keep from getting overwhelmed. I even know of an open source project that is talking internally about poising their skill file to say all issues must be written using Shakespearen English. That way they...

I think one thing that matters a lot is how easy is it for you to integrate into your workflow. For me given that I learned to code inside a unix terminal and never evolved to using an IDE to code with AI isnt to difficult to record my interactions with. The script command https://www.redhat.com/en/blog/linux-script-command does alot of the heavy lifting. I also write a bit of data like starting and stopping git hash as well as the ai model version and token usage to a file. That way I can restore...

One thing I recomend when it comes to AI is to keep internal metrics so that you can better help you evluete AI future solutions. That includes keeping track of the work done by AI which you can put a tag in an issue or a tag in the git commit message. You will want to be able to match that tag to a prompt, token usage and model version number. That way if you want to make changes later to your AI process you can test it aginst past solutions to see if the change adds value. On a side note one thing...

As someone who has written simulations for NASA the role cppcheck has always filled for us making sure our simulations are following C++ best practices. I would double check your definitions of what validation means to the FDA. A lot of times I find groups using the words verification and validation interchangeably which is a big mistake. For me verification means does the software meet it's requirements. Validation means does the software do what was actually wanted. A lot of the time I can't tell...

As someone who has written simulations for NASA the role cppcheck has always filled for us making sure our simulations are following C++ best practices. I would double check your definitions of what validation means to the FDA. A lot of times I find groups using the words verification and validation interchangeably which is a big mistake. For me verification means does the software meet it's requirements. Validation means does the software do what was actually wanted. A lot of the time I can't tell...

As someone who has written simulations for NASA the role cppcheck has always filled for us making sure our simulations are following C++ best practices. I would double check your definitions of what validation means to the FDA. A lot of times I find groups using the words verification and validation interchangeably which is a big mistake. For me verification means does the software meet it's requirements. Validation means does the software do what was actually wanted. A lot of the time I can't tell...

When I ran the example below it didn't take very long. This is built off of latest. system76-pc:~/Test$ time ./cppcheck/Build/bin/cppcheck check=all ./uncrustify/src/indent.cpp Checking uncrustify/src/indent.cpp ... Checking uncrustify/src/indent.cpp: HAVE_INTTYPES_H=HAVE_INTTYPES_H... Checking uncrustify/src/indent.cpp: WIN32=WIN32... Checking uncrustify/src/indent.cpp: WIN32=WIN32;QNXNTO=QNXNTO... real 0m18.128s user 0m18.100s sys 0m0.016s system76-pc:~/Test$