[fixxer]

I'm sure you mean well. You need to pare back the jargon and focus these blog posts on user experience, IMO. As an engineer dealing with all the usual bullshit from higher ups that learned a new buzzword and have to have it right now (even though it doesn't do what they think it does...), an article like this is always going to get a response like mine. And on this forum, I'm not alone.

[sirgiganticus]

I'm sorry you have issues communicating with your higher ups. However this particular post is written by the Head of Engineering at Monzo, who is the higher up, and seems to be aware of the implications and design decisions, as well as downsides and pitfalls.

I'd also wonder if a post marked "Technology" with a title that includes "Backend" really needs to pare down the jargon and focus on the user experience as opposed to say, this one https://monzo.com/blog/2016/08/08/updated-design/ , which has minimal jargon. Also when talking about architectural decisions across an entire platform, you're going to have to mention a lot of different technologies.

Finally, to quote you: "an article like this is always going to get a response like mine" == "it's not actually my fault, the post made me do it" - it's not an acceptable excuse.

[fixxer]

Lol. Loading up a blog article with tech buzz is a huge red flag to me that the CTO doesn't know as much as you might think. And no, I don't have a problem communicating with my higher ups: I just have had enough time in industry from startups to Fortune 500s to understand how decisions are made.

EDIT: I'm guessing you work there. You disagree with me; that is fine (many do). But... How quick did this fall off the front page?! From that alone, I'd claim my negativity is more representative of the readers that post was trying to target. I'm sure your company is trying to do something awesome, but you're not going to win hearts and minds with tech fodder like that.