Marcus Blankenship - Podcasts

SEPTEMBER 26, 2019

Instead, your first team becomes those other engineering managers, directors, VPs, whatever it is, those peers, those all-important peer relationships that are so, so vital to cross-team, cross-silo and cross-departmental work. Now, I wasn’t just given a program of videos, given a personalized set of books to read.

Training 40

Training Programming Groups Engineering Management 40

O'Reilly Media - Ideas

JULY 28, 2020

Ethics and Data Science is a short book that helps developers think through data problems, and includes a checklist that team members should revisit throughout the process. Some of the best lessons are captured in Ron Kohavi, Diane Tang, and Ya Xu’s book: Trustworthy Online Controlled Experiments : A Practical Guide to A/B Testing.

Marketing 145

Marketing Weak Development Team Metrics UI/UX 145

Altexsoft

JULY 19, 2022

In the last few decades, we’ve seen a lot of architectural approaches to building data pipelines , changing one another and promising better and easier ways of deriving insights from information. It took three years for her book “Data Mesh: Delivering Data-Driven Value at Scale” to finally see the world in March 2022.

Architecture 52

Architecture Data Analytics Data Engineering 52

O'Reilly Media - Ideas

OCTOBER 19, 2021

This is both frustrating for companies that would prefer making ML an ordinary, fuss-free value-generating function like software engineering, as well as exciting for vendors who see the opportunity to create buzz around a new category of enterprise software. Adapted from the book Effective Data Science Infrastructure.

DevOps 143

DevOps Data Software Review Technical Advisors 143

Marcus Blankenship - Podcasts

SEPTEMBER 12, 2019

Links: O’Reilly Software Architecture Conference – Berlin, Germany. Will’s book, An Elegant Puzzle: Systems of Engineering Management. Speaker 1: Welcome to the Programming Leadership podcast where we help great coders become skilled leaders and build happy, high performing software teams. Transcript.

Weak Development Team 40

Weak Development Team Software Review Architecture Training 40

UruIT

DECEMBER 31, 2018

O’Reilly Software Architecture Conference. This is the ideal conference for you if you want to learn everything related to software architecture. The conference covers approaches and technologies such as chaos engineering, serverless, and cloud, in addition to a range of leadership and business skills.

Conference 89

Conference CTO Coach Fractional CTO Serverless 89

Marcus Blankenship - Podcasts

OCTOBER 10, 2019

Psychological safety and safety of all kinds is really a hot topic, especially amongst software engineering teams. This wasn’t approved by the architecture board, Marcus: These kinds of things. ” So he can go out with my wife and balance my books and do my taxes, right? How dare you? I need to trust him.”

Software Review 40

Software Review Programming Leadership Agile 40

Marcus Blankenship - Podcasts

NOVEMBER 27, 2019

In this episode of Programming Leadership, Marcus and his guest, Camille Fournier discuss some points from her book, The Manager’s Path. They discuss the importance of time management and how to effectively manage employee turnover in a leadership role. Why was that book your book to write in that moment?

Technical Review 86

Technical Review Software Review CTO Coach Engineering 86

LaunchDarkly

JUNE 12, 2020

Our guests today are two superbly experienced front end engineers, and with several books, and many, many talks between them. We have Rebecca Murphey, senior technical lead at Indeed.com, and Ben Vinegar, VP of engineering at Century. The technical project manager role was actually pretty new. Worked there.

Weak Development Team 52

Weak Development Team Part-Time VPE Development Engineering 52

LeanEssays

DECEMBER 23, 2010

In 1988, Tom Gilb wrote the book Principles of Software Engineering Management, which is now in its 20th printing. One of the earliest advocates of evolutionary development, he has recently reiterated the elements of good software engineering in an article in Agile Record[2], from which I quote liberally: Principle 1.

SCRUM 58

SCRUM Weak Development Team Product Management Quality Assurance 58