98 Avsnitt

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

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

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

    Publicerades: 2022-05-31
  4. #74: SOAP: (not really) Simple Object Access Protocol

    Publicerades: 2022-05-16
  5. #73: Neo4j: all your data as a graph?

    Publicerades: 2022-05-10
  6. #72: React.js: library that won frontends?

    Publicerades: 2022-05-06
  7. #71: Erlang: let it crash!

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

    Publicerades: 2022-04-12
  9. #69: DevOps: not a job position, but culture and mindset

    Publicerades: 2022-02-14
  10. #68: ACID transactions: don't corrupt your data

    Publicerades: 2022-02-01
  11. #67: Version control systems: auditing source code, tracking bugs and experimenting

    Publicerades: 2022-01-25
  12. #66: Aspect-oriented programming: another level of code modularization

    Publicerades: 2022-01-18
  13. #65: Zero Downtime deployment: If it hurts, do it more often

    Publicerades: 2022-01-10
  14. #64: TypeScript: will it entirely replace JavaScript?

    Publicerades: 2022-01-03
  15. #63: Logging libraries: auditing and troubleshooting your application

    Publicerades: 2021-12-27
  16. #62: Object-relational mapping: hiding vs. introducing complexity

    Publicerades: 2021-12-20
  17. #61: Spring framework: 2 decades of building Java applications

    Publicerades: 2021-12-15
  18. #60: Haskell: purely functional and statically typed programming language

    Publicerades: 2021-12-07
  19. #59: How compilers work: from source to execution

    Publicerades: 2021-11-29
  20. #58: Consumer-driven Contracts: TDD between services

    Publicerades: 2021-11-22

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