Follow the documentation-as-code approach: Write documentation in your IDE, collaborate with other developers and writers using version control and let a continuous integration server scrutinize and publish your docs.
AsciiDoc is a lightweight markup language that translates for example to HTML and PDF. In a development environment, an IDE plugin provides editor support and preview pane.
Participants work in small groups using a web-based collaborative editor or their local IDEs. With small katas they will learn how to format text, structure documents, use images and embed diagrams. The workshop closes with a Q&A session to share best practices that participants can apply to their projects.

Learn about Everything-as-Code approach from our experience to enable effective and successful collaboration between hundreds of engineers by GitOps approach. In this session, I on-board you to “as-code” and GitOps practices and I share how have we married them to build “infrastructure-“, “observability-” and “permissions-“ as-code services. I will give you tips on how the system should be designed to help you start with GitOps quickly.

What’s Everything-as-Code?

Everything as Code is the practice of treating all parts of the system as code. This means, storing properties of your system along with its source code in a repository such as git. When we additionally apply GitOps practices – we get a single-click automation backed by review, dry-run workflow and auditing for free!

How have we applied GitOps in our company?

In Dynatrace, more than 1000 devs across multiple locations and timezones collaborate every day. Automation is key to support fast-paced innovation. We’ve started from a hackathon to build first version of project Monaco (aka MONitoring As COde) – where we essentially automate observability as code. Then, we realized we can apply same approach to any area – for instance by “permissions-as-code”, anyone and anytime can elevate their permission to access new services by submitting just a pull request.

How can I start with GitOps?

The most important enabler for GitOps is proper RESTful API. We’ll go through most important guidelines on how API should be structured. Then, I will teach you how a basic GitOps workflow looks like. Finally, based on open-source project Monaco, we’ll learn that applying a state from the repository can be easily achievable.

I’m sure that after this session many of you will be inspired that your team and maybe even users of your platform can unleash unprecedented power of automation and effectiveness.

Facing a global pandemic has been (and continues to be) an incredibly challenging period. There are very few people who have not seen dramatic impacts on their lives as a result.

While we as humans have been facing this struggle, a similar problem has been emerging in our software development community. Not only are we finding more vulnerabilities in our software than ever, but those weaknesses have been affecting a larger proportion of our software ecosystem.Are there lessons we can take from the last few years and the changes we have made to protect people from a pandemic and apply them to our software ecosystem? I believe there are.

In this talk, we will look at how the relationships between software projects improve our world whilst also making us vulnerable. We will do this by diving into the structures between codebases and looking at how these affect the risk faced by our people, data, and systems.

The end of password-based authentication is near. Weak passwords are the cause of endless security breaches, and the constant reuse of the same password across different accounts is what keeps the clock ticking for the next breach to happen.

The FIDO2 standard aims to replace passwords entirely, and there is a good deal of chance that it will succeed. It has gained significant momentum in the past couple of years, as all major browser and operating system vendors fully jumped on board.

This talk will provide a deep dive of the FIDO2 and W3C WebAuthn standards, with the main focus on how to quickly implement it on any application using open-source FIDO Alliance conformant libraries.

Best practices, including security token lifecycle management, will also be covered.

The idea of the talk is to present Apache Kafka in a different light. To pass the question “What makes a database?” and see if Kafka fulfils the requirements and to find the answer to “Should you use Kafka as a database?”.

A small unfortunate Java source code snippet is rushed to the emergency room with a multitude of symptoms (code duplication, complex logic, hidden bugs). Together we will diagnose it and attempt to gradually refactor it back to health.

How do you mix SQL and NoSQL worlds without starting a messy revolution?

This live coding talk will show you how to add Elasticsearch to your legacy application without changing all your current development habits. Your application will have suddenly have advanced search features, all without the need to write complex SQL code!

David will start from a Spring Boot/MySQL based application and will add a complete integration of Elasticsearch, all live from the stage during his presentation.

You have plenty of Open Office, Microsoft Office, PDF, images… documents and you may want to be able to search for their metadata and content. How can you do that?

In this talk, David will explain how Apache Tika can be used for that and how to combine this fantastic library with Elastic Stack:

