When we release something to the community, for free, that includes commercial use. If we don't want it to, there are licenses that can make it free for personal use, but not for commercial.

The Wikimedia Foundation made a decision to make their content free for everybody, and to not restrict the usage. Same as GNU, Linux and others. Even if you are making money. Even if we don't like what you do with it. We give it away because that's what we decided to do. And nothing is owed.

It doesn't mean companies (or people) that realize financial benefit can't make a contribution to the cause. Some do. But that's completely at their discretion.

This year I celebrate 20 years as a Perl guy. I have used it continuously, regardless of the languages used predominantly, and it has made me seem to be able to do the impossible, or at least the highly improbable. Thank you, Larry, for sharing Perl.

I don't pretend that Perl is necessarily able to to most things any better than other modern interpreted languages (autovivification notwithstanding), but I come back to it again and again -- partially for the same reasons that I usually start speaking in English. It is my first language, and my most fluent.

Perl 5 has been meeting my needs for literally my entire career. There's probably something in Perl 6 that I might find useful, but I have found that I have about as much desire to break open Perl 6 as any other new language that I have not yet looked at.

It would help my guilty conscience to receive your absolution. Or am I being unreasonable in my continued, pragmatic use of Perl 5 and it's amazing library of modules, both old and new?

Peace be upon you.

I scour the internet for stories about people who aren't thrifty with their money and responsible with their debt. Each time I post, I end with "Another wasted opportunity to save and pay down debt."

No wonder my credit score has suffered. Man, if only I was as smart as those guys.

In my view, nobody should comment on whether anything should be on-premises or not, if they are unable to distinguish between the word "premises" and "premise." Laziness of the tongue or of the quill is not an excuse.

Who says he has knowledge of business? Just because he's 40-something? And a PMI certification? For the love of God. Here comes another useless PM.

Please do not move to management simply because you're "of a certain age" and haven't kept up with technology. The last thing IT folks need is a manager who became a manager for the wrong reasons. "I can't find any other job" is a wrong reason.

I am a 44-year-old Perl developer (turned manager). But I haven't worked at a Perl shop in about 4 years. At my last full-time Perl job, I became a manager (because the team needed a new manager, and I felt I was ready to do it), and then from there I moved to a management job at a .NET shop, of all things. That was weird, but it was eye-opening too. I learned two things at that .NET shop:

1. That there are some useful things in the .NET world
2. That I prefer not to work in a .NET world

From there, I joined a small PHP shop as their CTO. PHP is a bit frustrating for this particular Perl guy, but fortunately I don't have to write much of it. However, we are small and I do write a certain amount of code. I actually use Perl for a lot of the stuff that I write. I hired another guy who writes some Ruby. I also dabble in node.js and some other stuff. It's an amazing time. In fact, it has BEEN an amazing time for our entire careers. Have you done anything with AWS? It completely changed the game. Web services in general? Back to Perl: Moose? Dancer? cpanm?

You are not a dinosaur because of your age. You are not a dinosaur because of your programming language. You are a dinosaur because you have let the world pass you by. Get busy learning: Node, Redis, PHP, Python, AWS. Pick one that sounds interesting and learn to do some cool new tricks. Nobody is stopping you.

While that's a good point, it would surprise me if that much thought goes into it. I assume it's simply a matter of zero-tolerance HR policies for all employees. That's the easiest and least risky thing for them to do, whether it's the right thing to do or not.

I'm an IT manager. The right thing to do is to treat every hire individually, and to examine the circumstances of every case. Not everybody's career prospects should be ruined forever, based on youthful mistakes (I made a youthful mistake or two myself).

I have benefitted from changing jobs every few years, but I never switch jobs after only a year. I'll stay at pretty much any job for a minimum of a year, and I try to stay everywhere 2 years. My career so far has been 1 year, 2 years, 3 years, 6 years, 3.5 years, and 2.5 years. I felt like I stayed at the 6-year job too long. It wouldn't have been too long if I had grown in the right way while I was there, but I didn't. I kind of plateued and stayed because it was comfortable.

