It was really fun to learn how transistors work, MOS gates and all this stuff.
I don't think it makes me a better software engineer though.
Can't relate to how it's helpful in my developer day-to-day work. I would still go ahead and learn again if I had to, but more to satisfy an intellectual interest.
I had a job where I worked with really low level programming, writing firmware and implementing an SPI protocol from scratch. I agree that the amount of jobs are fewer, but by understanding those fundamentals, I now am able to more easily work in an entire growing industry: IOT.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey Lane, thanks for instigating for more CS knowledge pursuit. I definitely agree every software engineer should have this in the roadmap.
"Processor Architecture" is the only topic I might not agree entirely.
I've learned this when was playing with Texas Instruments CIs and Arduino and RaspberryPi.
It was really fun to learn how transistors work, MOS gates and all this stuff.
I don't think it makes me a better software engineer though.
Can't relate to how it's helpful in my developer day-to-day work. I would still go ahead and learn again if I had to, but more to satisfy an intellectual interest.
What's your view and experience?
I had a job where I worked with really low level programming, writing firmware and implementing an SPI protocol from scratch. I agree that the amount of jobs are fewer, but by understanding those fundamentals, I now am able to more easily work in an entire growing industry: IOT.