(http://www.bonkersworld.net/images/2011.11.15_life_of_a_swe.png)
source: http://www.bonkersworld.net/cost-of-motorola/
That's about it haha
You go to build utopia and end up with several civilizations built on top of each other
And also!
(http://www.bonkersworld.net/images/2013.03.12_one_last_time.png)
source: http://www.bonkersworld.net/one-last-time/
BAM so true
"just one more thing"
No kidding.
http://i.stack.imgur.com/PJw3h.png
(http://i.stack.imgur.com/PJw3h.png)
Hah!
That's hilarious that they did it in Minecraft :)
Ah, good ol' software engineer hiring practices, "We need X, you don't have X, we can't hire you":
(http://ffn.nodwick.com/ffnstrips/2013-07-30.png)
source: http://ffn.nodwick.com/?p=1198
Heh, it's crazy looking at the laundry lists of "requirements" most companies spray out there for skills. And they'll spend months looking for that perfect applicant that has all the skills on their shopping list rather than just getting someone with a brain that can learn.
Actually thinking about it this is only breeding people who can successfully bluff their interviews better, they may apply for a job with 25 skill requirements and be deficient in the ones actually needed and proficient in the "nice to have" category, if they aren't quick learners they'll get swamped, if they are they can train themselves while working.
This leads to parties full of Rogues with surprisingly high CHA!
"Yeah, I'm a wizard" /roll d20+15 bluff
Having had to do hiring, I somewhat like our job posing format, it contains a laundry list of core skills you should have most of but then a section called something like.. To excel you will need these skills. Those are the special skill I am looking for, I just screen resumes based on how many applicants have. There is no end to applicants that have the generic skills.
I hate applicants that attempt to bluff... You can do that all you want in the fist part of the interview that includes the human skills questions but when you go through the list of things I absolutely expect you to know based on your resume, do not BS. There are good explanations for not knowing some of the answers, but if you give me a wrong answer with confidence your are done.
I hate working with people who bluffed their way through interviews, it's happened a few times now over my career.
The worst being my first experience of working with someone who claimed to know ASP in and out and turned out to know less about web dev than me, so I had to learn it, and then they left because they weren't happy with the extremely low salary they agreed to work.
Quote from: Mr. Analog on July 30, 2013, 04:44:04 PM
I hate working with people who bluffed their way through interviews, it's happened a few times now over my career.
The worst being my first experience of working with someone who claimed to know ASP in and out and turned out to know less about web dev than me, so I had to learn it, and then they left because they weren't happy with the extremely low salary they agreed to work.
I have some remarkably easy questions on my interview list (it really isn't intended to grill anyone) and I am AMAZED at how poorly some applicants answer.
Quote from: Lazybones on July 30, 2013, 05:08:41 PM
Quote from: Mr. Analog on July 30, 2013, 04:44:04 PM
I hate working with people who bluffed their way through interviews, it's happened a few times now over my career.
The worst being my first experience of working with someone who claimed to know ASP in and out and turned out to know less about web dev than me, so I had to learn it, and then they left because they weren't happy with the extremely low salary they agreed to work.
I have some remarkably easy questions on my interview list (it really isn't intended to grill anyone) and I am AMAZED at how poorly some applicants answer.
I can believe it!
Quote from: Mr. Analog on July 30, 2013, 04:44:04 PM
I hate working with people who bluffed their way through interviews, it's happened a few times now over my career.
The worst being my first experience of working with someone who claimed to know ASP in and out and turned out to know less about web dev than me, so I had to learn it, and then they left because they weren't happy with the extremely low salary they agreed to work.
...but enough about UPSIDE:: THE EARLY YEARS ;)
Quote from: Mr. Analog on July 30, 2013, 04:13:06 PM
Heh, it's crazy looking at the laundry lists of "requirements" most companies spray out there for skills. And they'll spend months looking for that perfect applicant that has all the skills on their shopping list rather than just getting someone with a brain that can learn.
Comes to mind a bit of dialog in "Odyssey 5" ep I watched this weekend; a guy is preparing for a NASA exam (early stages) and he's pre-planning a 500 word essay on "why I want to be an astronaut". Other guy points out that maybe they're looking for more "think on your feet" type of folks, suggests it'll be more like "come up with 100 uses for duct tape". THERE is the difference between a programmer and a developer ;) it's like "solve the problem based on all the fixes you've memorized" vs "solve this weird problem that nobody else has ever encountered, based on a bunched of known variables as well as the possibility of a bunch of unknown unknowns as well" (the latter has been my work life the past 3 weeks, tbh).
I think all of us on here that have written code have had to deal with an unknown bunch of unknowns before.
It's only greenfield development in the first ten minutes of writing code; after that it all becomes maintenance programming.
Quote from: Thorin on August 04, 2013, 06:57:09 PM
I think all of us on here that have written code have had to deal with an unknown bunch of unknowns before.
It's only greenfield development in the first ten minutes of writing code; after that it all becomes maintenance programming.
Especially when the requirements change every week/day/hour.
Quote from: Tom on August 04, 2013, 07:15:46 PM
Quote from: Thorin on August 04, 2013, 06:57:09 PM
I think all of us on here that have written code have had to deal with an unknown bunch of unknowns before.
It's only greenfield development in the first ten minutes of writing code; after that it all becomes maintenance programming.
Especially when the requirements change every week/day.
Weird way you spelled 'hour'. ;)
Quote from: Darren Dirt on August 04, 2013, 07:57:37 PM
Quote from: Tom on August 04, 2013, 07:15:46 PM
Quote from: Thorin on August 04, 2013, 06:57:09 PM
I think all of us on here that have written code have had to deal with an unknown bunch of unknowns before.
It's only greenfield development in the first ten minutes of writing code; after that it all becomes maintenance programming.
Especially when the requirements change every week/day.
Weird way you spelled 'hour'. ;)
I'm not sure what you're talking about. ;)
http://www.buzzfeed.com/lukelewis/28-things-only-developers-will-find-funny
#4 = could be a warning to women what they're getting into a relationship with...
unrelated link that I think is pretty fascinating:Spoiler
http://www.sadanduseless.com/2011/03/world-in-2000/