Doing software better at the south east’s largest power company. [www.charlotteagenda.com/97827/sko…](https://www.charlotteagenda.com/97827/skookum-tech-talk-duke-energy/)
> In practice, most stakeholders are not interested in detailed diagrams, but rather in one or two high-level diagrams which reflect the modularity and boundaries of the system. Beyond these, for a deeper understanding, the code should be the source of truth, which in most of the cases only developers are interested in. [www.infoq.com/articles/…](https://www.infoq.com/articles/why-architectural-diagrams)
Short plan for getting rid of outsources. [upperedge.com/system-in…](https://upperedge.com/system-integrators/when-is-it-time-to-say-goodbye-to-accenture-deloitte-ibm-or-kpmg/)
> There is also the cost of different people thinking about data differently because they are working with different platforms and not really speaking the same language as each other. I hear about this all the time from customers. They’ll have two people from their own organisation pitch up in a meeting with two different answers to the same questions, supposedly from the same data source.
> But those data sources are being run through different platforms and end up getting corrupted or changed or amended. And so you no longer have a single source of truth in your own underlying data. And that’s a big problem that many enterprises are facing. That is why, I think, for all those reasons, you absolutely see a trend towards consolidation. [www.computerweekly.com/feature/T…](https://www.computerweekly.com/feature/Tableau-CEO-Adam-Selipsky-talks-strategy)
Better predicting, targeting, and driving people to buy shit:
> While the general modus operandi of Google, Facebook et al has been known and understood (at least by some people) for a while, what has been missing – and what Zuboff provides – is the insight and scholarship to situate them in a wider context. She points out that while most of us think that we are dealing merely with algorithmic inscrutability, in fact what confronts us is the latest phase in capitalism’s long evolution – from the making of products, to mass production, to managerial capitalism, to services, to financial capitalism, and now to the exploitation of behavioural predictions covertly derived from the surveillance of users. [www.theguardian.com/technolog…](https://www.theguardian.com/technology/2019/jan/20/shoshana-zuboff-age-of-surveillance-capitalism-google-facebook)
Tips on finding good agile teams in large organizations:
> Are teams delivering working software to at least some subset of real users every iteration (including the first) and gathering feedback? [thenewstack.io/the-u-s-d…](https://thenewstack.io/the-u-s-department-of-defense-on-how-to-detect-agile-bs/)
Financial analysis of in wild with bizarre predictions. It’s hard to see synergies worth paying for in GCP owning Atlassian or ServiceNow. GCP is infrastructure. Plus, sounds like Google staff throw up resistance to buying old school companies:
> In the months before IBM’s mega-deal, Greene formed a close relationship with the Red Hat team, Business Insider reported in December. But she struggled to get the support from her colleagues at Google to actually make an offer, a source said at the time. [www.businessinsider.com/new-googl…](https://www.businessinsider.com/new-google-cloud-ceo-thomas-kurian-acquisitions-2019-1?international=true)
Things are getting much better. [ourworldindata.org/a-history…](https://ourworldindata.org/a-history-of-global-living-conditions-in-5-charts?linkId=62571595)
Tools and practices for remote agile stuff. [builttoadapt.io/tk-65faab…](https://builttoadapt.io/tk-65faab4cb826)
> When we create, we put forward a case for how we should interact with tech in future, and by extension how we should interact with each other. At the same time, we’re discarding thousands of alternative futures. [www.infoq.com/articles/…](https://www.infoq.com/articles/book-review-future-ethics)
> Please believe me when I say that I totally agree with Holger’s assertion that this process produces absolutely top quality software – and that the people doing the work are often among the very best in their respective corners of the software world. My main beef – which is why I use the term suckers – is that I think they should be compensated when that good hard work results in someone else – particularly a VC-backed company – making money on the fruit of their labor, in Red Hat’s case about $3 billion last year, with almost $500 million in profits, that after IBM bought the company for $34 billion. Or to use the Oracle example in Holger’s post: hell yes Oracle put aside a 1000 FTE effort in favor of adopting Apache – why not use the free labor of others to save a ton of money to be better used, or not, in Oracle’s case, elsewhere? The more free labor, or lumber, or whatever, the better.
Who will think of the poor open source developer? [www.eaconsult.com/2019/01/1…](http://www.eaconsult.com/2019/01/18/open-source-enterprise-software-and-free-lumber/)
> The customer win is another example of retailers choosing cloud vendors that are not Amazon. Microsoft last week announced a retail-as-a-service (RaaS) partnership with Kroger, with the super market giant splitting its cloud investments between Azure and Google Cloud Platform. Walmart is also partnering with Microsoft, with the retailer and frequent Amazon foe signing up to use Microsoft 365, AI, IoT tools and Azure.
Microsoft or Google is what you got in retail. Otherwise you’re just finding a competitor. [www.zdnet.com/article/m…](https://www.zdnet.com/article/microsoft-forms-7-year-cloud-deal-with-walgreens/#ftag=RSSbaffb68)
> Earlier reports indicated that AWS has for some time been working on a cloud service that would allow people with little to no software development experience create simple business applications without having to call up the IT department, but it wasn’t clear what that entailed. [www.geekwire.com/2019/aws-…](https://www.geekwire.com/2019/aws-everyone-new-clues-emerge-amazons-secretive-low-code-no-code-project/)
Checklists of things to check before deploying. https://medium.com/%5B@rakyll%5D(https://micro.blog/rakyll)/production-guideline-9d5d10c8f1e
The list of pains:
One cluster is not enough
Developers want clusters close to them, for low latency
Day two operations – upgrading, scaling, capacity management
Managing heterogeneous infrastructure underneath the platform
> This leaves MongoDB Inc. not unlike the record companies after the advent of downloads: what they sold was not software but rather the tools that made that software usable, but those tools are increasingly obsolete as computing moves to the cloud. And now AWS is selling what enterprises really want. [stratechery.com/2019/aws-…](https://stratechery.com/2019/aws-mongodb-and-the-economic-realities-of-open-source/)
> Rather than trying to deal with every single email, let them pile up, and allow the digital tide to wash over you. Accept that the number of messages in your inbox will always be infinite because the time you have to deal with them will always be finite.
To use the term of _Make Time_, flake-out more often. [www.theguardian.com/technolog…](https://www.theguardian.com/technology/shortcuts/2019/jan/14/inbox-infinity-is-ignoring-all-your-emails-the-secret-to-a-happy-2019)
> Finding a cadence upon which to work as an engineer can be difficult. As engineers are generally averse to meetings, oftentimes we wind up with sporadic meetings and a lot of people who are unclear on their priorities and goals. On the other side, we can find ourselves in environments that are extremely meeting heavy, and engineers often left wondering when there will be time to actually do the work they believed they were hired to do. The establishment of only necessary meetings, at specifically defined times, allows engineers to plan their time to minimize context switching, and and to maximize the time invested in their meetings with one another. [tech.mangot.com/blog/2019…](https://tech.mangot.com/blog/2019/01/09/an-agile-sre-meeting-plan/)