Build Stuff'16 Ukraine has ended

Sign up or log in to bookmark your favorites and sync them to your phone or calendar.

4. Sprint [clear filter]
Monday, November 21

11:25am EET

[SLIDES]Boyan Mihaylov @bmihaylov - Stop the Internet, I want to go offline
Traditionally we consider web sites to be working in an online mode only. If the Internet connection drops, the entire web site stops functioning. Mobile applications, however, change this perception as connection is considered unstable and applications should take necessary measures for good user experience. Now we are able to create web sites that react on changes in the Internet connection and provide certain functionality offline. AppCache, IndexedDB and File API are few of the mechanisms to allow us to store the application and its data in the browser. However, now we have some questions to think about: Who is the master of the data - the client or the server? What data should we download in advance? How do we handle updates of the application? In this talk I will give overview of how web applications can go offline and which precautions we should take.

avatar for Boyan Mihaylov

Boyan Mihaylov

Boyan is a software architect and developer, thinking both business and tech. Originally from Bulgaria, he works at a pension fund in the lovely Copenhagen, where with a team of highly motivated people they aim to transform the organization from being purely operational into becoming... Read More →

Monday November 21, 2016 11:25am - 12:15pm EET
4. Sprint

12:30pm EET

Denis Yaremov @yaremov - Offline-first application with Reflex
A client-server applications are locked inside request - response cycle and due to that when connection drops there's no way that application can work. On the other hand if user is allowed changing data while offline, this creates a wide variety of corner cases related to concurrent and conflicting changes. Reflex is a software methodology that provides a simple to understand concept makes offline-first application development simple. Reflex is not only about offline first. This is the architecture that makes web applications more robust, resource friendly and fault-tolerant. Most of the web applications we develop today can be made offline-first.


Monday November 21, 2016 12:30pm - 1:20pm EET
4. Sprint

2:20pm EET

[SLIDES]Mindaugas Mozūras @mmozuras - Engineering for Engineering's Sake
Code is a not an asset. Technology is not the solution to your company problems. And engineering for engineering's sake is not the answer. As engineers, we tend to focus a lot of our time thinking about "how?". How to solve this problem? How to structure code? How to name this method? We forget to ask "why?" and ponder the usefulness and greater impact of what we're doing. We don't work in silos. What we do affects our users. But not only that. It also affects our teammates and other developers in our organisations. Let's talk about why, having aforementioned things in mind, we should aim to write less code. Use less and more mature technologies. And don't do engineering for engineering's sake.

avatar for Mindaugas Mozūras

Mindaugas Mozūras

Head of Engineering, Vinted
Mindaugas Mozūras is a software developer, book reader, speaker, movie lover and an all around geek. Most of the time these days he spends doing his darned best to help make second hand the first choice worldwide as Head of Engineering at Vinted, world’s biggest preloved fashion... Read More →

Monday November 21, 2016 2:20pm - 3:10pm EET
4. Sprint

3:25pm EET

Serhiy Kalinets @skalinets - Making the Fun in Real World
Functional programming has been a hype for few years already. Almost every developer should already know that it isn’t just for scientific or financial programming but can be used for business applications as well. However it has not got wide adoption yet. It is still considered as a something like rocket science by many developers.
In this talk Serhiy will show how functional approach can be used in development of real life application. We will cover the process from development to deployment and end-to-end testing. And we will use F# everywhere.
Come to my talk and you’ll see how simple and elegant your code may be if you choose functional programming.

avatar for Serhiy Kalinets

Serhiy Kalinets

15+ years in development, regular speaker on various conferences and user groups (e.g. Build Stuff UA 2015), XP engineering practices coach.

Monday November 21, 2016 3:25pm - 4:15pm EET
4. Sprint

4:30pm EET

Izzet Mustafaiev @webdizz - Fabric8 CI/CD
Nowadays we cannot imagine development without Continuous Integration, the advance level of software engineering is Continuous Delivery. There are a lot of noise around this topic however successful implementations are still rare.

In this topic I'm going to share how to implement CI/CD in simple and efficient way using Fabric8 using theory and demo.

avatar for Izzet Mustafaiev

Izzet Mustafaiev

Izzet is a Software Engineer working in EPAM Systems with Java as primary language, hands on with Ruby/Groovy, exploring FP with Erlang/Elixir. Participated in different projects as a developer and architect. Advocating XP and Clean Code and DevOps habits and practices.

