IT/Software career thread: Invert binary trees for dollars.
- Thread starter Traak
- Start date
Asshat Foler
Log Wizard
- 49,135
- 41,660
Ya I mean people aren't writing in assembly most of the time thankfully. There's a number of RToS kernels out there that aren't Linux based. NuttX is pretty popular ATM and is posix/Ansi standards with unix-like API so if you know Unix ur good to go.
Noodleface
A Mod Real Quick
- 38,652
- 16,713
I wrote UEFI firmware and "BIOS", people will give me shit if I say it was UEFI BIOS but that's what we called it so people knew what it was. I also wrote UEFI POST, as well as drivers. I've also written legacy BIOS and legacy drivers/oproms.
It is boring to some people, and to others it's awesome. It's probably because my degree is in computer engineering so I love low level stuff. When I interned at EMC I got an internship in the Firmware department and I went "ugh this is exactly like what we're learning in school, this is so boring." But I'm an aspie so it spoke to me. It's the one job I regret leaving because I enjoyed the work so much. It's not easy finding UEFI/firmware jobs around here, in my experience.
I have written some legacy BIOS in assembly and that's really boring. We had some assembly gurus on the team and I couldn't ever even hope to come close to that skillset. I did do a log of assembly level debugging though. Very cool stuff.
On my current work I'm taking a DSP course offered by UMass because they're trying to get more DSP engineers in the company. Pretty sure this will lead to really good opportunities. Really low level stuff with a lot of math
It is boring to some people, and to others it's awesome. It's probably because my degree is in computer engineering so I love low level stuff. When I interned at EMC I got an internship in the Firmware department and I went "ugh this is exactly like what we're learning in school, this is so boring." But I'm an aspie so it spoke to me. It's the one job I regret leaving because I enjoyed the work so much. It's not easy finding UEFI/firmware jobs around here, in my experience.
I have written some legacy BIOS in assembly and that's really boring. We had some assembly gurus on the team and I couldn't ever even hope to come close to that skillset. I did do a log of assembly level debugging though. Very cool stuff.
On my current work I'm taking a DSP course offered by UMass because they're trying to get more DSP engineers in the company. Pretty sure this will lead to really good opportunities. Really low level stuff with a lot of math
- 2
Noodleface
A Mod Real Quick
- 38,652
- 16,713
Bit manipulation was my favorite part. I noticed new kids out of college seem to have no concept of it
- 17,190
- 8,198
It's a neat concept and I still use it rarely in higher level languages. But it does not lend itself to readable code most of the time.
Noodleface
A Mod Real Quick
- 38,652
- 16,713
Depends what you're doing but most engineers would have plenty of #define for the hex/bit values
- 17,190
- 8,198
Did you just try to excuse away a code readability issue with another code readability issue?
Noodleface
A Mod Real Quick
- 38,652
- 16,713
Noodleface
A Mod Real Quick
- 38,652
- 16,713
Noodleface
A Mod Real Quick
- 38,652
- 16,713
- 2,779
- 4,491
It's not that the higher level stuff is more "artsy", it's just that most high level language jobs have migrated to languages and frameworks that promise to achieve goals with the least amount of work. All at the cost of really understanding what is happening at a low level. After three metric tons of libraries and abstractions and APIs you get: "An error has occured."
Programming has evolved into a "finish something quickly and iterate from that" model (fueled by the Buzzword du jour, like Agile, DevOps, Scrum), because obviously the customer doesn't even know what he wants. So pick something, we'll have to rewrite it anyways.
- 4
- 17,190
- 8,198
Use some structs then!
I'm not really arguing that #defines can be useful, I just don't like the overall concept.