Slashdot Mirror


Advocating Linux / OSS to Management.

An anonymous reader writes "I'm the Senior Developer at a fairly large agency, we're currently a 100% LAMP shop, but I've heard a reliable report through the grapevine that the management a few levels above our office wants to standardize our region on MS .NET. As I'm sure most of you can appreciate, to do such a thing would be... counterproductive, and I could really do with a hand conveying this to a manager whose only real knowledge of Linux is "if it's so good, why would you give it away for free"?"

12 of 466 comments (clear)

  1. Created with love by freshfromthevat · · Score: 5, Insightful

    The difference between a professional and an amateur is that amateurs work for the love of it and professionals work because they get paid. Sort of the difference between a spouse and a hooker. Which side does MS fall on?

    --
    .. Blub falls right in the middle of the abstractness continuum. -- Paul Graham
    1. Re:Created with love by Anonymous Coward · · Score: 5, Funny

      MS is the hooker who wants $50 more for anal. You end up paying because of all the promises (s)he made but soon realize your mistake when MS calls her(his) pimp (we'll call him FBI) comes in and beats you into unconsciousness for not having a valid license. When you wake up, your money is gone, your respect is gone and you feel cheap and used. On your next visit to your doctor, you also find that MS left you with a very nasty social disease.

  2. Don't be fooled, it's the FUD by KingSkippus · · Score: 5, Insightful

    Don't be fooled by management's official reasons why they don't go with Linux or other open source software. It really just boils down to FUD.

    There's still a prevalent image of Linux and other open source software out there as just hobbyist software. The reason I hear most often cited for not considering open source software at my company is, "There's no one to hold accountable if it breaks." Even when I point out companies that offer paid support--people to be held accountable for making sure the software works--they still chant the "hold accountable" mantra. Those companies aren't big enough, they may go out of business any minute now, blah blah blah.

    It's really disgusting sometimes. I've seen software come into our environment that I know for a fact and can demonstrate is crap, and offered alternatives for it. I'm told, "That's all fine and good, but when the software we're going to use breaks, we'll have someone to sue over it." Of course, that doesn't really happen, we always just end up suffering for several years until the next version comes out or some other closed-source competitor comes in and convinces management that they're the way to go instead. Having people to "hold accountable" (which they never are) is more important to my company than having something that actually works.

    I don't know what to suggest. Another trait of large companies is that they won't do something until everyone else in the world is doing it. Once a company reaches a certain size, there's no longer a culture of trying new things and trying to separate yourself from the competition; it becomes an unrelenting strive for mediocrity. Right now, everyone else is moving to .NET, so that's probably where you'll end up, regardless of what is best for your company. About the only chance you have is to put together a pretty Powerpoint presentation showing that switching to .NET will cost a billion dollars. Make costs up if you have to. The problem is that if you show it will only cost a million, they'll still do it anyway just to be on that magical .NET bandwagon, and you'll need a ridiculously large cost to justify not doing so.

    1. Re:Don't be fooled, it's the FUD by ditoa · · Score: 5, Interesting

      I suggest you print out Microsoft' EULA from things such as Windows, Office, Visual Studio and the .NET Framework, highlight the paragraph stating you can't do anything to Microsoft if use of their product results in damage to your company, hardware, finances, etc. then leave it on their desk along with a cost of migrating from your LAMP environment to Windows Server/.NET

      People think that because you pay for it you get support or compensation when it goes wrong but you don't. You cannot do anything, when you agree to that EULA you agree that it isn't a perfect solution, it may screw up and your business might lose billions because of it. If that happens tough luck, you c^Hshould have bought Enterprise Edition and had a clustered solution :P

      Saying that I don't hate MS. For some thing Windows is fine and I am happy to use it just as I am happy to use Linux or Solaris or AIX.

      At the end of the day if the company you work for wants to change to MS that is up to them, if you feel it is a bad move for the company explain why. If they still switch to MS you can always find another job if you hate it that much. Their are plenty of FOSS based companies around.

  3. Who gives a fuck? by Progman3K · · Score: 5, Informative

    Just do your job and install and maintain whatever the hell management decides.
    Linux is not going to go away simply because a few chowder-head PHBs don't know anything about it. If that were true it would never have gotten established like it has.

    If YOU want to use Linux, install it at home and use it there. Let the employer have whatever s/he wants, the employer IS the one spending money, not you. It isn't your job to go on a crusade to change their minds.

    When your shop will have spent lots of money to convert from your current set-up to whatever they want and you wind up with more problems to boot, THEN they might start looking for solutions and be more open to something other than .NET

    There is nothing less attractive than people trying to force things on you, don't be one of those people yourself.

    As the world continues to explore and adopt Linux, things will change, but there will still be people running archaic outdated and sub-par systems, even when Linux will dominate.

    --
    I don't know the meaning of the word 'don't' - J
  4. Find and address his fears by martyb · · Score: 5, Insightful

    An anonymous reader writes "I'm the Senior Developer at a fairly large agency, we're currently a 100% LAMP shop, but I've heard a reliable report through the grapevine that the management a few levels above our office wants to standardize our region on MS .NET. As I'm sure most of you can appreciate, to do such a thing would be... counterproductive, and I could really do with a hand conveying this to a manager whose only real knowledge of Linux is "if it's so good, why would you give it away for free?"

    Question: Ask him if he charges his children for the parenting he gives them? Must be worthless, then, right?

    Question: Ask him how it is in the company's best interests to spend money on something you can get for free?

    Question; Ask him how much he thinks it would cost to convert over, and then give him an estimate of what you could do with the money on your existing LAMP platform.

    My guess: FEAR. It seems to me he's afraid that *something* *will* go *wrong* and he wants to be able to Cover His Posterior. (See: Sarbanes-Oxley Act.) Address his fear by pointing out the REALITY of what happens WHEN something goes wrong.

    • MS .NET: File a bug report. Wait. Hope nobody exploits it while waiting. Wait for fix to be developed. Wait for Patch Tuesday. Continue to be vulnerable while waiting.
    • LAMP: File a bug report. Wait. *OR* Look at the sources. Find the bug. Fix bug and move along. Problem solved.

    Of course, he could mention about coding a work-around, but that holds true for either platform. It's a non-factor.

    It might help to also point out that with LAMP, it is possible to be pro-active and actively search for vulnerabilities. Seeing as others would have the same interest in safety, this has already been done to a some extent, but you still have the option of doing this yourself. With MS .NET, you're screwed. It's closed source and there's no way to investigate what problems are there. Security by obscurity? Right.

    Testing for vulnerabilities: There's a big difference between what is POSSIBLE with: Black Box (.NET) vs White Box (LAMP).

    Still, with a bug in .NET the manager can say it's a bug with Microsoft and wave his hands around it. Sounds good, but in the meantime, his hands are tied, and the brown stuff is still hitting the spinnie-thingie. With LAMP, he CAN do more than just wait for a fix... and any fix that can be implemented in less than a month is a win compared to Windows.

    I know I waved my hands around some in the preceding, but the manager really doesn't care HOW your code works, or even WHAT your code is written in. He's just looking at an abstract "applications that do FOO". Speak to him at his level. Get him to be specific about his fears. For each one, address what could be done with either platform. Provide a reasonable time line. Keep harping on having to wait for MS to get back to you with a fix, while, with LAMP, you could have already constructed one.

  5. Show them the Money!!! by filesiteguy · · Score: 5, Interesting

    I am upper management, and I advocate OSS whenever possible.

    As a manager, I'm interested in two things - cost and productivity. If I can use a piece of software and get the job done faster and cheaper, I'll use it. End of story.

    There are no other variables.

    Now, as a technology geek - I have two 24" monitors on my desktop (running XP) and a 17" laptop (running SUSE) with me all the time - I want to use OSS because it is cool and because I despise Microsoft's business model. However, that philosophy will not fly with executives. They simply want to know how I'm going to save money and get stuff done faster. They don't give a sh-- about Linux vs. Microsoft.

    One other thing. I personally have a $7M budget for FY 2007/2008. About $1.5M of that is for software services and supplies and another $2M is for hardware. That means the majority of my "expenses" are for personnel. Again, executive management wants to know how to make things cheaper / faster / better. If I need to spend more on personnel to get an incremental savings in software, it ain't gonna look good.

  6. Why It's Free by Bob9113 · · Score: 5, Informative

    only real knowledge of Linux is "if it's so good, why would you give it away for free"?"

    While I can't help much with the advocacy side, I may be able to help you with this one.

    If your manager went to business school, he probably took price theory. If he did that, the question above is very easy to answer. Just ask him, "In a free-market capitalist society, what is the efficient market price of a mass market good whose marginal cost of production is zero?"

    WARNING: If he has not taken price theory (and even if he did but did not really "get" it) and you present this to him, chances are he will not understand. In that case, he may react much like a gorilla presented with a clear box full of fruit that is closed with a latch that he does not understand.

    Price theory says that the efficient market price of any mass market good is equal to the marginal cost of production. The marginal cost of production is the difference in cost between producing the first unit and producing the second unit (it's a little more complex than this, because marginal cost tends to not be a straight line curve, but it is a flat straight line with operating systems, so it works). With something like an operating system, the marginal cost of production is zero - once you make the first copy, the second copy costs nothing to produce. Therefore, the efficient market price of operating systems is zero.

    The following is from the Wikipedia entry for price.

    Theory of price asserts that the market price reflects interaction between two opposing considerations. On the one side are demand considerations based on marginal utility, while on the other side are supply considerations based on marginal cost. An equilibrium price is supposed to be at once equal to marginal utility (counted in units of income) from the buyer's side and marginal cost from the seller's side. Though this view is accepted by almost every economist, and it constitutes the core of mainstream economics, it has recently been challenged seriously.

    In short, the more interesting question is, "Why would any corporation in a free market capitalist society pay for an operating system?" It makes sense to pay for service because the marginal cost of an hour of technical support is significantly non-zero. It does not make sense to pay for an operating system.

  7. Re:Answer: by tomhudson · · Score: 5, Insightful

    " a manager whose only real knowledge of Linux is "if it's so good, why would you give it away for free"?"

    "Because the best things in life are free - you PAY for crap like Windows."

    Ask him is he things solaris or java or aix are "unprofessional" products. Versions of all those available for free downloads - heck, Sun sent me the install dvds for opensolaris for free. Then ask him why he thinks that a few thousand programmers working at Microsoft can beat out a world-wide network of programmers, many paid by industry leaders like IBM and Novell, whose work is peer-reviewed!

    Would he feel confident if his doctor started recommending non-peer-reviewed cures and drugs? Does he like the idea doing away with the notion of a fair trial by a jury of his peers? Would he trust an airplane, a nuclear power plant, his fridge or toilet if they ran Windows?

    Then tell him that he really needs to get with the times - his attitude is stuck in the '80s. - that's 1380, when everything was run by guilds with "secret knowledge." Lincoln freed the slaves in 1863, and since then, people want more and more of that "freedom" in all parts of their lives.

  8. This isn't about .NET vs LAMP by progprog · · Score: 5, Insightful

    We're currently a 100% LAMP shop, but I've heard a reliable report through the grapevine that the management a few levels above our office wants to standardize our region on MS .NET.

    Start looking around for other jobs.

    The issue here isn't about .NET vs LAMP, or proprietary vs open source. I would give the same advice if the decision had been the reverse, ie switch from 100% .NET to LAMP.

    Basically your company's upper management is going to make a huge decision without any input from developers. If senior developers like yourself weren't consulted before the change, it's unlikely they have a migration plan that is more detailed than "1) Switch from LAMP to .NET 2) ???? 3) Profit!". Is this a company you want to stay in?

  9. Your are extremely ignorant wrt business school by AHumbleOpinion · · Score: 5, Insightful

    It all depends on how individuals see the world around them. I think managers, who are mostly business school educated, don't see the world the same way the rest of us (developers) do.

    Actually most managers do not have an MBA. Many have undergraduate degrees in science and engineering. Also, I'm in an MBA program right now and there is no shortage of engineers and IT (including admins) in my class. Some of my professors who have decades of real world experience in strategy and marketing at major corporations have undergraduate degrees in electrical engineering, mechanical engineering, etc.

    They probably don't understand why someone would work for free or why someone would volunteer at a soup kitchen.

    That is an extremely ignorant statement. There is a lot of charitable work being performed by business schools, fund raising, volunteering, etc. Additionally, a couple classmates actually work at non-profit research or charitable organizations. I know several that made donations of their time to various charities before entering business school, and who have also continued to make such donations despite having far less spare time now that they are back in school. The school also maintains a list of local charities that could use help in some area of business.

    You are engaging in the same ignorant stereotyping that many around here complain of with respect to how geeks, and technical issues/people in general, are portrayed on TV and movies.

    Most of the managers would never think that work could be fun unless it payed lots of money. Manager-types chose business school just as a way to get more money, it was a pretty good shortcut -- you go to school, pick business as your major, party for 4 years with buds, and then one of their dads hires you as a manager -- the system works great

    That is also a fairly ignorant statement. I have BS and MS degrees in CS. Except for 2nd year calculus and theory of computation I am routinely using more advanced math in marketing classes. Yes, I was completely shocked. Yes, I used to hold the same arrogant and erroneous opinions you now hold.

    Developers became developers because they like to write software. Most found ways to get payed for it, but they didn't dream of reaches first, then thought that becoming a developer would get them there and chose 'computer science' as a major in college (those that did do that, probably ended up switching to 'communication', 'business administration' or 'comparative literature' before the 2nd year.)

    Bull. The vast majority of CS graduates that I have interviewed basically got into it because someone told them it was a good career path. It is difficult to wade through the applicants and find those truly have an interest in the work. Also, donating time to an open source project does not necessarily identify those with an interest. Some of the more savvy career path types realize that this is an easier way to get something on the resume outside of classwork.

    Also, some individuals donate time to FOSS for non-altruistic reasons such as ego, improving credibility/reputation, getting some experience in an esoteric area before applying for a job, etc. I'm not saying there is anything wrong with this. Just that your are romantically naive about FOSS developers.

  10. A better answer by einhverfr · · Score: 5, Interesting

    Management types like *business* reasons. So here is what I tell people.

    The fundamnetal difference between open source software and Linux is not whether people pay but rather who pays for what when. Microsoft pays developers to build software and absorbs all of the costs themselves. They then charge license fees to recoup those costs and make a profit. Open Source software costs money at the development stage too, but only the people or businesses that need those changes enough to pay for them must do so. Consequently the difference is that open source software spreads the cost of development around up front on an on-demand basis, while Microsoft charges in arrears and must control certain aspects of the use of that software to make money.

    As a result, moving to Microsoft software would require:
    1) paying license fees
    2) paying someone to track software licenses
    3) a move from a solid, peer-reviewed codebase where users and developers actually talk to eachother to one where marketing runs everything.
    4) scrapping all existing code and building everything from scratch.
    5) The loss of a large measure of control over your own existing infrastructure.

    Furthermore, Microsoft tech support is pretty much worthless these days.

    Additional points the management should consider if there are concerns about Linux:
    1) IBM is far larger than Microsoft and is putting substantial development effort into Linux. Linux is no longer the hobbiest operating system and there are a lot of people working on making it work well on high-end hardware.
    2) If .Net is desired, it may be better to focus on Mono instead. Mono is compatible in most cases with .Net (and will run even some Microsoft .Net tools like WIX), and it is fully cross-platform unlike .Net. If you write Mono code, you will be able to run it on Windows, Mac OSX, and Linux, but if you write .Net code, you may not.

    If they are not convinced, take a look at my web page and call the sales number :-)

    --

    LedgerSMB: Open source Accounting/ERP