|
Regardless of whether it's real or fake, big budget or not, both videos look and sound pretty impressive.
My plan is to live forever ... so far so good
|
|
|
|
|
Very true!
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
I'm doing a phone interview tomorrow with the lead tech guy and he, and I quote:
"wants to make sure that your strategies align more with Ruby best practices as opposed to a more traditionally .NET approach."
Now, what exactly does that mean? From my experience, Ruby developers have piss poor practices, but I really wonder Ruby brings to the table in terms of practices that are somehow different from "traditional" .NET approaches.
All I can think of is leveraging features like mixins that promote bad OO practices.
Anyone have a clue?
More generally, would you say that [Java / C / PHP / F# / etc.] has best practices that distinguish it from "traditional .NET" development?
Marc
|
|
|
|
|
They try to make things sound better by calling them "best" when they're not even good.
|
|
|
|
|
Let me rephrase for you; "Once you do things my way you will be following best practices"
My plan is to live forever ... so far so good
|
|
|
|
|
PIEBALDconsult wrote: They try to make things sound better by calling them "best" when they're not even good.
Yup. I've definitely encountered that in the Ruby camp.
Marc
|
|
|
|
|
Um... Testing... Testing...
Seriously. Many Ruby wallahs think that .NET guys don't do enough testing. That sounds like something someone would refer to as "best practices".
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: Many Ruby wallahs think that .NET guys don't do enough testing.
I suspect that is it, but I can't help wondering what else he might mean. I think the first thing I will do is fire back the question "What is your perception of .NET practices?" Might lead to an interesting conversation, or at least a revealing one.
Marc
|
|
|
|
|
Marc Clifton wrote: "What is your perception of .NET practices? I mean, I've been places where I don't think they do enough testing, but most places aren't too bad." As Lotrice will tell you, you've gotta get a good punch in first.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I can think of 3 points:
1. Using the strength of the language/environment (what is it for Ruby?)
2. Using common 'best-practices' - but why that should be different between Ruby and other languages?
3. The actual look-and-feel of your code - and I mean that your code is not write-only, and can be used in a group too...
In any way such a question would - in most cases at least - turn me hot...It sounds me like a 'tech' guy who didn't got over the slogans and buzzwords of the subject...
If you want the job, beware! Do not make him fool!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: If you want the job, beware! Do not make him fool!
Very good advice.
Marc
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: 1. Using the strength of the language/environment (what is it for Ruby?) 2. Using common 'best-practices' - but why that should be different between Ruby and other languages?
Not sure. I could see someone objecting to trying to write C# like Java or vice versa; but C# and Ruby are different enough that I don't see how you could abuse one into looking like the other.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
I am guessing he is either:
- talking about building up classes using Ruby's strengths and understanding how to apply duck typing in the best ways, or
- talking out of his arse.
veni bibi saltavi
|
|
|
|
|
FYI, these posts ended up in the Moderation Queue and I passed them through.
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
Why? What? How?
veni bibi saltavi
|
|
|
|
|
Not sure. Perhaps the filter confused the word 'duck' with something else
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
"arse" is a naughty word.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
So why didn't your message go into the queue?
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
'Cause even the server knows that it's a waste of time trying to make me behave.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
SoMad wrote: Perhaps the filter confused the word 'duck' with something else
Well, in my opinion, any conversation on duck-typing should be moderated!
Marc
|
|
|
|
|
But wait a second. Didn't you write an article about that not too long ago? I remember reading it.
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
|
Sure. BTW, there are currently 2 posts from Kornfeld in the Moderation Queue.
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
It's OK I'm getting used to it in the last two days...and I not even use words like a*se and d*ck...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Hmmm. My reply to this went straight to the queue.
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|