“Open-source software and components are important enablers of agility in modern development environments. Practically all developers use open-source components in applications, whether at the front or back end; there is a library for pretty much any stack you can think of. Developers can use these components to make their jobs easier and allow them to focus on organization-specific challenges, including building the core proprietary software features that add value to enterprise applications. Developers who understand open-source security and how to best manage open-source components are more likely to efficiently and prudently use these components when building proprietary software.“
Meet me here: Prague, APC:￼ Activity Pub Conference
What is this? Well, it’s the future…:
“Senior Developer is dying (a definite death) In programming world, too, craft is being lost gradually. A senior developer is losing his / her edge to:“
When you know that you’ve won and you were right for decades
Microsoft announcement: Announcing WSL 2 | Windows Command Line Tools For Developers … :
“Our Future Needs Exponential Leaders These roles—futurist, innovator, technologist and humanitarian—are interconnected and enhanced when knowledge and insights flow between them. The four pillars are a holistic system of learning to imagine, create, capture and scale hidden value in an increasingly complex and dynamic world.“
Leadership Without Management: Scaling Organizations by Scaling Engineers
Reality update: The Flying and The Thud: Mental Health Issues on Agile Teams | Agile Alliance … :
Especially the section on “What Are Typical Symptoms? (And How Can I Adjust for a Coworker?)“
Ein guter Vortrag über Teambuilding und Führung: “Erfolg im Team: So geht Führung” von Bernhard Zytariuk
Money quote: “Die Fehler bei uns Menschen zu finden, das ist total einfach. Wir sind alles Mangelwesen mit großen Unzulänglichkeiten und die zu finden ist wirklich keine große Kunst. Aber die Stärken der Mitarbeiter zu finden, das ist die Hohe Schule. Und die Stärken dann noch zu entwickeln, das ist noch viel wichtiger.”
“In an unexpected report, Bloomberg stated IBM is close to announcing that it will be acquiring Red Hat. The news has been confirmed. IBM is acquiring Red Hat for $190.00 per share in cash. This a total enterprise value of approximately $34 billion.”
“Rometty continued,”Most companies today are only 20 percent along their cloud journey, renting compute power to cut costs. The next 80 percent is about unlocking real business value and driving growth. This is the next chapter of the cloud. It requires shifting business applications to hybrid cloud, extracting more data and optimizing every part of the business, from supply chains to sales.”
… and Jim himself on the Red Hat blog:
“We have barely scratched the surface of the opportunity that is ahead of us. Open source is the future of enterprise IT. We believe our total addressable market to be $73 billion by 2021. If software is eating the world – and with digital transformation occurring across industries, it truly is – open source is the key ingredient.
Powered by IBM, we can dramatically scale and accelerate what we are doing today. Imagine Red Hat with greater resources to grow into the opportunity ahead of us. Imagine Red Hat with the ability to invest even more and faster to accelerate open source innovation in emerging areas. Imagine Red Hat reaching all corners of the world, with even deeper customer and partner relationships than we have today. Imagine us helping even more customers benefit from the choice and flexibility afforded by hybrid and multi-cloud. Joining forces with IBM offers all of that, years ahead of when we could have achieved it alone. Together we can become the leading hybrid cloud solutions provider.”
Here’s the full press release by Red Hat …
… and what you can do about it. http://ncase.me/trust has a great, in fact the best explanation I have seen so far. (From my Leadership presentation).
Reality update: Open source and the demise of proprietary software – Timescale … :
“The challenges with the open-source model
Developing a successful open-source project is not easy As we can see from its history, there has always been a tension in open source: e.g., philosophical licenses focused on preserving “freedom” vs. permissive licenses taking a pragmatic approach. But there are two larger tensions today: (1) how to balance openness with sustainability and (2) how to manage the transition to the cloud.“
We all now this never happens, but it’s good to be prepared.
The Muse explains how to deal with a difficult boss: 10 Brilliant Tips for Dealing With a Difficult Boss -The Muse
“In an ideal world, we would all have fantastic managers—bosses who helped us succeed, who made us feel valued, and who were just all-around great people. Unfortunately, that’s not always the case. But, whether the person you work for is a micromanager, has anger management problems, shows favortism toward one person, or just isn’t very competent, you still have to make the best of the situation and get your job done. To help out, we’ve gathered the best advice from around the web for dealing with a bad boss. Try one or more of these tips to find some common ground with your boss—or at least stay sane until you find a new gig.”
And Workitdaily has a good read about 5 Ways To Deal With An Incompetent Boss | CAREEREALISM … :
“While it can be frustrating to have an incompetent boss, an incompetent boss can seriously damage or derail your career. If they do have a serious lack of knowledge, we know that they can do nothing to grow you as an employee which means any growth will be yours to make happen. Let’s look at the potential damage they can inflict and what you can do to minimize or avoid.“
My friends from Agorum got to the point here (only in German, though) … : Entscheidungsprozesse in einem selbstorganisierten Unternehmen.
“Hierarchie ist keine gute Antwort auf immer schnellere und komplexere Prozesse”
I think this silicon valley image from Brian Solis fits very well to that context … that reflects much more the kind of hierarchies we need: