Tech Lead Journal

“Time is important for business. We have to model it explicitly. Temporal modeling means that we use time-based artifacts as first modeling citizens." Tomasz Jaskula is the CTO and co-founder of Luteceo and an experienced software developer and architect. In this episode, we started off discussing how Domain-Driven Design (DDD) influenced Tomasz’s view on software development approach and its relation with functional programming. Tomasz then explained in depth about the time concept in business applications and temporal modeling, in particular, bi-temporal modeling. He mentioned the different concepts of time in temporal modeling, explaining them using an example for easier illustration. We then extended our discussion further to Event Sourcing, understanding the key concept, its relation to temporal modeling, when we should decide to use Event Sourcing in our application, and some available tools that can help us implement Event Sourcing. Listen out for: Career Journey - [00:04:58] DDD and Bounded Context - [00:08:56] DDD and Functional Programming - [00:13:24] Temporal Modeling - [00:14:47] 3 Different Types of Time - [00:21:13] Event Sourcing - [00:25:42] When to Use Event Sourcing - [00:28:13] Event Sourcing Tools - [00:34:02] 3 Tech Lead Wisdom - [00:36:10] _____ Tomasz’s Bio Tomasz Jaskuła is CTO and co-founder of Luteceo, a software consulting company in Paris. Tomasz has more than 20 years of professional experience as a developer and software architect, and worked for many companies in the e-commerce, industry, insurance, and financial fields. He has mainly focused on creating software that delivers true business value, aligns with strategic business initiatives, and provides solutions with clearly identifiable competitive advantages. Tomasz is also a main contributor to the OSS project XOOM for the .NET platform. In his free time, Tomasz perfects his guitar playing and spends time with his family. He recently wrote a book with Vaughn Vernon titled “Strategic Monoliths and Microservices” published by Addison-Wesley. Follow Tomasz: LinkedIn – https://www.linkedin.com/in/tomasz-jaskula-16b2823/ Twitter – @tjaskula Luteceo – http://luteceo.com Our Sponsor Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags by visiting https://techleadjournal.dev/shop. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/66.

“The best leaders are those that get things done through other people." Nick Horney is the author of “VUCA Masters” and founder of Agility Consulting. In this episode, Nick shared his innovations in leadership agility that include AGILE Model® and Leadership Agility Fitness, which are the cornerstones for becoming inspiring leaders in the current VUCA world, i.e. the VUCA Masters. Nick also shared how we can extend his leadership agility concepts to improve organizational behavior, culture, and mindset in order to reach organizational agility. Towards the end, Nick shared some inspiring leadership lessons from his 23 years of experience serving the US Navy Special Operations, describing the true characteristic and hallmark of the best leaders. Listen out for: Career Journey - [00:05:48] AGILE Model® - [00:08:04] VUCA - [00:13:20] Leadership Agility Fitness - [00:19:46] Leadership Self-Agility Assessment - [00:24:14] VUCA Masters - [00:29:30] Leadership Agility and Agile - [00:32:10] Organizational Behavior - [00:34:26] Leadership Lessons From the Military - [00:40:35] 3 Tech Lead Wisdom - [00:43:55] _____ Nick Horney’s Bio Dr. Nicholas Horney founded Agility Consulting in 2001 and has been recognized for innovations in organizational and leadership agility, including The AGILE Model®, VUCA Masters™, Leadership Agility Fitness™, After Action Agility™ and Talent Portfolio Agility™. His coaching, leadership agility and organizational agility management consulting experience spans over 30 years and includes the start-up and management of the Coopers & Lybrand (now Price Waterhouse Coopers) Change Management Practice. Representative clients include Turner Broadcasting, Coca-Cola, Navy SEALs, Lenovo, CIA, ARAMARK, and REI. Dr. Horney has written four books. The most recent is VUCA Masters: Developing Leadership Agility Fitness for the New World of Work (2021). Nick retired from the U.S. Navy (Special Operations) at the rank of Captain and has applied that experience to his work with high performance team agility. He serves as a coach for The Honor Foundation focusing on the successful transition of Navy SEALs to the business world. Follow Nick: LinkedIn – https://www.linkedin.com/in/nickhorney Website – https://agilityconsulting.com/ VUCA Masters Academy – http://vucamasters.com/ Our Sponsor Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags by visiting https://techleadjournal.dev/shop. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/65.

