Building a Web Application is really common nowadays. Virtually everyone is in some kind of web project. Also everyone is running after the next new and shiny thing, be it a revolutionary framework, amaizing library or whatever is currently talked about. However if you do just that your project sooner or later will end up having great technology without good architecture and you will discover it’s weaknesses. I would like to walk you through some battle proven design patterns and solutions that will help you design a system that will be maintainable, testable and most of all one that people will want to work with. I’ll also show you that you don’t have to resign from new toys. You just need to know how and when to use them.
How can you speed up environment creation process?
This presentation shows how new technologies and solutions can be used in projects and how to adapt them without making basic pipeline errors in environment art. We will look on high level of pipeline process to seek the solutions on how to speed it up.
I have one thesis for you: every programmer is also a UX guy. Do you agree? I hope I can convince you! I’ll talk about the following problems and solutions:
When we develop our software, there's no worse thing than flickering tests. Seriously. It's hard to convince anyone to prepare automated tests if your tests blink like Christmas tree - especially if we talk about heavy system/E2E tests on working environment. Uncertain test results is not just QA's frustration, but also lost time and additional costs. Fortunately, there are plenty of approaches and libraries that will relief in development hell. I will show you how to deal with flickering tests and improve a little bit test culture in your team.