|
|
Because OO is something that is not on the radar of the professional hobbyist. Most common defense that I heard is that they get good enough results without using OO.
Walk away 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Exactly writing procedural & structured programming constructs and wrapping those in classes, rather than fundamental OO.
|
|
|
|
|
Lots of God objects? 
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
"Use the right tool for the right job." -- Scotty et al
|
|
|
|
|
There is an old saying: "Those who can, do. Those who can't, teach."
That's not saying "all teachers are cr@p" - good teachers are worth their weight in gold-pressed latinum - just that most teachers don't have a lot of "real world" experience; they aren't engineers; they aren't particle physicists; they aren't IT professionals. So they don't know the subject - and neither do the people who set the curriculum and exams.
Teach the simplest, so the "whole class" can cope, even those whose technical ability consists of charging an iPhone.
And you get "professionals" who have no idea how to do it for real.
(I believe there is at least one QA querist who is holding down a job purely by asking questions here and on SO)
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: There is an old saying: "Those who can, do. Those who can't, teach."
And those who can't teach, teach teachers!
Seriously, I once was asked by a school principal to get certified as an instructor, so he could hire me. I looked into the required classes, and there wasn't one real subject in the whole collection, just a bunch of psychobabble and fluff. Teachers here can't read, write, do simple math, or think logically. Unsurprisingly, neither can the kids they allow to graduate.
Will Rogers never met me.
|
|
|
|
|
And those who can't, can't teach, and can't teach teachers, manage.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
OriginalGriff wrote: (I believe there is at least one QA querist who is holding down a job purely by asking questions here and on SO)
only one? 
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Or bad OO.
I've used some objects - I'm OO.
I've created some classes - I'm an OO Architect.
Good OO requires understand the business space and OO principles, and the architecting of a coordinated set of planned classes. I'd venture most people don't even do any formal design, even if they know how. Most likely they just build objects on the fly, then resort to non-OO code to tape them together.
|
|
|
|
|
When I was a youngster, I was taught that anything worth doing is worth doing well. Now that I've lived almost 64 years of real life, I've learned that they lied to me. There are a lot of things worth doing that simply aren't worth spending a lot of effort on doing well. Quality OOP requires much planning and careful design, and trivial - but necessary - tasks just aren't worth the time and thought needed to do a quality job. Now I save my resources for those things that really matter, and do just enough for those that just need to get done.
Will Rogers never met me.
|
|
|
|
|
Because it was oversold. Or rather: Overdone.
I see (and write) a lot of C# code that is OO in the sense the term was used when OO was first introduced - I know, I was there! I also was there when "structured programming" was introduced. After ten years, everybody had abandoned GOTO and RETURN k (if you don't knwo RETURN k, dig up a Fortran IV manual). You indented loops, you broke the solution down into well defined functions. Today, that is simply how we do it; we do not think of it as "applying structured coding principles".
The academic OO guys developed the concept: Multiple inheritance, virtual functions, interface contracts, iterators, properties, delegates and a whole bunch of addons to the basic OO ideas. If your program doesn't illustrate that you master a minimum of 70% of all the facilities offered by the language, then you are a noob who do not utilize the power of OO  .
Plain, original OO, with the addition of a little bit of properties and delegates, maybe even virtual functions, is as everyday totay as while loops and switch constructs, without screaming out loudly: This is advanced OO, don't you see?? People "reject" OO, or rather: do not care to satisfy the requirements for being allowed to call it true OO, because the OO academics make too high demands to let the software pass the OO test.
(We had a similar situation in database theory around the same time as OO was introduced: To make developers design DB tables in an orderly way, the concept of normalizing were pushed: First 1NF, 2NF and 3NF. If it had stopped there, most databases would have been in 3NF today. But then the acacemics pushed on: You must make your DB to be in the fourth Normal Form! And then 5NF, 6NF and even 7NF. By that time, most developers had turned their back to NFs, "Heck, I don't understand the use of this at all!" - and if the DB is 2NF or 3NF today, it is not for the theory, but becase it comes naturally!)
I did OO before OO: In my first university programming course, the professor taught us to define Pascal RECORD types with a set of functions to operate on the fiels of the record. Every one of these functions shold take a record pointer as the first argumnent. So when OO arrived a couple of years later, we had to rewrite "Func(object, ...)" into "object.Func(...)", but otherwise, the code structure was unchanged. (Pascal variant records allowed for polymorphism, and one type declaration could specialize an earlier one.)
|
|
|
|
|
You indented loops, you broke the solution down into well defined functions. Today, that is simply how we do it; we do not think of it as "applying structured coding principles".
I am amazed yes we are doing exactly same these days.
|
|
|
|
|
Because LINQ is a functional approach, mayhaps?
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
The dumbest ideas, made real! ™
And this week, I present: The WiFi clothes peg[^]
No, seriously. For when you are at work and need to check how your clothes are drying, or a sudden squall means you have to jump in the car immediately!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
So this manager comes up with the "really good" idea and everyone is just to scared to tell him no?
Can you imagine your boss (in your case let's say your wife, probably equally scary as the average boss  ) coming to your office and telling you "Griff, we really need a smart clothes peg, it will REVOLUTIONIZE the way we do laundry!"
And you just sitting there like "ehhh... boss/sweetheart, I'm not sure if this actually solves anything."
"Nonsense, make it happen or I'll have your head on a platter!"
And so you start writing code.
namespace Omo.SmartPeg
{
public class Laundry
{
var absoluteNonsenseMyBossIsMakingMeDo = null;
}
}To be fair though, it seems like the peg is just a weather sensor, which is actually pretty useful, cool, and fun.
You could do so much more with that than just check whether your clothes dry as good as they should.
|
|
|
|
|
Quote: And you just sitting there like "ehhh... boss/sweetheart, I want you to imagine you are on Dragon's Den, and Peter Jones is looking at you with his mouth open ... "
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Sander Rossel wrote: To be fair though, it seems like the peg is just a weather sensor, which is actually pretty useful, cool, and fun.
For anyone who does not have access to radio, TV, internet or neighbours.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Eddy Vluggen wrote: radio, TV, internet
That's not as local.
Eddy Vluggen wrote: or neighbours
That's not as accurate.
I can't stand small talk about the weather.
Like "it's really nice weather today", first of all I KNOW I AM HERE and second "nice" is different to everyone.
So no, I don't think this 35 C beach weather is nice, I prefer a cold winter's day or a cool autumn's day.
And I really never got those people (like my grandparents) who inform about the weather in The Netherlands while on a vacation 
"It's warm and dry here in Germany, but I just got off the phone with X and at home they have rain." WHO CARES!? I'M NOT AT HOME!
Knowing the exact humidity is important though, it helps me keep my plants alive 
My previous plants died when the humidity in my house dropped to like 20% for a long period of time (no open windows, lots of heating) 
|
|
|
|
|
Sander Rossel wrote: That's not as local.
Local enough; you'll get a prediction, not an accurate forecast that's going to vary from mile to mile.
Sander Rossel wrote: I can't stand small talk about the weather.
Like "it's really nice weather today", first of all I KNOW I AM HERE and second "nice" is different to everyone.
So no, I don't think this 35 C beach weather is nice, I prefer a cold winter's day or a cool autumn's day.
And I really never got those people (like my grandparents) who inform about the weather in The Netherlands while on a vacation
"It's warm and dry here in Germany, but I just got off the phone with X and at home they have rain." WHO CARES!? I'M NOT AT HOME!
It's 25 degrees outside, so we are having lovely weather today, aren't we?
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Eddy Vluggen wrote: It's 25 degrees outside, so we are having lovely weather today, aren't we?
Thanks for sharing this crucial information.
I just put on my warmest vest, I cranked up the heating, and I'm under every blanket I could find.
Of course if you say it's 25 C I guess that's not necessary at all
|
|
|
|
|
Sander Rossel wrote: Thanks for sharing this crucial information.
Small talk is never and always crucial. We a social species, and we need to socialize even if there's no crucial information to exchange.
Sander Rossel wrote: I just put on my warmest vest, I cranked up the heating, and I'm under every blanket I could find.
Of course if you say it's 25 C I guess that's not necessary at all
22,7 degrees outside, and it hasn't been freezing during the night - the low was at 13 degrees. Even in Norway, it is still 16 degrees.
Not nearly cold enough for snow or ice
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