And that is the reason why I think switching companies every few years is essential, especially in IT. There are just so many things you will never learn if you don't work at different companies, even if the things you learn are simply how jacked up and ridiculous some companies are. I've been at startups, Fortune 100 companies, and companies in between. I highly recommend giving each company your full commitment for at least a couple of years, but always be willing to move on when you're no longer growing your skills or doing interesting things.

See, this is the attitude. He says his job is to make sure his employees go home every day. He's wrong. While nobody should be reckless with the lives of law enforcement, and it is a great tragedy when the lives of law enforcers are lost in the line of duty, it is their job to protect and to serve the public. It is their job, from time to time, to be injured and/or killed in the act of protecting and serving the community. That is the job. It is voluntary. It is not for the faint of heart, or for the cowardly. It is not, in short, for me.

When the number one priority of law enforcement becomes protecting the life and safety of officers, above all else, then the public suffers. And the lives and safety of citizens have been sacrificed on numerous occasions in the name of protecting law enforcement.

I am not anti law enforcement. But I am deeply concerned about their low tolerance for risk.

I manage development teams. First of all, like it or not, .NET is huge and seems like it will continue to be huge. I don't mind C# and I think Visual Studio is one hell of an IDE. Myself, I prefer to code in Perl or Ruby, and to use vim to code it. But C# and Visual Studio are tolerable. So if you had to choose one to really focus on, I think from a marketability standpoint, that's a good one. It's also a great idea, though, to have a true scripting language in your back pocket (in addition to PowerShell, which is, yes, really cool).

OK, back to the other question: Do you have to be a 7 or higher? Heck no. I find that there's very little "computer science" in what we do in a lot of professional software development. It's a lot of CRUD and knowing how to put various things together (REST plus AJAX plus responsive plus ORM plus third party integration plus memcached plus S3, etc, etc). You don't have to be a brilliant programmer for that. You have to be able to learn quickly, retain knowledge (at least enough to remember what you Googled to do it again), be a good communicator, and be a really good team player.

In summary, I would gladly take a 4 with potential and a great attitude, over a 9 who is a dick. I would do that over and over again. You just need to make sure that you have a few 7s around, but not too many.

Take this for what it's worth, but I find it relevant. I, too, laughed at Microsoft's Surface tablet, and it's dismal sales figures. I was the happy owner of a personal iPad and a work iPad, and I figured that was what the tablet experience was, and what it needed to be.

I was wrong. At least for me, I was wrong.

I have the strange situation of working at a Microsoft shop, as a manager of a development team (though I am an open source guy, by background). The local Microsoft sales office invited several of us to an Azure educational session. Part sales, part hands-on training. I am a big user of Amazon Web Services, and my team uses it as well. So I figured instead of just being an Azure hater, I would come along and do the hands-on walk-through, because it's some dedicated time for some busy people to really dive in and see what all the fuss is about.

But this comment is not about Azure. Azure was fine. I'm still AWS fan, and Azure was just similar enough, and just different enough, that I'm not chomping at the bit to start using lots of Azure.

But here's the thing: They had a door prize. And I won it. It was a Surface with Windows RT. And I love it.

Would I love it as much if it had not been free? We will never know. But all I can tell you is my story.

One might argue that it's stupid for this thing to have a "Desktop mode." But it also has a USB port (shocker!) and supports Bluetooth. I already have a Bluetooth keyboard for my iPad (which I never use), and a USB mouse that I use for my laptop. I put my Surface on it's kickstand, pair the keyboard, and plug in the mouse tongle, and the dang thing is transformed. It's a little laptop. It has Office installed. It has the full Windows version of IE. Yes, I hate IE, and it sucks that there's no Chrome or Firefox for this platform. But the point is that, in a jam, this makes a damn fine little PC.

And then it's NOT a PC. You pick it back up and it's a tablet. And a NICE tablet. The apps are nice. The Reddit app is my favorite Reddit experience, in fact. Netflix, Facebook, etc.

Oh, and the best part... the Surface team designed it to be used with mouse, or a finger. It behaves differently in each case. And it behaves generally the way you expect (want) it to.

So, call me a fanboy. I did not expect to really like it. But I do. I really like it. Anybody slamming Windows 8, and particularly Windows 8 on a table, isn't really giving it a chance. It's really nice.

