#011: Thoughts And Opinions On Live-Coding During Job Interviews For Programmers Artistry Of Code podcast

28:08

📚 ABOUT THE EPISODE Software projects are filled with all these hard decisions. Deciding between making use of a known technology or pattern versus picking something entirely new is one of the most difficult and impactful ones. In this episode, Grzegorz Godlewski, Artur Wolny and Marek Urbanowicz discuss how they approach this particular type of decision. Tune in for valuable insights! 📑 TOPICS COVERED 👉 When we think it's good to go with the solutions we already know 👉 What are the benefits of embracing the unknown 👉 What are the factors you should take into account while making such decisions 👉 Considering the macro, impact of the decision on your and other teams ⌚ TIMELINE 00:00:00 - Intro 00:01:24 - Examples of choices we had to make 00:05:24 - What can drive the decision making process 00:10:00 - Unknown as a possibility for learning 00:13:59 - Proof of Concept implementations - a way to explore 00:19:30 - When would we go for "the new" solution to a problem 00:23:52 - When would we stay with "the known" solution to a problem 00:27:04 - Wrap up 🔗 LINKS FROM EPISODE https://twitter.com/GregBDavies/status/1144530496078123009 🤝 CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com 😍 FOLLOW US ON SOCIAL MEDIA Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#022: Monorepos: The Good and Bad 30:28

2 years ago30:28

30:28

📚 ABOUT THE EPISODE Are you considering moving to Monorepos with your projects? In the 22th episode Grzegorz, Artur and Marek share their valueable opinions and experiences realted to working with these. Tune in to learn about the potential benefits and challenges of this approach. 📑 TOPICS COVERED 👉 We share subjective opinions and experiences from working with Monorepos in the JavaScript/TypeScript ecosystem 👉 We talk about hidden complexity - when a "simplification" on one end results with higher complexity in other areas 👉 We comment on the state of tooling for Monorepos specific in the JS/TS ecosystem ⌚ TIMELINE 00:00:00 - Intro 00:01:12 - Subjective opinions on Monorepos 00:03:58 - Benefits and challenges of Monorepos 00:26:20 - Recap and closing thoughts 🤝 CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com 😍 FOLLOW US ON SOCIAL MEDIA Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#021: What went wrong with Microservices 36:16

2 years ago36:16

36:16

📚 ABOUT THE EPISODE In the 21th episode Grzegorz Godlewski and Artur Wolny share their negative experiences with implementing Microservices. Three examples of misuse of that useful pattern shows us that even the greatest idea can lead us down the blind alley, when we are narrow-minded about it. Listen and take conclusions from those lessons that we learned! 📑 TOPICS COVERED 👉 Impact of blindly following recommendations: costly premature optimisations. 👉 Thing that might go wrong when you're focused too much on domain assignment of feature and too less on the app maintainability. 👉 How microservice hype-trains and poor organisational decisions lead to project failure. ⌚ TIMELINE 00:00:00 - Intro 00:02:08 - Story #1: Blindly following recommendations. 00:08:22 - Story #2: Too much domain, too little maintainability. 00:14:20 - Story #3: Microservice hype-train. 00:19:15 - Microservices or monolith? Benefits & drawbacks. 00:34:46 - Outro 🤝 CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com 😍 FOLLOW US ON SOCIAL MEDIA Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#020: Continuous Deployment 31:32

2 years ago31:32

31:32

📚 ABOUT THE EPISODE In the 20th episode of the main series Grzegorz Godlewski, Marek Urbanowicz and Artur Wolny discuss their experiences and preferences regarding the implementation of Continuous Deployment. With this episode we complete our micro-series focused on CI/CD implementation. We strongly believe that all code should hit production as soon as possible, as frequently as possible in a reliable, repeatable and automated manner. Tune in for experience and inspiration! 🎧 📑 TOPICS COVERED 👉 How implementing Continuous Delivery can benefit your team & product, optimizing costs and shortening the feedback loop 👉 What it takes to have a successful CD implementation 👉 Some tools/products which you might consider for your implementation ⌚ TIMELINE 00:00:00 - Intro 00:01:21 - How do we define Continuous Deployment 00:05:20 - Benefits of Continuous Deployment 00:13:21 - Challenges and requirements for CD implementation 00:21:54 - Tools which you can use to build CD 00:30:49 - Outro 🤝 CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com 😍 FOLLOW US ON SOCIAL MEDIA Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#019: Benefits of Continuous Integration 30:32

3 years ago30:32

30:32