Monday November 21, 2016 4:30pm - 5:20pm EET
4. Sprint

5:25pm EET

Adam Dymitruk @adymitruk - Build your own tools
We look for the easy answers, rarely paying attention to the hidden costs of our decisions like total cost of ownership. Our operating systems, scripting languages, shells, JavaScript and network utilities give yes al that we need. We'll look at how to bootstrap without using issue trackers, continuous integration tools and specification libraries. This is a peek into an upcoming book on the subject that I'm writing.

avatar for Adam Dymitruk

Adam Dymitruk

CTO & FOUNDER http://AdapTechSolutions.net, AdapTech Solutions Ltd.
As a passionate technologist, Adam has worked in the field for a few decades in numerous roles. He has inspired organisations to excel in approaches to software in modern workflows, inspired a culture of learning and instilled a modern approach to software architecture.

Monday November 21, 2016 5:25pm - 6:15pm EET
4. Sprint

6:30pm EET

[SLIDES]Arthur Evoyan - Scalability of systems. Points of view and approaches.
In software development company there is always a conflict between developers and system administrators especially when it comes to the subject of scalability. Having experience in both gave me an opportunity to see it from both sides and experience in creation of scalable sysyems which I would like to share.

Key points

Why do we need scalability
Types of scalability
Who is supposed to do that
Facts from experience
Modular approach

avatar for Arthur Evoyan

Arthur Evoyan

Over 12 years as system administration, over 8 years as database architect, designer and development, over 6 years as application architect and developer in Legal, Banking, Gaming businesses.

Monday November 21, 2016 6:30pm - 7:20pm EET
4. Sprint
Tuesday, November 22

10:10am EET

[SLIDES]Kyrylo Novotarskyi @kNovotarskyi - Product=People. Service Discovery in TransferWise
Rather than traditional departments, TransferWise is organised into several highly autonomous teams, each focused on solving a specific business or customer problem. It's the very essence of a lean approach – effort invested is justified by quantifiable impact. So what does this mean for engineering? How does this approach affect our cooperation? Building a platform-wise solution like Service Discovery is a good example for this

avatar for Kyrylo Novotarskyi

Kyrylo Novotarskyi

After getting master in Kyiv Polytech, and spending a couple of years in outsourcing, was building a couple of amazing products in Ukraine (Sixt, IronSource), Germany (Happycar) and now in UK, joining TransferWise engineering team in London

Tuesday November 22, 2016 10:10am - 11:00am EET
4. Sprint

11:15am EET

[SLIDES]Alex West @birdsncherries - A Visual Thinking Warmup for developers
Do strong personalities dominate your development team? Are code reviews painful? Are you blindly following  orders from a backlog, or are you learning from observation? Visual Thinking Strategies, or VTS, is a cross­disciplinary technique applicable to anyone working in a  collaborative setting where observation is key. VTS develops critical thinking skills by viewing and discussing  works of art in a group. It is backed by over 30 years of field research showing its effectiveness and  accessibility. By allowing individuals to talk about art ­ without needing a background in the field ­ VTS  advances skills you can use to create more relevant products and stronger teams: Observing, Brainstorming,  Speculating, Reasoning with Evidence, Cultivating a Point of View, and Revision & Elaboration. During this interactive exercise, we’ll discuss selected works of art as a group. There are no right answers or  group consensus being sought. We’re creating an environment and process for looking, thinking, reasoning  and revision skills that are mission­critical to anyone working in a software design or development role. After  our group discussion, I’ll introduce the basics of image selection and facilitating VTS sessions within your  organization. In addition to the above, I’ll cover how VTS can help you and your team with the following:  Comfort with Ambiguity, Openness to the Unfamiliar, Civil Debate, and Willingness to Participate in Group  Thinking.

avatar for Alexandra West

Alexandra West

Creative Director/Founder, Nerd/Noir
Alexandra West is a production designer, international speaker, and Creative Director of Nerd/Noir. Her present interest is in bringing a visual thinking mindset into the world of collaborative work. Alex has a long history as a creative. After earning her degree in Art History from... Read More →

Tuesday November 22, 2016 11:15am - 12:05pm EET
4. Sprint

12:20pm EET

