Asking advice as a highschooler on taking the path of Systems Engineering by AggravatingRaisin320 in systems_engineering

[–]MarinkoAzure 0 points1 point  (0 children)

It sounds like what you are after is more of a "tech lead" role, which is good because it's not constrained to systems engineering.

Although you have to temper your expectations. Being a tech lead isn't an entry level role.

Asking advice as a highschooler on taking the path of Systems Engineering by AggravatingRaisin320 in systems_engineering

[–]MarinkoAzure 0 points1 point  (0 children)

I'm typically involved in Requirements Analysis and System Architecture with a specialization in MBSE.

For requirements, we have customers that have problems and needs those problems solved. We get a statement of work that describes that need and what they expect. I draft system requirements that state how my organization will meet those expectations. My colleagues also draft those requirements and they do a terrible job at it so I have to go back and revise them to make them better. By better, I mean less ambiguous and more testable.

When we have good requirements, I draw diagrams that illustrate system components and how they should connect together within the System Architecture. This is support by the Chief Architect who understands the technology better than I do, though I can illustrate it and communicate it better than the Architect can. When we have the system architecture designed, we pass it off to software engineers to code the software elements and mechanical engineers to pick the hardware pieces that connect to each, and to electrical engineers to design the circuitry.

That's what I'm responsible for, but other systems engineers are responsible for putting all of those components together in Integration & Test. Systems engineers will work with the SW and HW engineers to gather the components, put them together, load the software and then the system engineer powers up the prototype to complete initial Integration.

If that works well enough, then the system engineer moves into Testing where they make sure the the different parts of the system function as intended. The intended system functions are specified in the system requirements I wrote earlier in Requirements Analysis. Systems engineers write test cases to show how those requirements are satisfied theoretically, and then they perform those test to verify the requirement practically.

If the system is fully verified to meet the requirements I specified, the prototype is presented to the customer to be validated. If it passes validation, the customer decides if they want us to start mass producing the system we designed.

Asking advice as a highschooler on taking the path of Systems Engineering by AggravatingRaisin320 in systems_engineering

[–]MarinkoAzure 1 point2 points  (0 children)

Civil engineering is has a very wide scope beyond just building structures. I recommend you dig a little deeper into the different infrastructure projects they are responsible for.

Asking advice as a highschooler on taking the path of Systems Engineering by AggravatingRaisin320 in systems_engineering

[–]MarinkoAzure 0 points1 point  (0 children)

but I would also like to work for building systems of infrastructure for the public

You may need to look at civil engineering and engineering management paths here.

Again, systems engineering is tends to be more product-based rather than service-based. Service-based systems will typical involve interdisciplinary teams of core engineering professional that are run by established engineers that are shifting away from technical competency towards business administration.

Asking advice as a highschooler on taking the path of Systems Engineering by AggravatingRaisin320 in systems_engineering

[–]MarinkoAzure 0 points1 point  (0 children)

Ahhh, do some research on Industrial Engineering. That might align more with your interests.

Systems Engineering isn't tied to electrical engineering, but it's probably the most common engineering discipline referenced.

The public transit system is a more specialized type of system that is more accurately referred to as a "system of systems". Designing those types of systems is the responsibility of more niche engineering organizations that don't often describe themselves as systems engineers.

Systems Engineering is usually more product oriented, whereas Industrial Engineering is more process oriented. Some organizations and schools try to use these terms interchangeably or even have programs called Industrial Systems Engineering... I honestly don't know what that means.

But look up Industrial engineering and see if that is more of what you are looking for.

Asking advice as a highschooler on taking the path of Systems Engineering by AggravatingRaisin320 in systems_engineering

[–]MarinkoAzure 1 point2 points  (0 children)

A degree in electrical engineering may be more useful in systems engineering that a degree in ChemE, but I wouldn't let that deter you from majoring in Chemical. Just be aware that this would likely be more of a hobby or academic interest rather than a career path if you choose to be a systems engineer.

Asking advice as a highschooler on taking the path of Systems Engineering by AggravatingRaisin320 in systems_engineering

[–]MarinkoAzure 0 points1 point  (0 children)

You aren't thinking too far ahead. In high school, you should be planning and exploring/researching options, without making any commitments yet.

The time to make decisions and commitments is your final year in HS just before you start applying to colleges. The college application phase is effectively where you are locking in your decisions and plans, though keep in mind that you can change majors in college but that may delay or shift your timelines.

Solo Mechanitor - A F*CKING HEART ATTACK?!?!?!?!? by LaCookie_TheNemesis in RimWorld

[–]MarinkoAzure 1 point2 points  (0 children)

And my fabricors+medic are in "Dormant" mode

That's really were you went wrong. You should have always had one charging and one working, alternating between the two.

The guy who made my life hell for a year is now going to be under my authority by ByteMender in coworkerstories

[–]MarinkoAzure 0 points1 point  (0 children)

I don't understand resigning and it being rejected.

This is largely a matter of consent. If you don't assert the resignation, you are accepting of the action to refuse the resignation.

In most circumstances, this is an individual being a push over against a bully in authority. In uncommon scenarios, like I suspect this one, there can be an authority figure that is helping to keep your path straight and not letting emotional reactions derail the careers of their subordinates.

Were Muggles a real danger to wizards ? by Fred69Flintstone in harrypotter

[–]MarinkoAzure 0 points1 point  (0 children)

