playlist

Engineering Management

In this week's podcast Richard Seroter talks to James Shore, author of The Art of Agile Development and one of the original signatories of the Agile Manifesto. Also on the podcast are Llewellyn Falco, creator of the open source testing tool ApprovalTests and co-founder of Teaching Kids Programming, and Rebecca Wirfs-Brock, inventor of Responsibility-Driven Design, as well as the author of books including Designing Object: Oriented Software and Object Design: Roles, Responsibilities and Collaborations.

Why listen to this podcast:

 - A lot of people know how to do TDD and refactoring for the back end, but not for the font, but the basics are the same.
 - The basics of Test-Driven Development are the same for the front or back end.
 - If you don't know what's wrong, you don't know how to fix it.
 - The most common code smells, according to Llewellyn Falco: Clutter, long lines, long methods, duplication, and inconsistency.
 - How do we make, in an agile way, the architectural work visible, and not ignore it?
 - How do you have an incremental architecture and get measurements? If I say to you I'm going to go away for six months and figure it out, that's not very measurable.

Notes and links can be found on InfoQ: http://bit.ly/1Pse2r1

1m:10s - The talk 'Agile Engineering for the Web' was about how do you bring typical Agile engineering ideas like TDD and refactoring to the front-end languages.
1m:33s - A lot of people know how to do these things on the back-end, but when you get to the front end a lot of people just throw up their hands.
2m:24s - I see CSS bugs all the time, because it's very hard to refactor CSS without breaking something.

Quick scan our curated show notes on InfoQ. http://bit.ly/1Pse2r1

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. http://bit.ly/24x3IVq

Show notes

James Shore, Llewellyn Falco, and Rebecca Wirfs-Brock on TDD and Architecture

Greylock Talent Partner Dan Portillo sits down with Twitter Head of Revenue Engineering Wade Chambers to discuss the art and science of managing technical teams. Wade shares personal insight into his development as a leader, and shares frameworks for structuring productive meetings, providing feedback, and optimizing for a high functioning organization.

Increasing Your Team's Capacity To Win with Dan Portillo and Wade Chambers | Greymatter

Following their podcast on managing technical teams, Greylock Talent Partner Dan Portillo and Twitter Head of Revenue Engineering Wade Chambers pair up for another podcast on recruiting and interviewing engineers. Wade outlines the processes he’s developed through years of management and building out teams at Yahoo, Proofpoint, TellApart and now Twitter.

The Art of Interviewing 10x Engineers with Dan Portillo and Wade Chambers | Greymatter

In this week’s podcast, QCon chair Wesley Reisz talks to Keith Adams, chief architect at Slack. Prior he was an engineer at Facebook where he worked on the search type live backend, and is well-known for the HipHop VM [hhvm.com]. Adams presented How Slack Works at QCon SanFrancisco 2016.

Why listen to this podcast:

 - Group messaging succeeds when it feels like a place for members to gather, rather than just a tool
 - Having opt-in group membership scales better than having to define a group on the fly, like a mailing list instead of individually adding people to a mail
 - Choosing availability over consistency is sometimes the right choice for particular use cases
 - Consistency can be recovered after the fact with custom conflict resolution tools
 - Latency is important and can be solved by having proxies or edge applications closer to the user

Notes and links can be found on: http://bit.ly/keith-adams

3m:30s Voice and video interactions are impacted by latency; the same is true of messaging clients
4m:00s The user interface can provide indications of presence, through avatars indicating availability and typing indicators
4m:15s Latency is important; sometimes the difference is between 100ms and 200ms so the message channel monitors ping timeout between server and client
4m:40s 99th percentile is less than 100ms ping time
5m:15s If the 99th percentile is more than 100ms then it may be server based, such as needing to tune the Java GC
5m:25s Network conditions of the mobile clients are highly variable&nbsp;
6m:20s Mobile clients can suffer intermittent connectivity

More on this:
Quick scan our curated show notes on InfoQ. http://bit.ly/keith-adams

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

InfoQ Podcast

Show Notes

Keith Adams on the Architecture of Slack, using MySql, Edge Caching, & the backend Messaging Server

In this week’s podcast, Thomas Betts talks with Chris Richardson, a developer, architect, Java Champion and author of POJOs in Action. Before his workshop on Microservices w/ Spring Boot and Docker at QCon San Francisco 2016, Richardson took time to discuss his ideas on how to use DDD and CQRS concepts as a guide for implementing a robust microservices architecture.

Why listen to this podcast:

 - "Microservice architecture" is a better term than "microservices".   The latter suggests that a single microservice is somehow interesting
 - The concepts discussed in Domain-Driven Design are an excellent guide for how to implement a microservices architecture
 - Bounded Contexts correspond well to individual microservices
 - Event sourcing and CQRS provide patterns for how to implement loosely coupled services
 - When converting a monolith to microservices, avoid a big bang rewrite, in favor of an iterative approach

Notes and links can be found on: http://bit.ly/2hZ8TM1