“API design centers on effective communication, not just between developers, but also communication that combines product thinking, business, and technology all in one." James Higginbotham is the author of “Principles of Web API Design” and an executive API consultant. In this episode, James explained why it is extremely important to design APIs properly and shared the five key important principles of API design taken from his book. James also recommended the API Design-First approach–a rapid & lightweight outcome-based API design process–to design and deliver APIs successfully, including the ADDR process and establishing API boundaries (in relation to DDD). Towards the end, James shared some recommendation for API testing strategies and also some anti-patterns that we should avoid. Listen out for: Career Journey - [00:05:00] Principles of Web API Design Book - [00:06:46] Importance of Designing API Properly - [00:08:17] Principle 1: API Should Never be Designed in Isolation - [00:13:13] Principle 2: Outcome-Based Focus - [00:15:10] Principle 3: Design Elements That Matches the Needs - [00:17:44] Principle 4: API Documentation as UI for Developers - [00:22:53] Principle 5: APIs are Forever - [00:27:52] API Design First Approach - [00:31:43] ADDR Process - [00:34:43] API Boundaries and DDD - [00:38:56] Testing APIs - [00:43:51] 3 Tech Lead Wisdom - [00:47:44] _____ James Higginbotham’s Bio James Higginbotham is a software developer and architect with over 25 years of experience in developing and deploying apps and APIs. He guides enterprises through their digital transformation journey, ensuring alignment between business and technology through product-based thinking to deliver a great customer experience. James engages with teams and organizations to help them align their business, product, and technology strategies into a more composable and modular enterprise platform. James also delivers workshops that help cross-functional teams to apply an API design-first approach using his ADDR process. His work experience includes banking, commercial insurance, hospitality, and the airline industry where he helped a startup airline off the ground – literally. Follow James: LinkedIn – https://www.linkedin.com/in/jameshigginbotham Twitter – @launchany LaunchAny – https://launchany.com/ API Developer Weekly newsletter – https://apideveloperweekly.com/ Our Sponsor Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags by visiting https://techleadjournal.dev/shop. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/64.

“If you’re a generalist, and if you’re good at multiple things, then you have a lot of options. You have a lot of career paths to choose from." Deepu K Sasidharan is a polyglot developer and a Senior Developer Advocate for DevOps at Okta. In this episode, Deepu shared why he consciously becomes a polyglot and generalist developer. He emphasized the importance of knowing more than one thing in the current rapidly changing tech industry. He gave practical tips for new engineers to start out and shared his technique to learn new stuffs, including languages, by building personal indexes. We then discussed the current interview practices trend and why he thinks it needs to change, especially to make it more inclusive and less biased. Towards the end, Deepu shared about developer experience, a topic that he is highly passionate about, on why it is becoming more important and some tips for building a good developer experience. Listen out for: Career Journey - [00:05:21] Being a Polyglot Developer - [00:08:25] Should We Become Polyglot Developers? - [00:12:05] Tips for New Engineers - [00:15:14] Learning a New Language - [00:18:29] Building Index for Learning - [00:22:16] Broken Interview Practices - [00:25:27] Importance of Developer Experience - [00:28:50] Building a Good Developer Experience - [00:32:55] 3 Tech Lead Wisdom - [00:37:33] _____ Deepu K Sasidharan’s Bio Deepu is a polyglot developer and OSS aficionado. He mainly works with Java, JS, Rust, and Golang. He co-leads JHipster and created the JDL Studio and KDash. He’s a Senior Developer Advocate for DevOps at Okta. He is also an international speaker and published author. Deepu is an enthusiast of cloud & container technology, and he is passionate about developer experience and user experience. Follow Deepu: Website – https://deepu.tech/ Twitter – @deepu105 LinkedIn – https://www.linkedin.com/in/deepu05/ GitHub – https://github.com/deepu105 Our Sponsor Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags by visiting https://techleadjournal.dev/shop. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/63.

