Tag: Continuous Delivery

Anarchy, Definitions, and Parallels to Continuous Delivery

Anarchy, Definitions, and Parallels to Continuous Delivery

by and | God, Government, Leadership, People

We’ve talked about Anarchy before, in part how it’s an incomplete “plan” for a political system. Twitter is sort of a hub of conversation regarding Anarchism and Libertarianism, and there have been some increasingly interesting arguments there lately, with people making some of those same points and arguing about what Anarchists actually want as an ideal state.

You can see one example in this thread:

https://twitter.com/Wesley_Gest/status/1386402544591724547?s=20

The argument can mostly be summarized like this:

Nice little farm - 9GAG
L: Except I don’t want chickens, because I’m allergic to feathers…

The general perception of Anarchists is that they want cities to burn, that they just want to do damage for the sake of doing damage. Anarchists say, over and over, “no, will you just listen” but a lot of people seem to be terrified of a lack of control. And when Anarchists show up and say they don’t want to be controlled and they don’t think that control is the right answer, it’s massively triggering for those people. When people are terrified, they don’t really listen so good…

Ace is one of our favorites on Twitter.

We thought this was great, and important, (and Ace is really good with words in general), but…incomplete. It covers the interaction pieces, or what it looks like to behave as an Anarchist, but we think it’s important to talk about the fact that it starts with accepting something about yourself, and what that acceptance means for the world around you.

Anarchism, to us, is a consistency of feeling and related action:

  1. You do not agree that you yourself need to be controlled, and/or you do not accept others’ control of you.
  2. You have no desire to control others, finding that repugnant and morally wrong. As such, you do not use any kind of coercion (including manipulation) to dominate others to your will.
  3. You resist and speak out against systems of control applied to people by other people.

That’s…it. No fire-throwing, no building-looting, no Molotov-cocktail wielding manifestos. Anarchism is, instead, the confluence of “I don’t deserve to be controlled” and the Golden Rule.

Anarchism is the confluence of “I don’t deserve to be controlled” and the Golden Rule.

We think people who want to steal and burn and smash just like to hide behind “Anarchy” instead of admitting that they are hateful, or really angry, and want to break stuff. Which we get, really, but could you process your feels before acting please?

What An Anarchist Utopia Looks Like by kickassia - Meme Center

If there was no government law against rioting, would you go out and burn down your neighbor’s buildings and businesses? If there were no government laws against doing heroin, would you go out and do heroin? No? Neither would we. Anarchists are mostly against the government’s tremendously violent history, and we just want to make moral laws consistent with state laws: states shouldn’t have the power to harm, jail, and murder people “legally”. We find that to be immoral. Unfortunately, a sober viewing of history shows that that is what all states do.

This is why we are Anarchists.

Continuous Delivery

We talked about how Libertarianism has a lot of overlap, conceptually, with DevOps (link). While talking about this post, we made an additional connection between Anarchism and Continuous Delivery.

One of the things we discuss in our talks is that Continuous Delivery can just…happen when you get enough barriers, bumps, and blockades out of the way of software delivery. Basically, if you remove enough pain points and things in the way, continuous delivery will just happen because developers want to write code/solve problems/deliver on technical business objectives.

Comparatively, to Anarchist good – focus on the fact that someone controlling you is fundamentally wrong, and…if you’re consistent there, you will treat others the same way.

If you focus on the fact that someone controlling you is fundamentally wrong, and you behave consistently with that conclusion, you will treat others the same way.

Remove control and fear about software delivery -> Continuous Delivery.

Remove control and fear in personal interactions -> Anarchy.

Anarchist Jokes

 

God Words, and Love

We’ll leave you with this, that Josh posted:

Tech Leader Summit and ArchConf 2019

Tech Leader Summit and ArchConf 2019

by and | Community, Leadership, Organizations, People, Technology

Before we start the actual post, today is the blog’s 1st birthday! <3 (Our first post.) Thanks to anyone who has been reading, or anyone who will read in the future. We blog because we love it, and we appreciate…well, everything related to it.

Last month, we spoke at Tech Leader Summit and ArchConf, which are conferences from the No Fluff Just Stuff tour. We also spoke this summer at UberConf, which is on the same tour. We had an AMAZING time, and we wanted to record and share some of it for posterity.

…

Read More Read More

Building Alliances – or, Why Security is Awesome

Building Alliances – or, Why Security is Awesome

by and | Leadership, Organizations, Technology

Time to Go Fast

We work with a lot of people who are implementing Continuous Delivery. We see that when various bumps and boulders get out of the way of delivering software stably and rapidly, there’s a strong push to go very very fast. When this happens, there are often barricades put up in the name of security – because traditionally speed and security have been considered enemies. Traditional enterprise IT security would say, you can’t possibly go fast in a safe way, 

…

Read More Read More

Applications are Gold

Applications are Gold

by and | Organizations, Technology

We’ve talked previously about how developers drive organizational success: they deliver the applications by which companies deliver their competitive advantages. Because they are a way for companies to deliver products to customers, those delivered applications are critically valuable. Application development is a lot like extracting gold – it creates value out of raw resources.

Application development is a lot like extracting gold – it creates value out of raw resources.

Gold, wealth, needs to have some amount of protection.

…

Read More Read More

Quick Hits: Coolest New Stuff In OpenShift 4

Quick Hits: Coolest New Stuff In OpenShift 4

by and | Technology

We talked in a previous post about neat stuff that was coming up in OpenShift. We wanted to follow up now that more information is available and 4.1 is GA and quickly break down some of the neatest stuff.

OpenShift 4 is the major version that will bring Kubernetes to being the standard platform: it provides features that let the majority of enterprises build and run the majority of their applications on an open, agile, future-ready platform.

OpenShift 4 crosses the chasm from early adopters to the standard platform for Kubernetes.

Istio (Service Mesh)

What is it: Networking upgrade for OpenShift Applications

Status: Tech Preview as of 4.1

How does it work: Injects a container sidecar to monitor (mostly to say who’s calling who, and how much), secure, and manage traffic. 

Key Features:

  • Transaction tracing, traffic graphs, full-transaction performance monitoring
  • Traffic (outing) control 
  • Rate limiting, circuit breaking

Big Talking Point: OpenShift Service Mesh makes managing all of the services you’re building visual and clear
Business Use Case: Enterprises looking to get visibility into their microservices, AppDynamics and Dynatrace customers.

Red Hat Code Ready

What is it: Containerized Application Development Environment. Tagline is  “cloud-native development.”

Key Features:

  • Single-Click Modern IDE
  • Tight integration with OpenShift
  • Debugging containers on OpenShift is a nice experience

Business Use Case:  Enterprises with poor developer IDES will appreciate CodeReady.

Competitors:  IntelliJ and VSCode

FaaS 

What is it: FaaS/Serverless is an even easier, and more restricted architecture than containers or PaaS. 

Serverless is an alternative to containers. Applications that would be a good fit in a simple container are an easy fit for serverless.

 

Knative

What is it: Kubernetes-based serverless “Application Easy Button” – just write code, forget about packaging. We talked about it in more detail here.

Key Features:

  • An open standard for serverless.
  • Build, scale, and trigger applications automatically
    Big Talking Point: Openshift 4’s Knative solution makes building, running, scaling, and starting applications even simpler.
    Business Use Case: Enterprises looking to turn their long-running (overnight) batch streams into real-time integrations should use Knative and AMQ streams on OCP

Competitors: AWS Lambda, Azure Serverless, Google Cloud Functions. K-Native provides this functionality without vendor lock-in from a single cloud provider.

The Operator Framework

What is it: intelligent automation that can manage an application by defining proper state and automate complicated application operations that using best practices.

Key Features:

  • Kubernetes-native application management
  • Choice of automation: Go, Ansible, Helm
  • Packaged with a Kubernetes application

Business Use Case: managing stateful applications like Kafka and databases, however new use cases show up all the time, such as managing the kubernetes cluster itself (Machine Operators)

Big Talking Point: Operators make managing complex applications in Kubernetes much easier, turning industry-standard practices into automation.

KubeVirt

What is it: Kubernetes-native virtualization. Run VMs on Kubernetes. Basically, this is VMWare for K8s.

How does it work: leverage open source virtualization technology inside a container to run VMs. 

Features: 

  • Run Windows or Linux containers on OpenShift
  • Manage complicated, hard-to-containerize applications alongside the  containerized applications that integrate with them

Business Use Case: ditch proprietary VM platforms and run you containers and VMs on one standard, open platform

What else is neat in OpenShift 4

Cluster Admin is so much easier: 

  • Fully-automated cluster spin-up: AWS install in less than an hour
  • Push-button updates
  • Immutable Infrastructure: RHEL CoreOS are immutable and extremely strong from a security standpoint
  • Nodes as pets: automatic scaling and healing
  • Cluster can automatically add nodes as load increases

Stuff We’d Like to Get Deeper With

Theres’s a lot more coming with OpenShift that we’d like to get hands-on time with:

  • Windows Containers
  • OpenShift Cluster Management at cloud.redhat.com
  • Universal Base Image: https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image
  • Quay and Clair

OpenShift: Still the Best at What it Always was Best At

 

 

 


OpenShift is still the platform we know and love.

  • Secure Kubernetes:  SELinux preventing security problems like the runc vulnerability
  • Fully backed by Red hat, which will be even more stable and well-funded after the IBM acquisition
  • Enabling Digital Transformation: Containers are still the best way to transform IT, and Kubernetes is the best way to enable DevOps and Continuous Delivery
  • Open Hybrid Strategy: Vendor Lock-in sucks. Open standards and great partnerships.

It was recently announced that more than 1000 enterprises across all industries are running OpenShift. 

There are No Maps in Leadership

There are No Maps in Leadership

by and | Community, Leadership

We were talking the other day about our leadership style, and what worked (through trial and error) for us. We came up with four points that we thought were critical.

Josh and Laine’s Plan for World Domination Leadership:

  1. There is no map
  2. Don’t be a jerk (unless necessary)
  3. Be good
  4. Find a partner/community

…

Read More Read More

Plan Replace Me

Plan Replace Me

by | Community, Leadership, Organizations, People

One of the greatest things about being a leader, for us, is building deep, enduring relationships with the people and teams we work with.

One of the hardest things, for us, about being a leader is leaving the relationships we’ve built. This is a sad, painful process. We love people a lot, and we keep leaving, maybe because there are always more dragons to teach people how to slay.

…

Read More Read More

Why Developers Love SonarQube

Why Developers Love SonarQube

by and | Human Architecture, Organizations, Processes, Technology

We’ve seen a lot of tool transitions across a large enterprise, and one of the coolest examples was changing the opinion of the company we worked for regarding source code analysis. We had a tool that was under-licensed, slow, ineffective, and largely ignored. At best, it was a check box labeled “we’re definitely secure, you guys!” that everyone on the ground ignored.

…

Read More Read More

Meta