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....
I have no side code projects to show
141–148 of 148 posts
Re: I have no side code projects to show
#142I always go through an extreme opposite hiring experience. I'm not on linkedin by choice. Currently I use my SO developer profile as my online resume. But the lack of a linkedin profile and associated connections makes it look like I'm not a professional in the view of certain employers. I have a decent bunch of side projects, and a moderately active github profile and I have gotten all my jobs including my current o…
Can you share some examples?
Re: I have no side code projects to show
#143Earlier quoted context omitted.
I've interned at a multibillion euro company for a couple of years. I have an idea of what it's like.
Lol try having the CTO say when the billing system you look after hits its first 5 mil a month "this had better be right other wise we are both out of a job"
Re: I have no side code projects to show
#144Re: I have no side code projects to show
#145Earlier quoted context omitted.
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.
but it means little when dealing with crazy.
Re: I have no side code projects to show
#146Re: I have no side code projects to show
#147Earlier quoted context omitted.
So if you have any other interests, such as rebuilding old cars, would that boss still have a problem with it? That is the thing I don't get, is how some companies see a big difference between regular hobbies and programing related hobbies.
[Google owns any IP you develop, even on your own time]( http://startups.stackexchange.com/questions/7822/working-leg... ), and you can't easily work on those interview-worthy side projects after you get hired.
Re: I have no side code projects to show
#148Earlier quoted context omitted.
[Google owns any IP you develop, even on your own time]( http://startups.stackexchange.com/questions/7822/working-leg... ), and you can't easily work on those interview-worthy side projects after you get hired.
This clause is illegal in many states. It definitively is in Wisconsin where I live, and I thought for sure it was illegal in California.
"For example, the California Labor Code stipulates that regardless of what an employment contract or PIIA says, an employee owns the copyright and patent rights to his inventions if the invention is made entirely on the employee’s own time, without using any of the company’s equipment or technology, as long as the invention (a) does not relate to the company’s business, or (b) did not result from work performed by the employee “as an employee” of the company. Washington state has a similar law protecting employee projects outside the 9-5 bounds."