There's plenty of valid reasons to configure a static IP address, I'd say I do it weekly. Configuring a commonly used machine to be static for ease of use. Connecting a TCP communication device (barcode reader, RFID reader, etc.) direct to your computer for testing. Just as a couple examples.
Yeah and you can still make a static IP with Windows 11. This is bullshit M$ whining. Shit changes. Explain to me why Debian fucking around with "ip" is less destructive.
Whenever I'm flying on the B787, I prefer to sit right behind the wing to watch the flaperons do their thing. I know it's a little different than this, as it's more of a PID driven behavior rather than an active predictive system. But regardless, it's quite impressive to watch how they are constantly reacting despite the plane seemingly not moving at all. They move very delicate and precise, which must be difficult to do when travelling at 500mph.
>as it's more of a PID driven behavior rather than an active predictive system
Self tuning and active predictive PID controllers are also a thing aided by the 'ye olde' faithful Kalman-Filter. At least I remember reading about them in research papers.
Now what exactly from those has materialized in commercial applications, I have no idea, since it's not like they publish such in depth info in the public facing spec sheet.
You kind of just described the job description of a modern "machinist". It's far more of a job regarding the machine itself (CNC in this case) and it's setup, versus the part itself being made. A mechanical engineer or manufacturing engineer deals moreso with that. Machinist is more synonymous with "operator" in my field.
To be fair, it's a lose-lose here. If we didn't implement strict and PITA-to-circumvent licensing, we would for sure have customers abusing it. As a small company, we cannot afford to patrol our customers constantly to make sure they are actually paying for software. We at least try our best to keep it out of their way. It's not my favorite thing to spend my dev time on, but I do understand it.
I use Angular daily as a frontend for our C++ app, hosted in Electron. I personally love the fact that it's opinionated (using their router, DI, etc) and most of their API is pretty extensible. For our purposes, it beats out Qt if you want an app with a highly custom UI. We chose it over React for the simple fact that it is so "batteries included".
Honestly I disagree that it's bad advice. The advice I give to a lot of new dads specifically is that Moms #1 job is to take care of baby, Dads #1 job is to take care of mom AND baby. Even if the little one is formula fed, the weeks/months after childbirth are so difficult for mothers. Sacrificing yourself a bit, in my opinion, IS balancing the work.
As time goes on and you have a toddler, things even out significantly.
Mom's job is not to sacrifice herself to take care of the child. She must both preserve herself, go through the healing process, and help take care of the child.
Dad's job is to also handle any healing, to help take care of mom, to help take care of the child, and to generally keep the house functional.
If Mom kills herself taking care of the child or sacrifices herself to take care of the child, that isn't functional. Something has gone wrong. If Dad has to sacrifice himself to take care of the child or the mother, something has also gone wrong.
You must _integrate_ the child into the family, not replace the family with the child. It is not just what works best for the child - it is what works best for the family as a whole. The child would love to constantly breast feed and comfort feed on mom forever - that is not functional for the mother, she must sleep and have time with the child off her nipple so she can continue to breast feed.
In the same way, it is not functional for dad to say, spend all his time cooking and cleaning and not sleeping. It is better for dad to sleep and some of the chores to go undone then it is to have a tidy home.
If you sacrifice yourself - if you spend and spend and spend - you will see it as a debt accruing that will never be paid back. You will breed resentment to your family. You will be unhappy and the family will no longer be a family. That does not work. It does not matter if you're the mother or the father, self sacrifice destroys families.
The family has to work as a whole. Everyone has to be integrated and the system has to work as a whole. What that looks like differs for every family and is an ongoing process, not a one time solution. The father and the mother have a relationship, and now baby is involved which means we went from 1 relationship to 3 (the baby has a separate relationship with each parent!). The family has to make that work not for a week or a month or a year, but for the rest of their lives.
I'm sorry to tell you this, but everything in life cannot be algorithmically driven. As others have said, generally speaking your baby is YOUR baby and you have to learn as you go and adapt. Take it a few days at a time, tackle the current issues, and repeat.
On the data driven side, Emily Oster and her prenatal (Expecting Better) and postpartum (Cribsheet) books are great resources, but they hardly prepare you for parenting. Those books can help you make some macro decisions for sure, but overall parenting is an experience which will likely be the most mentally challenging thing you've done, barring any exceedingly traumatizing events.
Probably, but I'd guess that the reflector still absorbs a small percentage of the beam it's reflecting. And at the GW scale I'm sure even a small percentage is enough to absorb a great deal of energy.
We use Angular for our large realtime process control application in place of a lower-level UI (like Qt). Having all of the tools you mentioned above has given us an organized codebase with components that we've been able to successfully reuse across the application itself and across different products. Having to work around "the Angular way" can be annoying sometimes, but to be honest at the same time it's nice to not have to make decisions that Angular has already made for you (routing, modules, etc)