“Coding well with others or being a team player is at the heart of everything we do as developers. Unless you’re coding yourself for a piece of software that only you are going to use, you’re not a solo developer." Fernando Doglio is the author of “Skills of a Software Developer”. In this episode, Fernando shared some insights from his book on how to be a successful software developer. He highlighted that software development is a mostly a team effort and shared tips on how we can work well within a team, including not to fall into the trap of over-engineering and early optimization. He then shared some practical tips on technical interviews and what we should avoid writing in our resume. Towards the end, Fernando gave his tips to aspiring authors who want to write a technical book and cleared some misconceptions and mental blocks that may stop a lot of them from writing. Listen out for: Career Journey - [00:05:34] Skills of a Software Developer - [00:09:05] Everyone Can Be a Successful Developer - [00:11:34] Tips to Work Well in a Team - [00:14:47] Avoiding Overengineering - [00:16:35] Focus on Working Code First, Then Optimize It - [00:20:30] Writing Readable Code - [00:24:46] Tips on Technical Interviews - [00:28:26] Tips for Writing Technical Books - [00:34:07] 3 Tech Lead Wisdom - [00:40:56] _____ Fernando Doglio’s Bio Fernando Doglio is a Data Engineering Manager at Accenture and has over 18 years of experience in the software industry, from web development to big data. Fernando loves to tinker and learn, and has written several technical blogs and books such as Node.js and React. His latest book, “Skills of a Software Developer”, is currently available through the Manning Early Access Program, and he’s open to talk about the industry, possible projects, or any help regarding choice of tech-stack. Follow Fernando: Twitter – @deleteman123 LinkedIn – https://www.linkedin.com/in/fernandodoglio/ Medium – https://deleteman123.medium.com/ Website – https://www.fdoglio.com/ Our Sponsor Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags by visiting https://techleadjournal.dev/shop. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/62.

“Understanding what makes code readable from a cognitive perspective will help you design better. There are so many areas of programming where knowing something about knowing is just going to make you happier and more effective." Felienne Hermans is the author of “The Programmer’s Brain” and an Associate Professor at Leiden University. She is also the creator of the Hedy programming language, the co-founder of Joy of Coding conference, and a host at Software Engineering Radio podcast. In this episode, Felienne explained why programming is one of the most demanding cognitive activities and described the three different cognitive processes involved. We discussed why code reading is hard and how to get better at it, the connection between programming and spoken languages, naming things and why it is so important to get it right, and how to avoid having bugs in our thinking. Listen out for: Career Journey - [00:05:09] Kids Learning Programming - [00:06:15] Writing “The Programmer’s Brain” - [00:08:58] Programming as a Demanding Cognitive Ability - [00:11:19] Code Reading is So Hard- [00:16:23] 3 Cognitive Processes - [00:19:32] How to Improve Code Reading Skills - [00:22:09] Power of Chunking - [00:25:07] Learning Programming and Spoken Language - [00:27:35] Bugs in Thinking - [00:31:02] Naming Things is Hard - [00:34:32] Code with Bad Names Has More Bugs - [00:37:36] Mental Models - [00:41:31] Other Cognitive Aspects - [00:42:45] Impact of Interruptions - [00:44:37] 2 Tech Lead Wisdom - [00:46:46] _____ Felienne Hermans’s Bio Felienne Hermans is an Associate Professor at the Leiden Institute of Advanced Computer Science at Leiden University, where she heads the PERL research group, focused on programming education. She also teaches prospective computer science teachers at the Vrije Universiteit Amsterdam. Felienne is the creator of the Hedy programming language, and was one of the founders of the Joy of Coding conference. Since 2016, she has been a host at Software Engineering Radio, one of the most popular software engineering podcasts on the web. Felienne is also the author of “The Programmer’s Brain” a book that helps programmers understand how their brains work and how to use it more effectively. In 2021, Felienne was awarded the Dutch Prize for ICT research. Felienne is a member the board of I&I, the Dutch association of high-school computer science teachers, and of TC39, the committee that designs JavaScript. Follow Felienne: Website – https://www.felienne.com/ Twitter – @Felienne LinkedIn – https://www.linkedin.com/in/felienne Our Sponsor Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags by visiting https://techleadjournal.dev/shop. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/61.