* Elasticsearch [ingest-attachment plugin](https://www.elastic.co/guide/en/elasticsearch/plugins/current/ingest-attachment.html)
* [FSCrawler](https://github.com/dadoonet/fscrawler)
* [Workplace Search](https://www.elastic.co/workplace-search) connector for FSCrawler to have a ready to use and powerful user interface for your documents.

Amazon Appstore is bringing your Android apps to Windows 11! The Windows Subsystem for Android enables your Windows 11 device to run Android apps and games that are available in the Amazon Appstore. Join us as we explore how you can use Windows Subsystem for Android to develop, test and debug your apps & games. We will also dive into how you can optimize your apps & games for Windows via Amazon features and tailored UX/UI improvements for desktop.

Тhe proven go-to solution for many common programming scenarios are the design patterns.
Not only generic and easy to extend but swift to tweak for your needs.
We will focus on some of the most useful Solidity Design patterns — knowledge that will truly come in handy when writing smart contracts for your dashing DApp.

Mainframe technology, nowadays called IBM Z, is more relevant than ever in today’s IT infrastructure. You probably make use of it on a daily basis without knowing it. During this session You will learn what mainframe technology is, how it is being used and how it integrates in a (Hybrid) Cloud environment. We will discuss how development on a mainframe is being done using the same modern tooling like any other platform and how you can start learning it yourself.

gRPC is a modern, high-performance framework that evolves the age-old remote procedure call (RPC) protocol. In cloud-native applications, we often work across programming languages, frameworks, and technologies. This interoperability complicates message contracts and requires great effort for establishing efficient cross-platform communication. gRPC provides a “uniform horizontal layer” that abstracts these concerns. Developers code in their native platform focused on business functionality, while gRPC handles communication unification.

In this session I will give you an overview of the gRPC, why and when to use it and why we have chosen it for mission critical applications. You will find out the benefits and drawbacks of this solution and in the end we will have a glimpse of what the future of gRPC will look like.

We will explore the differences between CPU-bound and IO-bound work as well as how both could be optimized. Starting with a quick theoretical introduction, we will then move on to code examples and benchmarks on both parallel and asynchronous challenges. We will see when we should vs. should not parallelize specific tasks. We will look at some best practices for exception handling and avoiding memory leaks when programming concurrently. Finally, we will briefly cover what libraries .NET provide us with to simplify our data processing.

In this session, we will journey through planning and executing the creation of a software product from the lenses of a solutions architect or a technical lead. We will explore the main characteristics of a software product. We will look at the differences between software as a product and a project. We will learn to plan and design our solution’s architecture to make it flexible, extendible, and maintainable. We will see what architectural features to focus on and which pitfalls to avoid. And finally, we will discuss how to best use product roadmaps for optimal results and successful execution.

This session is intended for software and solutions architects, development leads, technical project managers, and curious product managers who want to see the process from a technical perspective.

The Spotify model is an innovative agile approach, which focuses on scale and emphasizes on the importance of culture, network, people engagement and contribution. It helps organizations to increase their innovation approach, communication, accountability and quality. The model successfully combines technology and culture. We’re going to talk about squads, tribes, chapters, guild and alliances without going back to ancient times.

Mobile apps have become very popular in the past 10 years and a lot of companies are developing mobile apps or even basing their business around the mobile applications. However there is more than one operating system that runs on mobile phones – the two mostly used ones are iOS and Android. This would typically require building two separate mobile applications. A number of frameworks have emerged with the aim to simplify the development and minimize the cost and burden of building two separate applications – such as ReactNative, Flutter and others, all of which have their pros and cons. Kotlin Multiplatform is an emerging new technology aiming to approach the mobile application development from a different angle. We will showcase what the technology is about and why we think it has a unique advantage in specific use cases compared to the other Multiplatform solutions.

Nino spent the last six months focused on finding the most dangerous vulnerabilities and attack strategies against Microsoft Azure Technologies. In this unique 100% practical security session Nino will show the very dark side of advanced hacking techniques, and showing real unedited attacks to Azure Functions, App Services, AppFabric, Kubernetes, Web Jobs, Virtual Machines, BizTalk Server and more. Nino will also discuss fascinating points about some vulnerabilities he sees in cloud architecture, and he will provide his point of view to prevent this type of attack. It is a session for people to understand how hackers operate and how to protect from these very dangerous and effective attacks against serverless and Azure technologies.

In this session we will examine the most effective and dangerous attacks to the cloud, source code, scripts, protocols, configurations and more, no holds barred. We will see how a hacker thinks, creates his attacks and how he performs them. For each attack we will see the best defense and the prevention. A practical session full of invaluable information for every corporate asset and professional.

The talk will focus on the importance of knowledge sharing for promoting Technical Excellence at Scale. This topic has always been relevant for bigger organizations, while smaller ones have usually relied on Tribal Knowledge. But in today’s world we often see successful start-ups experiencing rapid growth – starting with just a small team of engineers and ending up with hundreds of engineers in just a few years. Imagine your engineering team doubling or tripling in size in a year or just a few months and a few of your initial key engineers leaving during that same period. How do you handle that without sacrificing the quality of your Software Delivery? One of the keys is, you guessed it, organizational policies that enable effective and efficient knowledge sharing which in turn promotes Technical Excellence. This is crucial for scaling your organization successfully. At Tide we’ve seen our Engineering Team more than double in size in the past year. Based on our experiences I’ll discuss what we’ve learned about policies and practices that do NOT scale well and ones that DO scale well as the organization grows. The talk will try to answer the following questions:

• Why Tribal Knowledge doesn’t scale well?
• What is “The Bus Factor”?
• Why does your Organization need Software Engineering Principles?
• Why does your Organization need Guidelines?
• Why do you need to automate them?
• What is Chesterson’s principle?
• How to create documentation that would allow readers to understand decisions made years ago?
• What is LADR?
• How can you automate documentation creation? (Open API, Async API etc.)
• Why does your Organization need a structured process for onboarding new engineers?
• Why does your Organization need Induction Sessions?
• Why are Code Reviews important for Technical Excellence?
• Why does your Organization need a Service Catalogue? (Backstage etc.)
• How do you handle Deprecation?
• Why does your Organization need Interest Groups?

In the current situation of increased remote working, having a common, easier to understand medium of communication such as an OpenAPI spec document is indispensable.

Things get exciting when this so-called OpenAPI spec document can help you build APIs and AUTOMATICALLY VALIDATE YOUR APIs! An OpenAPI spec document can also serve as a contract, generate clients, servers, documentation, and much more…

When this OpenAPI document can also:

• Put your developers, clients and client’s developers first!
• Have Automatic, Fail-fast, API Contract Validation!
• Be Cross-Platform and Language Agnostic!
• Generate clients, servers, and documentation from OpenAPI specs in a plethora of languages!
• Simplify communication by means of a common document in YAML or JSON!
• Speed up development, prototyping, R&D, etc.!
• Reduce costs! Using contract tests in conjunction with (or as a replacement for) traditional end-to-end integration tests will be cheaper in the long run.

… things get even more interesting in the demo…

Come at our talk and find out more!

CodeQL is a free and powerful static analysis tool to look for vulnerabilities in OSS projects. It is commonly used to detect known vulnerability patterns and their associated variants in code. CodeQL queries are usually aimed towards very specific vulnerabilities for variant analysis purposes and are often integrated into CI/CD pipelines to automatically detect bugs. For this reason, CodeQL is configured to operate in a developer-first mode which will reduce false positives to a minimum and return the most accurate results. However, CodeQL can also be configured to operate in a less conservative, more security researcher friendly mode which results in more false positives but also less false negatives.

In this talk, Alvaro Muñoz of the GitHub Security Lab will use Log4Shell to demonstrate CodeQL in action. He will review Log4Shell’s root cause, how it manifests in code and how it could have been discovered using CodeQL. In this process he will discuss some specific examples of what it means to operate on each of the above-mentioned modes and how someone could configure CodeQL to better serve their objectives, either as a security researcher or a developer.

Blockchain technology continues it’s vast growth and every single day new products gets release. In that session we will discuss what is the general direction of development of the technology and also will summarise the highlights from 2021 and 2022.