A recent Harvard Business Review (HBR) article appears to indicate that candid feedback should be avoided; in The Feedback Fallacy, the authors stipulate that this kind of feedback may be damaging. The authors' reference to the current excitement over apps based on 'Radical Candor' and the tendency toward direct, sometimes harsh feedback that is being promoted at a number of companies, seems to lead us away from that approach. But does it?

In this brief post I’ll illustrate how quick it is production-ready serverless environment for any Golang application or API using Apex Up. This post assumes you have AWS credentials configured on your machine, as Up deploys to AWS Lambda and API Gateway.

When designing APIs, it’s important to take a design-first approach to ensure the right API gets built. However, I don’t think the first step should be to write an OpenAPI or API Blueprint document. I think it should be to design a working application.

So, rather than be afraid of not reaching a goal and therefore not setting one, I’ve learned to just set it! And measure against it. And act on it. But that is the spirit of agile, after all, right?

When did we realize that more carbon dioxide equals a hotter planet? You could go all the way back to 1827, when French mathematician Joseph Fourier calculated that the atmosphere, somehow, was keeping the planet warm like a blanket. Or you could go as late as 1938, when British engineer Guy Stewart Callendar gathered data for the first time to show that the Earth was already getting warmer in line with emissions.

But over the last decade, a new answer has come to light: 1856. That’s when amateur American scientist Eunice Foote discovered what we now call the greenhouse effect. Yet we know very little about her. We don’t even know what she looked like.