@Circuitfantasist About my "philosophical" way of "thinking" - First off, your use of these words is vague. (10) I have lost count of the points:) So let me start with 10. I always try to avoid using words like "philosophical", "logical", "reasoning", because they are vague in meaning. Instead, I usually use words like how I "design" this circuit, how I "implement" this circuit. Actually I prefer to use how I "do" it. So I am sort of "Nike Just Do It". So I sometimes say I am a "Nike Engineer/Guy"

Actually I try to avoid to use the word "Engineer", because this word is also vague. I am an ex-MIEEE, ex-MBCS, ex-CEng, because I am a slash freelancer, I usually call myself a hobbyist electronics/programmer. These two years I have been messing around with Micky Mouse smart home projects, so I can call myself a smart home hobbyist . To make my home smart, I need to use a little bit of AI, so when I meet some guys claiming that they are robotics hobbyists, I would say "me too"

EE SE is actually quite vague or "multi discipline", cover Electrical Engineering (for centuries means AC Power Generation and Distribution and Application (motors etc). Traditional Educational Institute such as MIT, still have the perhaps 200 years old EE Dept, and they even avoid using the word "computer/computing", even thought they start doing AI in the 1950s with the AI language Lisp.

So when I mess around with robotic, i actually use my knowledge of physics and mechanical engineering, and of course mathematics (applied and pure). I sometimes tell myself not to call myself an EE, because I think an EE should understand the basic concepts of "e", "j", Laplace/Fourier Transforms, can of course more basic things like capacitors and inductors. I am bringing up the subject "inductor" for the reason, which I would say more later. / to continue, ...

I have diverted a bit far, but I have not forgotten that your main questions is "How to attract more followers?" I usually try to find/tell answers from examples. Here are some examples:

I am a huge fan of EEVblog, so I usually watch their YouTube first (this example has 1.7 million "viewers/followers"

I am playing with an analogue guy call "LoadCell" weight sensor and I am using a 24-bit ADC called HX711 to sense the weight down to perhaps 0.001g. I hope this would attract many "followers". By the way, I am hoping to use LTspice to show off that the ok boomer does know some new tools, so this bad Arduino friends would not LOL at the face losing old guy that much, and begin to respect him more than he deserves.

Errata in chatting. I forgot to mention that what you chat in this room cannot be edited, meaning every mistake in on record. So I usually keep a record and summarize it as a PenZu diary, or as answer.

I seem to have given the wrong web links in the above chat paragraphs. So I usually repeat the links to avoid visitor wasting time go back to find the correct link. The first YT I am watching is the follow in Dave Jones:

One reason of learning op amp is that I am playing with a analog sensor, a load cellor, with a Wheatstone bridge giving ouput voltage in the range of a couple of milli-volts. I am using a 24 bit ADC HX711 to amplify it to a couple of volts, but there is a problem of instability, unreliability, etc. So one workaround to use an op amp as a pre amp to amplify the weak mv signal to volts. Then perhaps I use low resolution ADC such as MCP3008 (10 bit) or MCP3201 (12 bit), or ADS1115 (16 bit).

This is the analog Load Cell with mV output and HX711 24 bit ADC chat record:

You can see from the above chat record my way of "philosophical thinking", actually engineering system development methodology in an anaglog and analog to digital projects.

You are right in commenting that I don't look like an EE. Actually I am also interested in ISAD and ESAD (Information/Engineering System Analysis and Design and Practice) which does not focus in just hardware engineering systems but also software business information systems (methodologies such as Water Fall, UML, Rapid Prototyping (sort of meddling through), Agile etc). I usually recommend the following FREE eBook for enggr system development:

@Circuitfantasist As you said, if you know the principles of one, you can do three. So If you know developing Business Information Systems, you will find it easy to develop Engineering systems. So I sometimes see myself an Engineering/Information System Analyst.

Looking at the resources and everything you have written, I understand that you are one of those young people like the boys of Elon Musk who work miracles today. I just wonder where you got this energy and motivation to do all this. I see that you have broad interests and erudition. The book is great and makes me realize how limited I am.

BTW around me are IT students who do similar developments in their diploma theses, some very interesting. Obviously, this is the spirit of the new age... and we, "old warhorses", only keep the wisdom of the past.

I have developed microprocessor devices but that was a long time ago. Gradually, I realized that my vocation is in finding powerful and simple intuitive explanations of basic electronic circuits.

For years I have been looking for an answer to the question not only HOW they were made but also WHY they were made this way... and I was able to come up with reliable explanations.

So if you feel the need to understand the idea behind op-amp inverting circuits, bootstrapping, dynamic load, negative "resistors" and other circuit phenomena, I can share it with you...

This is what I am actually trying to do here in SE EE but I meet fierce resistance from my peers and I am forced to do it in a hostile environment. Reactions range from passive (silence), negative (-1) to aggressive (hiding, closing, deleting and ultimately burying my questions and answers).

Regarding why OPS beginners find it difficult to understand my explanations, the explanation is very simple - they do not have the attitude to think that way...

Here is just one of the latest examples - electronics.stackexchange.com/a/529879/61398 where I have explained the behavior of a diode (in this case LED) at the lowest possible and understandable (even by a non-professional) level. The existing explanations are on a higher and more abstract level - something like "when the voltage approaches the LED threshold, the current starts to rise sharply"...

The existing explanations are on a higher and abstract level - something like "when the voltage approaches the LED threshold, the current starts to rise sharply" ... which is not actually an explanation but an observation. But why is the current rising? The next "explanation" is "because the IV curve rapidly changes its slope"…

In contrast, my explanation is based on a simple but powerful concept - "dynamic resistance". It is easy to understand (variable resistance), demonstrate (humble rheostat) and apply to any nonlinear element (diode, transistor, negative resistor...)