|
Coffee maker; dog whining. Not necessarily in that order.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Don't need an alarm clock, dogs and cats are on that. But just in terms of getting the mood up getting your steam on I like Elvis Costello's "This Year's Model". IMO it's one of those rare albums where every track is great. "Pump It Up" however is a shot of pure adrenaline.
|
|
|
|
|
Yeah, that is a good song! 
|
|
|
|
|
I used to wake up to Sonny&Cher, “I got you, babe” but I could never get moving forward with it.
|
|
|
|
|
If I needed to get amped up on the drive in it will be Rush, Boston, Van Halen (not Van Hagar), Robin Trower, etc.
This is a great waker-upper.
https://www.youtube.com/watch?v=jTZHHQplIX8
"Just one more morning, I have to wake up with the blues..."
|
|
|
|
|
|
I've received an email from a prospective employer inviting me to set up a job interview. A note at the end requests a link to my GitHub code repo or sample code/projects prior to the interview.
I don't have a personal GitHub repo or code samples because, unlike probably most here, I no longer do programming as a hobby on my own time. Everything I've done in the last 15 years that the interviewer would be interested in is proprietary code I've written for my current employer, and I don't feel comfortable sharing that outside the company, even though the two industries are not related by any stretch of the imagination, so they wouldn't be able to benefit.
What would you do in this situation? Rewrite some of your code to remove any hints of its purpose or value to your employer? Write new code?
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
TNCaver wrote: unlike probably most here, I no longer do programming as a hobby on my own time
Er hum, cough. never. I only do it if someone is paying. Cant stand bloody computers.
TNCaver wrote: proprietary code I've written for my current employer
You should still keep your own library of code, so you can cut and paste it into new projects, then charge the client full whack for doing sod all.
Use that.
|
|
|
|
|
Munchies_Matt wrote: I only do it if someone is paying
Me too. Coding at home would be like a dentist going home every night and practicing on his family and friends.
I don't deal with clients. I have never worked for a code-for-hire shop (and don't plan to start now). I code for the needs of the company I work for, their web site, their intranet, their windows services, and now, their Salesforce implementation (yuck, and one of many reasons I'm leaving after 17 years here).
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
That is like a truck driver who doesn't own a car but walks to the supermarket and the movie theater. (Which is a good thing to do, but it might take the entire evening to get there.)
|
|
|
|
|
I guess being honest and saying you don't have any non-proprietary code to show them, but that you've spent the last 15 years writing code about 8 hours a day so that you probably know what you're doing, is out of the question? 
I should say I know people who did that too and they are horrible programmers 
|
|
|
|
|
That's probably what I'll end up doing, though. I'm not a horrible programmer, I don't think I would have lasted 30 years in the biz if I wasn't at least decent at it (15 years is just how long I've been doing .NET).
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Unless the potential hire has been self-employed, I think most employers are going to find that there aren't too many people who have any code samples that they can legally show to anyone.
Here's a thought: maybe it's an ethics test. If you actually do show them code that you wrote for your current employer then you fail.
|
|
|
|
|
TNCaver wrote: What would you do in this situation?
Look for a company that appreciates people. If you have 15 years experience then a simple 5 minute conversation should be enough to find out if you know what you claim to know.
It sounds like the company may be too big and has to follow a ton of silly rules and procedures and that may be a glimpse of what it will be like working there.
But, if you are interested, I would just put NA in the fields. If they think that lowers your value then you don't want to work for them anyway.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
011111100010 wrote: Look for a company that appreciates people.
7 years later... (see image - much better)
https://i.stack.imgur.com/GQjxQ.png[^]
Actually took me 15 years and about 7 companies. Did find one though.
|
|
|
|
|
011111100010 wrote: If you have 15 years experience then a simple 5 minute conversation should be enough to find out if you know what you claim to know.
The only problem is that the interview done by HR...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Give them an honest reply: you have worked commercially for 15 years, but do not have a code repository outside of work, and, any product from work is the property of you employer.
If they are willing to discuss your qualifications, you can describe your abilities to them.
Either they appreciate your honesty and forthright attitude or they don't, but at the end of the day, when you look in the mirror, it is your reflection that is staring back.
|
|
|
|
|
I don't do github, but I do have a laptop that I can bring code samples on, plus I refer potential employers here if they want some code I've written.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
This might be a hint that this is not the company for you. I would tell them that you don't code as a hobby anymore and you don't have GitHub code. In my opinion, any quality technical interviewer can ask questions and determine your skill level and if you'd fit into their organization or not. I've been in my current position for 5.5 years and got it during a 1.5 hour interview. Today, the same level position requires a 8 hour test/program/interview. I would not consider my current position if I had to take a day off work for the opportunity for a new position.
|
|
|
|
|
jgakenhe wrote: would not consider my current position if I had to take a day off work for the opportunity for a new position.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
Tell them what you have told us.
If you are really keen on getting the job, you could also suggest that they set you a small project that would take no longer than a day to code then send back the resulting code to them.
I say this because I really dislike coding tests in interviews and have always done really well when I am set something in advance that I can then be questioned about during interview.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
GuyThiebaut wrote: you could also suggest that they set you a small project that would take no longer than a day to code
I like that idea. I'll float it at them and see what happens.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Never been asked that and at best I could point them here.
And definitely don't show code that another employer owns.
|
|
|
|
|
1. Imagine you owned the company you are interviewing for and you're interviewing a programmer.
2. Imagine you knew that the code is a representation of the actual business itself -- via business processes, etc.
3. Imagine that when the developer wrote the code that s/he would own a part of the business itself via owning the business processes it represents.
4. Imagine that the developer could walk out at any time leave behind a mess of business process behind that some other poor unfortunate would have to maintain.
5. Imagine your business might lose time, customers, and/or money because of that.
Now, what questions would you ask? 
|
|
|
|
|
I always try to leave documentation, standards, and well-commented code behind. My purpose isn't job security, it's to make sure that the next programmer does not face the same mess I walked into.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
