Board

No images? Click here In today's analysis, I share another insight we found from our most recent employee collaboration and productivity study.  Also, here is the direct link in case you want to save it to read later.

Plus! Reformatting Competition; Ending Oil Won't End Energy Politics; The Bullwhip Effect in Discounters; Russia's Gold; Negotiating Governance

After years of disputes between AWS and Elastic, the smaller company has now changed access policies to code libraries that are designed to make life harder for developers who aren’t using its commercial products.

"trying to listen to the horribly distorted jazz"

How companies that are successful end up creating new roles and job categories either directly or indirectly

Sean Fanning of OpenView discusses the implications of public market volatility on the software business.

We’ve entered into a period of extreme uncertainty. While it’s impossible to forecast what will happen, Jason Green and Jake Saper share why Emergence looks to previous system shocks to see how the enterprise cloud sector might be affected.

We dug into the data on B2B SaaS purchasing to see what’s really going on.

Gartner's Magic Quadrant research methodology provides a graphical competitive positioning of four types of technology providers in fast-growing markets: Leaders, Visionaries, Niche Players and Challengers.

Plus! Facebook Apologetics; Food Delivery and Unit Economics; More Air Taxis; Business and China

Watch the free video of C J Silverio at JSConf EU!

The benefits of adopting iPaaS, according to Typeform, and other considerations for scaling your tech partner program.

At a technical level, artificial intelligence seems to be the future of software. AI is showing remarkable progress on a range of difficult computer science problems, and the job of software developers – who now work with data as much …

This article is a guest post from Charlie Lougheed, CEO of Axuall.

In network routing, there’s a distinction between control planes and data planes. Control planes dictate how data is routed over the network topology. The data plane is responsible for the actual forwarding of the data packets. The idea of separating these two functions works well for higher abstractions like distributed systems. For a more concrete example, look at a service mesh. The data plane in service mesh has the responsibilities of service discovery, packet routing, load balancing, a

When I first joined Tailscale, I was horrified to learn that “the database” was a single JSON file that was rewritten on any change. We migrated to something better.

Techniques, strategies and recipes for building a modern web app with multiple teams using different JavaScript frameworks.

How to split up your large, complex, frontend codebases into simple, composable, independently deliverable apps.

WMR App

ipse se nihil scire id unum sciat He himself thinks he knows one thing, that he knows nothing There's a meme format that shows a bell curve – the X-axis depicting expertise or intelligence, and the Y-axis the number of people who share that opinion. It's used to show when beginners and experts share the same opinion (often the simplest one), but one that goes against common practice. Here are 16 bell-curve opinions on engineering. Disclaimer: I make no claim on what side of the bell curve I'm

Building APIs is fundamentally hard because it's an unusual UI paradigm. A bit like designing command line tools — you aren't interacting with things like a mobile app. Getting users to that happy path is super important! Here is a quick checklist of...

Many developers use Docker the old-fashioned way -- a docker build and a docker run. Some non-obvious ways to use Docker. As a compiler. I gave a talk at DockerCon back in 2019 about the potential to use Docker as a compiler, and the idea is finally coming to fruition.

There are a few choices when designing an API layer: REST or RPC, binary or plaintext, TCP or HTTP, schema or schemaless? A few of the tradeoffs and an overview of some of the tools. * Schema-driven? You can do this with REST (e.g., OpenAPI/Swagger) and RPC (e.g., protobufs). While having a schema means you can automatically scaffold client/server stubs and enforce message types, it doesn't come for free. The code generation step adds friction to the developer workflow, and developing outside

A pattern I've observed in software configuration of complex systems and that explains why bash scripts are everywhere, even at Google.