98 Afleveringen

  1. #77: DDoS: take down a server, one request at a time

    Gepubliceerd: 13-6-2022

  2. #76: 12th Factor App: portable and resilient services start here. Part 8-12/12

    Gepubliceerd: 6-6-2022

  3. #75: 12th Factor App: portable and resilient services start here. Part 1-7/12

    Gepubliceerd: 31-5-2022

  4. #74: SOAP: (not really) Simple Object Access Protocol

    Gepubliceerd: 16-5-2022

  5. #73: Neo4j: all your data as a graph?

    Gepubliceerd: 10-5-2022

  6. #72: React.js: library that won frontends?

    Gepubliceerd: 6-5-2022

  7. #71: Erlang: let it crash!

    Gepubliceerd: 26-4-2022

  8. #70: CRDT: Conflict-free Replicated Data Type (guest: Martin Kleppmann)

    Gepubliceerd: 12-4-2022

  9. #69: DevOps: not a job position, but culture and mindset

    Gepubliceerd: 14-2-2022

  10. #68: ACID transactions: don't corrupt your data

    Gepubliceerd: 1-2-2022

  11. #67: Version control systems: auditing source code, tracking bugs and experimenting

    Gepubliceerd: 25-1-2022

  12. #66: Aspect-oriented programming: another level of code modularization

    Gepubliceerd: 18-1-2022

  13. #65: Zero Downtime deployment: If it hurts, do it more often

    Gepubliceerd: 10-1-2022

  14. #64: TypeScript: will it entirely replace JavaScript?

    Gepubliceerd: 3-1-2022

  15. #63: Logging libraries: auditing and troubleshooting your application

    Gepubliceerd: 27-12-2021

  16. #62: Object-relational mapping: hiding vs. introducing complexity

    Gepubliceerd: 20-12-2021

  17. #61: Spring framework: 2 decades of building Java applications

    Gepubliceerd: 15-12-2021

  18. #60: Haskell: purely functional and statically typed programming language

    Gepubliceerd: 7-12-2021

  19. #59: How compilers work: from source to execution

    Gepubliceerd: 29-11-2021

  20. #58: Consumer-driven Contracts: TDD between services

    Gepubliceerd: 22-11-2021

2 / 5

Podcast for developers, testers, SREs... and their managers. I explain complex and convoluted technologies in a clear way, avoiding buzzwords and hype. Never longer than 4 minutes and 16 seconds. Because software development does not require hours of lectures, dev advocates' slide decks and hand waving. For those of you, who want to combat FOMO, while brushing your teeth. 256 seconds is plenty of time. If I can't explain something within this time frame, it's either too complex, or I don't understand it myself. By Tomasz Nurkiewicz. Java Champion, CTO, trainer, O'Reilly author, blogger

Visit the podcast's native language site