For some reason I can't fully grasp, a LOT of US citizens are ignorant to how the rest of the world is perceiving them at the current moment. There's countless US articles talking about US/Canada relations as if it is a trade dispute and that they think Canadians are eager to re-unite and go back to the way things were without ever addressing the threats to our sovereignty. Then you have comments like the parent to your post who is....wildly off the mark thinking that in a point of contention we'd prefer to keep our data on US controlled systems because their government would need to follow their own legal processes to acquire data of a foreign/hostile state??????

OP is discussing firings.

And yeah, there's crossover but they're not 1 to 1. At the same time, if a company is taking two people of equal position and firing one, or keeping the other, the honesty in how they came to that conclusion through transparency has value. Was the decision one of seniority? Performance? Geographical relevance? Was it favoritism masked in another reason? The person receiving the pink slip deserves to know the truth, especially in cases where legal matters could be of question where a company may say one thing, but be acting on another.

Radeon VII

https://www.amd.com/en/support/downloads/drivers.html/graphi...

From basically the very moment you realize you're having a kid you essentially become the #2 person in your own life. Its more so for the mother, but even the father likely needs to do some maturing in preparation to being a good dad.

If you're hoping to be a good parent you need to start weighing every decision on a basis of where it leads to. There's simple things like affordability: deciding to make smarter financial decisions because you're going to be supporting another human for the next couple decades at least. There's more complex things like suddenly seeing your own health as a liability and needing to straighten yourself out if you want to set a good example. Things get way easier if your life has structure honestly. Having good habits about food prep, cleaning, chores makes things way easier and bad habits really make life more difficult than it needs to be.

You also need to adapt quickly. You realize that you don't define your schedule any longer. Whether you sleep at night is up to the kid. As they grow from baby to toddler you start to see how the fundamental things like routine have impacted your child and you can begin to make connections to how you did things 6 months ago impacts how things are going now. Self reflection is huge, knowing how your emotions, your reactions, your behavior is a template this person learns from humbles you.

This line sticks out to me:

    you see life as a collection of experiences to be sampled

But thinking about it at this point? I've lost a few friends (not in a breakup sort of way, they just slowly faded out) but the ones who stick around were always those I was closest to. I do miss out on a lot more of the hobbies I once loved but at the same time I've traded those for experiences that are new, different, and fulfilling in their own ways. I've truly been a believer that the best reward always comes after a period of suffering or struggle. In the same way that cold glass of water feels like heaven after a strenuous workout that immense feeling of reward when your kid takes first steps, first words, first sentence just crush all other emotions and swell you with joy and love. Is 2 years of hard work worth that immense wash of emotion? Arguably yes. And I hope to keep getting hit with those experiences.

I've never been shy to say it isn't something for everyone. You sacrifice a lot to have kids. Financially, physically, emotionally, mentally, it all takes a toll, but the rewards are also so much deeper than anything else.

For me I wanted a smaller keyboard, but one that still included the numpad and ended up with this custom build:

https://i.imgur.com/H2sddCI.jpg

I use a fullsize board at work, but at home I prefer the slightly smaller footprint that I got in that design.

(1) Parts that total $9,980, but claims it totals $33,950 (2) Recommendations for parts that are both years out of date, and vastly inferior to other options (CPU = AMD Ryzen Threadripper 3990X, GPU = RTX3090)

So I'm guessing the AI data isn't trained enough and is going off some poor metrics like sorting by price, perhaps recommending multiples without indicating (was it asking me to double up on RAM or Stroage?)

I think part of the thing is Software Engineers haven't been a thing for as long in the industry. I'm the only Software Engineer I've met doing controls. My supervisor has a CS degree and an Electrical Technician diploma, but never another SE.

Second is I think up until recently, the work done by Control Systems has been what's capable of an EE or ME so having a SE hasn't been necessary. I've been with my company for 10 years now, and in that time I've watched the evolution of what my clients are seeking in terms of requirements to their systems.

I primarily work in Agriculture or Food Production. 10 years ago my projects were assembling plants and getting their motors to start, with the required protections then some rudimentary automation to align paths and ensure flow.

Today? I'm building traceability systems to report on exactly which truck load was the origin of contamination for a railcar shipped months later. Or integrating production data to ERP systems. Adding MES capabilities to track downtimes and optimize production usage. Generating tools to do root cause analysis on events... It's a different world and the skills of a Software Engineer haven't really been a super important role for quite a while.

I think the mindset is shifting, but it is slow.

I've basically found my niche in the industry as a Software Engineer though I can't say I see myself staying in the industry much longer. The amount of time's I've gotten my hands on code published by my EE coworkers only to rewrite it to work 10x faster at half the size with less bugs? Yikes. HMI/PLC work is almost like working in C++ at times, there's so many potential pitfalls for people that don't really understand the entire system, but the mentality by EE/ME types in the industry is to treat the software as a second class citizen.

