Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror

Comment Re:OOP is fine (Score 2) 386

OOP was sold to management on the basis of making maintenance more ... "manageable:" its re-usability features would make it easier for software engineers/technicians/slaves (now you know my bias) to be transferred between projects because coming up to speed on a new project would be that much easier. I know; I was there when OOP was first being pitched at IBM: people disparaged it as "just the latest attempt (after GOTO-less coding) to turn dog catchers (the unskilled) into programmers." Concurrently OO Design was pitched to the aerospace and financial industries (along with Ada) as a means to reduce the design-level fault rate.

All of this was dictated by the desire to evolve engineers from an ardently determined but unruly gang to a still ardently focused but easily interchangeable assemblage. That "easily interchangeable" point is key: it costs a lot of money to care for and feed engineers and the art of their deployment is foremost in the minds of middle and lower-level management.

History's verdict is, "Yeah, THAT worked well ... didn't it?"

-Rant-
The goals that OOD/OOP were to accomplish were eventually satisfied by converting software engineers from professionals to gig-economy itinerant technical comestibles who are driven by only delivery and cannot have a long-term investment in a product's sufficiency. Who cares if the engineer is under utilized? Furlough him/her and re-engage later! Who cares if the output is maintainable? It's going to be disposed of and recreated in short order anyway!

OOP was never actually used. Don't believe me? Look at the preponderance of function identities that lead an object with a verb (even in strict environments): createAThing, disposeOfAThing ... fesselAnAardvark, shaveAYak. OOP, if properly used would dispense with the object's identification: AThing.create, AThing.dispose ... AnAardvark.fessel, AYak.shave. Even when a language, such as Java or C#, impels the coder to form OOP-conformal names, the design documents are invariably non-OOD (dare I say ANTI OOD): they are full of Fesselings of Aardvarks and Shavings of Yaks.
-End of Rant ...er... Rant.End-

Comment This is Force Majeure (Score 1) 402

Force Majeure: Unforeseeable circumstances that prevent someone from fulfilling a contract.
from https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.lexico.com%2Fdefinition%2Fforce_majeure

from https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.law.cornell.edu%2Fwex%2Fforce_majeure
Examples:
A natural disaster (major earthquake, flood or hurricane) may be a force majeure if unpredictable
A rainstorm during an outdoor event is not - rain is a normal and common occurrence.
A war, or riot may be considered a force majeure.

I suppose it could be automatically and even retroactively applied to all existing contracts. Part of a proposed stimulus package is a half-trillion general purpose fund; maybe it could be explicitly earmarked to pay portions of personal debt owed to the federal government.

Comment Re:Fuck that noise. (Score 1) 277

There are a LOT of Windows applications in place that manage external hardware. Vendors are (so far, mildly) concerned that this forced migration to the cloud could result in liability issues. For example, imagine a service failure, caused by a simple connection breakdown, in the management of valves for a natural gas field. A ton of equipment and a good chunk of real estate could go up in smoke; no malicious actor needed. The stakes are even higher for medical systems.

Microsoft does not seem to be tracking the process control market. Maybe that's because it's too small, or maybe it's enormous but nobody knows it. It does drive what used to be called the "back office:" typically database engines, and a significant portion of their data sets are being migrated to the cloud. Microsoft is certainly watching that. Nonetheless some recent changes to Windows 10 make its use managing unattended hardware at best problematic. Vendors have noticed this hole and some are touting packages based on some flavor of Linux ... and users/reviewers have been quick to notice difficulties in installation and upgrades. Gone are the days when dumb MS-DOS systems could be deployed (and then ignored) to gather data and publish commands.

As for immediate tactics (work-arounds), I note that there still exist WinPE and WinRE, nominally provided for installation and recovery but providing some lean and mean support for data acquisition. Shhh! Don't let Microsoft know!

Comment Re:No respect (Score 1) 325

Well ... maybe not respected but feared ... as in, "We're using his code (which was written in hex and made use of the delays in the rotation of drum storage) but have no idea of how to replace it so we leave him alone and don't let him near the machines when he's had a beer or three." Yep, that's you, Bob! Bless yer ass; I miss ya.

Comment The Greatest Privilege (Score 1) 261

"None can match him or our great company." ...
"You're so big and so square and so true,
"We will follow and serve with you forever,
"All the world must know what ... can do."
      and
"It is just the greatest privilege of my life is to serve as the -- as vice president to the President who's keeping his word to the American people and assembling a team that's bringing real change, real prosperity, real strength back to our nation."

(Uh, I guess I won't get the job.)

Comment Re:Bad programmers write bad OO; and bad FP (Score 1) 782

Overhead in a NYC deli when a customer asked repeatedly if the chicken was fresh and never seemed to accept the answer: "Hey, Lady! God makes good food, but the devil makes bad cooks!"

Ever notice that OO (design, programming, posturing...) naming is very not-OO as soon as something complex or subtle must be accomplished? Imagine an object named Thingie. Thingie.Create and Thingie.Delete are expected but rarely seen during design; it's always CreateThingie and DeleteThingie. It's apparent that OO designers ... aren't (qualified).

Pulling on the food metaphor of the post's title, it's a bit like the naming of MREs (Meals, Ready to Eat; Meals, Rejected by Everybody). Want to drive incompetent software "engineers" crazy? Really use OO names during design and the whining becomes deafening. Just try it (a good way is to specify that dates and time shall be in ISO-8601). Then get your resumee polished.

Prediction: functional styles will be no more a panacea than OO which was no more a success than GoTo-less programming (although that did provide a means to identify just where to reset register optimization). It's the cooks that are the problem!

Comment There's No Point in Acting Surprised about It (Score 1) 111

"There's no point in acting surprised about it. All the planning charts and demolition orders have been on display at your local planning department in Alpha Centauri for 50 of your Earth years, so you've had plenty of time to lodge any formal complaint and it's far too late to start making a fuss about it now. … What do you mean you've never been to Alpha Centauri? Oh, for heaven's sake, mankind, it's only four light years away, you know. I'm sorry, but if you can't be bothered to take an interest in local affairs, that's your own lookout. Energize the demolition beams." - Douglas Adams, The Hitchhiker's Guide to the Galaxy

What say we enact another measure that says that anybody who signs on to this decree must forfeit 99% of all yearly income to those who did not? For good measure, require the donation of one vital organ, preferably a gonad.

Slashdot Top Deals

Thus mathematics may be defined as the subject in which we never know what we are talking about, nor whether what we are saying is true. -- Bertrand Russell

Working...