So now
I'm sure
many of you, just like myself,
are guilty of using the standard print
debugging method, where all you do
is you go in your program
and you do something like print
run or print run,
and then the value of a variable
and you just have a bunch of print statements
kind of scattered all over the place.
And this is really
what you're using as your debugging log.
This is giving you information.
Now, there's nothing inherently
...
repo | techs | stars | weekly | forks | weekly |
---|---|---|---|---|---|
arc53/DocsGPT | PythonTypeScriptCSS | 11.7k | +4.8k | 1.1k | +364 |
Pythagora-io/gpt-pilot | PythonOther | 9.5k | +4k | 722 | +297 |
OpenBMB/ChatDev | PythonJavaScriptCSS | 12.9k | +2.7k | 1.3k | +274 |
microsoft/autogen | Jupyter NotebookPythonOther | 8.1k | +2.5k | 811 | +315 |
mit-han-lab/streaming-llm | Python | 4.6k | +2.2k | 234 | +115 |
krahets/hello-algo | JavaSwiftC++ | 38.2k | +1.8k | 4.2k | +203 |
novuhq/novu | TypeScriptPythonJavaScript | 29.3k | +1.5k | 2.5k | +179 |
openai/openai-python | PythonMakefile | 12.8k | +1.3k | 1.8k | +77 |
microsoft/promptflow | PythonOther | 4.1k | +1.1k | 273 | +49 |
KillianLucas/open-interpreter | Python | 28.8k | +958 | 2.5k | +93 |