Functional vs. Object oriented API

[Mitya Sirenef]

On 04/12/2013 10:19 AM, Roy Smith wrote:
> As part of our initial interview screen, we give applicants some small
> coding problems to do.  One of the things we see a lot is what you could
> call "Java code smell".  This is our clue that the person is really a
> Java hacker at heart who just dabbles in Python but isn't really fluent.
> It's kind of like how I can walk into a Spanish restaurant and order
> dinner or enquire where the men's room is, but everybody knows I'm a
> gringo as soon as I open my mouth.
>
> It's not just LongVerboseFunctionNamesInCamelCase().  Nor is it code
> that looks like somebody bought the Gang of Four patterns book and is
> trying to get their money's worth out of the investment.  The real dead
> giveaway is when they write classes which contain a single static method
> and nothing else.
>
> That being said, I've noticed in my own coding, it's far more often that
> I start out writing some functions and later regret not having initially
> made it a class, than the other way around.


I've absolutely noticed the same thing for myself, over and over
again. I can't remember writing a class that I've regretted is not
a few functions, although it must have happened a few times.   -m


-- 
Lark's Tongue Guide to Python: http://lightbird.net/larks/