A common issue when trying this is trying to teach all layers at the same level of detail. But this really isn't necessary. You need to know the equation for Ohms law, but you can give very handwavy explanations for the underlying causes. For example: why do thicker wires have less resistance? Electricity is the movement of electrons, more cross section means more electrons can move, like having more lanes on a highway. Why does copper have less resistance than aluminum? Copper has an electron that isn't bound as tightly to the atom. How does electricity know which path has the least resistance? It doesn't, it starts flowing down all paths equally at a significant fraction of the speed of light, then quickly settles in a steady state described by Ohm's law. Reserve the equations and numbers for the layers that matter, but having a rough understanding of what's happening on the layer below makes it easier to understand the layer you care about, and makes it easier to know when that understanding will break down (because all of science and engineering are approximations with limited applicability)
> How does electricity know which path has the least resistance? It doesn't, it starts flowing down all paths equally at a significant fraction of the speed of light, then quickly settles in a steady state described by Ohm's law.
> because all of science and engineering are approximations with limited applicability
Something I heard but haven't dig into, because my use case (DIY, home) doesn't care. In some other applications approximation at this level may not work and more detailed understanding may be needed :)
And yeah, some theory and telling of things others discovered for sure needs to be done. That is just the entry point for digging. And understanding how something was derived is just a tool for me to more easily remember/use the knowledge.
The exams were typically essay-ish (even in science classes) where you either had to basically reiterate the reasoning for a fact you already knew, or use similar reasoning to establish/discover a new fact (presumably unknown to you because not taught in class).
Unfortunately, it didn't work for me and I still have about the same critical thinking skills as a bottle of Beaujolais Nouveau.
For example in electricity you need at least that amount of cross section if doing X amount of amps over Y length. I want to dig down and understand why? Ohh, the smaller the cross section, the more it heats! Armed with this info I get many more "Ohhs": Ohh, that's why you must ensure the connections are not loose. Oohhh, that's why an old extension cord where you don't feel your plug solidly clicks in place is a fire hazard. Ohh, that's why I must ensure the connection is solid when joining cables and doesn't lessen cross section. Ohh, that's why it's a very bad idea to join bigger cables with a smaller one. Ohh, that's why it is a bad idea to solve "my fuse is blowing out" by inserting a bigger fuse but instead I must check whether the cabling can support higher amperage (or check whether device has to draw that much).
And yeah, this "intuition" is kind of a discovery phase and I can check whether my intuition/discovery is correct.
Basically getting down to primitives lets me understand things more intuitively without trying to remember various rules or formulas. But I noticed my brain is heavily wired in not remembering lots of things, but thinking logically.
- Depth of Discharge - how often you go from full to low battery? Going twice from 80->30 (which accounts to a single cycle) is much better than single 100->0 cycle
- Thermal management - what are cell temperatures when battery is being charged? Maybe it is charged in direct sunlight? This will kill battery pretty fast. At what temperatures are the cells when driving the ebike?
- Ebike/scooter probably being charged to 100% more often than necessary.
- Did you leave your battery at winter completely discharged or fully charged in your garage? Bad.
TLDR: Info I gathered about reading how to take care of Lithium NMC batteries which are so widespread.
> The throw keyword causes a terminating error. You can use the throw keyword to stop the processing of a command, function, or script.
Moreover, the community plugins model is a fundamental security risk and the community plugins themselves frequently break on Obsidian updates. I’m not going to invest months to years building a curated personal knowledge base only to have it fall apart when a community plugins breaks.
For me it's a feature.
I thought I didn't know about "Throw-And-Exit" command, but no, my powershell doesn't have that and google also doesn't know a thing, so wonder what's up with that.
And instead of manual confirmations, one can write script with ShouldProcess support to have support for builtin -Confirm/-WhatIf/-Force parameters. And it would actually be a great use case for that scheduled task to run with -Force parameter instead of changing code to strip out confirmations. https://learn.microsoft.com/en-us/powershell/scripting/learn...
I am pretty sure the guys charging hundreds of dollars for IP addresses that cost them nothing to produce should be able to set up stripe, an identity verification product, and otherwise automate onboarding. Also, instead of writing giant process documents and slow-walking such wildly difficult problems as "allow domains to end in .cool" through infinitely nested committees they could try wielding their supreme governance over Who Owns Numbers And Names by killing off IPv4.
As long as ICANN/IANA remain in charge of Internet governance and operate with >$100mm budgets [0] "it made sense 25 years ago" is not a valid excuse IMO.
[0] https://www.icann.org/en/system/files/files/fy24-funding-sou...
https://android.googlesource.com/platform/frameworks/base/+/...
If I had the time, I'd try to compile a binary of it that will run on Win95 just to give my fuckings to the planned obsolescence crowd.