WHY IT MATTERS: Digital Transformation

Common characteristics of microservice architectures that we saw in the field:
- Componentization via Services
- Organized around Business Capabilities
- Products not Projects
- Smart endpoints and dumb pipes
- Decentralized Governance
- Decentralized Data Management
- Infrastructure Automation
- Design for failure
- Evolutionary Design

We are in the midst of an open source renaissance. But how do you turn an open source project into a business? a16z's Peter Levine and Jennifer Li cover the complete go-to-market from community management to enterprise sales.

Although writing code once sounds like a great bargain, the associated overhead made the cost of this approach outweigh the benefits (which turned out to be smaller than expected anyway). In the end we no longer share mobile code via C++ (or any other non-standard way) and instead write code in the platform native languages.
In addition we want our engineers to have a delightful experience and to be able to contribute back to the community. This is why we made the decision to align our practices with industry standards.

Inovation has always been part of the Amazon DNA, but about 20 years ago, we went through a radical transformation with the goal of making our iterative process—"invent, launch, reinvent, relaunch, start over, rinse, repeat, again and again"—even faster. The changes we made affected both how we built applications and how we organized our company.

Succeeding is no longer just about who’s able to build the technology, or who’s first to market. It’s about who’s got the best experience.

In this article, we discuss the advantages and disadvantages of coupled, decoupled, headless, and hybrid CMS architecture.

One of the many challenges with building or refreshing a website is the selection of a Content Management System (CMS). Despite our best efforts the CMS can often be a source of difficulty in a project, but there are alternatives. Read about the approach we took on www.thoughtworks.com to developing functionality to support content management in an incremental fashion.

CONCLUSION

This article has detailed an incremental approach to developing a content managed web application, in contrast to the adoption of a CMS at the outset. While there are the costs associated with developing functionality which you could get “off the shelf,” these are offset by some of the advantage of this approach – flexibility, simplicity, control, obviating the need to learn a bespoke framework and above all being able to move in small steps from a simple static web site to a managed one.

We applied the editing-publishing separation
pattern in building a two-stack CMS to support a global
readership while supporting complex coordination of legacy
editing tools. 

When content volume is low and only few trained people are responsible for content creation and maintenance, any added complexity of a two stack CMS isn't worthwhile. Such complexity makes it harder for content creators to learn how to use it and adds significant effort in system maintenance. (Although this may be mitigated by tools that are designed to work in this style.)

At LinkedIn, we use machine learning technology widely to optimize our products: for instance, ranking search results, advertisements, and updates in the news feed, or recommending people, jobs, articles, and learning opportunities to members. An important component of this technology stack is a knowledge graph that provides input signals to machine learning models and data insight pipelines to power LinkedIn products. This post gives an overview of how we build this knowledge graph.

A curated list of 700+ engineering blogs.

For the past five years, our Android project has maintained a similar package structure from when it was first created in 2012. 

We also want to keep our package structure clean. This rethought is about keeping the workspace that we interact with on a daily basis both tidy and organized.

So we set about to rethink the entire package structure of the Buffer Android app. I’m excited to share what our process looked like and all that we learned, and it’d be great to hear your thoughts and questions, too.