Luka has been doing computer stuff professionally for over half his life. Despises frontend, likes doing talks. Loves putting out trash fires for money. Runs Sekura Collective, a chaos management agency. Formerly engineering lead at meetup.com, infrastructure lead at noom.com, CTO/cofounder at hitlistapp.com and developer at deviantart.com. Splits time between Zagreb and New York. Dreams in matrixcode.
Since the dawn of software development, we’ve been faced with the same impossible choice every single day: do it quickly or do it well. We do our best to make the right choice for the task at hand, and we move on. Then came the lean startups & “Move fast and break things” and put their thumbs on the scale in the favor of the hacks, the MVPs, the just-ship-its, and the Product Managers just ate. it. up. That’s great, for proving a concept or finding a market fit. But what happens when that’s all you do? When the entire organization, top to bottom, has collectively forgotten how to write quality software. When you become unable to make the correct technical decision even by accident. We will take a deep dive on a mission-critical web application that is basically unusable on its best day, and trace the trivial bad decisions that got it there. You will never take a shortcut again.
|Zero-downtime datacenter failovers (Switching hosting providers for dummies)||Python Belgrade||January 2018|
|Don’t get pwned in 2018 - webapp lockdown checklist||Security StackUp||December 2017|
|Geo-distributed Development Teams in Practice||Drupal Heart Camp||May 2017|
|Security in the age of frameworks||FSec||September 2016|
|The importance of being a noob||Webcamp Ljubljana||March 2016|
|Web apps for mobile - hurdles and gotchas||MobileCamp Ljubljana||March 2010|