Skip to main content


 What is stagflation? Stagflation is an economic state where we have both below economical states happening simultaneously, inflation and no growth.  We can have periods of inflation, we can have periods of no growth, but when we have them together, we call this stagflation.

So, stagflation is when we have both:

  1. We have inflation
  2. We don't have growth
Let's define inflation, we have two mainstream definitions:
  1. Price inflation – the prices are getting higher
    1. We have a measure of a few goods in a basket – warning which goods
    2. The weight of these goods in this index changes over time to reflect their real life ratio
  2. Monetary inflation – increase in money supply
    1. Usually increase in money supply should reflect the actual economic growth
We actually see big inflation in a combination of both price inflation and also monetary inflation.  During inflation periods, we have brief stagflation periods.

Presently, we have over 4 decades of disinflation, but since 2020+ we started having commodities scarce and combining this with the monetary inflation we now have inflation that could start a new period.

What to invest during stagflation:
  1. Bonds – not good relative fixed yields
  2. Stocks – Medium they rise, but they have issues planning for future due to instability in currency
  3. Real estate – better but not liquid
  4. Industrial Commodities – best could be unstable at first – part of definition of inflation rise in prices of commodities.
To summarize, good investment during stagflation
  1. Cash and bonds do not give us any protection from inflation very minor
  2. Stocks are only moderate inflation defense
  3. Anything with fixed rate yield like bonds is not good
  4. Commodities while volatile, while good, can also be volatile in prices
  5. The industrial commodities are much better like oil, nickle, uranium
  6. Gold is also good during inflation and slow growth – during stagflation
The current best book to understand the global economic state


Popular posts from this blog

Functional Programming in Scala for Working Class OOP Java Programmers - Part 1

Introduction Have you ever been to a scala conf and told yourself "I have no idea what this guy talks about?" did you look nervously around and see all people smiling saying "yeah that's obvious " only to get you even more nervous? . If so this post is for you, otherwise just skip it, you already know fp in scala ;) This post is optimistic, although I'm going to say functional programming in scala is not easy, our target is to understand it, so bare with me. Let's face the truth functional programmin in scala is difficult if is difficult if you are just another working class programmer coming mainly from java background. If you came from haskell background then hell it's easy. If you come from heavy math background then hell yes it's easy. But if you are a standard working class java backend engineer with previous OOP design background then hell yeah it's difficult. Scala and Design Patterns An interesting point of view on scala, is

Alternatives to Using UUIDs

  Alternatives to Using UUIDs UUIDs are valuable for several reasons: Global Uniqueness : UUIDs are designed to be globally unique across systems, ensuring that no two identifiers collide unintentionally. This property is crucial for distributed systems, databases, and scenarios where data needs to be uniquely identified regardless of location or time. Standardization : UUIDs adhere to well-defined formats (such as UUIDv4) and are widely supported by various programming languages and platforms. This consistency simplifies interoperability and data exchange. High Collision Resistance : The probability of generating duplicate UUIDs is extremely low due to the combination of timestamp, random bits, and other factors. This collision resistance is essential for avoiding data corruption. However, there are situations where UUIDs may not be the optimal choice: Length and Readability : UUIDs are lengthy (typically 36 characters in their canonical form) and may not be human-readable. In URLs,

Dev OnCall Patterns

Introduction Being On-Call is not easy. So does writing software. Being On-Call is not just a magic solution, anyone who has been On-Call can tell you that, it's a stressful, you could be woken up at the middle of the night, and be undress stress, there are way's to mitigate that. White having software developers as On-Calls has its benefits, in order to preserve the benefits you should take special measurements in order to mitigate the stress and lack of sleep missing work-life balance that comes along with it. Many software developers can tell you that even if they were not being contacted the thought of being available 24/7 had its toll on them. But on the contrary a software developer who is an On-Call's gains many insights into troubleshooting, responsibility and deeper understanding of the code that he and his peers wrote. Being an On-Call all has become a natural part of software development. Please note I do not call software development software engineering b