4 ms·
> but the fundamentals are all the same. Sure. Also, any job that requires writing English all day has some cross-cutting fundamentals. I'm making a general p
by throwawaygh 5y ago
> but the fundamentals are all the same.
Sure. Also, any job that requires writing English all day has some cross-cutting fundamentals.
I'm making a general point about empirical software engineering research: "does the question that's being asked get at the fundamentals that are shared between all programmers, or do we need to be more careful about specifying what we mean when we say 'programmer'?"
> It’s unclear what kind of point you’re trying to make and how it had any bearing on the cannabis angle.
I could probably do the "$local_shop web dev job" high all day. Not probably. I definitely could write straight-forward iPhone apps or Django web apps all day long while high as a kite. No problem.
I definitely couldn't do other programming jobs high all day -- either because I need to spend a ton of time in careful conversation with other people, or because the technical problems require sobriety, or more usually a combination of both.
Apparently the basic observation that some programming is easier than other programming is divisive here. That's fine for an HN comment thread. But I'd love to see a paper that goes something like "here are some buckets of programming jobs. Let's try to replicate a bunch of empirical SE studies with samples selected from each of these buckets and see what happens."
- haswell 5y agoI don’t think there’s any question that some kinds of programming is harder than others. The only thing that seems to be divisive is automatically assuming that the size or prestige of the org is what drives the complexity of the work. It’s easy to find easy programming work in big shops, and not uncommon to find hard work in small shops. As I said in my previous comment, there is absolutely a difference between different kinds of work.