Would you like to translate it?
the internet is so weird
02:19 < Alystair> anyone here know someone passionate about colognes and perfume
02:20 < rojisan_roaming> wouldn't go that far, but i cooked up a scent for a
dance tour several years ago
02:25 < Alystair> you made your own cologne?
02:25 < rojisan_roaming> no, it was a custom scent. never made it to a cologne
02:26 < rojisan_roaming> worked with a chemist in pennsylvania
02:32 < japherwocky> for a dance tour?
02:35 < rojisan_roaming> moichandize
wherein your users push the movey parts
and every pixel matters!
great designs over at http://www.graphicpeel.com/ his style meshes well with Supermailer's UI concept: playskoolWhat a helpful error message
This is the gem you get when you try to run Windows 7 without enough RAM.
Why I use Python
There's an article about the difference between "blocks" and "lambdas"
over here: http://github.com/raganwald/homoiconic/blob/master/2010/04/blocks.md (Anecdotally, the kind of people with the mindset that care about that
seem to prefer Ruby.) It's a good excersize to analyze the hell out of a little code snippet
and find the ultimate most elegant solution. Especially for students!
Every competent programmer should be able to do that, and practicing
it a few times will make you a better programmer. That article exemplifies pretty well why I prefer Python to Ruby. In
Python you wouldn't write an "anonymous" block of code, you'd write a
"named" function. In practice, I don't think you need to know what
that means to write useful code. It's academic; I'm glad that someone
is thinking about this, just as I'm glad that it's not me. """
And thus endeth the lesson: An important use case for blocks is when
you want to write methods that emulate control structures and other
syntax. In this case, you want blocks of statement that do not alter
the behaviour of things like return. Blocks work. Functions and
lambdas do not.
""" Since he started from an example in javascript, (which does not have
blocks) I think it would be more accurate to say that functions and
lambdas (lambdas are "anonymous" functions, btw) work but in a less
elegant way, where elegant generally means "using less code".
over here: http://github.com/raganwald/homoiconic/blob/master/2010/04/blocks.md (Anecdotally, the kind of people with the mindset that care about that
seem to prefer Ruby.) It's a good excersize to analyze the hell out of a little code snippet
and find the ultimate most elegant solution. Especially for students!
Every competent programmer should be able to do that, and practicing
it a few times will make you a better programmer. That article exemplifies pretty well why I prefer Python to Ruby. In
Python you wouldn't write an "anonymous" block of code, you'd write a
"named" function. In practice, I don't think you need to know what
that means to write useful code. It's academic; I'm glad that someone
is thinking about this, just as I'm glad that it's not me. """
And thus endeth the lesson: An important use case for blocks is when
you want to write methods that emulate control structures and other
syntax. In this case, you want blocks of statement that do not alter
the behaviour of things like return. Blocks work. Functions and
lambdas do not.
""" Since he started from an example in javascript, (which does not have
blocks) I think it would be more accurate to say that functions and
lambdas (lambdas are "anonymous" functions, btw) work but in a less
elegant way, where elegant generally means "using less code".
unicorns and the asshole tax
I had an interesting chat last night with a pair of guys who run a
local computer service shop. Business was awful, they had shut down their offices and moved into
their homes last fall.. but now business is booming, they've even
hired an employee. I asked them what the magic bullet was. The owner actually thought for a second and pointed at his partner,
and basically said, "well we stopped doing things for free." For some reason, people in software don't seem to understand this.
Clients want everything, and they want it for free. They are
completely insane, and probably have no real concept of what they're
asking for. Sometimes you have to say, "No, you're paying this much,
I need to eat, this is what we can do." Or, when they say, "I want this and this and this", reply, "Well, I
want a unicorn. And I want it to shoot lasers out of it's eyes." There is a related principle known as the asshole tax, which is a good
rule of thumb for quoting prices: the more of an asshole it seems
like the client is going to be, the higher the price you should be
charging.
local computer service shop. Business was awful, they had shut down their offices and moved into
their homes last fall.. but now business is booming, they've even
hired an employee. I asked them what the magic bullet was. The owner actually thought for a second and pointed at his partner,
and basically said, "well we stopped doing things for free." For some reason, people in software don't seem to understand this.
Clients want everything, and they want it for free. They are
completely insane, and probably have no real concept of what they're
asking for. Sometimes you have to say, "No, you're paying this much,
I need to eat, this is what we can do." Or, when they say, "I want this and this and this", reply, "Well, I
want a unicorn. And I want it to shoot lasers out of it's eyes." There is a related principle known as the asshole tax, which is a good
rule of thumb for quoting prices: the more of an asshole it seems
like the client is going to be, the higher the price you should be
charging.
just spent 20 minutes searching for this link
why on earth didn't I put this on here in the first place? http://www.nytimes.com/2010/02/18/garden/18aqua.html?8dpc gardening is in the air! j
