this post was submitted on 12 Feb 2025
70 points (92.7% liked)

ProgrammingCircleJerk

131 readers
18 users here now

Programming CircleJerkCommunity at request of a user.

founded 1 month ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 20 points 1 month ago* (last edited 1 month ago) (2 children)

To be fair, if you have an engineering degree that covered programming you probably learned C, ASM, and low level details about system architecture. But the definition of "engineer" seems a little looser when you're taking about IT compared to some other fields - SWE is the only "engineering" title you can get without a formal education, AFAIK.

[–] [email protected] 3 points 1 month ago* (last edited 1 month ago) (2 children)

EECS, you gotta know all the way down to electron flow!

I love to gift TIS-100 to anyone who tells me they want to be a programmer. So far it's been a great measure of success, if they actually play and complete it (observed via steam achievements)

[–] [email protected] 3 points 1 month ago

I wanna be a programmer!

[–] ICastFist 1 points 1 month ago (1 children)

How close is it to actual assembly from an existing CPU?

[–] sukhmel 3 points 1 month ago* (last edited 1 month ago)

Far, but being a programmer is usually not about using assembly anymore

Edit: to elaborate a bit, TIS-100 has an overcomplicated architecture but oversimplified command set, and restricts the coder way more than the real assembly (e.g. you have a limit on line length of 12 chars or somewhat close, and that includes the opcode itself). Imo these design decisions allow it to be interesting and simple enough to comprehend, but severely limits what can be implemented on that architecture in reality without requiring for lots of boilerplate