“Software engineering involves a lot of decisions, and that decision has some trade-offs. We have pros and cons. It’s not like one decision is always better than the other." Tomasz Lelek is the author of “Software Mistakes and Tradeoffs”. In this episode, Tomasz shared what led him to write his book and one of the past software mistakes from his career experience. He also gave advice on how software developers should approach the potential software mistakes and explained some typical trade-offs when making software engineering design decisions, such as code duplication vs flexibility, premature optimization vs optimizing hot-path, data locality and memory, and finally delivery semantics in distributed systems. Listen out for: Career Journey - [00:05:00] Why Write about Software Mistakes and Trade-offs - [00:07:42] Software Mistake Experience - [00:10:16] Tips for Software Developers - [00:13:08] Trade-off 1: Code Duplication vs Flexibility - [00:15:24] Trade-off 2: Premature Optimization vs Optimizing Hot-Path - [00:20:08] Trade-off 3: Data Locality and Memory - [00:25:02] Trade-off 4: Delivery Semantics in Distributed Systems - [00:33:01] 3 Tech Lead Wisdom - [00:40:28] _____ Tomasz Lelek’s Bio Tomasz currently works at Datastax, building products around one of the world’s favorite distributed databases - Cassandra. He contributes to Java-Driver, Cassandra-Quarkus, Cassandra-Kafka connector, and Stargate. He previously worked at Allegro, an e-commerce website in Poland, working on streaming, batch, and online systems serving millions of users. He is also a published author of “Software Mistakes and Tradeoffs: Making good programming decisions” that is focusing on real-world problems you may encounter in your production systems. Follow Tomasz: LinkedIn – https://www.linkedin.com/in/tomaszlelek/ Twitter – @tomekl007 GitHub – https://github.com/tomekl007 Our Sponsor Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags by visiting https://techleadjournal.dev/shop. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/60.

“DevOps is about creating a collaborative environment between the development team and the operations team, and aligning goals and incentives between those two teams. Because so many of the problems that we encounter in life, not just even in technology, are due to misalignment of goals." Jeffery Smith is the author of “Operations Anti-Patterns, DevOps Solutions” and the Director of Production Operations at Centro. In this episode, Jeffery described DevOps essentials and emphasized what DevOps is not. He also explained about CAMS, a framework that outlines the core components required for successful DevOps transformation. We then discussed three anti-patterns taken from his book: paternalist syndrome, alert fatigue, and wasting perfectly good incident; and he explained how to recognize those anti-patterns in order to avoid them on our DevOps journey. Finally, Jeffery also talked about postmortem and shared tips on how to cultivate a good postmortem culture. Listen out for: Career Journey - [00:04:47] DevOps - [00:09:13] CAMS - [00:12:42] Why DevOps Anti-Patterns - [00:16:48] Anti-Pattern 1: Paternalist Syndrome - [00:19:55] Anti-Pattern 2: Alert Fatigue - [00:27:20] Anti-Pattern 3: Wasting a Perfectly Good Incident - [00:34:33] Postmortem - [00:39:59] 4 Tech Lead Wisdom - [00:45:57] _____ Jeffery Smith’s Bio Jeffery Smith has been in the technology industry for over 15 years, oscillating between management and individual contributor. Jeff currently serves as the Director of Production Operations for Centro, a media services and technology company headquartered in Chicago, Illinois. Before that he served as the Manager of Site Reliability Engineering at Grubhub. Jeff is passionate about DevOps transformations in organizations large and small, with a particular interest in the psychological aspects of problems in companies. He lives in Chicago with his wife Stephanie and their two kids Ella and Xander. Follow Jeffery: Website – https://attainabledevops.com/ Twitter – @DarkAndNerdy LinkedIn – https://www.linkedin.com/in/jeffery-smith-devops Our Sponsor Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags by visiting https://techleadjournal.dev/shop. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/59.

