# Fernando Cejas Blog Welcome! I'm Fernando Cejas, Head of Engineering @TignumEng, former Director of Mobile @Wire, @SoundCloud Alumni, former @IBM Developer Advocate and @Tuenti Alumni. I'm a geek/nerd, huge fan of Mobile Development, Artificial Intelligence, Quantum Computing and Software Engineering in general. Here I share my experiences and expose my ideas but all views, posts and opinions are my own. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Integrating Rust with Android for Cross-Platform Code Reuse DevFeed: [Integrating Rust with Android for Cross-Platform Code Reuse]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2023-07-27T00:00:00Z Content type: tutorial Language: en Sources: [Fernando Cejas Blog]() Topics: [Rust](), [Android](), [cross-platform](), [Development](), [Android Studio](), [Encryption]() Tags: [android](), [android-development](), [android-studio](), [architectures](), [code](), [compilation](), [cross-platform](), [culture](), [development](), [encryption](), [engineering](), [infrastructure](), [ios](), [java](), [kotlin](), [linux](), [open-source](), [programming](), [python](), [rust](), [scala](), [software](), [software-development](), [web-development]() ### AI overview A tutorial on integrating Rust with an Android application for cross-platform code reuse. It covers project structure, Rust compilation, Android CPU architecture libraries, JNI integration, Android SDK and NDK requirements, and an example involving encryption and decryption. ### Source excerpt In this journey, we will go through the **process, infrastructure and architecture** on how we can integrate **Rust in our Android Project** in a **cross-platform development** way. Topics like **JNI** and **NDK** are also covered, plus some **anti-patterns** and **real use cases/scenarios**. ## An over-engineered Home Lab with Docker and Kubernetes. DevFeed: [An over-engineered Home Lab with Docker and Kubernetes.]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2023-01-06T00:00:00Z Content type: article Language: en Sources: [Fernando Cejas Blog]() Topics: [Homelab](), [.env](), [Docker](), [Kubernetes](), [Linux](), [Hardware](), [Network Attached Storage (NAS)](), [Network](), [Security, Privacy and Abuse Prevention](), [Virtual Private Network]() Tags: [android](), [culture](), [data-privacy](), [development](), [docker](), [engineering](), [hardware](), [home-lab](), [home-server](), [infrastructure](), [internet](), [ios](), [java](), [kotlin](), [kubernetes](), [linux](), [maintenance](), [network](), [network-attached-storage-nas](), [open-source](), [openwrt](), [programming](), [python](), [rust](), [scala](), [software](), [software-development](), [web-development]() ### AI overview A personal account of building a private home lab using two Intel NUC Mini PCs, a modem/router, an OpenWRT router, and a NAS. The article compares Kubernetes and Docker, discusses maintenance and troubleshooting costs, and explains that the author ultimately chose a plain Docker setup. ### Source excerpt **Setting up a personal Home Lab is not a task for lazy people**: it incurrs a **big cost of maintenance** and **issues arise** even though we might use the **best IT-Infrastructure practices...** but we can always **learn a lot** out of it and make it also **super fun**. In this post I would like to share **my journey** and share some **tips and tricks and issues** I bumped into. **Let's jump in!** ## Arch Linux System Maintainance. DevFeed: [Arch Linux System Maintainance.]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2022-03-30T00:00:00Z Content type: tutorial Language: en Sources: [Fernando Cejas Blog]() Topics: [Arch Linux](), [Linux](), [Package manager](), [pacman](), [maintenance](), [upgrade]() Tags: [android](), [culture](), [development](), [engineering](), [guide](), [infrastructure](), [ios](), [java](), [kotlin](), [linux](), [maintenance](), [open-source](), [pacman](), [programming](), [python](), [rust](), [scala](), [software](), [software-development](), [upgrade](), [web-development]() ### AI overview A guide to maintaining Arch Linux installations. It covers system updates, troubleshooting keyring issues, cleaning the pacman cache, removing orphaned and unwanted packages, and managing cache data in the home directory. ### Source excerpt In this guide we will walk through the most important practices **regarding system maintainance for Linux home computers.** Most of them are **Arch Linux** (and variants) specific but we can get ideas on how other distros can use and apply the same principles. ## Cooking Effective Code Reviews. DevFeed: [Cooking Effective Code Reviews.]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2021-08-04T00:00:00Z Content type: tutorial Language: en Sources: [Fernando Cejas Blog]() Topics: [Code review](), [pull-requests](), [Development](), [engineering-culture](), [decision-making]() Tags: [android](), [code-quality](), [code-review](), [code-reviews](), [culture](), [development](), [engineering](), [infrastructure](), [ios](), [java](), [kotlin](), [legacy-code](), [linux](), [open-source](), [processes](), [programming](), [python](), [rust](), [scala](), [software](), [software-development](), [structured](), [team](), [tech-debt](), [web-development]() ### AI overview A tutorial on making pull request code reviews more effective through a structured process. It discusses their role in code quality, documentation, collaboration, engineering culture, and keeping reviews small enough to manage. ### Source excerpt **Reviewing code (PRs) is not an easy task**, so in this post I will share **tips and tricks** on how your code reviews can better contribute to **code quality**, **be more effective and increase team morale** by following a structured and organized process. **Let's jump in!** ## Writing First-Class Features: BDD and Gherkin. DevFeed: [Writing First-Class Features: BDD and Gherkin.]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2021-01-23T00:00:00Z Content type: tutorial Language: en Sources: [Fernando Cejas Blog]() Topics: [Behavior-driven development](), [domain-specific language](), [Development](), [Programming]() Tags: [android](), [bdd](), [communication](), [culture](), [development](), [domain-specific-language](), [dsl](), [engineering](), [feature](), [framework](), [infrastructure](), [ios](), [java](), [kotlin](), [linux](), [open-source](), [organization](), [processes](), [programming](), [python](), [rust](), [scala](), [software](), [software-development](), [web-development](), [writing]() ### AI overview The article explains how behavior-driven development (BDD) and the Gherkin domain-specific language can establish a shared vocabulary for writing software features. It presents BDD as a collaborative process involving developers, QA, and business participants, and describes how structured natural-language scenarios can express behavior and acceptance criteria. ### Source excerpt As our product evolves, **there is the need to adopt a common vocabulary**, interpreted by all the moving parts of our organization: business users, analysts, managers, engineers, etc. **A technique like BDD and the Gherkin language can help us to achieve this goal**. ## Install Arch Linux with Full-Disk Encryption DevFeed: [Install Arch Linux with Full-Disk Encryption]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2020-12-28T00:00:00Z Content type: tutorial Language: en Sources: [Fernando Cejas Blog]() Topics: [Arch Linux](), [Encryption](), [Linux](), [Package manager](), [Hardware](), [intel](), [dell]() Tags: [android](), [command-line](), [culture](), [debian](), [development](), [distribution](), [encryption](), [engineering](), [infrastructure](), [installation](), [ios](), [java](), [kotlin](), [linux](), [open-source](), [pacman](), [programming](), [python](), [rust](), [scala](), [software](), [software-development](), [web-development]() ### AI overview A guide to installing Arch Linux with full-disk encryption while explaining the concepts involved. It assumes basic command-line knowledge and covers installation on Intel-based hardware, including a Dell XPS 13. ### Source excerpt This post will act pretty much as **a guide** (a **long** one), in order to help you **INSTALL and UNDERSTAND Arch Linux** with **full disk encryption**. Let's also walk together through some of the **concepts involved in the amazing world of Linux**. ## Using Postmortems to Learn from Mistakes DevFeed: [Using Postmortems to Learn from Mistakes]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2020-06-21T00:00:00Z Content type: opinion Language: en Sources: [Fernando Cejas Blog]() Topics: [Learning](), [retrospectives](), [Resilience]() Tags: [android](), [culture](), [development](), [engineering](), [infrastructure](), [ios](), [java](), [kotlin](), [learning](), [linux](), [open-source](), [postmortems](), [processes](), [programming](), [python](), [resilience](), [retrospectives](), [rust](), [scala](), [software](), [software-development](), [web-development]() ### AI overview The article argues that organizations should treat mistakes as opportunities to learn, share lessons, and avoid repeating failures. It presents postmortems as a tool for drawing useful conclusions and supporting retrospective discussion. ### Source excerpt **Postmortems** are a valuable tool for learning out of mistakes. They provide **useful conclusions** and should be included in retrospectives for further discussion in order to **not fall into the same trap again.** ## Postmortems for Learning From Mistakes DevFeed: [Postmortems for Learning From Mistakes]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2020-06-21T00:00:00Z Content type: opinion Language: en Sources: [Fernando Cejas Blog]() Topics: [Learning](), [retrospectives](), [Resilience]() Tags: [android](), [culture](), [development](), [engineering](), [infrastructure](), [ios](), [java](), [kotlin](), [learning](), [linux](), [open-source](), [postmortems](), [processes](), [programming](), [python](), [resilience](), [rust](), [scala](), [software](), [software-development](), [web-development]() ### AI overview The author argues that organizations should treat mistakes as opportunities to learn without blaming people. The article presents postmortems as a way to share lessons, discuss them in retrospectives, avoid repeating failures, and build resilience. ### Source excerpt **Postmortems** are a valuable tool for learning out of mistakes. They provide **useful conclusions** and should be included in retrospectives for further discussion in order to **not fall into the same trap again.** ## Technical Debt and Legacy Code: Techniques for Improving Code Health DevFeed: [Technical Debt and Legacy Code: Techniques for Improving Code Health]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2020-03-13T00:00:00Z Content type: opinion Language: en Sources: [Fernando Cejas Blog]() Topics: [Software Engineering](), [legacy](), [maintenance](), [Testing](), [Unit testing]() Tags: [android](), [clean-code](), [culture](), [development](), [engineering](), [how-to](), [infrastructure](), [ios](), [java](), [kotlin](), [legacy-code](), [linux](), [maintenance](), [open-source](), [programming](), [python](), [rust](), [scala](), [software](), [software-development](), [strategies](), [technical](), [unit-testing](), [web-development]() ### AI overview This article examines technical debt and legacy code in software projects, defines legacy code as code without tests, and discusses techniques and strategies for assessing and addressing code health and maintenance challenges. ### Source excerpt As **Software Engineers** we know that **Technical Debt** and **Legacy Code** are familiar concepts we have to live with. **Code healthiness and maintenance are challenging**, so let's dive into **tips and techniques on how to effectively address this problem.** ## Technical Debt and Legacy Code: Techniques for Improving Code Health DevFeed: [Technical Debt and Legacy Code: Techniques for Improving Code Health]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2020-03-13T00:00:00Z Content type: opinion Language: en Sources: [Fernando Cejas Blog]() Topics: [Software Engineering](), [legacy](), [maintenance](), [Unit testing]() Tags: [android](), [culture](), [development](), [engineering](), [infrastructure](), [ios](), [java](), [kotlin](), [legacy-code](), [linux](), [maintenance](), [open-source](), [programming](), [python](), [rust](), [scala](), [software](), [software-development](), [technical](), [tips](), [unit-testing](), [web-development]() ### AI overview The article discusses technical debt, legacy code, and software project health. It introduces legacy code as code without tests and explores techniques and strategies for measuring and addressing these maintenance challenges. ### Source excerpt As **Software Engineers** we know that **Technical Debt** and **Legacy Code** are familiar concepts we have to live with. **Code healthiness and maintenance are challenging**, so let's dive into **tips and techniques on how to effectively address this problem.**