Live data from Hacker News

What real life bad habits has programming given you?

stackoverflow.com

81–90 of 90 posts

Re: What real life bad habits has programming given you?

#82

I keep a lot of things sorted. For example, my wallet's money is always sorted. With multiple denominations of bills, the insertions aren't O(1) when I'm in line if you know what I mean.

I do this all the time - all bills have to be the same orientation and in order of smallest to largest value. If I take a few out of the ATM I'll stand there sorting them for a few seconds annoying the people queueing behind!

Re: What real life bad habits has programming given you?

#83
post #34

what can i say? i lather, rinse, repeat. lather, rinse, repeat. lather, rinse, repeat. lather, rinse, repeat. lather, rinse, repeat... showers take a while

Hey, at least it's tail call optimized. It could have been lather, lather, lather, lather, lather, bottle empty, rinse, rinse, rinse, rinse, rinse...

Re: What real life bad habits has programming given you?

#85
post #67

Two stick out: 1. Answering questions fairly literally. a. "Did you like the salad?" "No, I did not." b. "Would you like to go to the fine art museum with me and 4 of my friends on Friday night?" "No, I would not like that." c. Note that I can escape from this pattern only when it's extremely obvious the truthful answer is a bad one. "Do these jeans make my ass look fat?" "I don't think it's the jeans..." I can avoid…

There could be a correlation between programming and the habits you've pointed out but correlation does not imply causation.

Correlation implies synergism!

Re: What real life bad habits has programming given you?

#86
1- Always trying to start something as soon as possible ensuring others that it would be improved in next iteration. even things like buying clothes, shoes and eating

2- using too much technical jargons in my discussions (switch, multitask, exception, stack etc)

3- finding bugs in almost everything. tv shows, movies, direction, games, house architecture, roads, street lamps you name it

4- getting frustrated in social gatherings, thinking "Why are all these people talking about so stupid things?" or "why dont they just get to the point?"

5- guessing what people are gonna say or do and preempt them in their discussions/actions

Re: What real life bad habits has programming given you?

#87
post #64
post #62

Earlier quoted context omitted.

where is here?

Australia

God Bless Australia. I love that country, and I really liked how tax is already included in all prices and payment is rounded to 5c since there are no 1c pieces. It makes payments so much simpler.

Re: What real life bad habits has programming given you?

#89
post #24

When I count things (in the real world), I now have a bad habit of starting a zero. "How many floors on that building?" "Let's see, 0, 1, 2... oh wait..."

Fence-post error. Are you counting the floors themselves or the distance from the ground?

I was actually trying to figure out where my window was on the outside of an office building I work in (5th floor). So I started with 0 which would have meant I would be looking at the 6th floor, not 5th.

Re: What real life bad habits has programming given you?

#90

Two stick out: 1. Answering questions fairly literally. a. "Did you like the salad?" "No, I did not." b. "Would you like to go to the fine art museum with me and 4 of my friends on Friday night?" "No, I would not like that." c. Note that I can escape from this pattern only when it's extremely obvious the truthful answer is a bad one. "Do these jeans make my ass look fat?" "I don't think it's the jeans..." I can avoid…

Along those lines, I find myself increasingly impatient with the verbosity of spoken English. Many times someone will ask me something, and before I even start explaining my reasoning, I think: "is accomplishing this worth the time commitment of explaining it?" ... sometimes it is not, so I simply just say "nevermind".

When it comes to responding to questions, I'm pretty sure this just makes me look rude. When asked about the salad or museum, I'd just reply "No." About the phone number: "Yes" (then I'd look it up in my phone). For the gloves: "Yes" (I tend to remember stuff like that). All the rest just seems extraneous and time-consuming to say, especially when it can be inferred by the listener if they would just think it through.

Post reply on HN