📚 ABOUT THE EPISODE In the 19th episode of the main series Grzegorz Godlewski, Marek Urbanowicz and Artur Wolny discuss their experiences and preferences regarding the implementation of Continuous Integration. We really encourage you to give this episode a listen, as we're sure that having a great CI implementation is key to launching products faster and with better developer experience! Tune in for experience and inspiration! 🎧 📑 TOPICS COVERED 👉 The common misconception about Continuous Integration 👉 How implementing Continuous Integration can benefit your team & product 👉 What it takes to have a successful CI implementation 👉 Some tools/products which you might consider for your implementation ⌚ TIMELINE 00:00:00 - Intro 00:01:19 - How do we define Continuous Integration 00:05:59 - The benefits of Continuous Integration 00:16:20 - Challenges and requirements for CI 00:23:36 - CI tools for pipelines (NodeJS) 00:29:19 - Wrap up 🔗 LINKS FROM THE EPISODE Continuous Delivery by Jez Humble and Dave Farley https://martinfowler.com/books/continuousDelivery.html Bulb light indicator https://en.wikipedia.org/wiki/Build_light_indicator 🤝 CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com 😍 FOLLOW US ON SOCIAL MEDIA Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#018: Implementing background jobs 29:52

3 years ago29:52

29:52

📚 ABOUT THE EPISODE Welcome to the 18th episode of the main series! This time Grzegorz Godlewski and Marek Urbanowicz met up to discuss their experience and recommendations on implementing background jobs. Any system which is growing in scale, will need those at some point either to implement performance improvements (by putting some work into the background) or new business requirements (which are supposed to run in background). Tune in for insights on how this can be done! 🎧 📑 TOPICS COVERED 👉 How simple business analysis can help you in determining candidates for background jobs 👉 What software architecture patterns come in handy while implementing them 👉 What are the best practices for reliable implementations 👉 Some tools/products which you might consider for your implementation ⌚ TIMELINE 00:00 - Intro 01:14 - How to identify candidates for background jobs 08:28 - Employ the transactional outbox pattern 11:53 - Dealing with state in background jobs 15:29 - Scheduling and processing batched operations 18:40 - Avoiding state with Event Carried State Transfer pattern 21:14 - Silver bullets and golden hammers - the tooling 28:08 - Emphasis on idempotency 🔗 LINKS FROM THE EPISODE M. Fowler: What do you mean by “Event-Driven”? https://martinfowler.com/articles/201701-event-driven.html Transactional outbox pattern description https://microservices.io/patterns/data/transactional-outbox.html BullMQ https://docs.bullmq.io/ RabbitMQ Delayed Message Plugin https://github.com/rabbitmq/rabbitmq-delayed-message-exchange Temporal: https://temporal.io/ 🤝 CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com 😍 FOLLOW US ON SOCIAL MEDIA Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#017: Why you should write Unit Tests 28:16

3 years ago28:16

28:16

📚 ABOUT THE EPISODE Welcome to the 17th episode of the main series! This time we reach the bottom of the Test Pyramid, focusing on the most common type of test: the Unit Test. As big fans of TDD (Test Driven Development) we happily discuss our experiences and approaches. We cover proven benefits which you could use as support material in introducing the practice of Unit Testing and TDD in your organization or day-to-day work. Tune in for new stream of inspiration! 🎧 📑 TOPICS COVERED 👉 How unit testing can be beneficial for individuals and organizations 👉 The do's and don'ts of unit testing 👉 How to write testble code 👉 Some mocking libraries for NodeJS which you might want to try out ⌚ TIMELINE 00:00 - Intro 01:35 - To be clear: how do we define Unit Tests 05:02 - Sound reasons for why we write Unit Tests 12:38 - To mock, or not to mock? 20:58 - Writing testable code 27:02 - Wrap up 🔗 LINKS FROM THE EPISODE ts-mockito mocking library https://www.npmjs.com/package/@johanblumenberg/ts-mockito jest-mock-extended mocking library https://www.npmjs.com/package/jest-mock-extended inversify library for dependency injection https://www.npmjs.com/package/inversify 🤝 CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com 😍 FOLLOW US ON SOCIAL MEDIA Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#016: Tips on integration testing 30:14

3 years ago30:14

30:14

