Go to uni. Join a fablab.

>I am trying to learn every and all about its software, hardware, and firmware troubleshooting but i dont know the whole spectrum of it... Im trying to master everything of it
Learn to G-Code. Practically every 3D Printers run on the the same code as the industrial CNC machines of the 50's. All software does is generate G-Code for dummies who are too dumb to maths. You can pick up books on it for dirt cheap (anything post 90's will suffice) and there's plenty of free simulators out there for running you G-Code.

Hardware and Firmware are machine specific and generally responsible for <1% of errors. If you can G-Code you're immediately ruling out software which is responsible for 50% of issues with human error being the remainder.

>>18294
FYI: I was certified as a CNC engineer so I know what I'm talking about, even if my career has taken me away from engineering.

>>18295
Can you please tell your story, anon?

>>18298
>Can you please tell your story, anon?
There's not really much to tell. I worked with a design team on latches, catches and cases (aftermarket automotive). You know those fancy machines that cut out a part a thousand times a day, I was the one who took the schematics and wrote the program that told the machine to do its job.

The long and short of it is the industry has changed. Used to be we'd write the entire thing by hand, run it through a simulator and perform a dry-run before putting it to work. Now days you can auto-generate your code and it's normally fine, you still need people like us but not so many as you used to.

My job was pretty damn comfy, but ultimately it got boring and less challenging. You know that feeling when you go home and you feel like you haven't done a good days work, that was me almost every day. So I quit, got a temp-job in retail and worked my way up to management. The pays not as good (not that it's bad mind you) but the job satisfaction is there.