What would you do if your client required you not to use object-oriented programming?

Question

I am writing a program to simulate the activity of ants in a grid (PDF). The ant can move around, pick up things and drop things.

The problem is while the action of the ants and the positions of each ant can be tracked by class attributes easily (and we can easily create many instances of such ants) my client said that since he has a background in functional programming he would like the simulation to be made using functional programming.

To be clear, the original words from the client is "no class" only, but not "functional programming". So I assume he doesn't mean functional programming and I can do it imperatively. Additionally, I have no prior experience in functional programming.

However, I think it's beneficial to focus on this question being particularly about a functional programming requirement than just simply "do it imperatively."

How would you handle this situation? Would you try to persuade your client that using object-oriented programming is much cleaner, try to follow what he required and give him poor-quality code, or do something else?

Answer 1

Object-oriented code is not by definition cleaner, and conversely non-OO code is not by definition crappy. While there does seem to be a rather obvious object-oriented mapping to this particular problem, I would suggest that you try the functional programming approach anyway. Give it your best shot, try to solve the problem in the best functional programming style that you can muster, and you might just learn something you didn't expect.

Answer 2

You mention that the client used to program in a functional language, maybe he has a reason that he requires you to write the code in a functional style. You should ask him why.

Maybe he intends to keep the code and maintain it himself later.

Moreover, I don't think the two choices are either do it OO-style or write crappy code like you mentioned. Sure writing functional code in an example like this could be harder, especially if you only have experience in object oriented languages, but if the client is willing to wait a bit longer for you to get up to speed with the functional style then it wouldn't hurt to ask him that.

I would ask him why he wants the code in functional style and if time isn't so much of an issue I would ask for some extra days to get up to speed with functional programming. (hurray for getting paid to learn!)

If all else fails explain that it would take you much less time to do it in a OO style.

Answer 3

Are you aware that functional programming doesn't just mean "programming without classes"?

See the Wikipedia article about it for the full schtick, but in short...

In computer science, functional programming is a programming paradigm that treats computation as the evaluation of mathematical functions and avoids state and mutable data. It emphasizes the application of functions, in contrast to the imperative programming style, which emphasizes changes in state.

Functional programming is a programming paradigm, just like OO is a programming paradigm.

If your background is in OO, then I can see how you'd want all your ants to be objects. On the other hand, if you're simulating an ant farm with millions of ants, OO and message-passing may become inefficient.

Luckily for you, Python has excellent tools for functional programming (the most important one being that functions are first-class objects.)

Python functional programming HOWTO

Answer 4

Explain to your client that if he wants functional programming, he should hire someone who specializes in that. Functional programming is very different from OOP, and you will be mistaken if you think you can easily pick it up and deliver a complex solution of high quality.

Answer 5

There is a common misconception that "OO" is completely contrary to "functional". These things can go hand-in-hand very well. In your example, I guess an "Ant" can be modeled well as an abstract data type, which can be straight forward implemented using classes and objects. Transitions between "Ant states" can be naturally modeled using functions, which will lead you to a functional approach as far as your "Ant" class is an immutable type.

And be aware that "objects" can be interchanged by the functional concept of a closure, since objects are the poor man's closures are the poor man's objects are the ... ;-):

https://stackoverflow.com/questions/2497801/closures-are-poor-mans-objects-and-vice-versa-what-does-this-mean

https://stackoverflow.com/questions/501023/closures-and-objects

Answer 6

After talking it over with the client, if he still wants it his way, you either do a professional job, or if you can't then you either don't take the contract or find some way out of it.

Producing "crappy code" just because you disagree would be highly unprofessional.

Answer 7

1. Why are we all assuming the client knows the difference between functional and imperative programming? A lot of people don't know the names or specifics of non OO programming paradigms and will readily interchange terms like "procedural" "imperative" and "functional".

2. Do not walk how others tell you to walk unless you believe you should walk that way. Therefore if you don't believe functional programming is suitable then don't set yourself up to fail or take on a project half-heartedly.

3. If the client writes the spec then implement the spec, otherwise you write the spec and implement your spec.