📚 ABOUT THE EPISODE Welcome to the 16th episode! We continue our step-down and share with you our understanding of integration tests and best practices we've learned when implementing them. In the IT world full of APIs, SaaS and databases, checking how your code collaborate with third parties is a must have. Want to know our way of integration testing? Just press play 🎧 📑 TOPICS COVERED 👉 Learn about our opinions on integration testing 👉 What NodeJS community is doing wrong in integration tests 👉 Get useful hints from people who implement integration tests on a daily basis 👉 Learn about the pros of having your code collaboration tested 👉 Learn when to favour integration testing over E2E or unit testing ⌚ TIMELINE 00:00:00 - Intro 00:00:56 - What is our definition of integration testing? 00:06:50 - Why do we need integration tests? 00:14:06 - When do we favour integration tests over E2E tests? 00:21:37 - What tools we use for integration testing in Node? 00:25:44 - How to make your integration tests robust and solid stable? 00:29:15 - Wrap up 🤝 CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com 😍 FOLLOW US ON SOCIAL MEDIA Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#015: Leveraging E2E tests in your project 23:07

3 years ago23:07

23:07

📚 ABOUT THE EPISODE In the 15th episode we met to discuss the matter of E2E (end-to-end) tests. Definitely one of the most difficult types of testing which also has considerable benefits, next to a comparable list of drawbacks. We decided that from this episode we'll aim to deliver shorter content, so that you can enjoy it more spontaneously 🎧, without scheduling a big block of time. Tell us if you like the new format 💖! 📑 TOPICS COVERED 👉 Learn about our opinions on E2E testing 👉 Get useful hints from people who did implement E2E tests 👉 Learn about the traps and caveats of E2E testing 👉 Learn how you might set this up in your organization ⌚ TIMELINE 00:00:00 - Intro 00:01:15 - What is the "Test Pyramid" 00:03:13 - Defining E2E tests and hints for implementation 00:09:37 - Why should we invest in E2E tests 00:12:52 - Who should be responsible for E2E tests 00:19:18 - The length of the feedback loop 00:22:10 - Wrap up 🤝 CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com 😍 FOLLOW US ON SOCIAL MEDIA Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#014: About data and state consistency in software 39:43

3 years ago39:43

39:43

📚 ABOUT THE EPISODE In the 14th episode we met in our full squad to talk about our hands-on experiences of data consistency challenges. Each of us has brought one detailed example from his career that challenged us to make the choice between strong and eventual consistency. Did you have to make that decision? Or maybe you're about to make one? Listen to this episode to learn what we have done to align data consistency and service availability. 📑 TOPICS COVERED 👉 How to make security team arrive at the right property? 👉 How to make decisions based on multiple asynchronous sensors in home automation systems? 👉 How to present temporal inconsistencies to the end user? ⌚ TIMELINE 00:01:17 - 🏖 Little warm up - about our vacations 00:08:10 - 🚔 Security system's data consistency 00:23:59 - 🏠 Smart home - decision making based on asynchronous inputs 00:31:44 - 📲 How eventual consistency affects the end-user experience 00:38:57 - 👋🏼 Dear listener, we need your help! 🤝 CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com 😍 FOLLOW US ON SOCIAL MEDIA Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#013: Why long term projects are awesome with Jarosław Wiśniewski from Viessmann R&D Center 53:11

3 years ago53:11

53:11

📚 ABOUT THE EPISODE In the 13th episode of the main series, we hosted a friend of ours: Jarosław Wiśniewski, who's working as Technical Leader and Architect at Viessmann R&D Center. Together with Jarek, we talked about "Why long-term projects are really awesome". We did it by sharing valuable experiences, lessons learned and actionable tips you might want to pick up! 📑 TOPICS COVERED 👉 The key lessons learned from developing the same product for 8 years 👉 How iterative code refactoring could ease your customer's cognitive shock 👉 How to communicate UI/UX changes to the customer's to avoid the backlash 👉 Deciding between evolution and revolution in a software product 👉 How working longer with a product helps in building professional seniority and open your path to a leadership role 👉 What are the pros and cons of working long with the same product 👉 What helps to keep great developers on board 🤝 THE EPISODE'S GUEST Jarosław Wiśniewski Technical Leader, Architect at Viessmann R&D Center Personal web page: https://appsisle.com/ LinkedIn: https://www.linkedin.com/in/softdeveloper/ 🤝 CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com 😍 FOLLOW US ON SOCIAL MEDIA Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#012: From Software Developer to Business Owner with Pierre de Wulf from ScrapingBee 1:06:39

3 years ago1:06:39

1:06:39

