Programming Circlejerk

144 readers

42 users here now

Community to talk about enlightened programming takes

Rules:

read and follow the programming.dev code of conduct
no flamewars
mark your unjerks
only programming related content allowed
link to the original source
do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.

founded 2 months ago

MODERATORS

[email protected]

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

submitted 2 months ago by [email protected] to c/[email protected]

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

[–] [email protected] 14 points 2 months ago (3 children)

Unless you're analyzing what microcode is doing with it, assembly is just hiding how things really work, too. Good engineers use early 1990s computers so that they can fully understand what's going on, and never have to trust anyone else to correctly do anything.

[–] [email protected] 7 points 2 months ago* (last edited 2 months ago)

Real engineers run all their code on CPUs they designed in verilog/VHDL.

[–] [email protected] 3 points 2 months ago (1 children)

Real engineers use binary.

[–] [email protected] 1 points 2 months ago

If by "real engineers" you mean the posers who do not work directly with the underlying analog waveforms that approximate digital logic, then I suppose you have a point.

[–] [email protected] 2 points 2 months ago

Lots of truth to this, lots of great eastern block engineers came from working with super janky computers that demanded high levels of mastery from their users.