Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×
Businesses Databases Programming Software Technology

Why You Should Choose Boring Technology 232

An anonymous reader writes Dan McKinley, a long-time Etsy engineer who now works at online payment processor Stripe, argues that the boring technology option is usually your best choice for a new project. He says, "Let's say every company gets about three innovation tokens. You can spend these however you want, but the supply is fixed for a long while. You might get a few more after you achieve a certain level of stability and maturity, but the general tendency is to overestimate the contents of your wallet. Clearly this model is approximate, but I think it helps. If you choose to write your website in NodeJS, you just spent one of your innovation tokens. If you choose to use MongoDB, you just spent one of your innovation tokens. If you choose to use service discovery tech that's existed for a year or less, you just spent one of your innovation tokens. If you choose to write your own database, oh god, you're in trouble. ... The nice thing about boringness (so constrained) is that the capabilities of these things are well understood. But more importantly, their failure modes are well understood."
This discussion has been archived. No new comments can be posted.

Why You Should Choose Boring Technology

Comments Filter:
  • by Dutch Gun ( 899105 ) on Monday March 30, 2015 @09:25PM (#49376569)

    A personal corollary for code related to this theme is to always try to make the code I write as "boring" as possible. I've found that programmers often get themselves in trouble by trying to be "clever", which often makes for horribly unintuitive or unnecessarily complex systems. I've heard people asking about how to perform crazy language tricks and I nearly always think to myself "My God, why in the hell would you even *think* about doing something like that?" Such things nearly always point to very fundamental flaws elsewhere.

    • by nine-times ( 778537 ) <nine.times@gmail.com> on Monday March 30, 2015 @10:31PM (#49376885) Homepage

      I'm not a programmer, but more in IT support, and but it seems like there's always someone doing the same thing: trying to be clever. Everyone wants to be a cowboy. Everyone wants to do something badass that serves their ego.

      more often than not, doing a good job is more about paying attention, being thorough, and doing the obvious thing. Listen to the user, read the error messages, look in the relevant log file. Tell the user what to expect, and then keep them informed until the problem is resolved.

      I wonder if that's that it's about in all professions. Maybe most jobs don't require special genius, but most of the secret is just being thorough and conscientious, and using some common sense.

      • by tnk1 ( 899206 ) on Monday March 30, 2015 @11:47PM (#49377125)

        There is a lot of flash these days in coding. Someone is always trying to sell their wares to a venture capitalist. To do this, you have two options.

        First, you can write a stable application in something boring and then develop a track record of excellent service underlying an elegant and interesting design that serves a purpose that can make a profit. This actually does get attention, but not as commonly as....

        Secondly, you come up with some glitzy idea, and attract elite developers who really want to do whatever the hell strikes their fancy. This works... mostly because they really are elite developers, and their team is young and motivated. They can use some random bleeding edge idea because they are good enough to make it work, and they may have even had a hand in developing the new ideas personally. When that fails, they are willing to work like coke addicts to get it done to a point where it can be sold.

        There is nothing inherently wrong with either option that rehab won't solve.

        The real problem is when everyone else tries to be like the people in the second example, when what they really need is to be the people in the first example.

        Look into a mirror and stare at yourself for a minute. You're competent, maybe even excellent at your job as a developer. Your team is solid. You're just not that kind of elite, however. You dearly love the flashy stuff, but you don't quite understand it as well as you'd like. Instead, you've been working in X technology for a number of years. You know how it works and so does your team. You have a track record of success. Boring, but successful.

        You need to be a professional and understand your limitations. If you do, you will be part of a team that makes things happen. If you don't, you're going to make a mess. Don't pick sexy unless you really have what it takes to back it up. That is all.

        • Re: (Score:2, Informative)

          by Anonymous Coward

          Also, like being sexy, be sensitive of how you age... some can do it, some cannot. I was clearly in your second group a few years back... now that I'm getting older, value sleep, try to avoid the hypertension that was destroying my heart, have to manage other people that also code... being in the first group is fine.

          • by qpqp ( 1969898 )

            I was clearly in your second group a few years back...

            Maybe you just were not sexy enough, hm?

            • by gmhowell ( 26755 )

              I was clearly in your second group a few years back...

              Maybe you just were not sexy enough, hm?

              I'm too sexy for my hat, what do you think about that?

      • by m.shenhav ( 948505 ) on Tuesday March 31, 2015 @03:26AM (#49377627)
        You have a good point, but only most of the time.

        Thomas Kuhn, in the context of science, spoke of 'normal' and 'extraordinary' science. Normal science was as you described; you stay in the paradigm and follow the conventional methods for resolving issues. However, these methods did not appear out of nowwhere; somebody was being a clever cowboy and decided its time to do things different. This is where revolutionary science came in. Of course most of these innovations - like any innovation - fails miserably. But if it wasn't for all the failures we would never have the successes that change paradigms and got us to the methods we use today.

        And I think this dichotomy does apply to almost every human endeavor.

        That said, for normal day to day operations, being a cowboy ALL the time is foolhardy and dangerous. But for people to NEVER have a little bit of an experimental and innovative mindset is also risky in its own way. Sometimes this is balance (known as a bimodal or barbell strategy) is maintained within a single individual by balance of exploiting the traditional and exploring the novel; sometimes its divided between individuals, with a good balance keeping more people stable than unstable.
        • Likewise: I know of people so afraid of "being a cowboy" they use all of 10% of a programming language's feature set because they're too afraid to mess something up if they... learned something.
      • I used to spend a lot of time answering questions that people simply had not taken the time to think through and usually didn't have all the information they needed to make a conclusion. The ability to approach varied problems in a logical manner probably is a special kind of genius.

    • by readin ( 838620 ) on Monday March 30, 2015 @10:52PM (#49376955)
      I was recently explaining to some students why I don't know about the trickier parts of the language I use everyday. I don't use those tricky parts and I would chew out anyone on my team who did, so the precise details of how those parts work never come up..
      • Re: (Score:2, Informative)

        by Anonymous Coward

        For pretty much every tricky language feature, design pattern, complex algorithm etc you'll run into, there exists a project that uses it correctly and gains significantly from that. The problem is that there are so many of them that you cannot expect to be able to master them all no matter how good you think you are. A good developer understands this balance while bad developers go to either extreme.

      • Not knowing about trickier parts of a language doesn't mean that you don't use them. I recently discovered some code where experienced C programmers didn't know that signed integer overflow was undefined in C. This meant that the compiler could optimise one of their tests away in a loop (nontrivially, in a way that's difficult to generate a warning for) and turn it into an infinite loop. After a few weeks, their code would hit this case and infinite loop and freeze. Unless you know that this tricky part
        • by readin ( 838620 )
          True, but sadly ( I do miss C sometimes) I'm not using a language that has those kind of gotchas.
        • by readin ( 838620 )
          I'm surprised to learn that it is undefined. I thought it always just rolled around.
      • by dave420 ( 699308 )

        So you don't know about something, yet assume you know enough to know it's not useful? And you'd chew someone out who found a great way to achieve something because you think it's using tricky parts of the language, parts you are intentionally ignorant of because of some unmentioned reason?

        You don't sound particularly rational. I could make a joke about your sig, but I'll leave that alone.

    • by dargaud ( 518470 )
      A former boss once told me: "Whenever you think of a clever programming trick: forget it !". At the time I thought it was a joke, but now with experience I see the wisdom of that.
    • "I've heard people asking about how to perform crazy language tricks and I nearly always think to myself "My God, why in the hell would you even *think* about doing something like that?"

      I wouldn't be so judgmental on that. You may not know the details on what they are trying to accomplish. What I really hate are respondes to those question admonishing the person for doing it wrong. Then tell them to do it in a way that they stated wouldn't work for their use case.
      If the question is posed then they may be fa

    • Valid for okay programmers. The great ones don't need to draw within the lines. You don't innovate by hashing together someone else's crap.

    • Re: (Score:3, Interesting)

      by Anonymous Coward

      "Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?" - Brian Kernighan

    • which often makes for horribly unintuitive or unnecessarily complex systems.

      Indeed. Witness the unmitigated mess which are today's web pages, filled with mountains of complex code creating unintuitive navigation and unnecessarily complex layouts.

      KISS has officially been abandoned in favor of crazy language tricks just because the programmer could.
  • by rjstanford ( 69735 ) on Monday March 30, 2015 @09:27PM (#49376577) Homepage Journal

    It's the same reason that your own small company should be trying to implement its own CRM (assuming that's not its core business), or drastically changing the way that it considers sales compensation. Being revolutionary in one area is hard enough - don't make anything even harder than it has to be.

    • by gl4ss ( 559668 )

      umm yeah?

      no. the article tries to argue that you should choose lotus as your crm, because you already used your innovation tokens on node.js, nginx and amazon s3 and now you have to wait 3 years to choose something else that's innovative - so you're also stuck on using exchange as the mail server for the time being and can just forget about targetting chrome in your product because that's too fucking innovative.

      • Re:Absolutely (Score:4, Insightful)

        by tnk1 ( 899206 ) on Tuesday March 31, 2015 @12:04AM (#49377179)

        Maybe it *is* too innovative.

        Its not a matter of Lotus being good. Its a matter of what you can do with limited resources.

        If Lotus Notes (shudder) is working for you at the moment, and you really, truly needed to move to node.js, nginx and S3 for some reason, then you need to weigh all the effort that goes into making all of those as stable as you need them to be in order for them to be an actual improvement.

        New things need not only code, but tests. If they go into production, they need the operations team to know how to tell if something is wrong with them, and how to fix it. Preferably without waking you up at 4am each time. More preferably with them able to proactively watch for signs of imminent failure and deal with it well before it becomes an issue.

        All of that sort of understanding is more than just what it takes to check in some code and some unit tests.

        The realistic situation in your scenario is a little backwards because I don't know of any reason to switch to the other three techs without putting Lotus Notes out of its misery first. There does need to be a realistic understanding of priority. What is not-so-good and what is a complete clusterfuck, like Notes.

        You can't do everything you want. If you try, you're going to create problems unless you can increase resources. If you can't increase resources, you need to wait.

        • by gl4ss ( 559668 )

          that's not the point!

          the point was that because your company used innovation tokens already then you need to stick to something old, leading to situation where you would use access 2000 to store data shown by a web front end generated by node.js, just because "well, can't have too much new stuff".

      • Yes, and I'm actually on board with that (although I'd have picked Salesforce if I'm just blind-picking out of a hat).

        If you're just the average 20-80 person software shop - somehow refusing to believe that the (literally) millions of businesses running on platforms like Lotus Notes or Salesforce are doing alright and that your business is so terribly revolutionary that its better to spend hundreds of hours deciding-on, deploying, customizing, and supporting your own specialized CRM is a better use of your

      • The article is meaningless bullshit.

        I evaluate things I use. When MongoDB came out, I told our dev manager we should use it because we are storing flexible, complex data in MySQL and that's just not a good fit. Document stores are better, and MongoDB with acknowledged write mode in a 3-node replica set has roughly the same data consistency guarantees as PostgreSQL with a replicated WAL in the common async mode (there's a small window where the slave server may crash, and the master server may also imme

        • And indeed, when MongoDB first came out it had all sorts of issues living in production environments. Now, on the other hand, its well-understood, the serious bugs are fixed, and its ready for casual users. How long would it have taken you to get everyone (including dev-ops) up to speed on MongoDB as opposed to actually building product over MySQL until (as it is today) a competitive solution was stable and "boring" enough?

          If handling data elegantly is your company's selling point, then maybe its worth inn

  • by TWX ( 665546 ) on Monday March 30, 2015 @09:28PM (#49376583)
    Mature technologies are proven. They've gone through their growing-pains. They may have limitations, but those limitations and workarounds are usually well known by seasoned professionals. There's a reason why COBOL, Fortran, and RPG are still in use in business applications almost sixty years after their initial development, because they reliably work.

    I've tried to work with NodeJS projects for production. It's a nightmare. NodeJS itself is revised too often, the actual project is revised too often, and the dependencies became a nightmare. It's not mature enough and not worth it.
    • Mature technologies are proven.

      Yes, but somebody had to do the proving. As that great fount of wisdom, John Wooden, once said; when we are young we tend to see all change as progress, but as we mature, we can forget that there is no progress without change. It's not easy to know when you should take on a new technology, but that doesn't mean you shouldn't take on a new technology.

      • It's not easy to know when you should take on a new technology, but that doesn't mean you shouldn't take on a new technology.

        And when you consistently refuse to take on new technologies, that's when the countdown to obsolescence has begun.

        • by tnk1 ( 899206 ) on Tuesday March 31, 2015 @12:21AM (#49377227)

          There has to be a balance. You need to move forward, but don't just change to change. The article suggested one method of moving forward while remaining stable.

          I understand as well as anyone that the world moves and sometimes even perfectly functional applications need to move with it, despite the fact that nothing is wrong with them. There are end-of-life issues with hardware. The code has gone missing. Customer support shuttered ten years ago. You have one greybeard who knows how to operate or make any changes to the app, etc.

          That said, there's a lot of stuff out there that is seen as "old" which is still fully supported and stable. It is getting security updates. It can handle large scale deployments. It is free and open source, &etc. You don't have to move away from that. You probably *shouldn't* move away from that.

          Fashions in development don't always require you to have followed the path all the way to the endpoint. You holding back now might mean that you can jump ahead two steps when the turn for the next component comes up. You don't need to track the curve constantly to be able to join everyone at the innovative end after a hop.

          Most of this stuff is a fad that will add more flash than actual feature set. Wait for two fads to pass and you might now have a real set of features to sink your teeth into. And in the meantime, you have had a stable and well supported application to build on.

          • There has to be a balance.

            I think you and I are in complete agreement across the board. I would mod you up.

            Not every new technology that comes along is worth knowing. It might be worth learning, but that doesn't mean it's worth knowing.

            As a developer, you have to update your skills along the way, if for no other reason to keep you ability to learn and improve going. I've seen too many times where we've had an inflection point (e.g., moving from Fortran to OO) and you can see it in the eyes one of the developers: I'm not g

      • Yes, but somebody had to do the proving

        somebody else can do it - somebody who isn't trying to make a product that will last. Startup type people who will bang something out and then, if it proves successful, rewrite it in boring technologies anyway.

        I think the simplest way is just to use boring technologies anyway, if you consider anything that has been around for a few years becomes either old and boring, or dead and unused.

        • somebody else can do it - somebody who isn't trying to make a product that will last. Startup type people who will bang something out and then, if it proves successful, rewrite it in boring technologies anyway.

          Startup types will use whatever technology lets them shortcut their way to being first to market. Once it's up and running they move on to the next startup and leave it to the new owners to figure out how to implement it using a boring technology that will actually scale and be a viable business.

    • Mature technologies are proven. They've gone through their growing-pains. They may have limitations, but those limitations and workarounds are usually well known by seasoned professionals. There's a reason why COBOL, Fortran, and RPG are still in use in business applications almost sixty years after their initial development, because they reliably work.

      I've tried to work with NodeJS projects for production. It's a nightmare. NodeJS itself is revised too often, the actual project is revised too often, and the dependencies became a nightmare. It's not mature enough and not worth it.

      I'm not disagreeing with you, but I thought you'd find it funny to know that IBM is now building products with NodeJS. (And other even more exotic bleeding edge stuff...)

  • by El_Oscuro ( 1022477 ) on Monday March 30, 2015 @09:29PM (#49376589) Homepage

    In about 1996, Oracle introduced the "Oracle Webserver", allowing you to serve dynamic webpages generated from stored procedures in the database. The beauty of this is that all of your website code is in the database, making it centrally managed and all application security logic is enforced by the database. The webserver is just a dumb client with no code, and has no permissions on any database tables.

    In 2001, it was now a mod for Apache and as since been opensourced (mod_owa). I convinced our client try it for a central website that we were developing, as the middle tier crap they were using didn't work. That system went live 2 weeks later with a few very simple webpages. It has been in production ever since and the website has over 50k users and 20+m hits a day.

    • I tried very hard to convince my manager that we should do this on a project that used DB2. She was adamant that we would have to write the web services with the full Java stack. Hundreds of thousands of lines of java later (complete with maven, spring, hibernate, ad nauseum) she is no long with the company and the project is cancelled.
    • by dwpro ( 520418 )

      The beauty of this is that all of your website code is in the database, making it centrally managed and all application security logic is enforced by the database.

      Ah yes, the beauty of non-version controlled code stored as giant strings in the bowels of a database with the most powerful of languages (pl/sql, of course) to grease the gears. I bet it's a complete joy to use.

  • Web is a mess (Score:5, Insightful)

    by Anonymous Coward on Monday March 30, 2015 @09:35PM (#49376615)

    I've recently been getting more heavily into javascript (proper apps, not just UI animation snippets). The whole scene is a mess. You try to learn about good code structure and you've got crockford saying use constructs to simulate classical OO and then a whole lot of other coders giving you really good reasons to use prototypical inheritance and stop trying to simulate a classical language. Then a whole other bunch are telling you to use coffee script but others point out the difficulties debugging it so then you should use typescript because it will eventually be ecmascript6. Once you get your head around the code structuring options, you then have to decide whether to just use jquery or an mvc like ember or angular. And when you choose a shiny new bbc because it is easy you realise that two way data binding makes your code super slow and start having to hack away at it to get it working on a mobile targets. Oh and don't forget the TDD framework unless you go for BDD because that is the new thing. And then do you use the closure compiler, requirejs for amd or should you even use amd at all.

    I will happily go with tried and tested, if only web developers would stop reinventing things every six months.

    • by Shados ( 741919 )

      I had that discussion recently at work.

      The problem with the JavaScript scene, is that there's basically 2 communities.

      One community is actually doing javascript, and trying to find the best ways to go at it, improving on what has worked, using the strength of the language and building on top of it, etc. This is where things like Express, Kao, Babel, Lodash, Bluebird, Mocha, Browserify/WebPack/SystemJS, Aurelia, etc come from.

      Then there's the other group, who hates JavaScript, and is basically going: "Hey, p

  • by shri ( 17709 ) <shriramc@nOspam.gmail.com> on Monday March 30, 2015 @09:37PM (#49376627) Homepage

    I think it is important enough to have atleast one 'skunk-works' type project that every developer needs to work on, just to keep up with what will be boring a year or two down the road.

    I avoided "not boring" for a couple of years and for the last month, while I look at hybrid mobile apps, I am stunned by my lack of knowledge and the abundance of terms, concepts and technologies that mean nothing to me ... angular, ionic, grunt, promises, JSX, reactjs, compass, gulp, firebase... the list could go on and on and on, these are just things I've started researching over the last few weeks, to make sure I make the right choice.

    Every organisation needs a "not boring" slot of time for their developers. Not for product that needs to ship NOW.. but for stuff that may need to ship next year.

    • by Lodragandraoidh ( 639696 ) on Monday March 30, 2015 @10:03PM (#49376763) Journal

      Every organisation needs a "not boring" slot of time for their developers. Not for product that needs to ship NOW.. but for stuff that may need to ship next year.

      /agree/

      Except I would add: "may never ship at all."

      The key point here is you aren't betting the company on it, but you still should be doing it. Every company should encourage innovation - and even if the company isn't willing to bet any cash on it. Another way is to encourage your developers to spend some time on their own personal FOSS projects. What this gives you is experience - and from a risk vs. reward perspective, success is attained not by how much working (boring) code you produce, but really how many times you try something that fails, and get up again and keep pushing on with new/modified ideas based upon this experience giving your customers real value. Companies without this perseverance will fail, or at best will be mediocre.

      On the flip side - if your core business (the part that you are trying to show your customers you are innovative and a leader in) becomes too boring - and by too boring I mean while it may 'work', it may not do what a customer really wants/needs - then you run the risk of losing those customers to someone who will try and be willing to fail.

      Just like all oversimplified prescriptions, the article's concept does not take into account the nuances of business goals, risk aversion level, available human factors and skills, and so on.

  • by tsa ( 15680 ) on Monday March 30, 2015 @09:37PM (#49376633) Homepage

    It's like Rincewind said: "I like boring. It lasts."

  • by plopez ( 54068 ) on Monday March 30, 2015 @09:38PM (#49376639) Journal

    This basically sums up things I've said over the years and thought about. You and your team have a problem to solve. Anything that gets in the way of solving that problem is the wrong solution. Learning a bunch of new tech looking for a silver bullet or because it is 'kewl' is the wrong answer. There is the learning curve to consider as well as the instability inherent in a new tool set which needs to be understood when making these decisions.

    What is even more distressing is when you see bad ideas return like bad pennies, network databases are now graph databases for example. ACID compliance sacrificed for 'speed'. Having to write you own threading management code. Those immediately pop into my mind. Sure, there may be some short term gains but what about 5 years from now? After a huge investment throwing something away and replacing it becomes difficult and expensive. I am looking for the citation but I once heard that the maintenance costs of software far outstrip development costs by about 10 to one.

    My advice is to first learn the problem domain which includes keeping a long term view in mind, then pick the tool set with a bias towards the tired and true workhorses. Spend less time thinking about your tools and more time solving the actual problem.

  • I concur! (Score:5, Funny)

    by Rogue Haggis Landing ( 1230830 ) on Monday March 30, 2015 @09:41PM (#49376651)
    As someone who has a lot of Perl on his resume, I heartily endorse companies hiring people who work with boring old technologies!
  • There's a reason I choose Debian Stable for my servers.

  • If your developers are really excited about the stuff they are doing then chances are the ops people looking after the 'finished product' (note the quotes, please) are going to have 'exciting' jobs (again, quotes).

    • by Anonymous Coward on Monday March 30, 2015 @11:28PM (#49377079)

      Yes. I know this for a fact. I'm going through this right now.

      Oh, this new NoSQL database is SO fast and wonderful. Except you can't get it to replicate without an Enterprise version, the price of which no one actually calculated into the cost per user budget. Because it's free and open source, except when it's not.

      And you need to have at least three servers to run it even without replication. And no, I am not talking about sharding. I mean running a standard one instance of this garbage requires three instances.

      Mind you, if you want NoSQL, there are versions out there that have replica sets for free and somehow manage to complete all standard operations with only one server. But we can't use those. No. They're too boring and predictable and STABLE. Not exciting at all.

      Not blaming the current developers, who are left with the pile of shit that the other developers made while having all sorts of fun trying shit out and making everyone else figure out how to actually make it *work*.

      The last job, they were circling the toilet bowl because we couldn't finish features. Yet their brilliant idea was to switch their technology, and even change from svn to git, and also chef to ansible. This for no discernible reason, other than the fact that it just seemed like a good idea to them at the time.

      Bear in mind, I understand why you might want git or ansible or whatever new libraries, but I'd think that we could wait to redesign our whole build process and switch to a new version control system until after we had enough finished features to attract a customer. Or something.

      A lot of good people lost their jobs because some architects and a certain CTO wanted to wank off about how bleeding edge they were. Of course, that dumbass still has a job. I hear they're considering a mobile app now. Or something. Good luck with making an app when you laid off all the testers.

      With all that talk, you'd think I had gotten laid off. Luckily I managed to get the hell out, but all the people I worked with there got canned a few weeks later. And none of them were fuck-ups. That is the price of not understanding how to maintain a solid foundation to build a project on.

      So yeah. Boring. Functional. Boring tech behind your app or site doesn't make it a bad. Bad design does that. Lack of features does that. Failure to understand operating an application on something more complex than your MacBook does that.

      The fact that you using the latest thing does NOT make your app good without you knowing what the fuck you are doing.

  • Townsend wrote about a powerful idea, of the perfect note. Clapton, who crossed paths with Townsend, preferred a simple guitar lick to communicate his ideas. I started as a business consultant with software skills, and I've always considered -- even now as a consulting developer -- a line of code to be the last resort when all else fails -- because of the cost involved. Back before the concepts had buzzwords, I advocated 'just in time' development over 'just in case', and that if you're writing a lot of cod

  • by mtippett ( 110279 ) on Monday March 30, 2015 @11:42PM (#49377115) Homepage

    The same thing happens with the hope for the "next generation" product solving all the ills of the current generation. Or the assumption that the code you have inherited was created by fools a number of years back.

    The reality is that software has a set of maturity related bugs and a set of structural, intractable issues that are related to the design and architecture of the system. Each piece of software has it's unique set of intractable issues.

    Software that has been in production has typically reduced it's maturity related bugs. The software built on top or that integrates with it is built around those intractable issues. When you move to a new piece of software - either a new architecture or the "groundbreaking ng version of XYZ", you end up with swapping a set of *known* intractable issues, for a set of *unknown* intractable issues plus a set of maturity related bugs.

    Similar to TFA, the risks of old+known vs new+immaturity+unknown needs to have another factor similar to "value-add". If the value-add *really* adds a lot of stare the risks in the eye and march forward. If the value add is marginal, make sure the meta-benefits (performance, maintainability, etc) are clear and understood, otherwise you may be facing a train wreck of an upgrade.

    Seen it many times, always wary of the ngXYZ project...

  • When it comes to offerings from Oracle or Microsoft, you in fact want to go with an older, more proven solution that is still supported for long time. But with open source, this will get you burned because all the developers got bored and went to work on something else. With newer projects, there will be bugs but also people fixing them, often quickly and for free. As far as comparison between the two, it comes to scale. If you are lucky enough to create a popular consumer product, at some point costs of pr

  • by GerryGilmore ( 663905 ) on Tuesday March 31, 2015 @12:19AM (#49377225)
    I'd once written what I thought at the time was a fairly simple C program to interface with a medical lab system, calculate the checksum (a very, very basic CRC), and pass the results to a file. For the record, I'm a self-taught programmer who started with the Data General Nova assembler, but I digress....Several years later, I happened to meet a programmer who'd inherited my code and, basically, said that it was the best commented, self-explanatory code he'd ever seen and later changes were really easy to make. At the time, I'd just written a device driver was so feeling all punky, but later I realized that what that dude had told me was the highest compliment I could ever receive. $.02 brothers and sisters....
  • "Let's say every company gets about three innovation tokens."

    Bullshit hypothetical statements are bullshit.

  • What he suggests has a lot of merit. On the other hand, there are so many companies languishing under inappropriate technology whose problems would be solved if they weren't so boring. Applications that would be transformed if they only used an object database for example. Business logic that would actually be maintainable if they used a functional programming language. Unmaintainable COBOL that would benefit from an object approach. Yes, there are a lot of times you'll ship something faster by being boring

  • Being on the bleeding edge is expensive. Who knew?

    Most of the time going for the already-proven technology that solves the problem will provide the best value.

  • No, thought not. IMHO a classic - almost, in fact, the canonical - example of boring technology that's good because it's boring. Look at all the criticisms of Ada, and you will find that most of them boil down to, "It's not so much fun and doesn't make me feel so good". But that depends on what makes you feel good. As many qualified people have remarked, if you are flying in an airliner you really want the avionics to be written in Ada, not C++ or Ruby or Python. Why? Because you're a lot more likely to sur

  • Now if only he can come up with an easily remembered acronym to remind people that they should keep these things simple as much as possible, or else they are stupid.

  • Boring technologies have usually been around awhile and there is usually a reason for that. Typically they are pretty good for what they are being used for. As a result there are usually a lot of support out there as well as large code bases. Lots of documentation. Resources not only in libraries, code, docs, but also in staff that understand the technology, so it is easier to bring someone in, have them understand what is there, and make what changes may be necessary quickly without a lot of downtime. So y

    • Also I forgot, because the tech has been around for awhile, they also usually have better integration capabilities, as other technologies may already leverage it, and the connectivity is understood and well documented...

"It doesn't much signify whom one marries for one is sure to find out next morning it was someone else." -- Rogers

Working...