“The main goal of unit testing is to enable sustainable growth of your software project that enables you to move faster with a more quality code base." Vladimir Khorikov is the author of “Unit Testing: Principles, Practices, and Patterns” and the founder of Enterprise Craftsmanship blog. In this episode, we discussed in-depth about unit testing. Vladimir broke down the four pillars of unit testing and the anatomy of a good unit test, as well as mentioned a couple of common unit testing anti-patterns. We also discussed topics such as test-driven development, code coverage and other unit testing metrics, test mocks and how to use it properly, and how to be pragmatic when writing unit tests. Listen out for: Career Journey - [00:05:32] Unit Testing - [00:08:20] The Goal of Unit Testing - [00:11:34] Test-Driven Development - [00:12:55] Code Coverage & Other Successful Metrics - [00:17:35] Pragmatic Unit Tests - [00:21:04] 4 Pillars of Unit Testing - [00:23:40] Anatomy of a Good Unit Test - [00:34:01] Test Mocks - [00:38:16] Unit Testing Anti-Patterns - [00:47:05] Tech Lead Wisdom - [00:49:56] _____ Vladimir Khorikov’s Bio Vladimir Khorikov is the author of the book “Unit Testing: Principles, Practices, and Patterns”. He has been professionally involved in software development for over 15 years, including mentoring teams on the ins and outs of unit testing. He’s also the founder of the Enterprise Craftsmanship blog, where he reaches 500 thousand software developers yearly. Follow Vladimir: LinkedIn – https://www.linkedin.com/in/vladimir-khorikov-bb482653 Twitter – https://twitter.com/vkhorikov Enterprise Craftsmanship – https://enterprisecraftsmanship.com/ Pluralsight – https://app.pluralsight.com/profile/author/vladimir-khorikov Our Sponsor Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags by visiting https://techleadjournal.dev/shop. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/58.

“Software telemetry is what you use to figure out what your production systems are doing. It’s all about shortening that feedback loop between the user experience and the engineers who are writing the user experience." Jamie Riedesel is a Staff Engineer at Dropbox working on the HelloSign product and also the author of “Software Telemetry”. In this episode, Jamie shared an overview of software telemetry and explained why it is important for us to understand how our production systems are behaving by using those telemetry data. She also explained different software telemetry types, concepts such as observability and cardinality, and shared some software telemetry best practices. In the second part of our conversation, Jamie opened up and shared her own personal experience dealing with toxic work environments. She emphasized the importance of self-awareness and psychological safety, as well as went through the five key dynamics to a successful team based on Google’s re:Work blog post. Listen out for: Career Journey - [00:05:15] Software Telemetry - [00:07:22] Knowing Your Production System - [00:12:13] Types of Software Telemetry - [00:16:45] High Cardinality - [00:22:34] Observability & Buzzwords - [00:27:08] In-House vs. SaaS - [00:30:04] Some Telemetry Best Practices - [00:32:35] Toxic Workplace - [00:38:45] Identifying Your Toxicity - [00:44:18] Psychological Safety - [00:49:02] Identifying a Person’s Baggage - [00:53:52] Who is On The Team Matters Less - [00:58:09] 3 Tech Lead Wisdom - [01:01:49] _____ Jamie Riedesel’s Bio Jamie Riedesel has over twenty years of experience in the tech industry, and has spent her time as a System Administrator, Systems Engineer, DevOps Engineer, and Platform Engineer. She is currently a Staff Engineer at Dropbox, working on their HelloSign product. Jamie’s blog at sysadmin1138.net has been there since 2004 and survived the apocalypse of Google Reader shutting down. Jamie is the author of “Software Telemetry” through Manning Publications, and also has a deep interest in reforming team cultures to be less toxic. Follow Jamie: Blog – https://sysadmin1138.net/mt/blog/ Twitter – https://twitter.com/sysadm1138 LinkedIn – https://www.linkedin.com/in/jamie-riedesel-983773b Our Sponsor Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags by visiting https://techleadjournal.dev/shop. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/57.