# Posts on Adam Bennett Recent content in Posts on Adam Bennett This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Using feature flags in GraphQL DevFeed: [Using feature flags in GraphQL]() Original publisher: [Read original article]() Published: 2024-09-10T19:42:33Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [GraphQL](), [feature flags]() Tags: [algorithms](), [android](), [apollo](), [blog](), [career](), [compose](), [development](), [engineering](), [feature-flags](), [finance](), [functional](), [graphql](), [growth](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview This tutorial explains how GraphQL directives can conditionally include fields in queries. It shows how passing a feature flag to a directive, including with Apollo, can prevent risky new fields from triggering backend requests and causing an entire query to fail. ### Source excerpt I've been using GraphQL in some form or another for a couple of years now, and I have... opinions about it. Opinions notwithstanding, it's a supremely flexible and powerful tool, and I just want to highlight something here that it seems quite a few people don't know about. That something is Directives, which is a way of optionally including fields. But why is this useful? ## Avoid Reading Feature Flags Inside Functions DevFeed: [Avoid Reading Feature Flags Inside Functions]() Original publisher: [Read original article]() Published: 2023-09-29T22:45:18Z Content type: opinion Language: en Sources: [Posts on Adam Bennett]() Topics: [feature flags](), [Development]() Tags: [advice](), [algorithms](), [android](), [blog](), [career](), [compose](), [development](), [engineering](), [feature-flags](), [finance](), [firebase](), [functional](), [growth](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [performance](), [remote-config](), [server](), [software](), [startup](), [startups](), [state](), [thoughts](), [training](), [tutorial]() ### AI overview This article argues that feature flags should be read once and passed into functions or constructors rather than looked up repeatedly. It cites performance costs in hot code paths and unpredictable behavior when flag values change during synchronization with a server. ### Source excerpt I Threaded - made a thread? Posted? Tweeted (can we use that again now)? Whatever - about this earlier but I thought I'd elaborate a little. You do use feature flags, right? You should. If you work with trunk-based development, like everyone does now, you must use feature flags to hide upcoming features. Side note: this is why release notes are so boring now, because features aren't really tied to releases. ## Migrating Your Design System to Jetpack Compose Part 4: Stakeholder Retro DevFeed: [Migrating Your Design System to Jetpack Compose Part 4: Stakeholder Retro]() Original publisher: [Read original article]() Published: 2023-04-03T11:19:56Z Content type: opinion Language: en Sources: [Posts on Adam Bennett]() Topics: [Design system](), [Jetpack Compose](), [Compose](), [Development](), [Logging]() Tags: [algorithms](), [android](), [blog](), [career](), [compose](), [design-system](), [development](), [engineering](), [finance](), [functional](), [growth](), [java](), [jetpack](), [jetpack-compose](), [kotlin](), [logging](), [metrics](), [money](), [opinions](), [software](), [startups](), [technical](), [thoughts](), [training](), [tutorial]() ### AI overview A retrospective on migrating a design system from Views to Jetpack Compose, focusing on stakeholder communication, measuring internal developer-facing metrics, and presenting progress during a risky refactoring project. ### Source excerpt Featured in jetc.dev. What, praytell, has caused me, nearly two years after I said I would, to finish this blog series? Could the single day of sunlight we had yesterday have triggered something in my Canadian winter-addled brain? Perhaps. A second theory: I've done a lot of interviewing recently, and I've had to talk a lot about projects - what went well, what went not so well, and talk a lot about some of my strengths and failings as a technical lead. And I spoke about this project a lot. ## Things you can do in Android Studio DevFeed: [Things you can do in Android Studio]() Original publisher: [Read original article]() Published: 2022-06-18T08:38:44Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Android Studio](), [IntelliJ IDEA](), [Dagger](), [Code]() Tags: [algorithms](), [android](), [android-studio](), [blog](), [career](), [code](), [compose](), [copy](), [dagger](), [dependency](), [development](), [engineering](), [finance](), [function](), [functional](), [growth](), [intellij](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [productivity](), [scopes](), [software](), [startups](), [thoughts](), [tooling](), [training](), [tutorial]() ### AI overview A practical list of Android Studio and IntelliJ productivity features, including excluding generated files with Scopes, using scratch files to test ideas, editing multiple lines simultaneously, and accessing clipboard history. ### Source excerpt Based on a recent discussion on Twitter: a list of things that you can do in Android Studio which can make your life much easier. Hide files you don't care about If you work in a project with lots of generated code (e.g.: you use Dagger), you can exclude generated files from searches using Scopes: ## How to Prepare for Data Structures and Algorithms Job Interviews DevFeed: [How to Prepare for Data Structures and Algorithms Job Interviews]() Original publisher: [Read original article]() Published: 2021-11-24T11:00:29Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Programming](), [Algorithms, Complexity](), [Data structures](), [Computer science](), [LeetCode](), [Mobile]() Tags: [advice](), [algorithms](), [android](), [blog](), [career](), [compose](), [data-structures](), [development](), [engineering](), [finance](), [functional](), [growth](), [interviewing](), [java](), [jetpack](), [jobs](), [kotlin](), [mobile](), [money](), [notes](), [opinions](), [remote](), [retention](), [shortage](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview This article shares practical advice for preparing for software engineering interviews, especially Data Structures & Algorithms interviews. It recommends actively studying computer science fundamentals, algorithms, data structures and related strategies instead of solving random LeetCode questions without a structured study method. ### Source excerpt In case you weren't already aware, the market right now for software engineers is super hot - it's crazy out there. A combination of the entire world moving online, people burning out of their jobs and a chronic shortage of experienced software engineers means there's never been a better time to see what's on offer. If you want fully remote, better pay and a title change, there are many companies out there willing to give it to you. ## MockWebServer + HTTPS DevFeed: [MockWebServer + HTTPS]() Original publisher: [Read original article]() Published: 2021-09-11T07:06:08Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [configuration](), [Testing](), [Instrumentation](), [JSON](), [Network](), [Firebase]() Tags: [algorithms](), [android](), [blog](), [career](), [compose](), [configuration](), [development](), [engineering](), [finance](), [functional](), [growth](), [harness](), [instrumentation](), [java](), [jetpack](), [json](), [kotlin](), [money](), [network](), [opinions](), [security](), [software](), [startups](), [test-lab](), [testing](), [thoughts](), [training](), [tutorial]() ### AI overview This article describes configuring MockWebServer to serve HTTPS responses for instrumentation tests. It explains the testing context, including acceptance and regression testing, legacy-code verification, network interception, Firebase Test Lab, and JSON responses for edge cases. ### Source excerpt Recently I ran into a fairly niche configuration problem with MockWebServer, where I needed to be able to connect to the server via https. What follows is some notes on the problem and the solution we used - hopefully somebody else finds this information useful and I'm sure there are other solutions which would have worked just as well. ## How a Clean Android Merged Manifest Still Led to Production Push Notifications DevFeed: [How a Clean Android Merged Manifest Still Led to Production Push Notifications]() Original publisher: [Read original article]() Published: 2021-06-05T05:55:42Z Content type: opinion Language: en Sources: [Posts on Adam Bennett]() Topics: [Android](), [Firebase](), [SDK](), [toolchain](), [XML](), [Google Play]() Tags: [algorithms](), [android](), [blog](), [career](), [compose](), [development](), [engineering](), [finance](), [firebase](), [fuckups](), [functional](), [google-play](), [growth](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [post-mortem](), [sdk](), [software](), [startups](), [thoughts](), [toolchain](), [training](), [tutorial](), [xml]() ### AI overview This post mortem describes how the author accidentally sent a push notification to every Android customer in production. It explains that Firebase Cloud Messaging integrations may come from SDKs and that checking the merged Android manifest can reveal capabilities and unexpected permissions, although the supplied text ends before the full incident is explained. ### Source excerpt Some of you may have seen that on Thursday, I had a bad day. In the grand scheme of things it wasn't that bad a day; it actually turned out pretty well. But what follows is a post mortem on how I accidentally pinged every Android customer in production, and a little bit of advice so that it doesn't happen to you. ## IntoSet: Dagger Multibindings and Architecture DevFeed: [IntoSet: Dagger Multibindings and Architecture]() Original publisher: [Read original article]() Published: 2021-03-05T09:30:09Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Dagger](), [Kotlin](), [implementation](), [Gradle]() Tags: [algorithms](), [android](), [architecture](), [blog](), [career](), [components](), [compose](), [dagger](), [development](), [engineering](), [finance](), [functional](), [gradle](), [growth](), [implementation](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview This tutorial explains how Dagger multibindings with sets can inject collections and register components across Gradle modules. It presents uses including decoupling runtime initialization, isolating third-party SDKs behind facades, reducing dependencies, and registering Moshi adapters. ### Source excerpt Featured in Kotlin Weekly #240 Dagger is typically my DI framework of choice for large projects (insert controversy here) and while most people are familiar with the basic concepts, some aspects immediately cause internal panic when mentioned. Multibindings is one of them, which is a shame because it's a highly useful pattern which can solve real problems. ## Migrating Your Design System to Jetpack Compose Part 3: Interop & Testing DevFeed: [Migrating Your Design System to Jetpack Compose Part 3: Interop & Testing]() Original publisher: [Read original article]() Published: 2021-01-25T16:32:43Z Content type: article Language: en Sources: [Posts on Adam Bennett]() Topics: [Jetpack Compose](), [Design system](), [Testing](), [Development](), [legacy]() Tags: [algorithms](), [android](), [blog](), [career](), [compose](), [design](), [development](), [engineering](), [finance](), [functional](), [growth](), [interop](), [java](), [jetpack](), [jetpack-compose](), [kotlin](), [legacy](), [library](), [money](), [opinions](), [software](), [startups](), [testing](), [thoughts](), [training](), [tutorial]() ### AI overview The third article in a series about migrating design systems to Jetpack Compose explains how to integrate Compose into an existing Android app using Compose interop and how to test Composable components. It describes incrementally replacing legacy Views with Compose components. ### Source excerpt Featured in jetc.dev. Welcome back to the third article in my series about migrating design systems to Jetpack Compose, where I talk about our experiences at Cuvva and how you can apply what we learnt to your team. In part one, I talked about planning ahead, modularisation and getting your team onboard. ## Migrating Your Design System to Jetpack Compose: Part 2 DevFeed: [Migrating Your Design System to Jetpack Compose: Part 2]() Original publisher: [Read original article]() Published: 2020-12-07T07:38:38Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Design system](), [Jetpack Compose](), [Compose](), [Library](), [API]() Tags: [algorithms](), [android](), [api](), [api-design](), [blog](), [career](), [component](), [compose](), [design](), [design-system](), [development](), [engineering](), [finance](), [functional](), [growth](), [implementation](), [java](), [jetpack](), [jetpack-compose](), [kotlin](), [legacy](), [library](), [money](), [opinions](), [software](), [startups](), [techniques](), [thoughts](), [training](), [tutorial](), [typography]() ### AI overview Part two of a series on migrating a design system to Jetpack Compose, covering custom theming, integration with existing APIs, risks from a rapidly changing library, and API design considerations. ### Source excerpt Welcome back to the second article in my series about migrating design systems to Jetpack Compose, where I talk about our experiences at Cuvva and how you can apply what we learnt to your team. In part one, I talked about planning ahead, modularisation and getting your team onboard. In part two, I'll talk about custom theming, about building ontop of existing APIs, how to minimise risk from relying on a rapidly changing library and pose a question about API design. ## Migrating Your Design System to Jetpack Compose: Part 1 DevFeed: [Migrating Your Design System to Jetpack Compose: Part 1]() Original publisher: [Read original article]() Published: 2020-12-05T07:59:06Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Design system](), [Jetpack Compose](), [migration](), [Mobile](), [Gradle]() Tags: [algorithms](), [android](), [blog](), [career](), [compose](), [design-system](), [development](), [engineering](), [finance](), [functional](), [gradle](), [growth](), [java](), [jetpack](), [jetpack-compose](), [kotlin](), [migration](), [mobile](), [money](), [opinions](), [software](), [startups](), [testing](), [thoughts](), [training](), [tutorial]() ### AI overview Part one of a series about Cuvva's migration of its design system to Jetpack Compose. It outlines the existing design system, the problems Compose was expected to solve, a test platform for mitigating migration risk, and ways to involve the team. The series also covers migration planning, practical and team-related steps, roadblocks, and lessons learned. ### Source excerpt Featured in jetc.dev. A few weeks ago, I gave a talk at the Mobile Notts meetup where I spoke about how we at Cuvva are migrating our design system to Jetpack Compose, what we learnt and how you can do the same. It was a fun talk which touched on a lot of content, and I've had quite a few people ask about a video. Sadly there isn't one (although I may give the talk again), but there's so much to cover that I decided to make a series of posts about it with more detail and examples. ## Server-driven theming in Jetpack Compose DevFeed: [Server-driven theming in Jetpack Compose]() Original publisher: [Read original article]() Published: 2020-11-12T09:17:16Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Jetpack Compose](), [Design system](), [Ktor](), [API](), [Server](), [Android]() Tags: [algorithms](), [android](), [api](), [blog](), [career](), [compose](), [design](), [design-system](), [development](), [engineering](), [finance](), [functional](), [growth](), [java](), [jetpack](), [jetpack-compose](), [kotlin](), [ktor](), [money](), [opinions](), [server](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview A proof of concept shows how to implement server-driven theming in a Jetpack Compose Android app. A Ktor server provides theme colors through an API, and the app consumes them so color changes propagate through the Compose UI. ### Source excerpt Featured in jetc.dev. At Cuvva, we've been playing with Jetpack Compose for a few months and we've just recently started porting across our design system. This has lead us to think a lot about design systems in general - how can we streamline the process? How can we ensure that it's always up to date? ## Disabling Jetifier DevFeed: [Disabling Jetifier]() Original publisher: [Read original article]() Published: 2020-08-14T16:56:57Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Android](), [migration](), [Gradle](), [build performance](), [ide]() Tags: [algorithms](), [android](), [android-studio](), [blog](), [build-performance](), [career](), [compose](), [development](), [engineering](), [finance](), [functional](), [gradle](), [growth](), [java](), [jetpack](), [kotlin](), [migration](), [money](), [multi-module-project](), [opinions](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview This article explains how Jetifier converts legacy Android support-library references in third-party binaries to AndroidX equivalents. It describes the build and Gradle configuration-time costs of Jetifier and recommends using the Can I Drop Jetifier Gradle plugin to identify dependencies that must be updated or removed before disabling it. ### Source excerpt Way back in the early-ish days of Android we used the support libraries, android.support, to backport certain features to different API levels. These days those libraries have been replaced by the AndroidX packages, announced at I/O 2018 - but their legacy lives on and many of the dependencies that your app consume may still depend on these android.support packages. ## The Result Monad DevFeed: [The Result Monad]() Original publisher: [Read original article]() Published: 2020-05-15T17:31:46Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Kotlin](), [Library](), [Error Handling](), [Exception](), [Android](), [Programming]() Tags: [algorithms](), [android](), [blog](), [career](), [compose](), [development](), [engineering](), [error-handling](), [exception](), [finance](), [functional](), [growth](), [java](), [jetpack](), [kotlin](), [library](), [monad](), [money](), [opinions](), [programming](), [software](), [startups](), [the-result](), [thoughts](), [training](), [tutorial]() ### AI overview This tutorial explains why the Cuvva Android team adopted the kotlin-result library, how Result-based error handling works, and what problems it addresses. It introduces the monad concept and discusses Kotlin's unchecked exceptions in comparison with Java's checked exceptions. ### Source excerpt Recently I've come to really appreciate the kotlin-result library as we've integrated it more and more deeply into the Cuvva Android stack. In this post, I'll explain why we needed it, how it works and what problems it solves, and show some examples of how we use it at the end. A great many people have tried and failed to explain what a monad is, and this is my attempt at being added to the list. ## Adventures in Compose - The Doom fire effect DevFeed: [Adventures in Compose - The Doom fire effect]() Original publisher: [Read original article]() Published: 2020-04-09T18:07:48Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Compose](), [Development](), [Game engine]() Tags: [algorithms](), [android](), [blog](), [career](), [compose](), [development](), [doom](), [engineering](), [examples](), [finance](), [functional](), [games](), [growth](), [java](), [jetpack](), [jetpack-compose](), [kotlin](), [money](), [opinions](), [programming](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview A tutorial exploring how to recreate the Doom fire effect with Jetpack Compose. It discusses drawing on the screen, updating state in a loop, recomposition, and the limitations encountered with stochastic rendering and memoization. ### Source excerpt Featured in Fragmented and jetc.dev. One of the best books I've bought in the last few years is the Game Engine Black Book: Doom by Fabien Sanglard. As someone who grew up on games but has never really thought about how they're made, it's been a fascinating book to dip in and out of, and there's some great bits of innovation detailed inside. There's an axiom about the greatest innovations spawning from constraints, and the original DOOM team had some pretty serious constraints around memory and processing power - things that we generally take for granted these days. Reading about how they solved problems in this environment is fascinating, and I highly recommend the book. ## Introducing the Activity Result APIs DevFeed: [Introducing the Activity Result APIs]() Original publisher: [Read original article]() Published: 2020-03-22T09:11:18Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [API](), [ui](), [Code]() Tags: [abstraction](), [algorithms](), [android](), [apis](), [architecture](), [blog](), [callback](), [camera](), [career](), [code](), [compose](), [data-type](), [development](), [engineering](), [finance](), [functional](), [growth](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [permission](), [software](), [startups](), [thoughts](), [training](), [tutorial](), [type-parameters](), [ui]() ### AI overview This tutorial introduces Google's Activity Result APIs as a reusable abstraction for handling activity callbacks. It explains the basic workflow, custom contracts, registration, invocation, and built-in contracts for permissions, phone calls, and taking pictures. ### Source excerpt Google has finally released the new Activity Result APIs, which are something I've been looking forward to for a very long time. In this post I'll run through the basics, how you can create your own contracts, and how this allows us to abstract away even more responsibilities from your UI. ## Scripting file templates for Android Studio DevFeed: [Scripting file templates for Android Studio]() Original publisher: [Read original article]() Published: 2020-03-10T09:31:04Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Android Studio](), [Boilerplate](), [Scripting, bash](), [Bash](), [jetbrains-toolbox](), [GitHub]() Tags: [algorithms](), [android](), [android-studio](), [architecture](), [automated](), [bash](), [blog](), [career](), [compose](), [developers](), [development](), [engineering](), [files](), [finance](), [formatting](), [functional](), [github](), [growth](), [install](), [java](), [jetbrains-toolbox](), [jetpack](), [kotlin](), [money](), [onboarding](), [opinions](), [productivity](), [script](), [scripting](), [software](), [startups](), [team](), [thoughts](), [training](), [tutorial]() ### AI overview This tutorial explains how Cuvva automated installing Android Studio file templates for team members across standard and JetBrains Toolbox installations. It also describes combining the setup with scripts that configure ktlint formatting, code style, and pre-commit hooks to streamline developer onboarding. ### Source excerpt As we've started locking down our architecture at Cuvva we reached a point where every new feature required very similar boilerplate, and building all of this by hand was getting tedious. The obvious solution here was to create file templates using Android Studio. I won't go into much detail as to how these are made (there's some good resources available for this already), but I wanted to quickly share how we automated setting these up for team members. ## Jetpack Compose - now on Maven DevFeed: [Jetpack Compose - now on Maven]() Original publisher: [Read original article]() Published: 2019-10-14T07:56:37Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Jetpack Compose](), [Maven](), [Android](), [aosp]() Tags: [algorithms](), [android](), [aosp](), [blog](), [career](), [compose](), [demo](), [development](), [engineering](), [finance](), [functional](), [growth](), [java](), [jetpack](), [jetpack-compose](), [kotlin](), [maven](), [money](), [opinions](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview A historical demo shows how Jetpack Compose libraries could be fetched from Google's Maven repository and used in an Android app. The author notes that the approach is deprecated and that the example compiles but has subtle runtime and behavioral problems. ### Source excerpt This article is also now deprecated, but I'm keeping it up for posterity. This article was a quick demo and explore of the Jetpack Compose library, with the binaries being fetched from the then-newly discovered Maven links. Whilst it technically compiles and renders the Views, it's broken in subtle ways (such as observing @Models, which is half the point of Compose). ## The Android Skeleton Project DevFeed: [The Android Skeleton Project]() Original publisher: [Read original article]() Published: 2019-09-25T08:42:43Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Android Studio](), [Template](), [Android](), [Boilerplate](), [Gradle](), [Dagger](), [ci]() Tags: [algorithms](), [android](), [android-studio](), [architecture](), [blog](), [build](), [career](), [ci](), [compose](), [dagger](), [dependencies](), [development](), [engineering](), [finance](), [functional](), [growth](), [java](), [jetpack](), [kotlin](), [libraries](), [money](), [opinions](), [projects](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview This tutorial recommends maintaining an Android skeleton project as a reusable starting point for new apps and coding challenges. It explains how a maintained template can preserve dependencies, extension functions, Dagger setup, and other boilerplate, with CI used to verify that the project still builds. ### Source excerpt How often has this happened to you? Some new library comes out and you want to try it, you have some kind of brilliant idea to solve a particular problem, or you've needed to build an example app for a new job you're applying for. So you boot up Android Studio, hit New project, skip through the steps and then you're presented with a new playground to work in. Amazing! ## MVI - The Good, the Bad, and the Ugly DevFeed: [MVI - The Good, the Bad, and the Ugly]() Original publisher: [Read original article]() Published: 2019-07-24T18:52:57Z Content type: opinion Language: en Sources: [Posts on Adam Bennett]() Topics: [Redux](), [Android](), [Development](), [reactive]() Tags: [algorithms](), [android](), [android-development](), [architecture](), [article](), [blog](), [career](), [compose](), [development](), [engineering](), [finance](), [flow](), [functional](), [growth](), [java](), [jetpack](), [kotlin](), [money](), [mvi](), [opinion](), [opinions](), [patterns](), [reactive](), [reactive-programming](), [software](), [startups](), [testing](), [thoughts](), [training](), [tutorial](), [ui]() ### AI overview An opinionated introduction to MVI, also known as Redux, for Android development. The article explains its unidirectional data flow, event and result modeling, reducers, sealed classes, and integration with functional reactive programming, while considering its benefits and downsides. ### Source excerpt For those keeping track of the latest trends in view architecture patterns, MVI, aka Redux, has seemingly become the latest and greatest for Android Development. There's tonnes of things to love about MVI - but what are the downsides, and what should you know going into it? For the sake of this article, I'm basing my thoughts on an adaptation of MVI which I've used for a while now for both personal projects and at work. You can find the important classes here for a deeper dive, but I'll run through the basics here too. ## Easy Augmentation with Decorators in Kotlin DevFeed: [Easy Augmentation with Decorators in Kotlin]() Original publisher: [Read original article]() Published: 2019-06-01T07:40:53Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Kotlin](), [Logging](), [Architecture & Design](), [Software Engineering](), [Code]() Tags: [algorithms](), [android](), [blockchain](), [blog](), [career](), [code](), [compose](), [design-patterns](), [development](), [engineering](), [finance](), [functional](), [growth](), [intellij](), [interfaces](), [java](), [jetpack](), [kotlin](), [logging](), [money](), [opinions](), [software](), [software-design](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview A Kotlin tutorial demonstrates how to augment an existing class with logging without modifying the original implementation. It uses an interface, a wrapper class, and Kotlin class delegation to forward most methods while overriding selected behavior. ### Source excerpt Often in software design you may wish that a particular class had more functionality than it currently offers, or that you could tweak its behaviour slightly. In this contrived example, we're going to add some logging to an existing class, but we've decided not to do it in the target class directly. There can be a few reasons for this: ## Hugo, Firebase Hosting and CircleCI DevFeed: [Hugo, Firebase Hosting and CircleCI]() Original publisher: [Read original article]() Published: 2019-04-28T09:34:57Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Hugo](), [Firebase](), [hosting](), [CircleCI](), [Google]() Tags: [algorithms](), [android](), [blog](), [career](), [circleci](), [compose](), [continuous-deployment](), [continuous-integration](), [development](), [domain](), [engineering](), [finance](), [firebase](), [functional](), [google](), [growth](), [guides](), [hosting](), [how-to](), [hugo](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [software](), [startups](), [thoughts](), [training](), [tutorial](), [web]() ### AI overview A practical guide to setting up a Hugo blog with Firebase Hosting and CircleCI, including domain configuration and DNS verification through Google Domains. ### Source excerpt Domain setup First thing's first - go buy your domain on domains.google.com. They're only GBP 10 a year, but if I remember correctly there's a GBP 120 initial fee. Your mileage may vary depending on the popularity of your domain name. The process is pretty user friendly, even for a web noob like myself. ## Migrating to Downloadable Fonts on Android DevFeed: [Migrating to Downloadable Fonts on Android]() Original publisher: [Read original article]() Published: 2018-06-28T13:16:14Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Android](), [Font](), [Android Studio](), [SVG]() Tags: [accessibility](), [algorithms](), [android](), [android-studio](), [blog](), [career](), [compose](), [development](), [engineering](), [finance](), [fonts](), [functional](), [growth](), [java](), [jetpack](), [kotlin](), [mobile](), [money](), [opinions](), [proguard](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview This article explains how Blockchain migrated its Android app from bundled fonts and the Calligraphy library to Android's downloadable fonts. It describes runtime font loading through a font provider, support down to API 14 through Support Library 26.0.0, and Android Studio's generated manifest and XML configuration. It also notes that the interface exposed only regular and bold Montserrat variants. ### Source excerpt This is a rehost of the article I wrote for the Blockchain Engineering blog. You can find the original article here. At Blockchain, we have many mobile users in bandwidth constrained environments such as developing countries. As such keeping the app small and lightweight is a priority for the Android team. Smaller app sizes increase both installs and conversion rates - important metrics for any mobile-focused company. We've used various techniques over the last year to prevent bloat to the app including shrinking what few PNGs we have, using VectorDrawables at every possible opportunity, and aggressively leveraging ProGuard. ## A Closer look at Slices on Android DevFeed: [A Closer look at Slices on Android]() Original publisher: [Read original article]() Published: 2018-05-31T13:11:02Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Android](), [SDK](), [Google](), [App](), [Framework]() Tags: [algorithms](), [android](), [app](), [blog](), [career](), [compose](), [developer-preview](), [development](), [engineering](), [finance](), [functional](), [google](), [google-assistant](), [google-io](), [growth](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [play-store](), [sdk](), [search](), [slices](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview This article examines Android Slices introduced around the Android P Alpha release and explains their relationship to App Actions. It describes how App Actions can connect apps with Google Assistant, Search, and the Play Store, using recognized user intents and app deep links to support queries such as cryptocurrency price requests. ### Source excerpt In the lead-up to Google IO 2018 and after peering into the Android P Alpha release, some people noticed a mysterious new "Slices" class within the P SDK docs. There was a lot of speculation as to what Slices actually did, and Sebastiano Poggi at Novoda did a great deep-dive into what was known at the time. [Next page]()