I am a full stack application developer fully experienced in procedural, object oriented and functional programming with a goal of continuous development and integration with a dash of test driven development and pair programming. It sucks. I want to do what you do! 😂
My old professor used to say that aiming to be both a Hardware AND a Software engineer, was like getting a Engineering/Law double degree. You end up being neither a competent Engineer nor a competent Lawyer!
Wow, you get it! I suck at hardware, I came across your channel looking for basic background information and got so much more. I am a software person 100%, I have my degree in software and I've been making my living with software for the last 30 years. Your advice to specialize in one part of the hardware domain also applies to the software side.
The speed at which these industries are changing means you'll need to spend your free time just trying to not fall too far behind in the area you have selected. I can tell the approximate year someone graduated from university just by reading their code (for most people), I can also tell the era that the managers worked based on the coding standards in use.
The explosion of low cost maker boards and development tools has brought me in to this new world where I can interface with the hardware directly. I know if I ever want to get past the breadboard stage for anything I do I'll need to hire a hardware person to do it correctly but the little I can do on the breadboard lets me explore and get my hands dirty enough that I can determine what might work and what doesn't work. The same is probably true on the hardware side, your software skills will let you explore but you'll need help before going to production.
What is exciting is when the best of both worlds come together to produce a product and if the offerings today are any indication of what is to come then hold on to your hat the changes are going to come really fast.
If you are a man I recommend specializing in hardware. The reason is there are too many women going into software and if the feminazis get affirmative action going you are screwed. The other problem is the false sexual harassment allegations the feminazis are going to make. The percentage of men going into STEM fields may be 20% but that is many fields in one statistic. Approximately 40% of computer programming students are female.
Unfortunately only the largest companies can afford to have a different people for each area of the design. If you are applying at a smaller company they will want you to be able to do it all. This a personal choice but I have found it to be much more interesting to work at smaller companies doing it all. When I worked at larger companies I was given such a small slice of the project that I found it boring.
Just a quick note for anyone who knows C and wants to learn C++. I learnt C many years ago when I was in my 20's, and about 15 years later I looked at C++ assuming that it would be similar, or at least I would be able to leverage my knowledge of C. When I looked at it superficially it looked like a completely different language, and left it. It wasn't until I took a longer look at it a couple of years back that I found that C++ is just C, or at least a subset of it, it's just C++ comes at things from a different way, put it this way the same compilers will compile C and C++. You don't necessarily have to write object orientated code with C++. My point is if you know C then have a bash at C++ don't be put off by first appearances.
As a firmware engineer for 20+ years, I feel that I am more of a systems level person that works at the hardware/software interface. I try to maintain my basic knowledge of electronics alive as a hobbyist, and dabble on hardware description languages and FPGAs from time to time. I believe it is easier for a hardware person to transition into firmware/software.
Chopping the mic end can produce un-wanted noise… for more professional quality sound (mainly for XLR unbalanced mics) you want a XLR adapter like the DXA or such!
As a software dev, I'm of the opinion that no, you can't "master" both hardware and software.
It's hard enough "mastering" just one discipline. And software is a vast field. If you try to "master" everything, you become a generalist who isn't very good at specialised work.
The best programmers tend to specialise on one or two languages only. Sure, they know about other languages, and can use them in a pinch, but they stick to what they know.
Professionally I'm software, but at home in my free time I'm hardware doing RF (ham radio) and audio (helping my friend with his recording setup). I love integrating microcontrollers into my home projects so I can code for pleasure 🙂
Companies usually want either hardware or software. if you know both you can easily fail because thay couldn't 'fit' you on a specific position. So basically they believe these skills disqualify each other and disqualify you as a candidate.
For those in the world, like me who found out too late at uni, that we do suck at electronics and or software…. I am REALLY getting on well running "my own" workshop in an events company repairing and maintining all kinds of toys, from stepper motors to signals to computer stuff to large 7kw discharge fixture ballasts etc etc.. Its really varied and its worth while. The pay isnt that great but we are always short of even bad engineers in the warehouses!
Go and do what you suck at. Go for the challenge, not the easy way.
I am a full stack application developer fully experienced in procedural, object oriented and functional programming with a goal of continuous development and integration with a dash of test driven development and pair programming. It sucks. I want to do what you do! 😂
My old professor used to say that aiming to be both a Hardware AND a Software engineer, was like getting a Engineering/Law double degree. You end up being neither a competent Engineer nor a competent Lawyer!
Wow, you get it! I suck at hardware, I came across your channel looking for basic background information and got so much more. I am a software person 100%, I have my degree in software and I've been making my living with software for the last 30 years. Your advice to specialize in one part of the hardware domain also applies to the software side.
The speed at which these industries are changing means you'll need to spend your free time just trying to not fall too far behind in the area you have selected. I can tell the approximate year someone graduated from university just by reading their code (for most people), I can also tell the era that the managers worked based on the coding standards in use.
The explosion of low cost maker boards and development tools has brought me in to this new world where I can interface with the hardware directly. I know if I ever want to get past the breadboard stage for anything I do I'll need to hire a hardware person to do it correctly but the little I can do on the breadboard lets me explore and get my hands dirty enough that I can determine what might work and what doesn't work. The same is probably true on the hardware side, your software skills will let you explore but you'll need help before going to production.
What is exciting is when the best of both worlds come together to produce a product and if the offerings today are any indication of what is to come then hold on to your hat the changes are going to come really fast.
If you are a man I recommend specializing in hardware. The reason is there are too many women going into software and if the feminazis get affirmative action going you are screwed. The other problem is the false sexual harassment allegations the feminazis are going to make. The percentage of men going into STEM fields may be 20% but that is many fields in one statistic. Approximately 40% of computer programming students are female.
Unfortunately only the largest companies can afford to have a different people for each area of the design. If you are applying at a smaller company they will want you to be able to do it all. This a personal choice but I have found it to be much more interesting to work at smaller companies doing it all. When I worked at larger companies I was given such a small slice of the project that I found it boring.
Thank you Dave for your insights !
Just a quick note for anyone who knows C and wants to learn C++. I learnt C many years ago when I was in my 20's, and about 15 years later I looked at C++ assuming that it would be similar, or at least I would be able to leverage my knowledge of C. When I looked at it superficially it looked like a completely different language, and left it. It wasn't until I took a longer look at it a couple of years back that I found that C++ is just C, or at least a subset of it, it's just C++ comes at things from a different way, put it this way the same compilers will compile C and C++. You don't necessarily have to write object orientated code with C++. My point is if you know C then have a bash at C++ don't be put off by first appearances.
Aside from taking an electrical engineering course, are there any good sources online for beginner/amateur/hobbyist PCB design?
So we can see all the exotic wildlife, like highway and cars!
I'd have liked a video where he is going into discussion with that other guy. But something tells me Dave is uncomfortable with that.
I'm finishing computer engineering and here I am… watching and enjoying your 5 years old videos about hardware. I hope I chose the right career…
As a firmware engineer for 20+ years, I feel that I am more of a systems level person that works at the hardware/software interface. I try to maintain my basic knowledge of electronics alive as a hobbyist, and dabble on hardware description languages and FPGAs from time to time. I believe it is easier for a hardware person to transition into firmware/software.
It is fun how you chose the hardware solution over software one with your mic.
I kind of like seeing out the window. It's like I'm in the car with him having a chat.
Bull and Bush product placement detected 🙂
Chopping the mic end can produce un-wanted noise… for more professional quality sound (mainly for XLR unbalanced mics) you want a XLR adapter like the DXA or such!
IMO.. cont… just focus. A lack of focus is a major reason why people don't succeed in their fields.
Be really really good at what you do, and just keep secondary tasks to a minimum.
As a software dev, I'm of the opinion that no, you can't "master" both hardware and software.
It's hard enough "mastering" just one discipline. And software is a vast field. If you try to "master" everything, you become a generalist who isn't very good at specialised work.
The best programmers tend to specialise on one or two languages only. Sure, they know about other languages, and can use them in a pinch, but they stick to what they know.
Professionally I'm software, but at home in my free time I'm hardware doing RF (ham radio) and audio (helping my friend with his recording setup). I love integrating microcontrollers into my home projects so I can code for pleasure 🙂
Companies usually want either hardware or software. if you know both you can easily fail because thay couldn't 'fit' you on a specific position. So basically they believe these skills disqualify each other and disqualify you as a candidate.
For those in the world, like me who found out too late at uni, that we do suck at electronics and or software…. I am REALLY getting on well running "my own" workshop in an events company repairing and maintining all kinds of toys, from stepper motors to signals to computer stuff to large 7kw discharge fixture ballasts etc etc.. Its really varied and its worth while. The pay isnt that great but we are always short of even bad engineers in the warehouses!
I got this problem – I hate specialization. I'd rather be an all-round guy.