4. The best strategy to influence clients' decisions is to make the undesirable option significantly more expensive. It works everytime.

5. If you are the expert (relative to the client), then you should be able to persuade them.

6. In order to really know whether the client has a valid point, you need to gain more experience with functional programming, either so you can shoot it down with confidence or realise that your bias towards OO is due to your inexperience.

7. Why not do it both ways then let the client see both implementations and decide which is easier to maintain. Just factor all this into your project estimates so you can enjoy the learning curve while you get paid.

Answer 8

Before bothering any further, I'd make sure that you both are talking about the same thing. You could ask him for when software is 'object-oriented' to him. Sine he said that it's not his main expertise himself, it may be that he has some skewed idea.

For instance, many people could consider

class C {
public:
  C();
  void f( int );
  void g();
};

to be a classical object-oriented approach, but

struct C;
void construct( C ** );
void f( C *obj, int arg);
void g( C *obj );

not (even though both are equally object-oriented as far as the classical "data together with the functions which operate on it" definition goes).

Answer 9

Would you try to persuade your client that using object-oriented programming is much cleaner?

I think you need to educate yourself more on programming paradigms. Object-Oriented programmed code is not necessarily cleaner, and in fact, it is not universally applicable. Also, a good object-oriented coder knows how to do good work using a procedural/modular (With Functional and Declarative paradigms, it is a bit harder, but it should not be overly difficult for a good programmer to arrive - via reading and deduction - to an acceptable FP/Declarative solution.)

You almost never cannot, I repeat, you almost cannot have a good understanding of when and how to use Object Orientation without having a good understanding of procedural and modular programming. OO is a lot more than just declaring classes and inheritance hierarchies.

Or would you try to follow what he required and give him crappy code?

If you cannot write good code procedurally, I doubt you can write good code in an object-oriented manner. Period. I'm not trying to judge here, but this has to be asserted.

Object Orientation is an extension of procedural and modular programming. Object-Orientation simply gives you tools that, when used appropriately, give you better mechanisms with which to deal encapsulation, coupling, cohesion and code-reuse/extensibility issues.

But all those issues are not inherent and unique to OO. They exist in procedural/modular code (and in other paradigms for that matter.) This is the type of complexity issues that, at its very core, is paradigm-independent. If you cannot handle them without OO glue, then it's unlikely you can handle them with it.

=========

Going back to your original question, of whether to try to persuade your client. It depends. As poster Sean McMillan said, if the client is simply trying to micro-manage the development effort for some agenda (read, office politics), walk away. People who do that sabotage projects to blame someone else, or push a particular agenda. You do not want to be involved in that.

OTH, there might be other reasons for such a requirement. Many embedded shops, for right or wrong, choose to put a lot of constrains on what you can do with C++ (no virtual methods, no exceptions, for instance.) Some times it is done in a knee-jerking fashion. Some other times, there are valid technical reasons for doing so.

So you need to understand why the client wants to avoid OO code. And if you can surmise that there is no political agenda (no red flags), then you should do the professional thing to do, which is simply do the code procedurally/modular, and do a good job at it.

There is really no excuse for delivering crappy code, independently of the programming paradigm. If you can't produce acceptable code with one paradigm, you most certainly cannot produce acceptable code in general.

Answer 10

You are mixing up data-structures and object-oriented-programming (a common confusion in this OO infested world)

If all you need to do is "track data attributes" in a data structure and modify them then almost any language made after the 70s will have good suppot for it, OO or not.

The things that are easier to do in OO are roughfly

• Class based inheritance (its easy to create a new class that pretends to be an old one)
• Class based polymorphism (its easy to add new kinds of ant to the simulation afterwards)

If you don't have a pressing need of one of these then basically any programming paradigm should solve this without too many problems.

Answer 11

my client said that since he has a background in functional programming he would like the simulation to be made using functional programming.

(This is yet another example of a social issue being mistaken for a technical/design issue.)

There are two possibilities here:

