Signs that you are a bad programmer • Hacker News Board

Re: Signs that you are a bad programmer

#121

Post by Zaak » Thu, Oct 20, 2011, 2:15 AM UTC

Androsynth wrote: post #108

JonnieCache wrote: post #100

Earlier quoted context omitted.

I guess the point is that there's no "privileged" position in these systems which changes with time, like the point of execution in programming. What is the proper name for the bit of code that's currently being executed? I've suddenly realised that its a concept you think about constantly when coding, but its so much a part of the scenery so to speak that you never consciously consider it.

At the hardware level it's called the program counter, which is a register containing the address of the current operation the processor is running. After the operation is finished, it increments itself and moves to the next step in the program. Edit: just realized I didn't really answer the question, I believe what your actually talking about is a statement. I usually jump at the chance to talk about stuff from my o…

The program counter isn't the only element of that "what the program is doing now" state though. The context in which the current instruction is being executed makes a world of difference.

Re: Signs that you are a bad programmer

#122

Post by Zaak » Thu, Oct 20, 2011, 2:16 AM UTC

kennywinker wrote: post #104

JonnieCache wrote: post #100

Earlier quoted context omitted.

I guess the point is that there's no "privileged" position in these systems which changes with time, like the point of execution in programming. What is the proper name for the bit of code that's currently being executed? I've suddenly realised that its a concept you think about constantly when coding, but its so much a part of the scenery so to speak that you never consciously consider it.

Top of the stack?

http://en.wikipedia.org/wiki/Coroutine

Re: Signs that you are a bad programmer

#123

Post by SimHacker » Thu, Oct 20, 2011, 2:18 AM UTC

FuzzyDunlop wrote: post #65

philwelch wrote: post #55

Earlier quoted context omitted.

"Good" already has a meaning, you can't arbitrarily redefine it. You have to actually figure out what the most "good" tradeoff is between shipping and writing maintainable code.

"Good" is also arguably subjective and relative to the subject's perceptions of "bad"(and vice-versa). So of course that "good" tradeoff to one programmer might be a "bad" one to another.

I'm not bad. I'm just drawn that way.

Re: Signs that you are a bad programmer

#124

Post by nhangen » Thu, Oct 20, 2011, 2:36 AM UTC

bmj wrote: post #23

nhangen wrote: post #18

Earlier quoted context omitted.

I'm in this position now. I'm not a great developer, and I love learning new tricks, but because I'm billed hourly, am constantly interrupted, and get brought in to useless meetings, I'm left with zero time to learn.

The other problem with this is that you never have the opportunity to improve the business, either. Often, management wants the rank and file to improve processes ("because they know them best") but it's hard to find the time for that when you're already working full time (and more) on your deliverables.

No doubt. In fact, this is exactly what happened to me today. I'm supposed to have great ideas, but when trying to implement them, told that I need to focus on paying the bills. I don't know how people manage this long-term.

Re: Signs that you are a bad programmer

#125

Post by sambeau » Thu, Oct 20, 2011, 2:57 AM UTC

JonnieCache wrote: post #100

Sniffnoy wrote: post #83

Earlier quoted context omitted.

I have to wonder if someone who can't determine order of execution should be an electrician or plumber either -- those aren't static systems!

I guess the point is that there's no "privileged" position in these systems which changes with time, like the point of execution in programming. What is the proper name for the bit of code that's currently being executed? I've suddenly realised that its a concept you think about constantly when coding, but its so much a part of the scenery so to speak that you never consciously consider it.

What is the proper name for the bit of code that's currently being executed?

I would have used 'Cursor' or 'Program Cursor'. But I'm now convincing myself that that a database term.

Re: Signs that you are a bad programmer

#126

Post by warmfuzzykitten » Thu, Oct 20, 2011, 2:58 AM UTC

kno wrote: post #31

oh my! I love when you recommend specific career base on specific issues. You made my day! I can't stop laughing. "Bag Lady" seriously looool

I agree with joe_the_user. I found the article snide and condescending. I suggest alternative careers for the author:

- Leader of a high school clique - Movie reviewer who concentrates on who's "in" - Coiner of demeaning nicknames

I wouldn't want to work with this person.

Re: Signs that you are a bad programmer

#127

Post by mrb » Thu, Oct 20, 2011, 3:05 AM UTC

JonnieCache wrote: post #100

Sniffnoy wrote: post #83

Earlier quoted context omitted.

I have to wonder if someone who can't determine order of execution should be an electrician or plumber either -- those aren't static systems!

I guess the point is that there's no "privileged" position in these systems which changes with time, like the point of execution in programming. What is the proper name for the bit of code that's currently being executed? I've suddenly realised that its a concept you think about constantly when coding, but its so much a part of the scenery so to speak that you never consciously consider it.

On the amd64/i386 platforms, the Instruction Pointer CPU register points to the executed instruction. Its name is IP for 16-bit code, EIP (extended) for 32-bit code, or RIP (register) for 64-bit code.

Re: Signs that you are a bad programmer

#128

Post by chernevik » Thu, Oct 20, 2011, 3:09 AM UTC

bitops wrote: post #78

The OP may be being ironic/sarcastic to a certain degree but I'm always wary of these types of articles. "You are a bad programmer". How would it make you feel to hear that? Probably not open to further suggestions on how to improve. While I agree that as programmers we should always strive to be getting better, these types of put-downs and belitting don't foster a culture of communication and trust. Personally, I'm…

I saw at least a half-dozen habits that have cost me I-don't-want-to-think-how-much time. And at least a half dozen I'm still doing. I was dimly aware of them as repeated frustrations, but identifying them makes it a lot easier to target them for deletion.

I'm going to mark this thing up, add "haven't crossed any of these off in the past year", and postpone my judgment until next fall.

Re: Signs that you are a bad programmer

#129

Post by yaix » Thu, Oct 20, 2011, 3:12 AM UTC

> eg: the "Delete Database" button is next to "Save", just as big, has no confirmation step and no undo

That was common practice all over the Web for over a decade, it only stopped recently (on most sites). [Submit] [Reset] Argh!

Re: Signs that you are a bad programmer

#130

Post by recoiledsnake » Thu, Oct 20, 2011, 3:49 AM UTC

kd0amg wrote: post #103

zbuc wrote: post #50

Earlier quoted context omitted.

But you still have something to ship, even if it's just to your buddies on github.

What you give to someone else may not be code -- it might just be the code's output.

That is still called shipping.