Last March we held a TODO Group track at Open Source Leadership Summit focused entirely on sharing best practices for businesses managing and building out open source programs. More than a dozen open source program leads and other leaders from companies shared their tips and best practices at the event.
To help companies inform and improve their open source practices, we here at the TODO Group have ramped up our knowledge sharing this year and are offering more free resources by open sourcing a set of living open source guides for the enterprise to help you learn more about setting up an open source program. Topics include:
In an entertaining keynote presentation at Open Source Summit in Los Angeles, Dan Lyons, author of Disrupted: My Misadventure in the Start Up Bubble, related his experience working at a tech startup and explained how that experience changed his mind about open source.
Lyons admitted to being famously skeptical about open source and Linux when he was a journalist covering tech for Newsweek. For example, he thought Richard Stallman was too extreme, too radical, that his ideas weren’t practical. But, then Lyons was laid off and decided to go to work for a startup. The company had every startup cliche imaginable — dogs in the office, bean bag chairs in the conference room, an open office plan, sales bros doing daily pushups in the lobby.
“It was like a frat house mixed with a Montessori kindergarten and a Scientology compound,” Lyons said.
“For a long time, I didn’t know what my job was,” said Lyons, “but I did know the way to succeed was just to love the company, just be super enthusiastic.” The company was so super positive that when they fired you, they called it graduating. And, they graduated a lot of people. Nobody, however, thought the turnover was a problem; they were proud of how well they fired people.
According to Lyons, that’s like proposing marriage and saying, “by the way, when we get divorced, I’m really good at it. It’s gonna be a great divorce.”
The Precariat
Lyons started to realize that something was changing in the industry in terms of how people define work, how they do work, think about work, and even why they work. He sees people returning to the work arrangements of 140 years ago, rolling back a century’s worth of worker rights. And now people in Silicon Valley brag about the long hours they work, celebrating their own exploitation. The term economists have for this new class of employee is “The Precariat” — people who have precarious employment, who don’t have benefits, who don’t know how they’re going to pay the bills.
“The rising tide is rising, but it’s not lifting all boats,” said Lyons. People are at work playing beer pong and not noticing what’s being taken away. Things that workers used to take for granted — like security, stability, and dignity — are being taken away. And, all the focus on fun and games is a magician’s trick, a misdirection to keep employees from noticing.
Motto of the New Economy
Why? Lyons said the key can be found in the motto of the new economy, which is:
Grow fast
Lose money
Go public
Cash out
“Every bad thing springs from this business model,” explained Lyons. If you don’t make a profit, you can’t take care of your employees. Moreover, if you don’t intend to make a profit — if you know you’re never going to make a profit — you have no interest at all in taking care of your employees.
The Precariat know that something bad is happening. Silicon Valley, however, is willfully blind to the problem they’ve caused. For them, it’s all about escape, said Lyons. They’re making fantastic plans to take their money and go to their private island, or New Zealand, or Mars. Meanwhile, they’re stepping over homeless people on the way to work.
They don’t want to take responsibility for the problem they created, which, Lyons said, “is the long way of getting to the point that Stallman was right the whole time. This is what I finally realized 20 years later.”
Lyons still believes that we can make the world a better place, that we can abandon the new model. He said the reason he loved covering technology was that it was an industry that had lifted up thousands of people and created prosperity for entire communities. Now, that industry has been hijacked by people who just want to get rich quick.
But, he said — addressing the audience at Open Source Summit — “you guys, the people who build things, who build companies, you’re the ones who can fix it.”
Zemlin said that for enterprises to make the most from open source they need to participate in creating open source: Unfortunately, “Organization still don’t know how to be a participate.”
“Today all software development is influenced by open source,” Zemlin said. “Just as projects are looking to create communities to sustain them over the long term, corporations are seeking to better understand how they can work with and contribute to open source. The new guides will help more organizations directly engage for the benefit of the broader community.”
Over the past decade, Bluetooth has become almost the default way for billions of devices to exchange data over short distances, allowing PCs and tablets to transfer audio to speakers and phones to zap pictures to nearby computers. Now, researchers have devised an attack that uses the wireless technology to hack a wide range of devices, including those running Android, Linux, and, until a patch became available in July, Windows.
BlueBorne, as the researchers have dubbed their attack, is notable for its unusual reach and effectiveness. Virtually any Android, Linux, or Windows device that hasn’t been recently patched and has Bluetooth turned on can be compromised by an attacking device within 32 feet. It doesn’t require device users to click on any links, connect to a rogue Bluetooth device, or take any other action, short of leaving Bluetooth on. The exploit process is generally very fast, requiring no more than 10 seconds to complete, and it works even when the targeted device is already connected to another Bluetooth-enabled device.
“Just by having Bluetooth on, we can get malicious code on your device,” Nadir Izrael, CTO and cofounder of security firm Armis, told Ars. “BlueBorne abuses the fact that when Bluetooth is on, all of these devices are always listening for connections.”
One of the first items discussed when companies start using and leveraging open source is the determination of what, in their IP portfolio, is the unique differentiation between themselves and their competitors. What is, in other words, their “secret sauce.” Companies can then use open source to allow them, and their development, to focus on their secret sauce and to consume, or contribute/donate, non-differentiating software to the open source community. This allows companies to focus their time, talent and resources on those aspects of technology that provide the most innovation to them and their customers.
Some companies, known as Open Core companies, also leverage the idea of “secret sauce” in that they release their code under an Open Source license, but sell “Enterprise Extensions” as commercial products, and keep that technology private and confidential, as their own secret sauce.
But the most important “secret sauce” in Open Source is also the most unrecognized and most misunderstood. Ironically, science fiction understands this secret ingredient better than most.
Red Hat’s product offerings are all built upon open source projects—they all are derived from one or more upstream, community-based open source projects. Red Hat’s product managers need to have a good sense of what is going on in their respective upstream open source projects to enable the product’s continued evolution based on the strength of the community and collaboration in the project. In addition to Red Hat’s own needs, the explosion of products and services that use the hundreds of thousands of open source projects to drive the technology revolution calls for a coherent, repeatable and objective tool/method to ascertain how a project is doing.
Enter Prospector, a tool we built internally at Red Hat to help measure this and that we now have contributed to the Linux Foundation to help form the basis of the new CHAOSS project.
A whopping 48 percent of developers say they’re most productive between 8 a.m. and noon, with 21 percent listing noon until 4 p.m. as their best hours. As for all-nighters: only 5 percent indicate 8 p.m. to midnight as a high production time, with only a few more, 8 percent, saying they’re at their best between midnight and 4 a.m.
That’s one of many takeaways from a new survey, aptly titled The 2017 State of the Modern Developer, that was conducted by research firm Coleman Parkes for the software analysis and measurement company CAST. In all, 500 developers in four countries — USA, UK, France and Germany — were surveyed. According to CAST, the research was conducted “to learn more about the motivators and behavior of modern developers, in addition to their attitude towards code quality.”
One of the hot topics right now in the web development world is functional programming in the language of the web, JavaScript.
Functional programming encompasses a whole host of mathematical properties and phenomena that is beyond this post, but what I am going to address here is how to write a a few functions with nominal functional programming.
This is going to be a series. I am currently researching these topics as I go along and what I find excites me. I will be digging into these topics, each array method bit by bit. You can find some more of this on Steve Smith’s blog Funky JavaScript.
Important Concept: Higher Order Functions
One of the best and worst parts about JavaScript is that you can pass functions into other functions. This can lead to beautifully expressive code and sometimes bugs.
Kubernetes is the hottest thing to hit containers since…Docker. That’s faint praise, given that Docker barely burst onto the scene in 2013. But, given the pace of enterprise infrastructure innovation these days, four years may be all the limelight one gets. As such, it’s critical to make the most of an opportunity, which Kubernetes has done by delivering great code and, as I’ve called out, superior community.
What hasn’t been as clear, however, is how Kubernetes does community so well. Google nailed the mechanics from the start, choosing to push the code to the Cloud Native Computing Foundation, rather than going it alone (as Docker and other open source projects have done). But a less-acclaimed feature of Kubernetes’ rise is the incredible developer advocacy that powers it.
My Lenovo T400 was already old when I bought it as a refurb four years ago. It’s still ticking along nicely with a variety of Linux distributions. Here are the details..
About four years ago (Nov 2013) I bought a used, refurbished Lenovo T400laptop computer and docking station. It was already about four years old at that time (most of the original product announcements and hands-on reviews I can find are from 2009), and another four years have gone by now, so I think it would be useful to have another look at it and see how it is holding up.