The Container Landscape, choosing what to do now

A round-up of all sorts of container stacks, and some advice on what to do: Therefore, the key lessons learned from this event (from developer’s perspective): Do not focus on developing code for the container under the hood. Care instead about the business logic. Implement your microservices in a vendor agnostic way. Do not make the same fault as we all did with J2EE / Java EE where all vendors used the same standard specifications, but still offered many vendor-dependent features and “added value” in their specific “standard implementation”.

The Container Landscape, choosing what to do now

A round-up of all sorts of container stacks, and some advice on what to do: Therefore, the key lessons learned from this event (from developer’s perspective): Do not focus on developing code for the container under the hood. Care instead about the business logic. Implement your microservices in a vendor agnostic way. Do not make the same fault as we all did with J2EE / Java EE where all vendors used the same standard specifications, but still offered many vendor-dependent features and “added value” in their specific “standard implementation”.

The Container Landscape, choosing what to do now

A round-up of all sorts of container stacks, and some advice on what to do: Therefore, the key lessons learned from this event (from developer’s perspective): Do not focus on developing code for the container under the hood. Care instead about the business logic. Implement your microservices in a vendor agnostic way. Do not make the same fault as we all did with J2EE / Java EE where all vendors used the same standard specifications, but still offered many vendor-dependent features and “added value” in their specific “standard implementation”.

The Container Landscape, choosing what to do now

A round-up of all sorts of container stacks, and some advice on what to do: Therefore, the key lessons learned from this event (from developer’s perspective): Do not focus on developing code for the container under the hood. Care instead about the business logic. Implement your microservices in a vendor agnostic way. Do not make the same fault as we all did with J2EE / Java EE where all vendors used the same standard specifications, but still offered many vendor-dependent features and “added value” in their specific “standard implementation”.

The Container Landscape, choosing what to do now

A round-up of all sorts of container stacks, and some advice on what to do: Therefore, the key lessons learned from this event (from developer’s perspective): Do not focus on developing code for the container under the hood. Care instead about the business logic. Implement your microservices in a vendor agnostic way. Do not make the same fault as we all did with J2EE / Java EE where all vendors used the same standard specifications, but still offered many vendor-dependent features and “added value” in their specific “standard implementation”.

The Container Landscape, choosing what to do now

A round-up of all sorts of container stacks, and some advice on what to do: Therefore, the key lessons learned from this event (from developer’s perspective): Do not focus on developing code for the container under the hood. Care instead about the business logic. Implement your microservices in a vendor agnostic way. Do not make the same fault as we all did with J2EE / Java EE where all vendors used the same standard specifications, but still offered many vendor-dependent features and “added value” in their specific “standard implementation”.

Getting paid to podcast, trump's possible effects on tech - Coté Memo #20

The long break is coming up - Thanksgiving and then Christmas, the holidays as it were. For sales people, Q4 of course is anything but a break, so hug your sales person. Getting paid, podcast editionI got a few offers sponsoring the Software Definded Talk podcast. It looks like we could get about $75 an episode (split three ways after costs). We're at just north of 2,000 downloads per episode (over a few weeks).

Help me finish this agile PDF, hear @bwhichard complain about Agile - Coté Memo #19

It’s the day before elections in the US. If you haven’t already, go out and vote. Kim and Cormac are up in Ohio block walking to get out the vote, which is amazing. In retrospect, I should have gone with them. I’ll have to remedy that for the next elections, about two year’s time I suppose. Help me finish this PDF Back when it was 37 pages. I’ve been posting some excerpt here and there from this PDF I’m working on: pulling together all the “so, how do we do better software here?

You're not really Agile, airports, hitting yourself & absurd AI TAMs - Coté Memo #18

There's not much to say at the moment, just some travel here and there before Thanksgiving and then Christmas. The end of the year is fun, it cools down and you get to see family. I'm trying to wrap up my big PDF for this year, the "second edition" of my cloud native journey book, check out a new excerpt for y'all below. There's also some content of mine and, as always, fun links.

Keeping sane at the airport

After 10 years of business travel, this is how I cope at the airport: You’ll get there, even if you’re late. Don’t worry about lines, just wait in them. Few people know what they’re doing here, don’t let their stress stress you out. There are no special snowflakes, unless you have a doctor’s note. The word of airline staff is law, you can’t argue against the agent of the FAA.