So couple of issues there. Never upgrade windows. Fresh install only. Never had a good day upgrading it.
Secondly, there isn't always a solution in Linux. I've got one now where something is utterly broken and it's 5 layers of maintainers down and no one gives a shit.
I started with Linux installing it from floppy disks in about 1996.
In 1995, I was back on Windows 95 within a week because I needed to get something done.
In 2000, I was back on Windows 2000 within a week because I needed to get something done.
In 2005, I was back on Windows XP within a week because I needed to get something done.
In 2012, I was back on Windows 7 within a week because I needed to get something done.
In 2015, I was back on macOS within a week because I needed to get something done.
In 2020, I worked out I'm wasting my time on this.
I watch my colleagues and friend struggling with it. Lots of small papercuts. Lots of weirdness. Lots of regressions. Plus many years of server-side experience says to me "I should probably just use FreeBSD" in that space.
No Linux desktop delivers what the user wants, needs or expect. Only what the developers think they need and find interesting to fix. It's more fun reinventing wheels badly than fixing shit generally. Some people are lucky this aligns with their needs, but for most it doesn't. It's jarring and unproductive.
It needs corporate (or government!) drive behind it or that won't change. I'm not talking about Redhat either who appears to just be a holding pen for the above.
There are considerable formatting issues when you're working collaboratively on documents with other people who use MS office when you are using MS office too.
We gave up for large documents, assigned an editor and just send them chunks of text.
It goes really fast if you turn off the connected experiences like linked in, the AI crap, the splash screen, all the cloud shit and crack it with massgrave.
You clearly missed something in the former or latter or do not know how to verify if stuff is as expected.
Usually I build out the DC bias model (static operating point), test it in LTspice, then add the AC/small signal model on top. Or large signal model for switching etc. Everything generally works unless I did something stupid or it’s RF where things get a little less predictable.
No. This book won’t teach you that because based on the author’s previous work he doesn’t either. He knows how to sell books.
If you really want to know how transistors work and how to use them properly it’s going to be difficult as they sit on a fairly large pile of algebra and theory. If you don’t know this you might be able to get simple circuits working by cutting and pasting bits but you won’t be able to get past that ever.
The best references on this are actually The Art of Electronics. Not necessarily the main book but the associated student manual. Also the book Experimental Methods in RF Design by Wes Hayward actually has the most useful functional description and modelling approach of transistors.
Yes the office door stop as it was known as at our place. Top book though just faded in utility and no one had the heart to dispose of it because of the good memories.
That and the apple touchpad to swipe three fingers left and right to switch desktops (and different machines as one desktop is remote desked into a windows box and another terminal+tmux session to a linux box).
Then use massgrave hwid activator.