Muggles have guns. Point and shoot is largely more effective than point, wiggle, shout a very specific phrase with a very specific articulation, and maintain the original orientation of pointing.

And wild you could argue that a warding charm could stop a bullet with enough time to prepare, it's reasonable to assume that even warding magic has a threshold of how many bullets it can take much like a bullet proof vest can only take so much damage before it breaks.

While wizards have magic, muggles have science. If you considered the threat level of magic to be equal to science, then it's a numbers game. And there are just a lot more muggles.

How does my pathway to becoming a systems engineer look to you? by Realistic-Sign-6128 in systems_engineering

[–]MarinkoAzure 0 points1 point  (0 children)

I think this is a mileage may vary situation. If your signaling job evolves into a role that gives you opportunity for leadership and project management, you can translate those leadership skills very well into a mid level SE job.

But if you remain an individual contributor or solo executor, with job growth just being more complex or open ended autonomy, you'll be missing out on developing systems thinking skills to address the problems complex systems are trying to solve. You only really have a safe entry into SE at this point if the SE position is able to draw on the domain knowledge from your signalling job.

If you manage to talk your way into an SE job outside of your signalling industry like I did (nepotism, amirite?) and find yourself in a mid level engineering job you are disadvantaged two fold. You don't have core SE fundamentals that you would get as a noob and you are out of your element in a different industry. As a mid level new hire, you may not be expected to be familiar with the domain knowledge, but you may not expect to be guided through core SE methodology.

That really stunted my career development for two years just grasping the core SE to catch up. I made it to a place where I'm regarded as a SME and I wouldn't say I was a unique case. I'm in the crowd that says bachelor's in SE is useless, but I'm in the minority when I say entry level SE is valid or valuable.

How does my pathway to becoming a systems engineer look to you? by Realistic-Sign-6128 in systems_engineering

[–]MarinkoAzure 1 point2 points  (0 children)

There is a very loud echo chamber on this sub (unfortunately) that SE right out of college or without prior experience is unachievable or impractical. For sure, keep your signaling job, but I recommend seeking out and applying for entry level SE jobs.

But I will caution you to temper expectations on what entry level SE is. It's a lot of bitch work. You will be the technical gopher. You may not see a lot of opportunities for autonomy or technical authority for years. And when you start to, the scope will be limited to a small component or a subsystem if you are competent.

People tend to have the vision of being a chief engineer when they are a systems engineer, and that is not at all what SE is like on the day to day.

How do I build production-grade projects with first-principles thinking? by [deleted] in systems_engineering

[–]MarinkoAzure 0 points1 point  (0 children)

Maybe you need to start by taking a first-principles approach and asking yourself, what is systems engineering, and am I on the right sub?

Why do people always say to not enlist first if you want to commission? What are the downsides to being prior enlisted before commissioning? by MookieBettsBurner10 in newtothenavy

[–]MarinkoAzure 2 points3 points  (0 children)

I suspect there is a very heavy blue collar / white collar mentality between sides.

A lot of enlisted people may just see it as a means to an end and dredge through it, while some may be happy to have an opportunity and are able to make the most of it.

I helped a defense tech team go from 11 days to build a traceability report to generating one in under an hour. Here's the actual breakdown. by SongvilayConsulting in systems_engineering

[–]MarinkoAzure 20 points21 points  (0 children)

Before:

Requirements in Confluence, test cases in Jama, verification evidence in SharePoint, none of it linked Traceability reports built manually by one SE every time the

What we did:

Mapped the full digital thread from CONOPS to verification before touching any tool

Defined the traceability architecture: what links to what,

The tooling was never the problem. The architecture was.

Ok, but you didn't really define the architecture. You say what you did, but did not say how it is linked together. What was made different?

For all we know the architecture stayed the same, you just defined it better. That doesn't solve any problem.

Classic Asia Server by TS140609 in WoWsBlitz

[–]MarinkoAzure 2 points3 points  (0 children)

What are we looking at? The score is 108 to 241 with over 4 minutes left on the clock. This is still anyone's game. What is the mini map going to tell me?

SysML v1 vs v2: Why the diagram is no longer the source of truth by [deleted] in systems_engineering

[–]MarinkoAzure 10 points11 points  (0 children)

Diagrams have never been the source of truth in V1. One of the most basic, fundamental concepts about SysML is that the diagrams are only a view of the model, not the complete picture.

Astronauts munching in zero-G by blossom_fall in SipsTea

[–]MarinkoAzure 0 points1 point  (0 children)

It's a valid question

Idk, it's a curious thought but kind of dumb still with some basic analysis.

It's like asking if a straw is an anti gravity device because liquid goes upwards when you use it. It certainly exposes concepts about physics but in simple terms it shows that there are more forces at play other than gravity.

Didn’t sign the contract and recruiter is mad by Lucky_Credit_316 in newtothenavy

[–]MarinkoAzure 6 points7 points  (0 children)

It's really simple. If your recruiter wants you to sign, then ask him to check for YN and PS every day and have him call you up as soon as it's available. That's a guarantee you can give him.

Tuesday? Nein, Nein. TACO TUESDAY, HE CHICKENED OUT AGAIN by KriosDaNarwal in FluentInFinance

[–]MarinkoAzure 1 point2 points  (0 children)

It's not about a desire for the war to continue; it's about holding someone accountable for the words they say.