Live data from Hacker News

I have no side code projects to show

linkedin.com

11–20 of 148 posts

Re: I have no side code projects to show

#11
post #7
post #4

I want to work in a group where they appreciate that I was basically born to code. That despite my youthful features, I have still been coding for over 30 years. That I can do many tasks in an hour, that other people would take days to do. That I will spend an extra 3 hours to put a cherry on top, just because I can. I may even do it on a Saturday, because code is what I like to do with my spare time too. So when the…

That's a pretty elaborate story to rationalize the fact you didn't know the difference between range and xrange....

The correct answer is of course, is that xrange doesn't exist.

Re: I have no side code projects to show

#12
post #9

As someone who does have a bunch of pet projects, I appreciate the author's sentiment. I often wonder whether my programming world presence (GitHub, HN, &c.) accurately reflects the kind of person I am (or perhaps want to be).

hint to the young: contribute anonymously. go to interviews and talk abou range vs xrange. it might never happen, but when one employer decides to go crazy and try to blame you for leaking code (that you may have written even before joining them) on open source projects, you are going to regret skipping the silly interviews by showing your open source persona to them. best thing you can do is keep it to yourself. the…

I appreciate the advice, although with the jobs I've had so far I've been sure to tell my employer in advance about my open source work.

Maybe I've just been lucky, but all have been either okay with it or actively supportive (even when concurrent with in-house development). That being said, I've been careful to avoid open-sourcing projects that I think come to close to hired work.

Re: I have no side code projects to show

#13
Here's a little example what happened to me:

I interviewed with a company. Naturally they asked for my side projects which I showed them. We talked about technical challenges, scaling, interesting bits of codes - all these kind of things. They were really excited. I passed the interviews and got the job.

Fast forward a couple month, still working on my side projects, some of which started generating a couple hundred bucks a month. My boss started asking me to stop any side projects and put all my time thinking about the company instead. I refused and said that I am 100% there during my work hours but what I do in my private time is not related and even the reason why I got this job in the first place. My boss didn't like that at all and even tried to figure the exact times out when I would work on private stuff to hold it against me. I eventually quit.

If your company wants to see side projects but dislikes the idea of you actually working on them after starting, you are doing something wrong.

Re: I have no side code projects to show

#14
post #8

I actually don't mind being a human machine. Not that I've had the chance yet. I'm still in college to get my CS degree and would fall into one of those people where "coding is a Craft". I genuinely love programming. I don't have a family, or really desire one. My weekend plans always consist of building another project of my own. A place that will let me code all day, give me a nap room, a shower, some salary, and f…

“I'm too old to know everything” ― Oscar Wilde

Re: I have no side code projects to show

#15
post #7
post #4

I want to work in a group where they appreciate that I was basically born to code. That despite my youthful features, I have still been coding for over 30 years. That I can do many tasks in an hour, that other people would take days to do. That I will spend an extra 3 hours to put a cherry on top, just because I can. I may even do it on a Saturday, because code is what I like to do with my spare time too. So when the…

That's a pretty elaborate story to rationalize the fact you didn't know the difference between range and xrange....

It doesn't need to be rationalized. I don't know it without googling it, but I can still get by writing some useful automation for Ops work. Granted, I haven't interviewed for a full-time Python gig, but even the one or two REALLY sharp programmers I know need to reference the web for a lot of stdlib stuff they don't use often.

Re: I have no side code projects to show

#16
post #8

I actually don't mind being a human machine. Not that I've had the chance yet. I'm still in college to get my CS degree and would fall into one of those people where "coding is a Craft". I genuinely love programming. I don't have a family, or really desire one. My weekend plans always consist of building another project of my own. A place that will let me code all day, give me a nap room, a shower, some salary, and f…

Just because the author has his priorities figured out doesn't mean that "this field isn't for them."

Re: I have no side code projects to show

#17
post #7

Earlier quoted context omitted.

That's a pretty elaborate story to rationalize the fact you didn't know the difference between range and xrange....

The correct answer is of course, is that xrange doesn't exist.

In short, it's the default behavior in Python 3; it doesn't exist anymore:

http://pythoncentral.io/how-to-use-pythons-xrange-and-range/

From that article (buried near the end for some reason):

>One more thing to add. In Python 3.x, the xrange function does not exist anymore. The range function now does what xrange does in Python 2.x, so to keep your code portable, you might want to stick to using range instead.

Re: I have no side code projects to show

#18
post #7

Earlier quoted context omitted.

That's a pretty elaborate story to rationalize the fact you didn't know the difference between range and xrange....

The correct answer is of course, is that xrange doesn't exist.

so they removed it from python 3?

Re: I have no side code projects to show

#20
post #13

Here's a little example what happened to me: I interviewed with a company. Naturally they asked for my side projects which I showed them. We talked about technical challenges, scaling, interesting bits of codes - all these kind of things. They were really excited. I passed the interviews and got the job. Fast forward a couple month, still working on my side projects, some of which started generating a couple hundred…

> If your company wants to see side projects but dislikes the idea of you actually working on them after starting, you are doing something wrong.

My impression was they generally want to see side projects for newbies/recent graduates, i.e. stuff the applicant would have been working on during college or something. Not stuff the applicant was doing on the "side" during his/her previous years of employment. Am I totally wrong here?

Post reply on HN