You know that feeling when you finish yet another self-development book, and all excited about your “new you”, but as days pass, nothing happens? Or worse, you get fatigued?
I might have an answer for you. And no, it’s not a course, or a masterclass. Just sharing wisdom.
A while back ago, I read an interesting blog post. The author was talking about the ratio of consumption and creation.
Imagine that your brain is a bucket. And every time you consume, this bucket fills up. And when you consume too much, like a real bucket, it will explode or overflow.
Consumption is mostly passive: reading books/articles/newsletters, watching YouTube/reels, listening to podcasts, attending self-help seminars, etc.
And the only way to empty the bucket, is through a release valve called “creation”.
Creation is active: writing a blog post, building a software, speaking at conferences, teaching, journaling, etc.
Consumption is useless, unless you do some creation with it. So go create something in order to reach your potential!
Consumption is, however, very important. It’s just that we need practice after consuming something. But what to do if we practice, but don’t know how to sharpen our skill?
If you are a software engineer, you probably have to write technical documents. And you probably don’t really like that. Com’on! We would better write some code. But technical writing is an important, and crucial part of a software engineers’ career. And sometimes in order to perfect our creation, we need to consume some content.
This is why I want to offer you a limited time 20% discount on my recent book—Technical Writing for Software Engineers: A Handbook.
This book is a compilation of all my knowledge, and mistake I’ve made, presented to you in a short and concise form. If you struggle with technical writing, consider getting this handbook.
And don’t worry—it’s covered by 7 days money-back guarantee, no questions asked.
The discount is limited to for one week, and will be given to the first 10 people to follow this link → https://kudmitry.gumroad.com/l/technical-writing-for-software-engineers/0v69fmq