Articles

Vibe Coding, Kotlin, Finance, and Data Visualization

Vibe Coding, Kotlin, Finance, and Data Visualization

Recently, I came across a paper discussing an experiment and tried to reproduce it. Here’s a brief summary: - Portfolio A: In a bull market, grows by 20%; in a bear market, drops by 20%. - Portfolio B: In a bull market, grows by 25%; in a bear market, drops by 35%. - Bull market probability: 75%. According to the paper, both portfolios should have a one-year expected return of 10%.
Treat life like a marathon, not like a sprint

Treat life like a marathon, not like a sprint

Like most of us, I am daily flooded with thoughts about life, my objective position in it, whether I am missing anything, or whether I need to do better. Am I providing enough for my family? Is my career on track? Am I being healthy enough? Am I just passing through life instead of aiming to strive? Those thoughts have been slowly mitigated, but they never got away. Over time, I have been slowly accepting this reality, and I came to realise that all the marathon training and long-distance running have helped me come to terms with these facts.
Uploading SARIF Reports to GitHub

Uploading SARIF Reports to GitHub

Recently I wanted to add Lint reports to a repository on GitHub. The goal is to report potential Lint violations when new code is committed, to make sure that all the committed code is lint-warning-free and pretty. My first idea was to look for a GitHub action that could run ./gradlew lint and report it as a PR comment. After asking about ideas in the Android Study Group, Carter Jernigan and Justin Brooks suggested me to upload directly the SARIF files into GitHub.
KotlinConf 2024 announcements

KotlinConf 2024 announcements

The first day of the KotlinConf 2024 is over, and there has been a significant amount. After 5 years the conference happened again at The Bella Center in Copenhagen, a fantastic venue close to the historical center of the Danish capital. The last two weeks have been intense, with the Google I/O announcing another set of relevant features for Android and Kotlin developers. Most notably, Google is now supporting KMP for Android development.
HTTP chunk requests with Android and ktor

HTTP chunk requests with Android and ktor

In this very short article, I will explain briefly what is a chunk or streamed HTTP request, what are the benefits of using it, and how it works in Android. Android apps use HTTP requests to download data from a backend. This information is stored and processed on the app to make it functional. HTTP requests are executed using different frameworks on Android. The most common ones are Retrofit or OkHttp.
My Investing Summary of 2022

My Investing Summary of 2022

Another solar rotation passed, and the world experienced a plethora of unexpected events. In the aftermath of the Corona epidemic that altered the course of the last couple of years, we had the unfortunate invasion of Ukraine by Russian forces, the tightening of Corona measures in China (and toward the end of the year, their withdrawal and gradual reopening of the economy), an ongoing economic recession, the rate hike by the FED and the general uncertainty of the most immediate future.
KMP, iOS Developers and Production

KMP, iOS Developers and Production

Kotlin Multiplatform (or KMP, KMM Mobile, etc) has been widely used for a number of years in applications that are currently in production. JetBrains compiled a website listing some of the companies that are currently using KMP. Since the advent of the mobile platforms we enjoy today, there has always been a certain market interest to push multiplatform technologies, such as Cordova, Xamarin, and others. With more or less success, those technologies aimed to provide a unified framework to develop multiple codebases, mostly focusing on the aspect of pricing (create code once, deploy multiple times).
A recapitulation of investing in pandemic times

A recapitulation of investing in pandemic times

It has been around 14 months since the pandemic started. We have all been affected by it to a greater or lesser degree, and the investing world has not been an exception (although surprisingly, the stock market is one of the winners of the pandemic). In this post I will share how the pandemic changed my investment thesis, the things I learned, and the mistakes I did. 14 months into the crisis of our generation (and with a few months to recover whatever the new normal will be), we now know that things will never be the way they used to be.
A short story of randomness (I)

A short story of randomness (I)

I have always been fascinated by the above comic strip. A discussion on randomness and determinism becomes as much a philosophical issue as it is a practical one. They are used in a variety of applications: from the obvious cryptography, gaming or gambling to the less evident politics or arts. How can we be sure that a number is random? Will observing the process mine our efforts on generating the random number, similar to the observation of a cat inside a box with a decaying radioactive atom?
From Java to Kotlin and back (III): Calling Java from Kotlin

From Java to Kotlin and back (III): Calling Java from Kotlin