11m:51s - Microservices must be loosely coupled, usually creating a model with one database per service.
12m:45s - There is a business requirement to maintain data consistency across services, and using an event driven architecture is a good way to achieve that.
13m:38s - Event sourcing is specific technique for persisting domain objects as a series of events.
14m:11s - Just as transactions don’t like to be split across microservices, queries cannot simply join across multiple data sources. CQRS provides a solution that accommodates querying via microservices and materialized views.

More on this:
Quick scan our curated show notes on InfoQ. http://bit.ly/2hZ8TM1

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Chris Richardson on Domain-Driven Microservices Design

Jonas Bonér, CTO of LightBend and creator Akka, discusses using Akka when developing distributed systems. He talks about the Actor Model, and how every Microservice needs to be viewed as a system to be successful. 

Why listen to this podcast:

 - Akka is JVM-based framework design for developing distributed systems leveraging the Actor Model - an approach for writing concurrent systems that treat actors as universal primitives and the most successful model with abstraction has been streaming
 - Circuit breakers in Akka are a backup and retry policy; they protect you by capturing failure data and allow you to roll back 
 - Every Microservice needs to be viewed as a system, it needs to have multiple parts that run on different machines in order to function and be fully resilient - thus is a Microsystem
 - Two different trends have emerged when it comes to hardware and environments: one is the trend toward Multi-core, the is a movement toward virtualized environments and the cloud
 - Saga pattern of managing long running transactions in a distributed system fits very well with messaging style architectures

Notes and links can be found on: http://bit.ly/2kwB2eB

Akka
The Actor Model
When Akka and the Actor Model is the perfect choice
Circuit breakers patterns in distributed systems
Two trends toward Multi-core
Reactive Manifesto
Event Driven vs. Message Driven
Reactive Programming and Streams
Microliths to Microsystems
What do you have to get right before you start trying to deploy a distributed systems?
Working with ML / AI at Lightbend to understand tracing through distributed system
Saga Pattern

More on this:
Quick scan our curated show notes on InfoQ http://bit.ly/2kwB2eB

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Jonas Bonér on the Actor Model, Akka, Reactive Programming, Microservices and Distributed Systems

In this podcast Ben Linders, an InfoQ editor in the Culture & Methods area, spoke to Lianping Chen of Paddy Power about their adoption of continuous delivery.

Why listen to this podcast:

 - An introduction to continuous delivery
 - It is possible and feasible to go faster while maintaining and improving the quality of the products being built
 - The benefits from adopting continuous delivery include reduced time from completing development to getting product into production and getting faster customer feedback
 - The way you elicit and represent requirements also needs to change when adopting continuous delivery
 - Implementing continuous delivery needs significant investment in time and money – don’t underestimate the costs involved and plan the adoption to deliver benefits early and get some quick wins

More on this:
Quick scan our curated show notes on InfoQ http://bit.ly/2mgLhA8

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Lianping Chen on Implementing Continuous Delivery

Demand for designers is higher than ever. Great products — the outcome of thoughtful design — are a result of stellar user experience. As design becomes a higher priority for startups, we are seeing a fundamental shift in how designers work. In this episode of Greymatter, John Lilly of Greylock catches up with Figma CEO and co-founder Dylan Field to talk about how he got started as a entrepreneur, the Figma product, and the shift they’re seeing in the design space.

Figma CEO Dylan Field on Collaboration and Design in the Workplace | Greymatter

We talk about growth all the time in the context of startups. How they grow, how they attract users, how they engage users. In this episode of Greymatter, two of the top minds in growth, Greylock Partner Josh Elman and Greylock Growth Advisor Casey Winters, talk about scaling Grubhub and Pinterest, starting growth teams, how to think about SEO, and optimizing user onboarding. The podcast is packed with full-stack growth marketing strategy and tactics Casey has implemented in his career, and these lessons are widely applicable to any consumer startup scaling up.

Scaling Users, Products, and Growth Teams with Casey Winters | Greymatter

This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences.

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Patrick Kua from ThoughtWorks on growing technical leadership and evolutionary architecture

Why listen to this podcast:

 - There is a significant gap in technical leadership capability in teams and across the industry as a whole
 - Your experience as a developer doesn’t prepare you for a tech lead roleRecognize that the skills and responsibilities are very different and find ways to build the new skills – training, mentoring and support
 - Software will continue to be changed so it is important to build it for changeability from the beginning
 - Many of the big decisions which are made at the beginning of a product’s life will change over time, build the ability to change into the core architectural design

More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2vy4xl4

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Want to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2vy4xl4

Patrick Kua on Growing Technical Leadership and Evolutionary Architecture

Software engineers, architects and team leads have found inspiration to build better, high performing teams by listening to the weekly InfoQ Podcast. We have achieved that by interviewing some of the top CTOs, engineers and technology directors from companies like Uber, Netflix and more. Over 500,000 downloads in the last 3 years.

Lianping Chen on Implementing Continuous Delivery

Engineering Culture by InfoQ