I'm a big fan of 3D printing, I am. And at the beginning of this video, I just thought this was the coolest thing. Well, except for a couple of things.

Tape measures are widely available and inexpensive.

This one is REALLY short (just over 4 feet), and it was comparable in size to a standard 25-foot tape measure.

Worst of all, it's not accurate. It's off by a 16th of an inch at the maximum length, and it would only get more and more inaccurate, as the length increases.

Other than that, it's perfect :) Oh, it's definitely impressive, and I still find it hard to believe that these sophisticated contraptions are printed already assembled. It's amazing.

Computer Science has its place, certainly, but it's not in every IT shop in America. I've been giving this a lot of thought lately: How do you take those unemployed and underemployed people, whose jobs have basically disappeared, and are never coming back... and intersect SOME of those people (not all of them will be able to do it) with the enormous shortage of talented and capable IT people.

I've come to almost accept, over the last couple of years, that there's such an insatiable demand for IT, and such a shortage of competent IT people, that it's just a reality that we're going to have lots of lots of crappy people in IT, and there's nothing that can be done about it.

But I'm having difficulty completely accepting that. Because I know that the skills that you need to be good at solving technology problems are not extraordinary. I just barely started college, and then quit to join the Air Force. Five years later, I got into the web business (in 1996) and I've had a great career for 18 years. I recently decided to finish my degree, but that's a different story.

The point is: I'm not a computer scientist. There have been a few times in my career when I would have benefited from a CS degree, but not many. Mostly, what I have needed is intelligence, verbal and written communication skills, the ability to quickly learn new things, a passionate interest in technology, the three Larry Wall traits (laziness, impatience and hubris), and an understanding of how users think and act. Editorial skill has not hurt me, and neither has graphic design skill.

While I would be really interested in helping to build an educational program, one problem I have is that I'm self-taught, and therefore don't really know how you're supposed to teach this stuff. But I would love to be part of a workshop where industry folks come together for a week and brainstorm on this topic, or something.

My big sticking point is this: I honestly believe that the one non-negotiable requirement for being a good technologist is intelligence. And this seems to be controversial, because it makes it sound like I'm calling other people stupid. And, well, I am. I really wrestle with this. I wonder how good a web developer you can be if you're not quite smart.

I've heard about that awful EHR (Electronic Health Record) integration effort between the Veterans Administration (VA) and the Department of Defense (DoD) for years. It's a failure of a lot of things, but if open source is even on the list of those things, it's low on the list. At the top of the list is dotted lines and bureaucracy, of course. Heck, IT projects often go off the rails, particularly big expensive ones. Let alone one done for the Department of Defense (DoD). And of course, it's not just the DoD, it's also an inter-department collaboration. Doomed for failure, unless it's managed excellently.

It appears that one big reason that this integration project is so hard is because the VA can't compete when it comes to process and bureaucracy. They don't have nearly as large a budget. This quote is telling:

"The iEHR demise was expected by all, accordingly," one VA source said. DOD officials "outspend, outtalk and outlast us at every engagement. We try to emulate much of their process-based decision-making as if we could afford to. We can't. The overhead is crippling, and we are not funded equivalently."

Source: http://fcw.com/articles/2013/05/01/veterans-affairs-trouble.aspx

It pains me to see any IT project that gets out of control and ultimately fails. I hate it even worse when it's the government. As a veteran, I especially hate to see this one. And as an open source user, contributor and advocate, Oracle blaming that massive failure on open source adds insult to injury.

Not only is this reduction in redundant staff probably appropriate, but this is one of the rare situations in which "synergy" is used in a non-lame, non-stupid way.

When two companies merge, the hope is that the two joined as one company will be more effective than they were when they were working together, but separate companies. Synergy is a reasonable word to describe that.

But unsurprisingly, that synergy does not always happen. You're combining two companies, with two different cultures, perhaps incompatible systems, perhaps conflicting ideals. And you're certainly going to have some redundancy. For example, in each company, you probably have one person ultimately in charge of technology. Now you have two, and have to work that out. You also have one person ultimately in charge of smaller things: The phone system, for example. Now you have two. These things have to be worked out.

A successful merger in which some people don't get laid off would be very surprising.