Also, I find myself having a conversation as I would with a real person, so it's less of spitting out the right answer for any technical question I might have, but more of a design buddy to consult when you're blocked on your search through the massive electronics solution space. Of course, this is a very preliminary use case and I can't wait to see what other people use it for.
About 12 years ago I designed an RF addon board for an RC car (to toggle lights). Even something as simple as switching with NPN transistors looks good on the bench software but when the chips came it didn't work at all. Did I mistakenly ask for PNP? Ugh! I used fritzing at first (still great software) and then upgraded to Eagle. I want to do something beyond Raspberry Pi/Arduino work but not quite ready to design my own radio/motherboard. I know electricity but I don't know why I would need a capacitor/resistor/transformer other than the very basics.
What resources would you recommend since you love to teach PCB design?
[0] https://www.edx.org/xseries/mitx-circuits-and-electronics
GPT-4 produces a lot of my code now.
I'm leap-frogging my team a bit in productivity because they still don't like it, but it's so close to being undeniable.
Which one of us is lying?...
Yesterday I had a ticket at my job to extend some functionality in a code base that was probably 200 files and 100+ lines of code in each file, and that's before any `import` references to other libraries.
How can you feed all of these tokens to GPT-4 in a cost effective way so that it knows about your application well enough to recommend/pull off code completion at a human-like level?
This is an actual thing[1] and it’s something larger models are actually worse (better?) at. They score higher and higher on the loss function (did I predict correctly), but their utility (does it work) goes down.
Just thought it was noteworthy.
I asked it to start and it provided me the flaws :D I can share the prompt if you'd like.
I've seen it happen several times.
Holy cow this is awesome! The integration of project context with an LLM enabled more than the sum of its parts when it comes to information access.
When designing circuits for fast iterations, you're constantly managing risk and time expenditure; this leads to copying a lot of "flight heritage" circuits so to speak.
With the LLM, I'm able to get highly condensed starting points for better circuits when it comes to simplicity, understandability, or performance. As of right now, all I have to do is fact check the solution which is much easier than synthesizing one myself. I'm citing the example where I got it to design me a viable high gain analog frontend that meets my gain, bandwidth, noise, and biasing requirements.