I got 99 problems but my branching strategy ain't one. Back in the year of 2017. I wrote an article that to some seemed like a dream. I said , and I still do. It's been a few years and now you should, too. I commit to master "But how do I deploy to staging?" you might declare, "not using GitFlow seems unfair!" Don't despair! Don't despair! I'll show you how to turn the implicit into the explicit simplifying your workflow so you can finish it Instead of representing environments using branches you create artifacts using Helm and then schedule the advancements just create a pull request to your codified environment then just wait for JX to do the rest Instead of keeping a mental map of loosely defined entries you're permanent environments will be tersely defined dependencies. Making implicit concepts explicit is the thing to do! To get away from GitFlow I codify my environments and you should too!

Bring In The Bots, And Let Them Maintain Our Code!

A Simple Mistake That Costs Engineers Time and Money

Engineers! Learn how to become a software entrepreneur... click here!

Read My Stories

Too Long; Didn't Read

Make resilience your competitive advantage

If you’re still using GitFlow I feel bad for you son (or woman)

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

Releasing New Versions Should Be Boring. Really Boring.

The Ten Top Cities for Highest Cloud Engineering Salaries

10 Popular Websites Built With Django

10 Best VS Code Extensions to Improve Your Productivity

11 Reasons Software Engineering Will Never Die

Releasing New Versions Should Be Boring. Really Boring.

The Ten Top Cities for Highest Cloud Engineering Salaries

10 Popular Websites Built With Django

10 Best VS Code Extensions to Improve Your Productivity

11 Reasons Software Engineering Will Never Die

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps