As an engineer:
- Receive or identify a problem.
- Design a solution that solves or mitigated the problem.
- Usually pay someone to make a prototype or do it ourselves
- Test the prototype and see if it solves the problem. If no, go back to #2 until a workable solution is found
- Get someone else to build the final thing.
- Make sure thing works. Ship it.
This is a recursive and iterative process. Meaning you will find problems inside your solutions and need to fix them.
Eventually you finish the thing and get a new problem and do the whole game over again. It’s like a puzzle that requires absurd amounts of knowledge to play well, but anyone could try to solve the problem. That’s why good engineers are paid pretty well.
DaCookeyMonsta@lemmy.world 10 months ago
I’m an engineer. I’m on my phone looking at memes until someone asks me a question, then I do a thing in 5 minutes that they expected to take 5 days because people don’t understand computers, then I go back to the memes.
HootinNHollerin@lemmy.world 10 months ago
Sounds like tech support not engineering
surewhynotlem@lemmy.world 10 months ago
I have been downvoted to hell for what I’m about to say, but I’m going to say it again anyway.
IT support people are now called engineers. No, I don’t like it. No it’s not proper “engineering”. Yes, language evolves and there’s nothing we can do about it. If that’s a problem for people, I recommend screaming into the void. It doesn’t help, but you feel better after a while.
EvilHankVenture@lemmy.world 10 months ago
Quiet! You are giving the secret away.