Even the clients treat their IT/OT systems that way. A production mill has super strict service intervals with very defined procedures to make sure there is NO downtime to production. But get the very same management team to build a redundant SCADA server? Or even have them schedule regular reboots? God no.

I hate PLC work for other reasons. I'm starting to look at going back to more traditional software role. I'm a bit tired of the road work and find the compensation for the amount asked of you to be drastically underwhelming. This meme is very much relevant:

https://i.redd.it/rawo5uki1v9b1.jpg

You're not wrong, but in the context of a PLC controlling a motor or gate it is far more segregated than the code you're probably thinking of. Having a timer override on a single gate's position limit sensor would have no effect on a separate sensor/gate/motor.

If the gate's function block had specific code built into it that affected all gates then what you're talking about would be more applicable.

I do a lot of support work for Control Systems. It isn't unheard to find a chunk of PLC code that treats some sort of physical equipment in a unique way that unintentionally creates problems. I like to parrot a line I heard elsewhere: "Every time Software is used to fix a [Electrical/Mechanical] problem, a Gremlin is born".

But often enough when I find a root cause of a bug, or some sort of programmed limitation, the client wants removed. I always refuse until I can find out why that code exists. Nobody puts code in there for no reason, so I need to know why we have a timer, or an override in the first place. Often the answer is the problem it was solving no longer exists, and that's excellent, but for all the times where that code was put there to prevent something from happening and the client had a bunch of staff turnover, the original purpose is lost. Without documentation telling me why it was done that way I'm very cautious to immediately undo someone else's work.

I suppose the other aspect is knowing that I trust my coworkers. They don't (typically) do something for no good reason. If it is in there, it is there for a purpose and I must trust my coworkers to have done their due diligence in the first place. If that trust breaks down then everything becomes more difficult to make decisions on.

For the confidence? It was working with others. The first job I had I got to sit down with one of the company's programmers as part of my on boarding and watch him work through tickets. After I saw just how flawed everyone was I felt a lot better about myself. I suppose that's a weird thing to say: Oh he was pretty shit, so I shouldn't feel bad about my poor performance...but that's not the point I want to make really. More that, it is wrong to compare your efforts to learn and grow against the final product of others. Once you sit down with the experienced devs and see how they shape and form the product and all the bumps along the way it doesn't feel so bad to struggle on your own.

Ultimately the skills that I honed that gave me the best boost in confidence were not really the direct programming parts where I put letters and numbers in files. It is the debugging. Understanding how things move and where to look for problems makes me feel like I can solve any problem with the right tools.

If a seasoned mechanic is unable to figure out how to reset the Maintenance Reminder or look up how to sync Tire Pressure sensors, run away.

In the same way that one can use knowledge of one programming language as a means to leapfrog into other languages, other skilled trades are similar. Perhaps there's something that could be said about an ICE mechanic trying to dabble on Electric but that's not the point you're making. So yeah. I know you're trying to make a point about lock in, but when I think of people I want to hire for tasks who might say "Oh, sorry, you have a Volkswagen and I only know how to work on GMC" I wouldn't take my GMC to them either. It shows a fundamental lack of skill in that they don't understand the broader concepts and their universal applications. If I, a programmer, can figure out my Volkswagen, my GMC, my Mazda, my Nissan, certainly a mechanic can. If my appliance repair specialist can only do Whirlpool when I ask for help on a Bosch that's red flags.

One might specialize. Sure. But to refuse? Weird. But I fear I might be getting lost in the weeds here because its all about the approach. "Sorry, too busy to take on work on things that aren't my specialty": yep, understood. "Sorry, I don't know I only know " bad.

This is honestly a good question to ask at times. I remember back when I was trying to get into weight lifting. I was searching for apps and tools that would help me track milestones and progress, setting up routines and all that. I remember going through some options, then making a spreadsheet, and refining the spreadsheet and just hating the whole process.

So then I opened a notebook and just wrote down my lifts for the day. At the top I wrote my 1 rep maximums for the big 4 lifts and had a page for my program that denoted the rep#/set#/1RM% and done.

What did it lack? Maybe some categorizing or search tools. Maybe some graphing to visualize progress over large spans of time? Well I don't need any of that. What matters is what I'm doing now.

There's probably several examples of things like that. I can't count the number of times I've tried using organizers for things like groceries or maintenance that have me spending more time fiddling with settings and formats than just doing the task. At my job I create a new text file daily to note what I worked on and shit that came up. I date it and save it to a directory and just use grep to recall info when I need to look back over large spans. No awkward TODO lists or planner apps. No updates or UI changes. No subscription fees or "Share" buttons.

Sometimes, asking how much time you save with a computer/app/whatever is the right thing.

You think our government respects people taking time to rear offspring? Of course not! They're not contributing their labour to our economy while being parents so we've structured the incentives to start families in such a way that they're driven back to work ASAP. Strictly speaking: having children is bad for our labour force and should be avoided.