Need someone to lead product management at your software company? I build high-craft software and the teams that build it. I'm looking for my next opportunity. Check out my resume and get in touch.

Adam Kalsey

This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Development

Clearly marking your staging server

21 May 2003

Web developers often have development, staging, and production (live) servers. If you’re like me you typically have several browser windows open at a time, some opened to the staging server, some to dev, and some to production. And you probably sometimes open the wrong browser window and start testing, finding it hard to figure out why the change you just made on the staging server doesn’t seem to be appearing.

What you need is a way to make it easy to see which server you are on. Create an include file at the top of each page on the site. On the staging and development servers, the include file consists of a big banner at the top of the page with a colored background and "Staging server" or "Development Server" in big letters. The banner also has links to the other two servers. On the production server, the include file is empty. Now just make that you set up your source-control software to ignore the include file (you are using source control software, aren’t you?) and you’re all set.

As an alternative, you can also set your include file up to conditionally display the banner depending upon what server you’re on, but I’ve found that can get messy when several developers are running the code in their own local development environments or when you have multiple, load-balanced production servers.

Recently Written

Decoding Product Leadership Titles
Mar 18: Not all product leadership titles mean what they sound like. ‘Head of Product’ can mean anything from a senior PM to a true VP. Here’s how to tell the difference.
What branding can teach about culture
Jan 8: Culture is your company’s point of view in action—a framework guiding behavior, even in the unknown. You can’t copy it; it must reflect your unique perspective.
Think Systems, not Symptoms
Dec 15: Piecemeal process creation frustrates teams and slows work. Stop patching problems and start solving systems. Adopting a systems thinking approach helps you design processes that are efficient, aligned with goals, and truly add value.
Your Policies Aren’t Your Culture
Dec 13: Policies guide behavior, but culture is the lived norms and values of your team. Policies reflect culture -- they don’t define it. Netflix’s parental leave shift didn’t change its culture of freedom and responsibility. It clarified how to live it.
Lighten Your Process Burden
Dec 7: Everyone hates oppressive processes, but somehow we keep managing to create them.
Product Add-Ons Are An Expansion Myth
Dec 1: Add-ons can enhance your product’s appeal but won’t drive significant market growth. To expand your customer base, focus on developing standalone products.
Protecting your Product Soul when the Same Product meets New People.
Nov 23: Expand into new markets while preserving your product’s core value. Discover how to adapt and grow without losing your product’s soul.
Building the Next Big Thing: A Framework for Your Second Product
Nov 19: You need a first product sooner than you think. Here's a framework for helping you identify a winner.

Older...

What I'm Reading