Highlighting and sharing patterns to enable new approaches and increase velocity on old applications. Just as a car undergoes a binary conversion from “new” to “used” as soon as it leaves the lot, so do custom applications.

DevOps: Transition the Path to Production

Multiple projects with automated handoff to mitigate generic roles

DevOps: Transition the Path to Production

When transitioning from classic methods to Agile and DevOps, the gatekeepers can feel stuck in limbo. The first step to easing the transition for security reviews, change management, and independent verification is to give them a place they control. As of GitLab 13-ish, the existing roles do not meet this need, despite the merge request approval with branch, tag, and environment protections.

This article lays out a 2 project workflow with an automated merge request handoff to support the access levels needed for segregation of duties with Auto DevOps.

[Read More]

iPad and Code-Server in Kubernetes Workflow

Building software with a comfortable device and capable tools

Pushing the limits of mobility and performance has become easier now that the iPad Pro has the Magic Keyboard and Visual Studio Code can be web-based as code-server.

TL;DR: It’s pretty nice but has some shortcomings. This article covers both the workflow and configuration.

[Read More]

Kubernetes Problems to Solve

GitLab's delightful Kubernetes development workflow

One of GitLab’s strengths is creating productivity-boosting constraints that positively impact system architecture and DevOps cycles. This is very clear in the Kubernetes-powered workflow, but discovering this can be impossible if an org is already locked into an ops-focused Kubernetes deployment.

Also, Kubernetes is entirely optional so don’t force it before the operations team is ready. Avoid ClickOps, even if that means delaying orchestration.

[Read More]

Approaching Data

Benefits of modernization and strategy to get started

The relational database approach where all data is normalized and business logic runs in stored procedures creates maintainability problems that create unlimited risk and cost over time. Every year of continued database operation puts the product and organization further behind.

[Read More]