|
As someone who has had to hired staff, I would say that it won't hurt, however there is a but.
I have never checked anyone's Facebook but I have checked their web presence and sometimes what I saw has put applicants in the 'Not in my lifetime' category.
Published articles could be a positive however too many may raise suspicions on what you are doing at work instead of working.
As a general rule I looked for staff that have diverse interests ( as long as it's not dodgy!) as I prefer balanced people who have a life outside work. I do believe there needs to be more to life then just slaving for a business This creates a happier work environment and thus improves staff retention. This is a benefit to the company because of their company/business knowledge they gain over time.
I do realise however not all employers are like me !
|
|
|
|
|
RossMW wrote: what you are doing at work instead of working
Perhaps some people create their projects/articles outside of work...
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
True. But how is a future employer to know that...
|
|
|
|
|
It helped me, as it showed that I was genuinely interested in IT and that it is not just a job for me but something of a passion.
When I see CV's of new young devs I scan the CV to see if they have done anything outside of their degrees - much of the time there is no sign of this.
I come from a generation where computers were primarily a hobby and any interest in a job in IT was subservient to a passion in IT.
It does seem nowadays, that many of the graduates coming through with computer science degrees(some with firsts, goodness knows what a first means nowadays) show little interest, or aptitude, in IT outside of their course material and what they think will be required to get a job.
So I would say - go for it, write as many good articles as you can.
If the articles get votes on codeproject they will show up on a google search and that can do nothing but help your job prospects.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
One good article wouldn't impress me that much. A history of writing good, high quality, original articles will definitely impress me. One thing to be aware of - when I'm hiring, I just look at CVs, so chances are that I'm not going to have the time to read through a whole series of articles, so try to pick the best ones and highlight them for me.
|
|
|
|
|
It did help me every time I changed a job. On each interview someone would ask me a few questions about an article I wrote. Now, I have no idea how much real weight it brought to the hiring decision, but it was definitely noticed.
Surprisingly, my open source project seemed to impress the interviewers far less than the articles.
|
|
|
|
|
In general, yes but iif the quality of the articles written is good/ reasonable.
I did see one candidate taken off an interview list when his blog was checked out on-line, and his blog seemed to be written by someone who needed to buy themselves a clue.
Alberto Brandolini: The amount of energy necessary to refute bullshit is an order of magnitude bigger than to produce it.
|
|
|
|
|
In my experience, at best it gets you in the door. On the other hand, a few years back it helped me judge a possible future company when the hiring manager complained that he couldn't find my articles. That was about all I needed to know.
|
|
|
|
|
|
So... I've got to beat Rocket Hands to take out more than £50? 
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
"ATMs like this run Windows XP"
I'm just gonna leave this here, and point out your financial details are going through this thing...
Alberto Brandolini: The amount of energy necessary to refute bullshit is an order of magnitude bigger than to produce it.
|
|
|
|
|
Not necessarially, and in fact, highly unlikely.
There will be a sub OS that will deal with security. XP just displays the graphics and handles the non sensitive stuff.
(I work on these kinds of machines by the way).
|
|
|
|
|
"ATMs like this run Windows XP"
Well, except the ones that run Linux.... 
Yes, not a hard hack, they needen't fart around with hardware, just connect a USB keyboard though! 
|
|
|
|
|
Munchies_Matt wrote: Well, except the ones that run Linux.
Man, imagine a Beowulf cluster of those.
Alberto Brandolini: The amount of energy necessary to refute bullshit is an order of magnitude bigger than to produce it.
|
|
|
|
|
Can anyone explain to me a good reason why anyone would use CF outside of "it's just what we know"? Every time I see the phrases "ColdFusion" and "enterprise" tossed in together I can't help but laugh.
Jeremy Falcon
|
|
|
|
|
Yeah, I'm replacing a ColdFusion site at work with a MVC site.
The database also has to be rebuilt from the ground up as the old one is so infested with ColdFusion garbage that it's impossible to adapt it to new requirements without scraping it and rebuilding anyway.
Sooooo the data in about 10 badly designed tables (yes, that's the entire database) is being migrated to a database that now spans 96 tables! I absolutely HATE tables that span 200 to 300 columns!
|
|
|
|
|
Dave Kreskowiak wrote: I absolutely HATE tables that span 200 to 300 columns!
Is this something imposed by CF or just a bad DB? To me when I see crap like "wipes your backside for you" I think of things like FoxPro with its oddities.
Jeremy Falcon
|
|
|
|
|
Both.
The CF code does some weird things with radio buttons and checkboxes. To mark options as selected in the website, it writes a string of character values to a database field, either as a bunch of characters packed together or comma separated.
The real pain in the ass is that these fields are fixed length in the database and there's no room for new options in these lists.
The existing site was written by a bunch of different people at different times and nobody had any clue as to what they were doing with databases.
And now replacing the site has fallen on a friend of mine and myself. We're 18 months into this project and were finally starting to see the light at the end of the tunnel.
|
|
|
|
|
Dave Kreskowiak wrote: We're 18 months into this project and were finally starting to see the light at the end of the tunnel.
Been there, done that. Good luck with it.
Jeremy Falcon
|
|
|
|
|
Dave Kreskowiak wrote: We're 18 months into this project and were finally starting to see the light at the end of the tunnel.
That's just a freight train coming your way.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
I hope not! But, yeah, my partner and I have both thought the same thing at various times during this project.
We go Beta in about another 6 to 8 weeks.
|
|
|
|
|
Dave Kreskowiak wrote: written by a bunch of different people at different times
Power users dontcha love em. The people that keep us in work. Let them kludge a solution together, let it become core to the business and THEN get a professional to rewrite and migrate the data.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Professional?? What professional? Where is this person you speak of?
You are correct as the existing site is the main system used during my teams primary function.
Sadly, migrating the data is what's taking most of the time in this project. I've got a extensible data importer framework built and a bunch of importers interpreting, correcting, filtering, and normalizing the data on-the-fly during import into the new database.
It's also being used to sanity check and test the EF model for the new database during the migration.
There's nothing like tearing down a site that's been built (badly) over the last 10 years and rebuilding it from scratch.
|
|
|
|
|
Dave Kreskowiak wrote: tearing down a site that's been built (badly) over the last 10 years
Thankfully I only do LOB work that does not include web (until Silverlight came along) so I usually have to deal with Access and Excel (used as a database) and the myriad of redundant, duplicated sheets and forms created.
My usual data transform is a bunch of sql scripts that end in truncate everything so I can repeat again and again and again.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: Power users dontcha love em. The people that keep us in work. Let them kludge a solution together, let it become core to the business and THEN get a professional to rewrite and migrate the data.
This is why MS Access needs to burn!!
Jeremy Falcon
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