This article is part of a series. You can find the remaining article of the series here: From Java to Kotlin and back (I) — Calling Kotlin from Java From Java to Kotlin and back (II): Calling Kotlin from Java In this last chapter of the series, we will evaluate consideration when calling Java code from Kotlin. One could argue that even in this situation happens often, keeping considerations in mind for some code that might legacy is not that practical.
From Java to Kotlin and back (II): Calling Kotlin from Java

From Java to Kotlin and back (II): Calling Kotlin from Java

This article is part of a series. You can find the remaining article of the series here: From Java to Kotlin and back (II): Calling Kotlin from Java From Java to Kotlin and back (III): Calling Java from Kotlin In the previous article, we explored how Java and Kotlin can interact with each other, and some considerations in this regard. In this second edition, we will keep reflecting on some relevant aspects to consider when Java is calling Kotlin.
From Java to Kotlin and back (I): Java calling Kotlin

From Java to Kotlin and back (I): Java calling Kotlin

This article is part of a series. You can find the remaining article of the series here: From Java to Kotlin and back (II): Calling Kotlin from Java From Java to Kotlin and back (III): Calling Java from Kotlin I am currently working on a multi-module project that combines a variety of Java and Kotlin code, so I decided to publish my thought and notes as an article series. It will likely help me as a journaling practice, and hopefully can help other potential readers that end up here trying to find some tips while they are facing the same problem.
Considerations when creating Android libraries

Considerations when creating Android libraries

If you are an Android developer, chances are you might have been working on your own Android libraries. A library is a useful way to create a reusable set of features that need to be integrated through different apps (or even different libraries). A library is a self-contained package including code and resources required to execute some functionality. Importing a library in our Android app is the same process as importing a .
GitHub Actions for Android developers

GitHub Actions for Android developers

If you are developing Android apps, chances are you have confronted any sort of CI at some point in your career. If you thought Android fragmentation was a thing, the wide availability of CI systems will be familiar to you. GitHub Actions was released around November 2019, and since then it has proved itself to be reliable for a production environment (one of our requirements before committing to any software system).
Using the Signature class to verify data

Using the Signature class to verify data

When there is an exchange of information happening, we often want to verify that the origin of the data is the right one. This can be used to ensure that the right clients are having access to our resources. For instance, let’s imagine that we want to ensure that an authorized device is querying a file with sensitive information from our backend. An immediate solution could be to use a X-Api-Token in our device.
Managing the Kotlin Weekly

Managing the Kotlin Weekly

I just sent the issue #182 of the Kotlin Weekly. #182 means that this has been the week 182 that the Kotlin Weekly is alive. Many things have changed since the first edition on the 7th of August 2017, sent to over 200 initial subscribers with 5 articles. In some of the first editions, the content was so scarce that I ended up writing my own articles to include them, or adding some code snippets I posted on Twitter.
2019 in retrospective

2019 in retrospective

This year is over. During the last 365 days, I fulfilled some of the goals I meticulously established at the beginning of the year. In other goals, I failed without palliatives or anesthesia. During the last 9 years, I have been following a process to determine my goals for the upcoming solar rotation. I sit at a coffee place next to my home in Munich, order a ginger tea and take notes.
A Gentle Introduction to Investing for Software Engineers (IV) — My methodology to determine which…

A Gentle Introduction to Investing for Software Engineers (IV) — My methodology to determine which…

You can access all the articles of the series through the following links: (I) — Motivation (II) — Compounding interest and introducing other factors (III) — Determining a company value and acquisition point (IV) — My methodology to determine which stock to buy In this fourth and last article of the series, I will explain my methodology to acquire individual stock in the market. Most of the guidelines I expose are thought of as a guideline that you might need to adapt depending on your circumstances (for instance, the double taxation will play a role depending on your tax residence).
Re-post: Which city has the most intense Android scene in Europe?

Re-post: Which city has the most intense Android scene in Europe?

I wrote this post originally 5 years ago. For a side project, I had to use the StackExchange data explorer again, so I decided to revisit it and update the numbers. StackExchange Data Explorer is an open-source tool to run SQL queries against public data from StackOverflow. Since StackOverflow is the biggest development forum of the world, there is surely a lot of information that companies can actually retrieve from their system in order to take some business decision (this is actually a brilliant place to apply BigData)
Using Git Hooks to improve your development workflow

Using Git Hooks to improve your development workflow

