I must admit... you might possibly likely be superbly rightly correct...Or maybe pointing out that 'invaluable' can't be modified by the adverb 'extremely'?
I must admit... you might possibly likely be superbly rightly correct...Or maybe pointing out that 'invaluable' can't be modified by the adverb 'extremely'?
And that's what LTspice has mainly done for me. It has helped me learn specific things by allowing me to tweak individual components so as to more easily visualize how they affect the complete system.... the hardest part of solving many problems is gaining a firm understanding of what the problem is.
I live to serve.Mmhhhh.... it seems that I did not make a mistake after all:
http://www.merriam-webster.com/dictionary/invaluable
So I'm taking it you were twisting my words to make an ironical point?
Heinlein (?) had a story where number and set theory were taught in grade school, and you could do your PhD on long division.I remember reading a science fiction short story set in the future where the character was brought up on heresy charges because he claimed he could do math in his head but everyone knew that only machines could do math.
It was the thread title, and no apology is required since it was a rhetorical question.Ah, I misinterpreted your question. I didn't see a specific post that made a statement about "too much" and so I thought you were throwing out a general question. My apologies.
I personally try not burning any mcus, with or without simulationPersonally I don't burn a mcu without having tested the code in simulation.
I've learned more mathematics than most people have an opportunity to forget. I vote no.Has computer made us dumber? Every coin has two sides ~~
I started out as a trouble shooter, not a designer, so I learned to go fast. I could always turn around and go back without any cost. But when you carry that mentality into design it can make things expensive and slow - order parts, pay for parts, find out parts don't work, etc.. So I always simulate first to eliminate the obvious mistakes while paying attention to voltage, power, and common mode rejection by hand.And that's what LTspice has mainly done for me. It has helped me learn specific things by allowing me to tweak individual components so as to more easily visualize how they affect the complete system.
And yes, I've been warned that it has its quirks and limitations. So I take everything it reports with a grain of salt.
I'm guessing the cost of the die justifies all that prior work... and also, that afterwards thorough testing is done in the real world and compared to the original simulationIn general, all ICs are simulated, but not with something as crude as LTSpice. The IC simulators include layout, connection resistance, feedthrough capacitance, etc.
I worked on microprocessor projects containing hundreds of millions of transistors being designed on a process that was currently being developed. Running multiple types of simulators is still no guarantee that the device will perform as simulated. With a mature process with dozens/hundreds of "tapeouts", simulations can be very accurate.I'm guessing the cost of the die justifies all that prior work... and also, that afterwards thorough testing is done in the real world and compared to the original simulation
That sounds like the fault of the operator, not the tool the operator is unable to use correctly.If you let the simulator make you dumb, it certainly will.
Any approach is going to be limited in one way or another, because no tools can ever be perfect.you'll find that simulators are limited in that it is very hard to prove anything exactly
You cannot be 100% comprehensive any any approach, simulator or not. The fact that a tool (simulator or a human brain, or actual circuit) isn't 100% accurate or comprehensive should be a reason not to use it.Even with simulators, which can't be 100% comprehensive, mistakes will still escape detection.
I don't think that came out the way you intended.You cannot be 100% comprehensive any any approach, simulator or not. The fact that a tool (simulator or a human brain, or actual circuit) isn't 100% accurate or comprehensive should be a reason not to use it.
Again, it sounds like the fault of the operator, using a tool incorrectly.The problem, as I see it, is...