-MarkM-
Topic: web developers check this (Read 815 times)
So not a lot of experience with brown, then?
-MarkM-
-MarkM-
Quote
Interviewer: OK, one more thing for today. We're using Rock 5.1 to bang nails with. Have you used Rock 5.1?
Carpenter: [Turning white...] Well, I know a lot of carpenters are starting to use rocks to bang nails with since Craftsman bought a quarry, but you know, to be honest I've had more luck with my nailgun. Or a hammer, for that matter. I find I hit my fingers too much with the rock, and my other hand hurts because the rock is so big.
Interviewer: But other companies are using rocks. Are you saying rocks don't work?
Carpenter: No, I'm not saying rocks don't work, exactly, it's just that I think nail guns work better.
Interviewer: Well, our architects have all started using rocks, and they like it.
Carpenter: Well, sure they do, but I bang nails all day, and -- well, look, I need the work, so I'm definitely willing to use rocks if you want. I try to keep an open mind.
one more thing...if you're insinuating what it seems, then consider that what you call 'rock 5.1' is actually a standard that i've watched develop for the past 11 years since xmlhttprequest was first introduced! i was doing xml/xsl right in the browser with full xml based web services long before the terms ajax or rest were even a thought in someone's head! i was probably coding javascript before you knew what an array was, and i've coded on unix, linux, windows and using dozens of languages, from c++ to masm/tasm, perl, python, c#, visual basic, even 'cut my professional teeth' with ibm system/36 (not 360) with cobol, rpg, etc, and with almost every database imaginable and on sizes i'm confident you've never even seen (e.g. smallest datasets measured in tens of gigabytes) but what's happening on the web is unique and if you're thinking of the technology blend i mentioned as the latest 'rocks 5.1' then you are obviously in for a nice wake up call
Quote
NEXT DAY:
Ring...
Interviewer: Hello?
Carpenter: Hello. Remember me, I'm the carpenter you interviewed for the black walnut job. Just wanted to touch base to see if you've made a decision.
Interviewer: Actually, we have. We liked your experience overall, but we decided to go with someone who has done a lot of work with brown.
Carpenter: Really, is that it? So I lost the job because I didn't have enough brown?
Interviewer: Well, it was partly that, but partly we got the other fellow a lot cheaper.
Carpenter: Really -- how much experience does he have?
Interviewer: Well, he's not really a carpenter, he's a car salesman -- but he's sold a lot of brown cars and he's worked with walnut interiors.
Carpenter: [click]
i know you probably think you just made a brilliant observation...kudos to you!
Quote
If Carpenters Were Hired Like Programmers
The following joke was posted to an internal Magenic list. I don't know who actually wrote it, and I'll give credit if someone points out the creator of the joke. It perfectly illustrates what I think developers (especially consultants) have to go through all the time when they're interviewing for the next gig.
Interviewer: So, you're a carpenter, are you?
Carpenter: That's right, that's what I do.
Interviewer: How long have you been doing it?
Carpenter: Ten years.
Interviewer: Great, that's good. Now, I have a few technical questions to ask you to see if you're a fit for our team. OK?
Carpenter: Sure, that'd be fine.
Interviewer: First of all, we're working in a subdivision building a lot of brown houses. Have you built a lot of brown houses before?
Carpenter: Well, I'm a carpenter, so I build houses, and people pretty much paint them the way they want.
Interviewer: Yes, I understand that, but can you give me an idea of how much experience you have with brown? Roughly.
Carpenter: Gosh, I really don't know. Once they're built I don't care what color they get painted. Maybe six months?
Interviewer: Six months? Well, we were looking for someone with a lot more brown experience, but let me ask you some more questions.
Carpenter: Well, OK, but paint is paint, you know.
Interviewer: Yes, well. What about walnut?
Carpenter: What about it?
Interviewer: Have you worked much with walnut?
Carpenter: Sure, walnut, pine, oak, mahogony -- you name it.
Interviewer: But how many years of walnut do you have?
Carpenter: Gosh, I really don't know -- was I supposed to be counting the walnut?
Interviewer: Well, estimate for me.
Carpenter: OK, I'd say I have a year and a half of walnut.
Interviewer: Would you say you're an entry level walnut guy or a walnut guru?
Carpenter: A walnut guru? What's a walnut guru? Sure, I've used walnut.
Interviewer: But you're not a walnut guru?
Carpenter: Well, I'm a carpenter, so I've worked with all kinds of wood, you know, and there are some differences, but I think if you're a good carpenter ...
Interviewer: Yes, yes, but we're using Walnut, is that OK?
Carpenter: Walnut is fine! Whatever you want. I'm a carpenter.
Interviewer: What about black walnut?
Carpenter: What about it?
Interviewer: Well we've had some walnut carpenters in here, but come to find out they weren't black walnut carpenters. Do you have black walnut experience?
Carpenter: Sure, a little. It'd be good to have more for my resume, I suppose.
Interviewer: OK. Hang on let me check off the box...
Carpenter: Go right ahead.
Interviewer: OK, one more thing for today. We're using Rock 5.1 to bang nails with. Have you used Rock 5.1?
Carpenter: [Turning white...] Well, I know a lot of carpenters are starting to use rocks to bang nails with since Craftsman bought a quarry, but you know, to be honest I've had more luck with my nailgun. Or a hammer, for that matter. I find I hit my fingers too much with the rock, and my other hand hurts because the rock is so big.
Interviewer: But other companies are using rocks. Are you saying rocks don't work?
Carpenter: No, I'm not saying rocks don't work, exactly, it's just that I think nail guns work better.
Interviewer: Well, our architects have all started using rocks, and they like it.
Carpenter: Well, sure they do, but I bang nails all day, and -- well, look, I need the work, so I'm definitely willing to use rocks if you want. I try to keep an open mind.
Interviewer: OK, well we have a few other candidates we're looking at, so we'll let you know.
Carpenter: Well, thanks for your time. I enjoyed meeting you.
NEXT DAY:
Ring...
Interviewer: Hello?
Carpenter: Hello. Remember me, I'm the carpenter you interviewed for the black walnut job. Just wanted to touch base to see if you've made a decision.
Interviewer: Actually, we have. We liked your experience overall, but we decided to go with someone who has done a lot of work with brown.
Carpenter: Really, is that it? So I lost the job because I didn't have enough brown?
Interviewer: Well, it was partly that, but partly we got the other fellow a lot cheaper.
Carpenter: Really -- how much experience does he have?
Interviewer: Well, he's not really a carpenter, he's a car salesman -- but he's sold a lot of brown cars and he's worked with walnut interiors.
Carpenter: [click]
The following joke was posted to an internal Magenic list. I don't know who actually wrote it, and I'll give credit if someone points out the creator of the joke. It perfectly illustrates what I think developers (especially consultants) have to go through all the time when they're interviewing for the next gig.
Interviewer: So, you're a carpenter, are you?
Carpenter: That's right, that's what I do.
Interviewer: How long have you been doing it?
Carpenter: Ten years.
Interviewer: Great, that's good. Now, I have a few technical questions to ask you to see if you're a fit for our team. OK?
Carpenter: Sure, that'd be fine.
Interviewer: First of all, we're working in a subdivision building a lot of brown houses. Have you built a lot of brown houses before?
Carpenter: Well, I'm a carpenter, so I build houses, and people pretty much paint them the way they want.
Interviewer: Yes, I understand that, but can you give me an idea of how much experience you have with brown? Roughly.
Carpenter: Gosh, I really don't know. Once they're built I don't care what color they get painted. Maybe six months?
Interviewer: Six months? Well, we were looking for someone with a lot more brown experience, but let me ask you some more questions.
Carpenter: Well, OK, but paint is paint, you know.
Interviewer: Yes, well. What about walnut?
Carpenter: What about it?
Interviewer: Have you worked much with walnut?
Carpenter: Sure, walnut, pine, oak, mahogony -- you name it.
Interviewer: But how many years of walnut do you have?
Carpenter: Gosh, I really don't know -- was I supposed to be counting the walnut?
Interviewer: Well, estimate for me.
Carpenter: OK, I'd say I have a year and a half of walnut.
Interviewer: Would you say you're an entry level walnut guy or a walnut guru?
Carpenter: A walnut guru? What's a walnut guru? Sure, I've used walnut.
Interviewer: But you're not a walnut guru?
Carpenter: Well, I'm a carpenter, so I've worked with all kinds of wood, you know, and there are some differences, but I think if you're a good carpenter ...
Interviewer: Yes, yes, but we're using Walnut, is that OK?
Carpenter: Walnut is fine! Whatever you want. I'm a carpenter.
Interviewer: What about black walnut?
Carpenter: What about it?
Interviewer: Well we've had some walnut carpenters in here, but come to find out they weren't black walnut carpenters. Do you have black walnut experience?
Carpenter: Sure, a little. It'd be good to have more for my resume, I suppose.
Interviewer: OK. Hang on let me check off the box...
Carpenter: Go right ahead.
Interviewer: OK, one more thing for today. We're using Rock 5.1 to bang nails with. Have you used Rock 5.1?
Carpenter: [Turning white...] Well, I know a lot of carpenters are starting to use rocks to bang nails with since Craftsman bought a quarry, but you know, to be honest I've had more luck with my nailgun. Or a hammer, for that matter. I find I hit my fingers too much with the rock, and my other hand hurts because the rock is so big.
Interviewer: But other companies are using rocks. Are you saying rocks don't work?
Carpenter: No, I'm not saying rocks don't work, exactly, it's just that I think nail guns work better.
Interviewer: Well, our architects have all started using rocks, and they like it.
Carpenter: Well, sure they do, but I bang nails all day, and -- well, look, I need the work, so I'm definitely willing to use rocks if you want. I try to keep an open mind.
Interviewer: OK, well we have a few other candidates we're looking at, so we'll let you know.
Carpenter: Well, thanks for your time. I enjoyed meeting you.
NEXT DAY:
Ring...
Interviewer: Hello?
Carpenter: Hello. Remember me, I'm the carpenter you interviewed for the black walnut job. Just wanted to touch base to see if you've made a decision.
Interviewer: Actually, we have. We liked your experience overall, but we decided to go with someone who has done a lot of work with brown.
Carpenter: Really, is that it? So I lost the job because I didn't have enough brown?
Interviewer: Well, it was partly that, but partly we got the other fellow a lot cheaper.
Carpenter: Really -- how much experience does he have?
Interviewer: Well, he's not really a carpenter, he's a car salesman -- but he's sold a lot of brown cars and he's worked with walnut interiors.
Carpenter: [click]
watching. I will tell my developer friends.
i am working on a new project that is currently in alpha. however, i anticipate releasing into beta within 1-2 weeks. i have some of the code staged to github, and have started a wiki (note: half those that read the wiki tell me it makes no sense, and half tell me it's great!)
in any case, i am currently working on implementing this platform on GAE, but am actively working to deploy a range of services across aws, azure and gae with full, open builds, everything for all three platforms.
i started this project in january, and will take me until end of year to complete across all three platforms. i have the technical skill to complete project on time, myself.
however, at least two developers have expressed a very strong desire to be involved, and the more that get involved, the quicker this thing can grow legs.
what's also great is this is especially for you if you love web 2.0, oauth, social software, and html5 development as opposed to having to download and install every freakin' alt-chain that comes along...
At the end of the year, there will be enterprise class implementations of full suite of shaman server classes
with any additional help, we'll be able to generate dozens or maybe even hundreds of apps on this platform during the year's development
current skill-sets immediately helpful:
server-side: Translation, jinga templating (to help with translation template/i18n file mappings, etc), python, ndb, experience with oauth
client-side: jquery, standard dhtml and html5, canvas, three.js, any other skills helpful to build engaging apps (e.g. json, yui, etc)
https://shaman-labz.appspot.com/
and the wiki
https://github.com/shamaniotas/yotagem/wiki
so if you see value of mining in the browser, understand the transactional limitations of bitcoin network, don't believe in centralization (but also understand fully-mirrored primitive p2p is not the answer), comprehend the value of micro (and sub-micro) economics and transactions, then maybe you'll be interested to watch how this evolves over the next year, or even get involved!
note: i have taken a complete leave of work for the next year to dedicate my life to this project. regardless of win or lose, this ship is going to float, and all her flags will be flyin' by the end of this year. this may seem crazy, and it is crazy enough that it just might work!
in any case, i am currently working on implementing this platform on GAE, but am actively working to deploy a range of services across aws, azure and gae with full, open builds, everything for all three platforms.
i started this project in january, and will take me until end of year to complete across all three platforms. i have the technical skill to complete project on time, myself.
however, at least two developers have expressed a very strong desire to be involved, and the more that get involved, the quicker this thing can grow legs.
what's also great is this is especially for you if you love web 2.0, oauth, social software, and html5 development as opposed to having to download and install every freakin' alt-chain that comes along...
At the end of the year, there will be enterprise class implementations of full suite of shaman server classes
with any additional help, we'll be able to generate dozens or maybe even hundreds of apps on this platform during the year's development
current skill-sets immediately helpful:
server-side: Translation, jinga templating (to help with translation template/i18n file mappings, etc), python, ndb, experience with oauth
client-side: jquery, standard dhtml and html5, canvas, three.js, any other skills helpful to build engaging apps (e.g. json, yui, etc)
https://shaman-labz.appspot.com/
and the wiki
https://github.com/shamaniotas/yotagem/wiki
so if you see value of mining in the browser, understand the transactional limitations of bitcoin network, don't believe in centralization (but also understand fully-mirrored primitive p2p is not the answer), comprehend the value of micro (and sub-micro) economics and transactions, then maybe you'll be interested to watch how this evolves over the next year, or even get involved!
note: i have taken a complete leave of work for the next year to dedicate my life to this project. regardless of win or lose, this ship is going to float, and all her flags will be flyin' by the end of this year. this may seem crazy, and it is crazy enough that it just might work!
Jump to: