31–40 of 123 posts
I grabbed this article and replaced: - "carpenter" with "data scientist" - "brown" with "machine learning" - "walnut" with "AI" and - "rock" with "Kubernetes" It was perfectly up to date regarding my neck of the woods :) (edit: formatting)
I'd like to know what you replaced "nail gun" or "hammer" with.
I grabbed this article and replaced: - "carpenter" with "data scientist" - "brown" with "machine learning" - "walnut" with "AI" and - "rock" with "Kubernetes" It was perfectly up to date regarding my neck of the woods :) (edit: formatting)
lynx --dump http://www.jasonbock.net/jb/News/Item/7c334037d1a9437d9fa6506e2f35eaac 2>/dev/null | nl | head -102 | tail -98 | sed -e 's/[Cc]arpenter/data scientist/g;s/[Bb]rown/ML/g;s/[Ww]alnut/AI/g;s/[Rr]ock/Kubernetes/g'
The last part, esp.
NEXT DAY:
Ring...
Interviewer: Hello?
data scientist: Hello. Remember me, I'm the data scientist you interviewed for the black AI 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 ML.
data scientist: Really, is that it? So I lost the job because I didn't have enough ML?
Interviewer: Well, it was partly that, but partly we got the other fellow a lot cheaper.
data scientist: Really -- how much experience does he have?
Interviewer: Well, he's not really a data scientist, he's a car salesman -- but he's sold a lot of ML cars and he's worked with AI interiors.
data scientist: [click]At my company: Inteviewer: So you are a carpenter? Carpenter: Yes. Inteviewer: Can you make a start fixing that leaky roof over there? We will monitor your skills and might hire you. Carpenter: Done.
It makes a difference if a person has 5 years java experience or 5 years php experience only. There is a lot to learn about culture, tools, frameworks etc.
Software is software. The paradigms are the same. The languages have the same roots. What is culture for a programming language anyways? Sure, the tools and frameworks are different, and every language has it's own quirks and uniqueness but they're not as different as you make it sound. If a developer is skilled, these are small differences.
A novice PHP developer will (or at least would have 5 years ago) create a messy script with interspersed HTML and PHP, a SQL injection vulnerability or two, and little code organization.
A novice Java developer will implement a bunch of patterns they don't understand (probably misusing them), and write a mess of code with too many side-effects.
An experienced developer can write good code in either language, and many of the patterns will end up looking similar.
It makes a difference if a person has 5 years java experience or 5 years php experience only. There is a lot to learn about culture, tools, frameworks etc.
But the more collaborative your environment is, the more the trivia doesn't matter. I often work on pair-programming teams, and in that context I mainly care about deep skills.
At my company: Inteviewer: So you are a carpenter? Carpenter: Yes. Inteviewer: Can you make a start fixing that leaky roof over there? We will monitor your skills and might hire you. Carpenter: Done.
So you always have leaky roofs at your company? And if you don't like what he did, you just keep the repairs? Sorry for being picky, but you could've used "make a dog house" or something like that. I hope you don't put patches from interviewees in production code.
Earlier quoted context omitted.
Software is software. The paradigms are the same. The languages have the same roots. What is culture for a programming language anyways? Sure, the tools and frameworks are different, and every language has it's own quirks and uniqueness but they're not as different as you make it sound. If a developer is skilled, these are small differences.
> The paradigms are the same So Clojure, Java, Javascript, Haskell and Ruby are all basically the same? I think damage can be done hammering different languages into the same methodologies.. > If a developer is skilled You suggest skill is generic. If a programmer is smart they can learn new paradigms. Projecting the paradigms they are used to onto new domains can produce problems, least of all the standardisation.
Basically, yes. You learn to think how, the rest is implementation. Don't get me wrong, it's not an immediate switch, it takes learning and time, but deep inside, the are the same indeed.
Hiring a good carpenter is probably way easier than hiring a good programmer. Carpeting is just more tangible, I think.
At my company: Inteviewer: So you are a carpenter? Carpenter: Yes. Inteviewer: Can you make a start fixing that leaky roof over there? We will monitor your skills and might hire you. Carpenter: Done.
So you always have leaky roofs at your company? And if you don't like what he did, you just keep the repairs? Sorry for being picky, but you could've used "make a dog house" or something like that. I hope you don't put patches from interviewees in production code.