> my company is based in Oakland. This is like being based in San Francisco, but with fewer microclimates. Rolling up to work in a company hoodie, jeans, a t-shirt from your last company, and a pair of Tevas is A-OK. But the further east you go, the more formal everyone’s business wear gets. Jeans turn into chinos somewhere around the Mississippi, and then into actualfacts slacks. T-shirts become button-down plaid, and then long-sleeve with ties.

Why you’d use it, what it does, the parts, and the additional stuff you’ll need. www.infoq.com/presentat…

Microservices for .Net. thenewstack.io/steeltoe-…

> As a scheduler of containers, Kubernetes does a pretty good job. If you keep it focused on that key task, it can take you miles. As a manager of a large scale distributed infrastructure, it’s not so good. twitter.com/danvelope…

It either means not having to worry about managing your middleware stack and/or a trigger-driven event system. m.subbu.org/contempor…

You use an in-store device or you phone to scan items to buy: > The speed is most visible when a shopper calls up an item on her pre-determined shopping list and is guided to the exact aisle and shelf position of that item. As the shopper gets within range, of say, the jar of pasta sauce she’s shopping for, a food icon that she has selected as her “emoji” of choice appears on the EDGE shelf display — which is helpful when there are dozens of brands of pasta sauce on those shelves.

> The microservice architecture, which breaks complex applications into sets of single-purpose networked components, can be a challenge to manage, as each microservice must be instrumented, secured and locatable in a dynamically reconfiguring network. In addition, multiple copies of microservices may be run in parallel, to meet the demands of a growing demand. Their traffic must be managed as well. > > A service mesh, which attaches a sidecar to each microservice, standardizes and moves the development of these tasks from the individual developer.

> The microservice architecture, which breaks complex applications into sets of single-purpose networked components, can be a challenge to manage, as each microservice must be instrumented, secured and locatable in a dynamically reconfiguring network. In addition, multiple copies of microservices may be run in parallel, to meet the demands of a growing demand. Their traffic must be managed as well. > > A service mesh, which attaches a sidecar to each microservice, standardizes and moves the development of these tasks from the individual developer.

I’m always trying to find a reference to Linda Rising’s cake law. Here it is! Original source: Where there’s cake, there’s success

I’m always trying to find a reference to Linda Rising’s cake law. Here it is! Original source: Where there’s cake, there’s success