1. Your client is expecting to be able to take the code you have written and adabpt or maintain it himself after you are done writing it. If so, you should know a lot more about the "house style" -- functional vs OO is only the tip of the iceberg. You will either need to limit yourself to a style of programming that your client understands, or you will need to educate your client in the styles you prefer. (Once, I was asked to build a web app with CGI, without using templating or libraries because the client might want to make changes.)

2. Your client is trying to control the development because of some agenda. This is a bag full of crazy that you want nothing to do with. If you are truly providing a "turnkey" piece of software, the client shouldn't care if it's made of hamsters running on wheels, as long as it does the job reliably. Allowing yourself to be micromanaged this way is just asking for pain.

It's up to you to decide which situation you're in, and act accordingly.

Answer 12

Umm... am I the only one here thinking "this is obviously a test job/assignment"?.

Firstly - the assignment itself is kind of "academic" in nature (simulate an aspect of behavior of ants).

Secondly - a request to implement requirements using (or avoiding) a very specific programming paradigm smells of the "client" who can read code and make such assertions.

If this is the case, you better do what is required of you - it will be rather nice learning experience and if you can do it, you'll learn a lot in the process...

If this is not the case, you should indeed ask yourself and/or the customer for the reasoning about the assignment. If the reasoning is solid, then do it - you'll learn and you'll be better as a programmer for the experience. Who knows - you might even learn to like functional style over OO.

If the explanation is lacking, then all bets are off.. I can not recommend you what to do.

You might want to try regardless to implement the requirements in functional language/style or you might politely turn down the offer if you sense something fishy.

The main thing is - once you understand the motivation behind the requirements, the proper course of action becomes evident.

EDIT: After taking a diagonal look at the referenced PDF, the algorithms described there surely seem like a good fit for functional style rather than OO

Answer 13

There are several good aspects in their request to use functional programming:

1. You have a client, it's always a good sign
2. The client expects you to be very good at what you're doing. This is why they ask functional programming. So your sales organisation is doing a good job or you're asking very high price for your services.
3. Client organisation has some people who know functional programming is a good thing and will be big in the future

But there are some alarming signs also:

1. You don't seem to be prepared to implement it in functional programming. You're already slightly outdated in your skills and cannot keep up with the changes.
2. Or the client is expecting you to be better programmer than you really are. This means you might need to downgrade their requirements until you can do it properly.

Answer 14

Seconding the above responses that maybe OO isn't the best solution in which case the client may have a point.

Take a look at the AI Challenge which models some of the behaviour detailed in the question here http://aichallenge.org and then take a look at the variety of starter packages - http://aichallenge.org/starter_packages.php/ most are languages I wouldn't place within the OO paradigm.

Answer 15

You've wrote nothing about programming language, which is propably the most important thing there. The difference between OOP and functional programming is not only the way the code is organized but the language itself. When high concurrency is the case, functional language Erlang is in usage, and it has very high advantage over e.g. Java (it is used e.g. by Facebook chat). OOP solution could simply fail because of performance issues.

The client here is university, so language isn't only performance/configuration issue, the code could be also used for didactic work with students or own research. So 'persuading' client to choose other paradigm is in my opinion not applicable here. This is either you can deal with the task or you can not (and so, you should not take that project).

Answer 16

Client says "jump", your answer is: __ _?

For me, I would make an attempt to persuade if it made sense (new project), but I also have a client with a 10 yr old VB6 app that I do upgrades for occasionally... not going to convince them to

Answer 17

'Cross Examine' your client a bit (in a non-confrontational manner):

Does client actually know the difference between OOP and functional programming? Are client's concerns/requests legitimate?

If 'Yes': If you're qualified, do what they want and take your money. If you're not qualified, tell them so and let them decide what to do.

Else: hi-tail it outta there!

Answer 18

double dist(Point p1, Point p2) 
{
  //return distance
}

This function is functional as long as it doesn't read/write anything outside the function. If the function touched a class variable it would no longer be "functional". The advantage of functional style is there are no more bugs from changing or invalid state. A large amount of functions are just mathematical formulas. That's functional programming in a nutshell.

BTW you can combine a functional style within an object based or oriented design. For example the two "Point" variables are objects with state. And the function is still functional! Yay!!