Recently, I was contributing for the first time to a new codebase. I extended and implemented some functionality that I needed. After thorough testing on my machine, where I checked that the functionality was properly working, I committed my contribution. Minutes after, our CI environment delivered a message: 4 Tests failed This happens so often, even on the codebases we are used to work with. We tend to focus on developing the new features, and forget that there is a test that is covering them.
A Gentle Introduction to Investing for Software Engineers (III) —Determining a company value and…

A Gentle Introduction to Investing for Software Engineers (III) —Determining a company value and…

You can access all the articles of the series through the following links: (I) — Motivation (II) — Compounding interest and introducing other factors (III) — Determining a company value and acquisition point (IV) — My methodology to determine which stock to buy In this third article of the series, I am giving an introduction to some of the factors that we commonly use to determine whether a company is apt for our investment strategy, whether it is the right moment to acquire stock, and in general to provide us some insight beneath the numbers.
A Gentle Introduction to Investing for Software Engineers (II) — Compounding interest and…

A Gentle Introduction to Investing for Software Engineers (II) — Compounding interest and…

You can access all the articles of the series through the following links: (I) — Motivation (II) — Compounding interest and introducing other factors (III) — Determining a company value and acquisition point (IV) — My methodology to determine which stock to buy In this second article of the series, I want to keep exploring some metrics to show the evolution of our investment keeping in mind different scenarios. This time I will be including screenshots from a Google Spreadsheet instead of displaying text tables.
A Gentle Introduction to Investing for Software Engineers (I) — Motivation

A Gentle Introduction to Investing for Software Engineers (I) — Motivation

You can access all the articles of the series through the following links: (I) — Motivation (II) — Compounding interest and introducing other factors (III) — Determining a company value and acquisition point (IV) — My methodology to determine which stock to buy If you are reading this article, chances are you a Software Engineer that has ended up here looking up for saving, investment or retirement advice. Or maybe you have a different profession, but ended up here anyway.
Approaching a methodology to select speakers for conferences

Approaching a methodology to select speakers for conferences

After a great first edition, this year I organised the second edition of the Droidcon Vietnam with some local folks. Before I organised a conference like this, my experience was limited to local Meetups in Munich (I am currently the organiser of the Kotlin User Group Munich, and the Firebase User Group Munich). The latter has a different nature in terms of resources, logistics and efforts required. They are community-based events, local and — without requiring an easy trajectory — they are certainly less complex than the former.
Creating a library for Android: The Good, the Bad and the Ugly

Creating a library for Android: The Good, the Bad and the Ugly

Software Development is like an Ouroboros. You end up going to the place you have previously resided, with requirements and knowledge updated and refashioned. You might have started working on an initial prototype that began the journey as a basic HelloWorld, and it has evolved into one of those mythological Nordic monsters. Or maybe Greek monsters are more terrifying and frightening. I do not know. At one of my projects we recently came up with the requirement of extracting some of the functionality well buried there to expose to third-party consumers.
On Strategies to apply Kotlin to existing Java code

On Strategies to apply Kotlin to existing Java code

Since the latest announcement at the Google I/O, things have been crazy. At the Kotlin Weekly Mail List we had an increase in subscribers over 20% in the last two weeks, over 200% increase in article submissions, and at a Meetup I organise (Kotlin Users Group Munich) we had a huge increase in attendees. And all this combined with the general blast in the developers community. A trend that will only continue to grow.
A follow-up on how to store tokens securely in Android

A follow-up on how to store tokens securely in Android

As a prologue to this article, I want to remark a short sentence for the notional reader. This quote will be important as we move forward. Absolute security does not exist. Security is a set of measures, being piled up and combined, trying to slow down the inevitable. Almost three years ago, I wrote a post giving some ideas to protect String tokens from a hypothetical attacker decompiling our Android application.
Using Firebase as a Real Time System

Using Firebase as a Real Time System

I was captivated by exposed pictures since I was a child. Is a unique way to capture movement in a static image. I have been an avid user of Firebase since more than a year now. When Parse.com announced it would be shutting off, I was attending a Google Launchpad in Mountain View as a mentor. If you haven’t heard of the Google Launchpads, they are great. Not only for the startups, which get a fair amount of advising and mentoring from people in different fields (UX, Tech, Marketing, Monetizing and Fund raising…) but also for mentors itself!
Learning to use and abuse Mutability

