IOT is the future..

Pp

Glad you're enjoying the videos. Thanks for being here.

which books and resources did you find most useful after you landed your first job?

@@Jaavv It really depends on what your work involves. Embedded systems is a very big field in terms of what type of work you can do. For me, the more practical stuff about programming microcontrollers was the most important

Great idea! I'll add it to the list. Thanks.

Great idea!

I might be able to work that in. I'll see what I can do.

The skill of being able to read a datasheet definitely seems undervalued in general!

i mean thats what I did and I work as an embedded software engineer now LOL. Self-taught though.

Any particular project recommendations?

@@JacobSorber I liked your plant watering automation a lot, mine keep dying ;p Jokes aside, it sounds like a good project to cover a lot of interesting topics. I personally am right now working on my first embedded system, which goes further than a breadboard, trying to replicate the modern car blinker's running light with a Raspberry Pi Pico and a multiplexer. I find this a very cool project since it's practical and can even be pushed further to maybe implement it on a bicycle. Just talking from a systems engineering perspective, it's missing a sensor to dive into some feedback control. Anyways, just me thinking in out loud in the comment section :) Looking forward to what the others will suggest and I'm sure you'll make a great pick!

Thanks! Are you asking if it's possible to work with APIs in C? (Definitely , yes!) Or, are you asking if I can do a video about APIs in C on this channel? If so, do you have a particular API in mind?

@@JacobSorber Thank you for the answer :) I watched a guy on youtube how he programmed a trading bot in python and he used APIs for that and I wondered if that would be possible in c.

@@carsfan3124 Yes, you could do it in C. It might be more difficult. It depends on how the API works, but I might stick with python, and just run the python code from your c program. If it's an HTTP/REST-based API, you could also use LibCURL to make your job easier. But, yes, everything is possible in C, if you're willing to do it.

I am on the same boat as you. I've fiddled with some protocols but not enough to say I'm experienced/expert level. I've done a bit of 8bit (Ave Assembly) mcu stuff and some MSP430 / TI higher level stuff (more C less Assembly) but still lacking knowledge in circuit design / ideas to make a project from start to finish

Thanks. My best to India, as well. 😀

Best of luck, and thanks for the recommendation.

Thanks!

Thanks. I'll see what I can do. You can't do embedded systems very long before energy becomes an issue.

I'll probably stick with one that have laying around, so probably either an AVR or MSP430. I guess it depends on the project, though.

Thanks! All the best with learning embedded systems. And, of course, let me know if there are any topics you think I'm missing.

Definitely. I haven't looked into how they work, but...yeah. Thanks for the project idea.

Either works, as long as you're willing to pick up the other side. I approached it from the computer science side, but I have hired great people from the EE side, too.

Thanks. I probably will as the MSP430 support improves.

Yes it will be really amazing

I would say that eyesight wouldn't be much of an issue. It's not unexpected to have a $20-$50 USB microscope by your desk to zoom in on stuff. During embedded development cycles, however, you will often need to tweak the circuit slightly to address for hardware errors in prototypes. I've done 15 years doing embedded development (predominantly industrial instrumentation and IoT). Within a lot of the teams that I've worked with, there is usually 1 or 2 people that are just better at soldering and electronics assembly than others and the entire team informally relies upon them and asks them for most of the finicky work (soldering fly-wires, deadbugging components, etc). Just treat them with respect, ask nicely and buy them a beer or a lunch for doing you a favour. Also, if you have a properly trained, disciplined and experienced hardware designer, they will provide test/debug infrastructure to facilitate firmware development and they should be quite easy to access. Sadly, those are really hard people to find though, and I've found that many ill-informed managers push back on such things - which is counterproductive to the whole R&D process. One trick that I use during job interviews is to ask to see the hardware you are expected to work on. You can tell waaaay more from 30 seconds with a PCB: do they have test points for most nets? Do they have a serial port specifically firmware debugging? Did they even bother adding a few test LEDs? Finally, I've found that industrial electronics have better design practices than commercial electronics. They often still use big components (I've even seen through-hole components still used in active products) for vibration tolerance, heat dissipation, serviceability, etc. Just look for businesses that operate in "small volume/high margin" markets (industrial, medical, etc) instead of "high volume/low-margin" (typically consumer markets). Hope this helps you!

I was thinking a bit on this too - but because of Ohm's Law, V = IR, if voltage is high and resistance is at some small constant value, current will surely be high. On a deeper level, the potential difference of the circuit (the voltage) is what sets the current in motion in the first place, even though "it's the amps that kill."

Good point. It's true that the amps are what kills, but I've yet to hear about anyone accidentally killing themselves with a 3V battery or power supply. When dealing with mains power, there are MANY such examples (see Brandon's comment). And, a warning about Li-Ion/LiPos is definitely welcome. Though again, I've watched people abuse them a lot, and 99.99% of the time, the worst you ever see is a swollen cell because most current LiPo cells ship with some protection circuitry built-in.

@@JacobSorber im not talking about death by electrocution, Im talking about someone using jumpers on breadboard and doing something silly like shouring a battery, even an AA can deliver a few amps, which can melt that wire and burn you. I actually think that something like a usb power supply, even mains is safer as it has automatic short detection, or a fuse, or even just the regulation will keep it under the rated power. Batteries dont have current limits. Im not saying it to discourage people, Im saying it so that they have that knowledge in the back of their head all the time.

Hey Owen. Great to see you on here. I'll add fabrication to the list. As far as the custom OS idea goes, are you thinking some modified version of Raspbian (or the Linux kernel) or are you thinking from scratch? Both might be doable given enough time, but the later would be a serious project. 😀

With a basic project as well.. :) :)