All decks
  • Slow App

    You did great job finishing this web app on time and budget. Design patterns, good code coverage, cutting edge frameworks and best CI ever. It goes to production and boom, clients complain it's too slow. They don't really care, if it's best engineering ever, if each view loads 2 seconds. My presentation will give you hints on how to look for bottlenecks. I will also share simple tricks to make the app work faster, or at least seem to work faster.

  • DevConf - slow app

    You did great job finishing this web app on time and budget. Design patterns, good code coverage, cutting edge frameworks and best CI ever. It goes to production and boom, clients complain it's too slow. They don't really care, if it's best engineering ever, if each view loads 2 seconds. My presentation will give you hints on how to look for bottlenecks. I will also share simple tricks to make the app work faster, or at least seem to work faster.

  • Devoxx - slow app

    You did great job finishing this web app on time and budget. Design patterns, good code coverage, cutting edge frameworks and best CI ever. It goes to production and boom, clients complain it's too slow. They don't really care, if it's best engineering ever, if each view loads 2 seconds. My presentation will give you hints on how to look for bottlenecks. I will also share simple tricks to make the app work faster, or at least seem to work faster.

  • Slow-app

    You did great job finishing this web app on time and budget. Design patterns, good code coverage, cutting edge frameworks and best CI ever. It goes to production and boom, clients complain it's too slow. They don't really care, if it's best engineering ever, if each view loads 2 seconds. My presentation will give you hints on how to look for bottlenecks. I will also share simple tricks to make the app work faster, or at least seem to work faster.

  • Powolna Aplikacja

  • JUG - Powolna Aplikacja

  • Engineering studies vs job market

  • Testowanie sprawą całego narodu!

    Programiści programują, testerzy testują. A co kiedy w projekcie nie ma testerów? Kto odpowiada za jakość, kiedy nie ma działu Quality Assurance? Odpowiadają wszyscy. Zawsze. Największy wachlarz możliwości mają programiści, ale nic nie stoi na drodze Product Owner'owi, który chce pisać testy automatyczne.

  • Jednolite zespoły

    Kariera IT, Wrocław 2017

  • Why you should (not) use Scala on production

  • Smutny zgodny zespół

    Chamberconf 2016