program and English

Amye Scavarda and Leslie Hawthorn talk about how to assess where you are and move forward in your career - it includes post its and not starting with what you are worst at.

Growing Your Career

Neal Ford, the author of The Productive Programmer, discusses the benefits of polyglot programming and the impact it's had on software development.

Polyglot Programming

Author Harry Percival discusses how he got into TDD, why you should too, and shares some tips

The Case for Test-Driven Development

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

This week's podcasts features Yao Yue of Twitter. Yao spent the majority of her career working on caching systems at Twitter. She has since created a performance team that deals with edge performance outliers often exposed by the enormous scale of Twitter. In this podcast, she discusses standing up the performance team, thoughts on instrumenting applications, and interesting performance issues (and strategies for solving them) they’ve seen at Twitter.

Why listen to this podcast:

* Performance problems can be caused by a few machines running slowly causing cascading failure
* Aggregating stats on a minute-by-minute basis can be an effective way of monitoring thousands of servers
* Being able to record second-by-second is often too expensive to centrally aggregate, but can be stored locally
* Distinguishing between request timeout and connection/network timeouts is important to prevent thundering herds
* With larger scale organisations, having dedicated performance teams helps centralise skills to solve performance problems

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

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/2wnBemB

Twitter's Yao Yue on Latency, Performance Monitoring, & Caching at Scale

This week's podcast features Simon Brown well known for his work training software architects. Topics include the differences between a tech lead and an architect, how much documentation is enough and what that looks like in a continuous delivery environment.

What you'll learn on this podcast:
•	As an industry we seem to have lost our knowledge of how to do architecture well in the context of modern agile software teams.
•	Architecture is about the expensive decisions; things that are costly to change later.
•	Ideally architects should code in the production code base. If you are not able to do this at least be involved in quality reviews and peer reviews in the production code so you can get feedback on your designs.
•	It is often said the the code is the only documentation you need but the code can’t tell you everything. You do need to document the things you can’t get from the code such as the architectural drivers, they key quality attributes and so on along with some high level diagrams and how you operate the system.
•	As you step into the role of architect go and find a mentor or a local meet-up. The major change is that you have to influence and lead people.

This podcast is sponsored by AppDynamics. Software architects play a critical role in designi¬¬¬ng, executing, and migrating large infrastructures to the cloud. Download AppDynamic’s FREE eBook “10 Tips for Enterprise Cloud Migration” and launch your migration project with a proven plan. Download the eBook now at http://infoq.link/web_sndcld_appdynamics 


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/2xvq7qM

Show notes

Simon Brown on the Role of the Software Architect in a Continuous Delivery Environment

Shubha Nabar is a senior director of data science for Salesforce Einstein. Prior to working for Salesforce, she was a data scientist at LinkedIn and Microsoft.  In the podcast she discusses Salesforce Einstein and the problem space that they are trying to solve, explores the differences between enterprise and consumer for machine learning, and then talks about the Optimus Prime Scala library that they use in Salesforce.

Why listen to this podcast:
* The volume of data, and hardware advances have made it possible to do machine learning to do them a lot faster.
* AI is a science of building intelligent software, encompassing many aspects of intelligence that we tend to think of as human.
* If you can’t measure something, you can’t fix it.
* You have to think about what you can automate, rather than having a human to try and engineer out all those features.
* Get feedback on design.

Nora Jones, a senior software engineer on Netflix’ Chaos Team, talks with Wesley Reisz about what Chaos Engineering means today. She covers what it takes to build a practice, how to establish a strategy, defines cost of impact, and covers key technical considerations when leveraging chaos engineering.

Why listen to this podcast:

- Chaos engineering is a discipline where you formulate hypotheses, perform experiments, and evaluate the results afterwards.
- Injecting a bit of failure over time is going to make your system more resilient in the end.
- Start with Tier 2 or non-critical services first, and build up success stories to grow chaos further.
- As systems become more and more distributed, there becomes a higher need for chaos engineering.
- If you’re running your first experiment, get your service owners in a war room and get them to monitor the results of the test as it is running.

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

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 extended shownotes? Check the landing page on InfoQ: http://bit.ly/2xK7OxR

Shubha Nabar Discusses Einstein, the Machine Learning System in Salesforce

In this podcast, recorded live at Strange Loop 2017, Wes talks to Charity, cofounder and CEO of honeycomb.io.  They discuss the social side of debugging and her Strange Loop talk “Observability for Emerging Infra: What got you Here Won't get you There”.  Other topics include advice for testing in production,  shadowing and splitting traffic, and sampling and aggregation.

Why listen to this podcast:

 - Statistical sampling allows for collecting more detailed information while storing less data, and can be tuned for different event types.
 - Testing in production is possible with canaries, shadowing requests, and feature switches
 - Pulling data out of systems is just noise - it becomes valuable once someone has looked at it and indicates the meaning behind it.
 - Instrumenting isn’t just about problem detection - it can be used to ask business questions later
 - You can get 80% of the benefit from 20% of the work in instrumenting the systems.

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

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/2y6OP1b

program and English

Iury Amicussi