Tag: Evergreen
-
Microservices vs. inner source
I just listened to Eberhard Wolff’s BED-Con talk on microservice-based system architectures, which he prefers to call Independent Systems Architectures (ISA). One purpose of calling it ISA is to emphasize that there should be no common data model and no shared reusable libraries between microservices. Obviously, by discounting reuse, ISA may increase development speed short-term…
-
The 120 seconds open source pitch
I often have to “sell open source” and the pitch for this is ever changing. Here is the current one; it stands at 120 seconds and is aimed at the German Mittelstand. Any feedback is appreciated! “Software is eating the world” says a Silicon Valley venture capitalist. This is not just American hyberbole. Not only…
-
Reasons for why companies are getting serious about open source licenses 1/4
The times are changing: More and more companies are finally taking stock of the open source code embedded in their products. The main driver is to be (finally) compliant with the requirements of the licenses of the open source code. I see three main reasons for why companies are finally shaping up: Occasionally, due diligence…
-
Ten years of inner source case studies (video)
Georg Grütter of Bosch recorded my keynote at the Inner Source Commons summit in Renningen, Germany, on May 16th, 2018, and put it on Youtube. Please watch it below (original video, local copy). According to Georg, the video is licensed under CC BY-SA 3.0 (for the Bosch part) and I agree (for my part). Hence…
-
The fiercer the competition, the more companies open source
How come that companies like IBM, Oracle, and Microsoft are leading so much open source these days? How is it possible that they harmoniously (most of the time anyway) collaborate with each other at the Apache Software Foundation or even Linux Foundation, while they fight each other to the bone in front of the customer?…
-
Code of conduct for code reviews
On Twitter, @arkwrite suggested that a code review should always say something nice and @chaos_monster commented that we need a code of conduct for code reviews. All of this makes sense to me, however, I suggest that we first have a general code of conduct of productive discussions (and most companies have something like it).…