Comment by ghm2180

A lot of the comments have to do with how does one use these things to speed up learning. I've tried a few things. A couple of them are prompts: 1. Make me a tutorial on ... 2. Make probes to quiz me along the way ...

I think the trick is to look at the references that the model shows you. e.g. o3 with web search will give you lots of references. 90% of the time just reading those tells me of the model and I are aligned.

For example the other day I was figuring out why using SQL alchemy Sessions and PyTest async might I get the "Connection was attached to different loop" error. Now If you started using o3 to give you a solution you would take a long time because there would be small mistakes it would make in the code and You would spend a lot of time trying to fix it. Better way to use 03 then was to ask it to give you debugging statements (session listeners attached to Sqlalchemy sessions) and understand by reading code output, what was going on. Much faster.

Once it(and I) started looking at the debugging statements the error became clear: the session/connections where leaking to different event loop, a loop_scope= param needed to be specified for all fixtures. O3 did not provide a correct solution for the code but I could, but it's help.was crucial in writing a fuck ton of debugging code and getting clues.

I also asked o3 to make a bunch of probe questions to test me, for example it said something like: try changing the loop_scope module to function, what do you expect the loopid and transaction id to be for this test?

I learned More than I realized about ORMs and how it can be used to structure transactions and structuring async PyTest tests.

One thing I'm trying these days is to have it create a memory palace from all the stuff I have in my house and link it to a new concept I'm learning and put it into an anki decks.