Changing in increments was the only thing that worked for me and had a long-term impact.
Last year, my newsletter topics were everywhere, providing little value to software engineers. The format was also inconsistent. My writing sucked.
By the end of the year, I decided to change _everything_.
Of course, it didn't work out, except for one thing...
I can consistently write about topics that engineers (might) find valuable. And although I failed my original plan, changing even a single aspect of my newsletter motivated me to write more.
Changing in increments was the only thing that worked for me and had a long-term impact.
Last year, my newsletter topics were everywhere, providing little value to software engineers. The format was also inconsistent. My writing sucked.
By the end of the year, I decided to change _everything_.
Of course, it didn't work out, except for one thing...
I can consistently write about topics that engineers (might) find valuable. And although I failed my original plan, changing even a single aspect of my newsletter motivated me to write more.
Your format is excellent 👌
Thanks so much for this Akos.
Another side effect of trying to improve something is that it becomes more interesting and fun to do to. 👍
Wow, this was really cool to read and see the principles of Smart Brevity applied in realtime.
I can see a huge difference, already Richard.
Also, thanks for the mention. Means a lot.
One other tip I wanted to share is to try to stick to a max of 3 bullets in any group. Not an "always" rule, but a rule of thumb.
After 3, it starts to get hard to keep track of everything and it all kinda meshes together.
Looking forward to more of the articles, Richard!
Thanks Jordan, really appreciate your feedback 👍
I really like this new format Richard! Looking forward to read you more!
Thanks Nicola, appreciate the feedback 👍