Thank you, will check this out.

Thank you, perhaps it is the CMRR that I need to explore? Perhaps this explains the noise floor difference? Thank you.

Thank you, yes I specifically saw a breakdown in my sin wave at ~60 kHz on ua741, and NE5532 got to ~650 kHz before I saw distortion. I thought that was awesome. I will study the layouts as you suggested. Any other advice? Does this also explain the noise floor difference or no?

I will check this out, thank you for sharing.

Thank you very much for your advice, I will follow.

Awesome, yes can just do the chemical outside if volume is small and time is fast. I see there a number of how to, thank you for the inspiration, I will be trying this for sure.

Okay, I will also spend time here, please let me know any advice for newbies. Thank you for your consideration.

I am open to try this because it appeals to my sensibility. Do you have any advice to get started because I am interested and will try this if it is feasible in my garage environment? I am serious. What are the minimum materials needed/must-have requirements? I am down for this shit.

I have a laser jet printer, what kind of ventilation are we talking for the chemical? I have fume extractor on my soldering station,

Okay, I am going to spend time with this then, please let me know any advice for beginners. Thank you so much.

That’s cool and I would say I mostly agree, I am also going to add a couple specific pointers that I consider practical: use ChatGPT on a desktop in a browser, use VS Code and extensions, keep ChatGPT instructions OFF the CLI so you don’t end up in a loop of running CLI codes and reporting back to your SupervisorGPT, make deals with ChatGPT in terms of complete code files and check every line, run midnight commander in a separate terminal and pay attention to permissions and ownership, force ChatGPT into lock down checklist mode and force it to go step by step, focus on the BIG picture with ChatGPT and don’t let it runoff to the next shiny object before you completed and tested everything that you wanted to do and hardened before you listen to the next bullshit suggestion prior to project completion. It’s not all bad and it does help you learn and punch above your weight class, but it can be downright infuriating and is by no means a turnkey solution: my two cents. Nobody going nowhere doing nothing.

That’s cool. It doesn’t sound like you are vibe coding because you don’t expect a working code, rather using LLM to learn more about coding in general. Is there any technique you learned to make it go faster or work better thru that process?

I have tried vibe coding on a couple small hobby projects and it did not workout in any of the cases, zero out of 4 or 5 ish attempts. It will get you kind of close, but it takes way way too long and it doesn’t work so you are actually just getting started. Are there actually techniques to vibe coding or is this all bullshit? I don’t want to spend more time looking into it…