Anton Moldovan @antyaDev - Orleankka. Making Orleans F#un (since 2015)
Orleans is a runtime and programming model for building distributed high-scale systems based on actor model. Orleans is an implementation of an improved actor model that borrows heavily from Erlang, adds static typing, message indirection and actor virtualization, exposing them in an integrated programming model known as "Virtual Actors". Orleans has been used to build multiple production services, including back-end services for a number of popular games, like Halo 4. Unfortunately, despite being truly unique and practical project, Orleans didn't make a lot of fans in F# community, due to its dependency on static code generation, verbosity of programming model and complex configuration. Orleankka - is a complementary API for Orleans built with functional paradigm in mind. It brings proper support for F#, custom DSL that will be familiar to all Akka users, and heaps of other usability improvements over the original API. Be aware: demo heavy talk! Lots of code examples demonstrating major Orleans features done with Orleankka’s API will be presented.

avatar for Anton Moldovan

Anton Moldovan

F#; Distributed Systems Design; CQRS; ES; CEP; Actor Model

Tuesday November 22, 2016 12:20pm - 1:10pm EET
4. Sprint

2:10pm EET

James Nugent @jen20 - Building self-assembling, self-healing, systems in the AWS cloud
No-one likes being woken up with a PagerDuty alert at 4am for a problem which could resolve itself with no human intervention, but for looking at it a bit differently. When moving existing applications into the cloud, or designing new ones targeting the cloud, it's important to consider and take advantage of the capabilities of the target platform, while not locking yourself in to a particular vendor. In this talk we'll look at a variety of different types of software and look at real world deployment patterns for running them in a self-assembling, self-healing manner in the Amazon cloud, and about how we might be able to replicate some of these capabilities on other cloud platforms.


Tuesday November 22, 2016 2:10pm - 3:00pm EET
4. Sprint

3:15pm EET

Dylan Beattie @dylanbeattie - Webmasters, Full Stack Developers and Other Legends
Once upon a time, when the web was young, phones were dumb and people still thought progressive JPEGs were a pretty neat idea, there were people who called themselves... THE WEBMASTERS. They were brave, they were bold. Armed with a 56k modem and a stack of O'Reilly books, the webmasters were fearless in their ongoing quest, driven by a humble vision - to connect the entire world together. Using Netscape Navigator. Of course, that was a long time ago, and nobody really believes the stories any more. Some say the webmasters are gone. Some say they never existed in the first place - it was just a bunch of marketing people with delusions of grandeur. But a few, a select few, believe they changed. They evolved. They learned new skills, they embraced new technology... and the Legend of the Full Stack Developer was born. The history of software development is rich with tales of extraordinary individuals, whose knowledge of their own systems was absolutely unrivalled. But here in 2016, in a world where distributed systems, machine learning and autoscaling cloud systems are ubiquitous and the average web app uses three JavaScript frameworks, four server-side languages and six different kinds of caching technology, does it really make any sense to talk about full stack developers? Are we clinging to outdated paradigms, nostalgic for the simple days when one person really could know all the answers - or does overspecialisation represent a genuine threat to the established discipline of software development? And if it does - should we be resisting it, or embracing it as a change that's long overdue?

avatar for DYLAN BEATTIE


System Architect, Skills Matter
Dylan Beattie is a systems architect and software developer, who has built everything from tiny standalone websites to large-scale distributed systems. He's currently the CTO at Skills Matter in London, where he juggles his time between working on their software platform, supporting... Read More →

Tuesday November 22, 2016 3:15pm - 4:05pm EET
4. Sprint

4:20pm EET

[SLIDES]Oleg Chorny @OlegChorny - Nonfunctional Requirements as Gordian knot
Nonfunctional requirements (NFRs) describe system attributes such as security, reliability, maintainability, scalability, performance, supportability, usability, testability, etc.
Definition and implementation of NFRs is a critical concern for the system builder. Over-specify them and the solution may be too costly to be viable; under-specify them and the solution will not be adequate for its intended use. An adaptive and incremental approach to exploring, defining and implementing NFRs is a key.
But how does an Agile team include NFRs into their incremental releases? Let's discuss.

avatar for Oleg Chorny

Oleg Chorny

Microsoft MVP, Ciklum
Oleg is a DevOps Architect at Ciklum and leading a team who develop and maintain the infrastructure for ecosystem of financials products at American market. As Microsoft Trainer he spent years to deliver different courses to IT professionals. Today, as Microsoft MVP and coorganizer... Read More →

Tuesday November 22, 2016 4:20pm - 5:10pm EET
4. Sprint