>>64719711>a really useful post on here?
Please, you flatter me too much! (don't forget the balls tho)>did an electronics degree, which while it had a programming aspect, was very basic and functional
No worries, it's normal for EE to have shitty code - it's a stereotype for a reason.
Vice versa, it's normal for CS fags to be embarrassingly clueless about electronics, and I'm sure you folks have stereotypes for that too.
Specialization and all.>While I can get a program up and running, I don't think about the resources available
Folks who don't focus on embedded/systems programming often aren't too great in that regard too. Just think about all the Java pajeets and so on. Hell, niggas be doing missile guidance systems that leak memory like a sieve, since it leaks slow enough that the system hits the target before it becomes an issue.
Don't forget the old maxim:https://cbednarski.com/articles/make-it-work-make-it-right-make-it-fast/>, which makes me think that I can't really apply for more software engineering focused jobs, as I won't have the background on how to properly structure my programs.
Don't sell yourself too short. You might be able to score a Junior position, given that folks switch from HVAC to this shit.
Just don't lie on your resume, explain your strengths (more disciplined approach compared to non-engineering lads - but phrase it more tactfully) and weaknesses, but don't overdo it to avoid getting shafted during the compensation negotiations.
Still, let's see. You did engineering, know EE-tier C programming, and would like to get a dev job, does that sum it up? Add anything that I'm missing.
What field would you like to focus on? Webshit (front/backend), embedded, automotive, HPC, scientific, academic, meme learning, big data, enterprise, etc?