What's something difficult programmers make look easy?

Post by d0mine » Sat, Jan 20, 2024, 5:07 AM UTC

ravenstine wrote: post #27

danielvaughn wrote: post #4

Earlier quoted context omitted.

This. I feel fortunate that I didn't start out in tech - I didn't become a programmer until I was 30. I'd been working since I was 15 or so, so I'd had about 15 years of experience in various industries. I think a lot of devs who go into comp-sci and land into tech right after college have very little understanding of how hard life can be outside of tech. This isn't an easy industry, but goddamn it's so much better t…

Reminds me of the recurring conversation on HN about how people should stop driving cars and just walk everywhere. It's like, yeah, in an ideal world, all 8+ billion humans could pick up craft coffee as they stroll 5 minutes to their big tech employer who doesn't actually care when they show up. There's legitimate criticisms for how cities have been designed, but going further by vilifying car owners in the present a…

Post by [deleted] » Sat, Jan 20, 2024, 3:47 PM UTC

d0mine wrote: post #71

ravenstine wrote: post #27

Earlier quoted context omitted.

Reminds me of the recurring conversation on HN about how people should stop driving cars and just walk everywhere. It's like, yeah, in an ideal world, all 8+ billion humans could pick up craft coffee as they stroll 5 minutes to their big tech employer who doesn't actually care when they show up. There's legitimate criticisms for how cities have been designed, but going further by vilifying car owners in the present a…

What do you think about public transport vs. personal cars?

Post by HumblyTossed » Sat, Jan 20, 2024, 11:55 PM UTC

thiht wrote: post #72

HumblyTossed wrote: post #17

I would argue that difficult programmers don't make anything look easy.

Shouldn’t there be a "that" between "difficult" and "programmers" in the title to make parsing less ambiguous? I’m not sure if adding it would be grammatically correct (Non native speaker)