📚 ABOUT THE EPISODE In the 12th episode of the main series, we hosted Pierre de Wulf - the co-founder and one of the core developers of ScarpingBee. Tune in to learn about Pierre, his path to running a successful business and the challenges he had to face along the way. In this episode, we also cover the technical challenges of building & operating developer-oriented software products. Together with us, you'll see that a "programmer's life" comes in different forms and flavours! 📑 TOPICS COVERED 👉 How programmers could use their day-to-day job to find a business idea 👉 Advantages and disadvantages of being a dev and building a product (both for marketing and building) 👉 Getting involved in the community you want to help now 👉 How ScrapingBee is built internally 👉 Why developers are the coolest testers in the world :) 👉 How Pierre approaches architecture and scalability challenges 👉 What techniques and practices are applied to help a small team to build their product 🤝 THE EPISODE'S GUEST Pierre de Wulf Co-Founder of ScrapingBee You can find more about the project here: https://www.scrapingbee.com/ Twitter: https://twitter.com/PierreDeWulf Mail: pierre@scrapingbee.com 🤝 CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com 😍 FOLLOW US ON SOCIAL MEDIA Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#011: Thoughts and opinions on Live-Coding during job interviews for programmers 48:47

3 years ago48:47

48:47

📚 ABOUT THE EPISODE In the 11th episode of the main series, Grzegorz, Marek and Artur talk about their experience with live coding during job interviews for programming positions. How did these look like and if they enjoyed it at all. Tune in to hear about the thoughts and opinions on the matter, along with ideas on how to make it a pleasant experience for everyone involved. If you're hiring a lot, that's a must-listen :) 📑 TOPICS COVERED 👉 How each of the hosts experienced live-coding exercises - what was great or bad about it 👉 Based on the bad experiences, how can this be done better 👉 How can this exercise be helpful or harmful for employer branding 👉 What are the traps waiting for the interviewers and candidates alike 👉 Tips on preparing for such an exercise 👉 Should live-coding exercise be part of all interviews ⌚ TIMELINE 00:00:00 - Intro 00:01:34 - Highlights from the last two weeks 00:06:52 - Marek's experience with live-coding during interviews 00:11:50 - Artur's experience with live-coding during interviews 00:15:55 - Grzegorz's experience with live-coding during interviews 00:21:32 - What information about the candidate does a live-coding exercise provide? 00:32:34 - Tips for doing the live-coding exercise right 00:35:38 - The importance of doing it right for employer branding 00:37:08 - Retrospective summary - how do we feel about live-coding after this conversation 00:47:20 - Dear listener, we need your help :) 🤝 CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com 😍 FOLLOW US ON SOCIAL MEDIA Podcast Social Accounts Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#010: Out of order and ensuring delivery in the asynchronous communication 56:05

3 years ago56:05

56:05

ABOUT THE EPISODE This episode follows up on the subject of challenges in asynchronous communication which was started in episode #009 🧵. Join us for another journey into the depths of this domain! TOPICS COVERED In episode #010, in which we dug deeper into the ground of Asynchronous Communication, talking about: 🔢 How we can deal with "out of order" processing? Is it the responsibility of the transport layer only? 📬 How to ensure the message delivery? What strategies are used by message brokers to give us some guarantees? How does using those strategies affects a producer and a consumer code? ⏱ Using Asynchronous Communication in long-running business processes and how to make it blend into the synchronous APIs environment? That's not all the concerns one needs to consider when implementing Asynchronous Communication. We intend to follow up on this in future! TIMELINE 00:00:00 - Intro 00:01:37 - Our last 2 weeks 00:07:37 - The problem of ordering in async communication 00:10:06 - Issues with ordering comming from the producer 00:11:20 - Competing consumers as source of ordering problems 00:14:03 - Tackling the concurrency issues on the entity level 00:22:13 - Ordering in queues vs event streams 00:25:55 - Ensuring delivery 00:36:05 - Idempotency in the asynchronous communication 00:42:26 - Long running processes 00:51:08 - Importance of requestId/correlationId 00:53:15 - Wrap up CONTACT US / COLLABORATION If you: - want to send us your valuable feedback - you would like to appear on the show as a guest - you would like to help out the show to grow - you would like to sponsor the show Then please contact us via: podcast@artistryofcode.com You can also check out our website: https://artistryofcode.com FOLLOW US ON SOCIAL MEDIA Podcast Social Accounts Facebook: https://www.facebook.com/ArtistryOfCode Twitter: https://twitter.com/ArtistryOfCode LinkedIn: https://www.linkedin.com/company/artistry-of-code Reddit: https://www.reddit.com/r/ArtistryOfCode/ Grzegorz Godlewski LinkedIn: https://www.linkedin.com/in/ggodlewski/ Twitter: https://twitter.com/GGodlewski Marek Urbanowicz LinkedIn: https://www.linkedin.com/in/marek-urbanowicz-0ba65254/ Twitter: https://twitter.com/UrbanowiczDev Artur Wolny LinkedIn: https://www.linkedin.com/in/artur-wolny-35150664/…

1
#009: Challenges of asynchronous communication 57:01

3 years ago57:01