Need someone to lead product management at your software company? I create software for people that create software and 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

Freshness Warning
This blog post is over 21 years old. It's possible that the information you read below isn't current and the links no longer work.

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

Micromanaging and competence (Jul 2)
Providing feedback or instruction can be seen as micromanagement unless you provide context.
My productivity operating system (Jun 24)
A framework for super-charging productivity on the things that matter.
Great product managers own the outcomes (May 14)
Being a product manager means never having to say, "that's not my job."
Too Big To Fail (Apr 9)
When a company piles resources on a new product idea, it doesn't have room to fail. That keeps it from succeeding.
Go small (Apr 4)
The strengths of a large organization are the opposite of what makes innovation work. Starting something new requires that you start with a small team.
Start with a Belief (Apr 1)
You can't use data to build products unless you start with a hypothesis.
Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.

Older...

What I'm Reading