ProgrammingCircleJerk

59 readers

90 users here now

Programming CircleJerkCommunity at request of a user.

founded 2 weeks ago

MODERATORS

FirstMajesticComet@programming.dev

crmsnbleyd@sopuli.xyz

Not knowing how to write C means you are objectively a very bad engineer (sopuli.xyz)

submitted 1 week ago by crmsnbleyd@sopuli.xyz to c/programmingcirclejerk@programming.dev

37 comments fedilink hide all child comments

URL: https://www.linkedin.com/posts/ahmadnwirah_not-knowing-how-to-write-c-means-you-are-activity-7294682256160260096-0g

you are viewing a single comment's thread
view the rest of the comments

[–] jet@hackertalks.com 3 points 1 week ago* (last edited 1 week 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)

[–] JoeBigelow@lemmy.ca 3 points 1 week ago

I wanna be a programmer!

[–] ICastFist@programming.dev 1 points 1 week ago (1 children)

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

[–] sukhmel@programming.dev 3 points 1 week ago* (last edited 1 week 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