Learning to use and abuse Mutability

I am an old Java man, I never allocated many of my thoughts to reflect on the philosophy of mutability. In Java, unlike in other languages, there is no precise control over what is mutable and immutable. I never thought of Java objects as having this feature. Instead, I would always refer to them as “that Java class that has no setter”. “That Java class that cannot be modified once the value has been set up”.
An Overview of Polls for (Android) (Mobile) Developers in 2016

An Overview of Polls for (Android) (Mobile) Developers in 2016

Last year I started a weekly routine consisting on posting on my Twitter a poll every Monday, with topics related to Android / Mobile / Software Engineering (in that order). It has been a total of 18 polls during the year, with an overwhelming response and engagement of the community. (On a side note, I can‘t stress enough how lucky I am of being able to be a part of the Worldwide Android District.
On properly using volatile and synchronized

On properly using volatile and synchronized

In the last weeks I have been writing about the transient modifier and the different types of references available in Java. I want to hold the topic of underused/misused topics in Java and bring you this week the volatile and synchronized modifiers . Multithreading is an entire discipline that takes years to master and properly understand. We will keep a short introduction in this article. In computing, a resource can be accessed from different threads concurrently.
Diving deeper into the Java transient modifier

Diving deeper into the Java transient modifier

Nothing is tied forever. Neither are transient variables. Last week I published an article to help you understand how references do work in Java. It had a great acceptance, and I got a lot of constructive feedback. That is why I love the software community. Today I want to present you another article diving into a topic that it is not widely used: the transient modifier. Personally, when I started using it I recall I was able to quickly grasp the theoretical aspect of it, although applying was a question of a different nature.
Finally understanding how references work in Android and Java

Finally understanding how references work in Android and Java

A few weeks ago I attended Mobiconf, one of the best conferences for Mobile Developers I had the pleasure to attend in Poland. During his eclectic presentation “The best (good) practices”, my friend and colleague Jorge Barroso came up with a statement that made me reflect after hearing it: If you are an Android developer and you do not use WeakReferences, you have a problem. On an example of good timing, a couple of months ago I did publish my last book, “Android High Performance”, co-authored with Diego Grancini.
You live in a better world today

You live in a better world today

This has been a very tragic week in Germany. In less than five days, four attacks happened in the southern provinces of Bayern and Baden-Württemberg (the motivation of some of them being disputed, but being mostly assigned to the refugee crisis and open-borders policy of Merkel). After the attacks followed the classical harangue from certain civil and political sectors drawing attention on the rapidly deteriorating social peace in Germany and Europe.
The theoretical animal

The theoretical animal

We are theoretical animals. We spend our entire lives analyzing our immediate environment, theorising on how to solve our most immediate problems or improve processes. We think of having conversations with beloved people, we think of carrying out actions we have planned for a while with relatives and friends, and we think of starting new projects. Yet we do little to implement them and put all this knowledge into practice.
A Comprehensive Introduction to Perform an Efficient Android Code Review

A Comprehensive Introduction to Perform an Efficient Android Code Review

You are working in a team that cares about code quality. You have been doing -or thinking of doing- some code pairing. Your team regularly carry out hacking events to talk and present new technologies, or to talk about the personal discoveries of each member. And you are trying to devise the perfect code review process for your organisation. Is this situation familiar to you? Code reviews are hard to implement.
Automating Android development

Automating Android development

I have been recently talking at the DroidCon Spain and DroidCon Italy about how to automate a traditional Android workflow. To my surprise, there are still many organisations that do lack a Continuous Integration (CI) strategy. This is a big mistake! I decided to put down in words my thoughts about how to efficiently implement CI. As a software engineer, your aim is to automate as many processes as possible. Machines are more efficient than people: they do not need food neither sleep, they perform tasks errorless and they make your life easier.
Event-driven programming for Android (part III)

Event-driven programming for Android (part III)

(This is the third article in a three-part series) Previously, I have given an introduction to Event Driven programming with Android, and show some code to create a HelloWorld Event-Driven application. Now we are likely facing another problem: how can we easily scale an application using Event-Driven development without falling into a messy and unorganised code? In this article, I will provide a proposal architecture that serves to scale an application based on Event-Driven development, but that can also be used to create a more general type of applications.
Event-driven programming for Android (part II)

Event-driven programming for Android (part II)

(This is the second article in a three-part series) In the previous article we had a short introduction into Event-Driven programming. Now let’s see some actual code and how to perform the basics with EventBus. First I will present the entities that play a central role in Event-Driven programming. Refer to the following image taken from the EventBus repository. An Event Bus. This is the central communication channel that connects all the other entities.
Event-driven programming for Android (part I)

Event-driven programming for Android (part I)

(This is the first article in a three-part series) Although Android includes some event-driven features in its development, it is far away from being a pure event-driven architecture. Is this something good or bad? As in every issue with software development the answer is not easy: it depends. First, let’s establish a definition for event-driven development. This is a programming paradigm where the flow of execution is determined by events triggered by actions (such user interaction, messaging from other threads, etc).

A Gentle Introduction to Investing for Software Engineers (IV) — My methodology to determine which…

Planted December 5, 2019
Pruned June 9, 2025

A Gentle Introduction to Investing for Software Engineers (IV) — My methodology to determine which…

You can access all the articles of the series through the following links:

(I) — Motivation

(II) — Compounding interest and introducing other factors

(III) — Determining a company value and acquisition point

(IV) — My methodology to determine which stock to buy

In this fourth and last article of the series, I will explain my methodology to acquire individual stock in the market. Most of the guidelines I expose are thought of as a guideline that you might need to adapt depending on your circumstances (for instance, the double taxation will play a role depending on your tax residence). I hope they can serve as an inspiration, and provide ideas to any fellow investors.

Determining our portfolio

The most important thing to do is to determine how do we want our portfolio to look like. For investors looking for a dividend based portfolio and DGI companies, the main components should be defensive companies, and incorporating over time more DGI companies. This is how my current portfolio looks like:

image

image

This portfolio does not reflect my ideal state (although it is on its way). I would ideally like a composition with approximately 60% of my companies in the defensive sector. Since this is a long term project, you do not need to worry about not fulfilling the percentages from the beginning. Keep in mind the figure you feel more comfortable with, and move towards that direction.

Since I am a German tax resident, I initially added a few German insurance companies that were cheap at the time (Allianz and München RE), and a few automotive companies (BMW and Daimler). This was before I started internationalizing my portfolio, and until now has decompensated the percentages I want. However, in the long term (a few years from now) I will be moving towards my desired direction.

Another important point is to keep several companies per sector. Let’s think of Communication Services. There are a few companies that could be acquired (AT&T, Vodafone, Verizon, Telefonica…). We can determine which company is performing better right now, but not which company will do it better in a few years. That is why you should always own at least two or three per sector and country.

Company distribution

As a rule of thumb, I avoid having more than 5% of weight for an individual company. If all companies of my portfolio have a 5% representation, I would have a maximum of 20 companies, but note that we are talking about a maximum here.

This is a representation of my current portfolio in December’19:

image

As you can see, a few companies exceed this 5% (Allianz and Axa). This is perfectly normal since some companies might grow from the original price of the acquisition, and the percentage will exceed. When a portfolio is being created, any new acquisition will decompensate it by a factor — for instance, think of a portfolio of 10K USD, and a new acquisition of 1K USD. Think of this as a long term goal — as a rule, no company should exceed a percentage that you estimate.

The motivation for this is to diversify and protect ourselves from the Concorde Fallacy. The main problematic impediment for investors is our own psychology, and when a stock looks cheap, we might be tempted to keep over-investing in it. If the stock keeps sinking, this can result in looses or a missed opportunity. Over my investing lifetime, I have realised that there are always many stocks that are cheap at a single time. Diversify by specifying a maximum percentage you want for each stock — and at the same time, do not obsess too much about it.

Similarly, I have declared percentages for each company type. Utilities (Enagás, REE, E.ON, RWE…) and consumer defensive (Johnson and Johnson, General Mills…) can be on the upper side of the spectrum (3–5%), whereas I prefer cyclical companies (automotive, energy…) to be on the low side (1–3%). Again, those are approximated percentages that should not be followed “too” strictly.

Having this diversification protects us. Let’s remember Kraft Heinz: they cut their dividend in February by 36%. If you would have (for instance) 50% of KHC on your portfolio, your income would have been reduced by 18%. If you are holding only 3% of KHC of your portfolio, your income would be reduced by 0.6% — this is negligible, and probably covered with the increase in other companies.

Price to Earnings Ratio (PER)

As I mentioned in my previous article, the Price to Earnings Ratio (or PER) is the measure of the share price relative to the annual net income earned by the firm per share. In a nutshell: it shows us “how much we pay in order to earn money”. There is no unique number that specifies what a good (cheap) PER is and what is not. In some literacy, 15 is taken as the standard value for PER (neither cheap or expensive), but this is a wrong measurement. PER should be considered as follows:

  • Historical PER of the company: how was the PER of a company, and how it compares with the current one?
  • PER in the same sector: how are other companies in the same sector (insurance, technology, utilities…) comparing with the desired company?

For instance: BMW has a PER of approximately 9 (that means, every 9 years it earns as much as it is valued), whereas General Mills has 17. Does this mean that BMW is cheaper than General Mills?

The right thing would be to compare BMW and General Mills with companies of their own sector. For instance, we could take Daimler, and see that the current PER is 13. And we could take Diageo, and check that the PER is 23. We can even search for the history of the company for a given ratio. Let’s check in the following graph the historical PER of General Mills — right now is rather on a high historical value:

image https://www.macrotrends.net/stocks/charts/GIS/general-mills/pe-ratio

As a summary: I prefer to buy companies that are on a historically low PER compared with themselves and their sector.

Dividends

When I started my investing career, I would only invest in companies with a high dividend yield (5%+). At that time, those companies were Vodafone, Daimler, BMW, Unibail… With the time I have seen that a high dividend can be a premonition for problems — in many cases, this is symptomatic of company problems, and will likely be cut in the future.

There is no problem to invest in companies with high dividend yield even if it is reduced, especially at the beginning. This helped my portfolio to grow faster, since I was getting at the beginning big dividend yields, and I was reinvesting them and getting increasingly higher yields. However, now that my portfolio is more shaped, I am trying to incorporate DGI companies — companies that will grow sustainably their dividend over time.

Let’s see the following graph: company A paying an initial dividend of 3% and growing 10%, versus company B paying an initial dividend of 7% and growing 3%.

image

After 23 years, company A has surpassed the high yield company and keeps growing much faster than company B.

You need to evaluate based on your own circumstances the percentage you want for each type of company. In my case: since my portfolio has already a decent size, and I do not need to accelerate the snowball, I am starting to swing towards companies of type A. I keep my high dividend yield companies, and they provide a nice fuel to feed DGI companies.

The ability for a company to pay growing dividends in the future is sustained by a few factors: growing EPS (earnings-per-share), contained payout (amount of cash being paid from dividends), reduced or controlled debt and other circumstances (defensive companies are more likely to be DGI than cyclical ones, for instance).

Repurchases

Some companies have a plan to repurchase stock, and although this does not immediately mean an increase in our dividends, over time it helps. Dividends that are repurchased are out of circulation. For instance, if a company owns 100 stocks and repurchases 10%, there are now 90 in circulation. If this company was having an EPS of 1, now the EPS will be 1.1, without having done anything in particular — and this extra benefit can be distributed among shareholders. Check out in this graph some information combining companies' yield with their repurchase program.

image

For instance: Cisco has been paying only 2.74% on dividends, but it has repurchased 9.98% of its stock. That is an impressive combined number of 12.72%. Furthermore:

Cisco dividends in 1Q2020 = 1.486 Mill

Cisco dividends 1Q2019 = 1.500 Mill

They are paying less cash in dividends, but the dividend yield has increased by over 6% from 1Q2019 to 1Q2020.

As a summary: I consider companies both by their buyback and dividend yield.

Ranking

Another thing I have started lately to take into account is to add more companies belonging to a denominated rank (aristocrats, kings, champions). Aristocrats companies have been paying growing dividends for 25 years and belong to the S&P500. Kings have been paying growing dividends for at least 50 years and belong to the S&P500. Champions have been paying growing dividends for at least 25 years, and do not necessarily belong to the S&P500 (requirements for European companies are different). This is my current ranking distribution:

image

Over time, I will feel more comfortable with at least 50% of my portfolio belonging to a rank. Past benefits do not ensure future benefits, but companies that have a growing dividend policy have been highly profitable historically, and they have lower volatility than the index.

image

Geographical considerations

Depending on our tax residence, we are subject to double taxation. For instance, if you live outside France you are subjected to French double taxation (15% right now, and at the top of that your own local taxes). This can become a burden.

I am a German tax resident, so German companies are the best ones I can acquire. Dutch and UK companies have 0% foreign taxation, so I incorporate them into my mix. France and Canada have higher taxes than other countries, whereas Spain and the US have acceptable ones. I take those things into consideration when I am acquiring stock. This is my current geographical distribution:

image

If I am following a company that belongs to Germany, the UK or Netherlands and I am convinced by their fundamentals, I will add this company to my portfolio. Almost the same for Spain and the US (lower taxation). However, if the company is in France or Canada, I consider it twice before acquiring.

I currently hold two french companies: AXA and Unibail Rodamco, and Canada Imperial Bank of Commerce.

  • I hold AXA for being one of the best insurance companies in Europe and the world, and having acquired it during a cheap period.
  • I hold Unibail Rodamco for being the only European REIT, with premium units in most of the European major cities.
  • I hold CIBC for its very healthy fundamentals, and for having paid a dividend for more than 120 years.

One French company I have been following for a while now, Engie, has nice fundamentals and I believe it is on a very good moment to acquire (has finished some investments to increase productivity, is expanding in some other countries and has finished repurchasing some stock). However, I have already several utilities from different countries, and at this moment there are better companies I can acquire.

The geographical distribution provides another mean in terms of diversification. Currently, the US economy is growing stronger than the European economy, but this has not always been like this, and it might change in the future. Investing in companies from different geographical regions, in different currencies and with different countries exposition adds diversification to our particular cocktail.

Timing

I do periodic contributions to my portfolio. I reinvest the dividends as they come (normally putting them together to make bigger acquisitions), and I do monthly transfers to my broker at the beginning of the month, following the principle Pay yourself first. Every extra cash flow I receive from different sources is automatically sent to the broker. In fact, I do not keep too much in cash — something between 6–10 months of living expenses. This approach was scary at first, but it has helped to grow the snowball more than I was expecting when I started. Over time, the passive income has grown to a point where it covers most of my expenses.

Some folks prefer to wait until the prices are lower and do their purchases. I do follow prices as a hobby and invest also frequently when there are random market drops, but I do not obsess too much about it.

Community

I cannot analyze all the companies in the market — that would be unfeasible. So I rely on other sources. I have added my portfolio to Seeking Alpha, and there are a few investors I follow there, and I read their analysis. Their analyses do not necessarily convert into a buy from my side, but I read them with attention.

There are some individual folks I follow and chat with. There is a huge Spanish community I have the pleasure to belong. I check the analysis of Snowball, Capturando Dividendos and Gregorio. There are some channels where we communicate (forums, Telegram groups and Twitter), and we exchange ideas.

A practical example

In my very particular circumstances: for my upcoming acquisitions, I am considering companies such as Texas Instruments, Cisco (increasing dividends over the last year, nice buyback programs, low representation on my portfolio, historically cheap), Enagás, REE (high yield, low representation on my portfolio, defensive sector), SPG (historical lows, nice dividend yields), Diageo (nice buyback program, historical lows, nice dividend increase, no representation yet on my portfolio, geographical diversification), etc.

Other considerations

Since this is a long term game, I do not care too much about the initial acquisition price. The companies I acquire will rarely be sold, so the price does not matter too much. In fact, I do not compare my portfolio performance with the S&P500 or by its growth. The main metric I use is how many dividends I am getting this year in comparison with the last year, and how many dividends I will be receiving this year in comparison with the last year. This year I have earned 38.2% more than in 2018, and I forecast for 2020 an increase of about 26–30%. I also have a calculator where I can input the dividend growth per year, my yearly contribution and taxes, and see how this will grow over time. I have released a light version of my template that you can use here.

I do choose also companies with a Wide Moat, high capitalization and generally belonging to an index — the so-called blue chips. They are the companies that most likely will be with us in 30 years.

Some last words: if you are investing long term, you are choosing a selection of excellent companies from around the globe, and distributing them in your portfolio. You reinvest all the income, and keep contributing towards it. This has a compounding effect, and over time the snowball grows and it keeps growing alone. You are investing in real-world companies (that means, the products you buy and use every day) and holding them for a lifetime period. It is almost impossible to go wrong with this approach, it just takes time to see the effects.

I write my thoughts about Software Engineering and life in general on my Twitter account. If you have liked this article or it did help you, feel free to share it, ♥ it and/or leave a comment. This is the currency that fuels amateur writers.