source{d} analysis of the @cloudfoundry codebase: The results show a mature and complex architecture yet extraordinarily active and agile. buff.ly/2oSXjGW #MLonCode

Data Retrieval pipeline at source{d} "Data collection and processing might be less sexy than #MachineLearning but nevertheless is crucial for any progress" buff.ly/2JZ0WTa #MLonCode

Managing with Context, Not Control by @aspyker, #Engineering Manager, @netflix Container Platform buff.ly/2PShiAO

Software Delivery Performance, Multi-GPU #DeepLearning and Overton buff.ly/34DRmwJ

How do you know if your software is good enough? @rich_archbold, VP of #Engineering @intercom shares his engineering standards that will help protect you from easily avoidable mistakes buff.ly/2riyFQU #DevOps

We analyzed all the @TensorFlow git repositories with source{d} EE to extract interesting insights for the Tensorflow community. Check out our summary here: buff.ly/2PSnY1K View the dashboard of the entire analysis here: buff.ly/2WQATCT #MLonCode

"Many of the threats facing #DevOps and #Agile transformation fall into four main camps." 1. No sense of urgency and an unclear vision 2. Lack of senior stakeholder sponsorship 3. Cultural resistance to change 4. Not understanding the change maturity curve buff.ly/32oHPIx

💥 "...Vendors such as source{d} are enabling developers to build increasingly complex software faster, with high quality, and better user experience.” 💥@marksdriver , @Gartner_inc buff.ly/2POU7ay #MLonCode #GartnerCoolVendor

Yesterday we shared Part 1. Here is Part 2 of "Clean code... Why bother?" buff.ly/34DzTVn by @pauxdsantamaria, co-founder of @uppernauts 1. Clean code leads to better practices 2. Reviewing PRs is hard work 3. Reusability 4. Faster bug fixing

Check out source{d} Lead #MachineLearning Engineer, @vadimlearning's article on @kdnuggets "What is #MLonCode?" buff.ly/36Cjh1Z 🤖🎓 💻 📄

@sourcedtech CEO, @Eisokant had his article, "How #MLonCode Could Disrupt #SoftwareDevelopment," published on @EnterpriseAI_ buff.ly/2NHu4iJ