Wednesday, December 9, 2020
Analytics should be more than a buzzword used to sell your application - it should be an experience.
Building an insight-driven application shouldn't take up half your roadmap. Learn how you can easily use different disparate data sources to develop a modern and beautifully designed dashboard that can be easily embedded into applications.
We’ll dive into how you can use platforms to seamlessly embed an analytics experience, and also how you can aim for aspirational analytics using REACT or more modern architecture frameworks.
Since the mid-1980s, relational databases have been standard for most applications needing to store and query structured data. As architectures became more complex, databases have generalized to fit a variety of use cases. Simplicity was key: databases encapsulate storage, indexing, caching, querying, and transaction management, all under a unified SQL view.
Alex Silva examines what could happen if microservices could “unbundle” the database into its separate constituents and distribute these concerns into different layers and be able to optimize them individually. He proposes a stream processing architecture that can be used to successfully “deconstruct” the database while analyzing the challenges and pitfalls.
You’ll approach subscription and replication protocols under a different light by exploring how relational databases have overcome these challenges and focusing on what works and what doesn’t while discussing the paradigm shift proposed by stream processing and the architectural differences between the two approaches.
Building performing React apps is hard. Like really hard. You have to know how to setup webpack, Babel, code-splitting, TypeScript, and the list goes on.
In 2020, when building React web applications, my default choice is Next.js. It offers built-in performance, route prefetching, dynamic imports with code splitting, and probably the best server-side rendering experience — all of that with a no config setup.
By the end of this talk, you'll be a lot less scared of creating high-performance web applications that are scalable with both static and dynamic serverless components.
Observability contains many aspects - metrics, logging, tracing, alerts, and more. There are so many open-source tools to accomplish these tasks but which are considered the right ones? And what are the best practices?
In this session, we’ll discuss why observability within distributed systems is essential to understand how your application is performing and ensure reliability at all times. We’ll also review the most popular open-source monitoring tools, and explain the Whys, Whats, and Hows in your observability journey.OPEN TALK: The Open-Source Observability Playbook
You want to build great cloud-native applications. You don’t want to bother with cumbersome server infrastructure. Microsoft Azure offers a host of serverless choices, but where to start? In this session, we will explore the “bread and butter” serverless offerings that form the building blocks of most applications. We’ll take a deep dive into an open source content management system that was built serverless from the ground up on Azure. We’ll start with Azure Functions and humble Storage Accounts, and we’ll progress all the way to worldwide Content Delivery Networks. Together, we’ll build a complete, full-stack application without provisioning a single server.
In this session we will walk through the nuts and bolts of designing a microservice for a complex business need. We will go over some conceptual considerations such as eventual consistency through messaging and data ownership. We will also go over the implementation of event sourcing and command-query responsibility segregation (CQRS), what that would look like within a single microservice, and how they relate to an entire system.
Building a healthy development team has never been more challenging for start ups, but this is not another talk about hiring. It is about necessary endings. Being a newly born startup in Germany’s startup capital in need of fast results, we have often hired too fast but rarely fired too slow.
This talk will not prescribe the right way of growing an engineering team because small startup founders are beggars and not choosers when it comes to staffing. It is about a balanced trade-off. Motivating and shaping software engineers is a no-brainer, however, letting people go has never been popular thus crucial to the health and growth of the team.
Hiring developers in Germany’s start up capital is hard, but as the CTO, it’s one of your most important tasks. Startups in need of quick results hire fast and sometimes this leads to making a less than ideal hire. Successfully navigating this circumstance is difficult as you seek to balance: ensuring your team culture is healthy, developing your juniors, managing people out and when need be having tough conversations and letting people go, while maintaining a good relationship.
How to Become a Great Developer: Case Studies of How Individuals Rose from Nowhere to Become ExpertsJoin on Hopin
After mentoring many developers over the years, I summarized the advice into a trending article on LinkedIn. Here are case studies of how individuals rose from nowhere to become experts.
22,000 is the number of public APIs referenced on ProgrammableWeb. In such a competitive environment, providing good APIs is not enough.
How long does it take for your users to understand what your API does? How long to create an account? How long to make the first API call? Do you provide guides? Code samples? SDKs (generated or manually written)? Do they need to write code to test your APIs? What tooling are you offering? Are you open and transparent with your users?
In this talk, we will take a look at the things that need to come in addition to your APIs to offer the best on-boarding process and an outstanding user experience.
RED (Rates, Errors, Duration) is a spinoff from Google’s Golden Signals designed for monitoring microservices. However, RED use has clearly demonstrated that the applicability is applicable to any services-based architecture.
With RED, unlike the modern belief in observability, your architecture is watched from aspects of multiple dimensions. You receive alerts and indications not just from anomalies, but also from headache alerts. By seeing multiple dimensions of concerns, be they failures in service or activity to close to the edge of capability, these combined monitors and deep-dive, focused access get you to your root cause faster, with less false positives and quicker resolution.
Join Dave McAllister as he explores a RED driven analysis of an active application environment.
The open source software community continuously supports and advances the adoption of CI/CD best practices and toolsets.
For example, the CD Foundation serves as a vendor-neutral home of many software projects within CI/CD space, such as:
1) Jenkins X, a Kubernetes-native continuous delivery solution for cloud applications. This project uses a completely new architecture and code base in comparison with the original Jenkins project.
2) Spinnaker, an open source, multi-cloud continuous delivery
3) The Tekton Pipelines project, which provides Kubernetes-style custom resources for declaring continuous integration and delivery pipelines. Spinnaker can use Tekton as its pipeline engine.
4) And more
What’s more is that the open source community is helping to define shared terminology, open standards, and abstractions for CI/CD to help enterprises increase performance and software delivery. These resources help to assist with interoperability between CI/CD components, and also promote innovation in the areas that can provide the most value to the business.
This talk outlines important initiatives taking place and ways to tap into community resources and get involved so we can all work together to accelerate CI/CD adoption around the world.
Attendees will learn:
- A brief overview of multiple open source projects and how the community is working toward interoperability between them to serve as a model for the future of software.
- Take a look at the goals of the open source community today and key initiatives such as CI/CD landscape, security, diversity and MPs.
- How to get involved in open source projects to drive forward the direction of CI/CD and make software delivery better for everyone.
The ongoing data revolution has a new front: financial services. Even with so much data created, financial services data is often siloed and lacks accessibility. The emergence of open banking is enabling a new relationship with financial data and new possibilities for innovation.
In this session we’ll discuss the shift to an open financial ecosystem, shifting control to consumers, the regulatory market shifts toward privacy and permissioning, what the impact is for technologists and developers, and how AI enabled by open banking is being leveraged to improve financial literacy and inclusion.
This talk presents a variety of different tools that teams can use to determine if their product is accessible to all their users. Specifically, I plan to introduce the audience to:
- screen readers (using ChromeVox, a free web-based screen reader, as an example)
- high contrast mode
- magnification mode
- scripts that help detect potential accessibility issues
I will introduce these topics via demonstration on a laptop. The audience will hear what a good screenreader experience vs a bad screenreader experience looks like. They will see how different ways of styling your page make it more or less possible for the text to be magnified. They will learn about keeping contrast high between text and the background.
If time permits, I will also demonstrate how to test some of these features on mobile devices (navigation, for example, is quite interesting to see on mobile devices). As well as topics that are somewhat unique to mobile devices such as touch target size.
I will not cover how to go about how to implement the variety of issues we will see. I intend for this talk to serve as an introduction, allowing people to investigate the state of their own products and justify spending time improving their products' accessibility.
"DevOps" is the operations people’s crafty plan to make developers do other people's work, but we are smart enough to see right through this naive rebranding trick!
Baruch suggests you think about it: we, the developers, have written all the code. It passes all the tests; it obviously works, and works well (Are we a little proud? We are!); so we are DONE.
Now, out of the blue, a bunch of "thought leaders" (all with an operations background, mind you!) are trying to tell us that we have to learn YAML, Docker, Kubernetes and Terraform to deploy our software because suddenly it is our concern?!
In this talk, we'll discuss why developers do or don’t need DevOps. We'll consider arguments made by DevOps visionaries and see whether they hold water. Hopefully, by the end of the talk, we'll understand whether DevOps really helps developers to deploy better code to production more often, or if it is just another scam made up by marketing and evangelists.
Identity on the web isn’t so much broken as it is non-existent. With no universal identity layer for the Internet, services and applications have resorted to building walled-garden identity models that have no use on the broader web. The result: a fragmented identity experience across services and a near-constant cycle of major password breaches.
The root cause of this siloed identity model is the way we authenticate users today. In this talk, we will examine this relationship and discuss how technologies such as blockchain and zero knowledge cryptography can be used to build a more secure, user-centric, and universal identity for the web.
Thursday, December 10, 2020
Have you felt frustrated by your team's speed of execution? Have you asked yourself, perhaps in the middle of a sprint planning session: Are we stuck?
Why do some teams seem to work faster than others? Why do some people perceive a team as too slow, while others consider the same team fast enough? And engineers on some teams appear to be more satisfied and more motivated than those on other teams; why?
Engineers don't lack motivation -- it is systems that fail to create an environment for engineers to make magic. In this talk, I’ll lay out a step-by-step guide for managers and ICs to ask the right questions towards this problem.
Alignment: Are the team’s goals and metrics aligned with the business? Is the team aware of broader priorities and constraints? Is there agreement around when to optimize for user-visible features vs technical debt? Is there alignment around what exactly the team owns?
Doing Too Much: Is the team keeping too many projects active at the same time? We’ll talk about how to identify if this is happening, and how to use metrics and models to choose what to prioritize.
Thrashing: Big and frequent changes in priority can make engineers take the priorities themselves less seriously— but such change is a reality in a fast-growing company. How do you reduce thrashing as well as increase adaptability to change?
Deep, slow projects: Some projects simply take a long time. This is especially true for infrastructure work. In this context, it’s important to demonstrate value early— engage with users, go deep before going broad.
As a manager or lead developer, this talk will give you a playbook to analyze and work on your team’s engineering velocity— and ultimately, to create an environment where people work together at their highest potential.
As we have seen with solutions from technology companies, the world is changing due to innovation in Perception, Mixed Reality (MR) and Artificial Intelligence. How about extending this relatively new immersive technology (MR) to create experiences that add value in different sectors?
In this talk, we would look at an introduction to Mixed Reality and see how some of these solutions are being used to create unforgettable experiences.
We would also look into:
- Mixed Reality as a way to change (evolve) the way we do computing in the new decade
- How to get started in building Mixed Reality experiences.
- Platforms where Mixed Reality experiences can exist.
- Real-world problems that Mixed Reality applications can help solve.
o your company just took a round of funding and you’ve been asked to rapidly grow your engineering team? Congratulations! This is an exciting challenge. It can also be daunting. You’re in for a lot of hard work, a lot of organizational changes, and the satisfaction of building an amazing new team. I’ll share some experience and advice from being given this challenge multiple times at both large and small companies.
Who is this for?
My advice will mostly focus on growing teams of ~10 to teams of ~40, but much of the advice applies to any serious hiring push regardless of current team size. The people who will get the most out of this are managers of multiple teams, VPEs/Director’s of engineering at smaller scale startups, but also people that are part of an interview panel on a fast growing team.
In this talk we will demo an optimized PDF workflow using pdfOCR to recognize data in PDF documents, and pdf2Data to extract selected data from your OCR search. The beauty of using pdf2Data in this way is it can pick up exactly where pdfOCR leaves off, allowing you to both recognize and extract all kinds of data from PDF documents that would otherwise be inaccessible.
pdf2Data is our iText 7 add-on for smart data extraction from PDF documents. It’s tailored especially for extracting hard to reach data locked inside PDFs, and it fits neatly into the iText 7 ecosystem. The cherry on top? Anyone can quickly create a template for data extraction using the sleek user interface, with no need to tediously define document structures programmatically. Let the template designer assist you in creating your data extraction templates; no coding required!
If you haven’t tried it already, we’d like to give you a quick tour of its capabilities, while also demonstrating how it’s a great companion for our pdfOCR add-on.
Context switching between your IDE, Github.com, JIRA, Terminal, and Slack is no way to optimize collaboration and it results in countless hours of distraction and lack of focus, hurting code quality. Team alignment and productivity depend on just the right mix of collaboration and staying in the zone. Extensible IDEs are opening the door to great innovation in developer workflow. Turning the IDE into the true Hub of the development flow is the best way to integrate the essential tools into a cohesive and streamlined process. In the future, your code host, issue tracker and messaging app will be placed where they belong: In your editor. Here we will discuss how such an integration should happen, and we will spell out the benefits that accrue to the individual developer, the team and the organization.
Logs are ubiquitous and indispensable. They are arguably the most important tool used by software engineers in our day-to-day work. In development, we use them to mark key points in our code, so we can peek into its execution (without using a debugger). In production, they serve as a way of understanding software execution in the real-world, providing immense value at both the macro and micro levels; they can be used to diagnose systemic problems, which affect your entire user base, but also to trace the journey of a single user, thus allowing you to provide individualized support.
Unfortunately, most companies are not taking full advantage of logs, because they fail to see what logs really are: a source of rich, real-time event data. In this session, we will explain how the Observability team at Brex unlocked the power of logs by allowing other teams to access and build on top of structured log streams. This was accomplished by (1) designing and implementing a super-powered logging infrastructure, which delivers log messages to multiple consumers in near-real-time, and (2) creating a strict log schema as well as a schema-adherent logging library to make the underlying data useful and coherent.
We will also deep dive into a particular use case: powering the alerts used by our Fraud team to identify suspicious behavior.
Your first time as a manager is not easy. You say some wrong things, make a few wrong decisions, and face lots of uncertainty. Being a great developer doesn't guarantee that you can help others be better developers.
This talk is about what I learned after going from a senior engineer in a team of three to managing a team of seven engineers. I will focus on the things you can do to prepare yourself if you are making the same transition, and the things a senior engineering leader can do to help someone in that transition.
Blockchain has revolutionized the technology industry—yet the barrier to entry has left many developers without a path to connect to the world of crypto despite its emergence as the next wave of technology. How can developers forge a path to adoption when walking through uncharted territory? In this workshop, Michael will discuss how to move the dial for developers to connect, communicate, program, while building trust, utility, and liquidity for a blockchain powered economy. The RippleX open-source platform, which targets a network of more than 20 million developers globally, allows developers to get started with blockchain, without needing to know the nuances of the underlying protocols. Michael can discuss how a platform approach is moving the industry forward to improve the way that developers transact using protocols such as the XRP Ledger, Interledger and PayID, and what that means for the broader world of finance.
Summary: To share how R3 brings an enterprise grade blockchain software to the open source communities and how we help the community participants build their blockchain solutions.
1.Brief introduction of Corda and client case
• Technical overview and architectural benefits of enterprise blockchain
• Client case study, with a brief demo.
2.R3's approach to reaching out to the OS community, and how R3 increases the developer experience for OS project Corda?
• Project Braid: Braid is an open source tool that we had developed with an external team aiming to streamline the Corda developers’ deployment process. It starts a Vertx web server, automatically reads in the Corda application, and exports an API template. The API template can then be used to generate the API library using OpenAPI-genrator, which is another open source tool. The process can generally shorten the development cycle by at least 15%.
• In-house projects: We have developed multiple tools that help our developers have a better experience. This includes a web IDE and a Corda VSCode extension. I will share our journey of making such tools available to the communi
Well written instructions, informative comments throughout code, clearly scripted screencasts, and smart information architecture can take complex code and make it accessible to new developers. In the age of code sharing, this can be imperative to teaching the next generation of developers, passing along your code to successors, and help you better understand your own work.
When I was an engineer, helpful READMEs and other docs created by my colleagues were crucial to quick onboarding and coming back to old products. Now, as a full time technical writer, I rely on our engineers to be able to concisely explain how products work. From these experiences, I feel it is essential that everyone feel empowered to write documentation, not just the technical writers.
In this talk we’ll discuss:
+ Why writing docs is important for engineers
+ Understanding your audience
+ Optimizing for the deliverable: READMEs, code comments, tutorials, release notes, and more
We’ll also cover some tips for communicating about your past work to your future self.
Blockchain has undoubtedly broken the Internet in the past few years. This technology enabled developers to disrupt not only financial systems but also virtually every industry. Blockchain gave rise to the development of Decentralized Apps. Dapps have interesting properties: they are fault tolerant, auditable, open source, and there is no central control after they're deployed. They also incentivized people to run them with currency that's worth money.
This presentation is about building a Decentralized App with Node.js on top of the Ethereum network using Truffle and web3.js.