This is a short message to let you know that this Substack won't be publishing any new articles for the foreseeable future.

I'll explain the reasons below but first let me tell what this means.

What will happen next

First and foremost, this doesn't mean the community is disbanded! On the contrary, we'll double down on community events this summer, especially recurrent virtual meetings at our Discord server.

On the other hand, I'll still publish some opinionated articles on technical writing in my own Substack from time to time, , so feel free to subscribe there if you want to keep getting these.

Now, this Substack will stop publishing indefinitely. I won't delete anything, though, so all previously published articles will remain freely accessible forever (or as long as Substack exists) and I will slowly move the most important articles to my main publication, probably updating them as well.

Why I'm doing this

To give you some context, I started this Substack as a way to reunite a small diaspora of technical writers who were fed up with social media and seeking a new digital home compatible with our values. We started sharing insights and tools of the trade, as well as spotlighting novel and experienced writers alike.

Over the last year and half, we have grown to more than 1000 readers, and 80 or so regulars at the Tech Writers Discord. Many of us have had plenty of insightful discussions on all topics around technical writing, learned from each other, and forged what I think is a valuable and lasting friendship.

And as the community grows and the conversation moves more and more to interactive and cozy spaces, the relevance of this publication keeps waning.

The Tech Writers Stack is no longer my pet project. It's a thriving community of writers who have found a digital home to share and grow together. I feel honored to have helped spark this community, and I want to put all my effort in the future into the social part of the community: hosting real time events, fostering collaborations, and helping new writers kickstart their online writing journey.

And so, I believe this Substack is no longer the best vehicle to help grow this community. As much as I've enjoyed writing and publishing here, the most impactful work I've done has been at Discord, Notes, and other online spaces for discussion, where I've met many of you. And there is where I want to focus my efforts.

Farewell, and see you soon

So that's it. This is the last article you’ll get from this Substack, at least until we figure out what, if anything, is worthwhile to publish here. Maybe, some time in the near future, we'll find something relevant to share through this channel. If and when that happens, we'll knock on your inbox once more.

In the meantime, come join us in Discord at The Writers Stack server and discover a community of writers eager to help you kickstart your technical writing career.

And finally, I want to extend a huge thanks to some of you who've been critical for the success of this community:

, , , , and .

And of you've read this far, thank you for your continued support. See you on Discord and Notes, and anywhere else we're connected.

Best,

Subscribe now

First, tell us a bit about yourself. Who are you? What is your day job? What are your professional interests?

My name is Riccardo Vocca and I am a marketing student (I’m in the last month of my Master’s Degree) and Research Assistant. In particular, in addition to preparing my final experimental thesis, in this period I am supporting a research project related to Artificial Intelligence. Every day I divide myself between different tasks, including reading papers, analysis and so on.

My clearest life goal is certainly to pursue an academic career, starting with a PhD. 

I am strongly interested in the entire field of Consumer Behavior research, that is, very briefly, the field of study that seeks to understand how consumers behave in certain situations - and why they do so. In recent months I have come into contact with research on interactions between consumers and artificial intelligence, and it was 'interesting at first sight', I dare say! From there I began to delve deeper into the topic until I decided to share the large amount of information and insights on the topic I was coming into contact with.

From there The Intelligent Friend started, the first - to my knowledge - newsletter on Substack that is focused on the relational perspectives between humans and AI.

Now tell us about . What is it about? What topics do you cover? Who is your intended audience?

As I was saying, is the newsletter that focuses on the relationships between humans and AI, a field that is both specific and broad at the same time. The prospects of AI and especially the recent developments of ChatGPT-4o have highlighted how important it is to understand how we not only use - from a functional point of view - this technology, but also how we relate to it, how we interact, how we perceive it from a social and psychological point of view. The ChatGPT-4o video with the very similar (if not the same) voice from the movie 'Her' should further highlight the importance of the topic. 

In each weekly issue I talk about a paper deriving from this field of research, which I find absolutely fascinating! For example, in the past I have talked about how we can feel 'love' for Alexa or perceive her as a close friend of ours, how we sometimes find it more difficult to discuss some things with a doctor than with a chatbot, how AI can help us make very risky decisions and much more. As you can imagine, therefore, the themes are different, but all share the relational perspective, which is what my newsletter focuses on. 

To tell the truth, in addition to this weekly issue, two formats have been added: Nucleus, in which I summarize 4 papers and bring other interesting readings and insights (even not specifically on the topic of AI-human relations), and Intellibox, in which every week I invite people to experiment by creating an immersive challenge that they can 'play' on any chatbot, even a free one. These two are part of the paid membership of The Intelligent Friend, which however I'm proud to keep at the minimum (and therefore super accessible) price here on Substack: 5 USD. 

My initial audience was very clear: academics and professionals already aware of the topic but who had not yet explored relational perspectives. In reality, I have gradually seen that the theme and the newsletter have attracted an increasingly varied audience, and I am really glad about it.

How, when, and why did you begin writing about technical topics on the Internet?

To tell the truth, I have always been an extremely curious person, since I was a child. I have always loved reading animal atlases, illustrated scientific magazines and much more. And this wasn't my first newsletter that I tried to start. However, this time, I felt confident in the consistency with which I could bring engaging content to my audience every time. 

So, when I saw that I was reading a large amount of papers and articles on a weekly basis, I said: "now is the time to give it a try". And so I started. In reality, beyond the theme, what I like about my newsletter - and the many authors I subscribe to - is the very challenge of trying to explain science in a simple way. It's a truly exhilarating challenge, which every time opens your mind and stimulates you to surpass yourself.

What role does technical writing play in your job and life?

I'm not going to lie: writing plays a really big part in my life. I'm not saying that anyone should start a newsletter, of course, but I think that if you have a strong interest in a topic and a desire to talk about it, maybe you have what it takes - along with consistency, of course! - to create your own little place and write what you find interesting and valuable. 

For me, writing means above all three things:

1. A continuous drive to know and learn new things;

2. A continuous push to improve myself in writing itself and in many skills, as well as training in determination and organizational capacity;

3. Here on Substack it also meant meeting new people and being valued regardless of the titles I held. I have PhDs who consistently appreciate my work, University Professors who have said they were impressed by one of my acts, professionals who have said you inspired them at work. Meeting people, even if they're not people who read the newsletter, is something priceless and I'm noticing it more and more. And then, the exciting thing is the diversity of all of us. I met people from Chicago and London in an online meeting, and I constantly interact with writers from all over the world. 

P.S. is one of the wonderful people I have met!

How is your writing process? How do you organize your writing schedule? How much time does writing take you, on average?

Definitely one of the questions I like the most! Like almost everything I do, my writing process is very planned and rational. I write three issues a week, so it has now also become a fundamental necessity. Basically, at the beginning of the week I dedicate my evenings to searching for interesting papers and links for the 'classic' issues of The Intelligent Friend (those in which I talk about one paper per week, open to all) and Nucleus. 

The next day I focus on writing and creating the challenge for Intellibox. In general, during the week, in the evening or very early morning, I carve out a moment to read and collect papers, articles from scientific journals, pieces written here on Substack that I have found particularly interesting or enlightening. I also have a folder in Gmail where I put things 'to read later' that I think will be really interesting. They often end up being numbers that I repost and comment on in Substack notes. Each issue of The Intelligent Friend takes several hours of research, preparation and writing. I usually start writing when I have already done everything work-related or otherwise during the day. I immerse myself in a flow and I also have a playlist that is now fixed to help me concentrate and relax. P.S. If you want I'll share it in the comments!

What kind of advice could you give people considering or getting started with technical writing?

There's some advice I want to give that maybe goes a little against what some people say - but it's a personal opinion, obviously: choose a theme that you really like that is specific, but broad enough to let you wander. It's ok to write about parrot mating, but perhaps starting by writing about parrots in general (a specific topic in any case) will allow you in the near future to write about something that has stimulated you and not have to stay within the established canons. Without prejudice to the fact that, naturally, like all things, newsletters evolve. The important thing is to always be clear with your readers and explain the changes you want to implement. For me, at least, it's always worked! 

One more thing: choose a topic that you were already interested in or knowledgeable about before writing and that you would feel comfortable writing about at length. Practical example: I have always read research related to animals, but I have never had enough continuity or perspective - nor the preparation - to be able to write at all about this thing. You don't have to be an expert - very few people are! - but choosing something you like and that you already read a lot about can really help. Finally, although you don't have to be an expert, there are some 'parameters' of 'good manners' in my opinion that are important to respect:

• being clear in what you write, even if you use specific or pompous language; 

• respecting and citing the authors of the sources (very important!);

• not misrepresenting what is written in certain sources. 

And don't forget to have fun!

Any closing words you’d like to share with the readers of The Tech Writers Stack?

Glad to have a closing note! I would like to address all those people who would like to start with their newsletter and constantly think that they are not good enough, ready, excellent, meticulous, or anything else, to be able to do it. Impostor syndrome is fine, it's part of the process, but if it has to be something stopping you from writing your newsletter, it doesn't have to be this. 

Do you feel that stimulus to start your own publication here on Substack? Go! And, I would like to say, an important piece of advice, interact with many people on the platform, writers of more or less large publications, writers who write on the same topic, writers who write about different topics. And don't be afraid to ask for advice or an opinion: the community is ready to support you. If I hadn't written to Alejandro there would hardly be this number today, and yet, here it is. Have a good start and, if you start with your newsletter, let me know!

Before you go, I must happily suggest you sign up for this newsletter which supports many 'small' newsletters and, if you are interested in the topic of Artificial Intelligence, stop by The Intelligent Friend. If you like it, sign up! If you want to tell me something, propose an idea or comment, feel free to write to me in chat, I'm always happy to meet new people and exchange opinions!

This was The Tech Writers Highlight, a section of the Tech Writers Stack where we recommend new and seasoned writers. Leave a comment or question for to learn more about his work and writing.

Subscribe now

First, tell us a bit about yourself. Who are you, what is your day job, what are your professional interests?

Hi! I’m Kanaye. I’m a student and recently started writing here on Substack. As you can probably tell from my publication, I really enjoy coding! I’ve been coding for nearly eight years now, and I am passionate about writing about it too!

Now tell us about . What is it about? What topics do you cover? Who is your intended audience?

As the title suggests, my publication is written for all curious minds who like coding! I am an informatics olympiad silver medalist. I decided that I’d like to share the knowledge I gained from all that practice and study to share with the world. It’s not really intended just for competitive coders. Rather, all people who enjoy coding have something to learn from what I write. The main purpose was to expose people to a new realm of creative problem-solving, that is unlocked by what I learned. 

How, when, and why did you begin writing about technical topics on the Internet?

After winning my medal, a few things came to mind. Mainly, I realized that I didn’t want all my learning to just end after this, I wanted to share it. I learned so much from studying competitive coding that people can actually apply to their lives and to real-world coding problems! But, I don’t want people to have to dive down the rabbit hole and study rigorously as I did, so I decided to write these articles to spread the knowledge that I gained. I also wanted to gain a new skill, writing, so I decided to give it a try!

What role does technical writing play in your job and life?

Writing Elucidate is my passion. I feel genuinely happy when I write about what I learned, that’s the reason I code in the first place! When I think about a reader enjoying my work, I smile. It’s the joy you get from helping others I know everyone has experienced.

How is your writing process? How do you organize your writing schedule? How much time does writing take you, on average?

Generally, I try to post something new on a weekly basis. Writing every article takes several hours of dedication. First, the topic comes to mind. I have so many topics to write about that this part is not the main challenge. After the topic is decided, I then start writing. I always imagine the article in my mind before a single word is typed. If I were reading, what would I want? Once that’s in mind, I start typing. The journey from introduction to conclusion is a thrilling one. All illustrations are either hand-made by me using OneNote, or using Bing AI. Occasionally, I use other sources and credit them. I research new problems and modify them, then write and explain the solutions. Also, I ensure to leave my readers with a challenge problem at the end of every article, good to stimulate the mind :)

What kind of advice could you give people considering or getting started with technical writing?

Passion is important. If you are truly passionate about your work, you will continue writing even during the first few tough months when nobody reads your work. I encourage anybody considering this to simply go ahead and start writing. Any topic will do, as long as it truly interests you. Don’t think too much, you’ll get stuck in analysis paralysis and end up doing nothing. After that first post, consistently post, promote your work, and look for like-minded people. Writing about what gives you joy while educating others on tech-related topics is really an amazing thing to do. Good luck!

Any closing words you’d like to share with the readers of The Tech Writers Stack?

Thanks a lot to all readers for reading this. If after reading you’re interested in reading Elucidate: for the curious coder, you can check it out at kanaye.substack.com. I also would like to thank the entire community for being so kind, and for providing an avenue for writers such as myself to find an audience. Thanks a lot guys :)

This was The Tech Writers Highlight, a section of the Tech Writers Stack where we recommend new and seasoned writers. Leave a comment or question for to learn more about their writing.

Almost a year ago I decided to give the paid subscriptions a go, not because I thought I could make technical writing my day job - I already have like three of those, and I can't imagine not doing any of them. It was mostly for validation: to see if I could get anyone to care enough about my writing to be willing to pay something, not a lot, for it. And also, it couldn't hurt, right?

Long story short, it worked... somewhat. In terms of validation, I'm more than happy for my 68 paid subscribers. I couldn't imagine even a single person would be willing to support my writing. That bit of extra energy also helped motivate me to write more, and, I hope, a bit better.

However, in terms of affordability, technical writing still is, for me and probably for the 95% of my fellow writers at The Tech Writers Stack, little more than a hobby. And sometimes a rather expensive hobby. Many of you have deep expertise in areas where you could charge a substantial amount by the hour, and yet you choose to share that expertise for free.

And I get it, believe me. I also struggle with the dichotomy of wanting to share as much as possible to the widest audience I can with the reality of having too little time and too much work—like, real work, the one that pays the bill—to be able to give my Substack all the love I'd like to pour into it. So, over the past year I've tried different models to strike the right balance for doing something that I love—sharing some hard-earned lessons on sometimes pretty complex topics—in a way I can afford to.

On one extreme, I tried doing exclusive articles, but I found out some of my best writing was hiding in plain sight from the vast majority of my readers. Why write exclusively for 68 people when other 2000 are eager to read it? On the other extreme, I tried the patron-like support-me-if-you-can model, but of course, the vast majority of readers can't afford to support you, even if they wanted to. And to top it all, the subscription model seems to be on the decline—I know I have subscription fatigue, and probably you too.

But now I think I've found a sweet spot, and I want to tell you about it because I honestly think if it works for me, it'll work for many of you, probably even better than for me. The gist is this: write a technical book alongside your Substack, using free articles as the main material for content and the medium to drive sales.

How it works

Here is (just one way) how to do it. Pick a topic that you're reasonably knowledgeable and you think you'd enjoy writing consistently about. As an example, graph theory is one of those topics for me. Aim to write between 2 and 4 articles a month on that topic. Each article is published for free in your Substack and becomes a new chapter (or part of a larger chapter) in your in-progress book.

Now, here's the part no one tells you (or at least no one told me!) You don't have to wait for the book to be complete to sell it. On the contrary, set up a Gumroad account from day zero, and start pitching the book on each of your free articles.

And yes, some people will buy that crappy version 0.1, assuming it's an interesting topic! To sweeten the deal, I set a fairly low “early access” price compared to what a full technical book might cost. And I also offer other perks, such as a private Discord for early readers, a special shout-out in the acknowledgment section, stuff like that.

But mostly, the selling point is just the fact I'm writing this thing in public, incorporating early feedback. That, and the fact your readers are amazing and will do everything they can to support you. And this gives them something concrete, a one-time transaction that doesn't trigger our dread for another subscription.

It's so simple that it seems it can't work, but my early experiments say it works one order of magnitude better than paid subscriptions. Of course, your mileage may vary, but I've seen in little more than a month almost the same net profit from early book sales than a year of paid subscriptions.

I've completely changed my Substack business model in the last month. No more paywalled articles. With this model, I've been able to make all my content open and free, and still have something valuable enough that some readers are willing to pay for.

I still have subscriptions enabled on my Substack, though they have now become a free-ride ticket to all my current and future books. Readers who want to support all of my work, and can afford to, will still go for a traditional subscription. But those who can’t or simply don’t want to be attached to yet another subscription, have this alternative. It's a win-win

And besides all the advantages in terms of profitability, there's another way in which this pivot has positively impacted my writing and it's even more important: I'm more motivated than ever to write. Since all my writing is now public, I know I'll have as many eyes as I could wish for every article. And at the same time, I know I'm not writing exactly for free. Each article brings a trickle of new book sales, not enough to make a living out of it (yet) but enough to trick my primate dopamine-seeking brain.

But, but…

"But wait—I hear you ask—writing a book is supposed to be very hard!"

Yes, it is. It is harder than just writing a sequence of more or less interconnected articles. There is definitely extra work involved in writing, formatting, and setting up yet another platform (because why the hell Substack doesn't have that feature yet, right?).

But here is the thing. Writing is way harder than any of that, and you're already doing the bulk of it. The rest is not that much harder. If you can consistently pump one article every couple of weeks, believe me, you can write a technical book.

"Ok but, what if I don't write about a single, focused topic?"

I hear you, I'm writing not one but three distinct books on very different topics and for different audiences because I have many diverging interests. Perhaps you can find a subset of your articles that can be tied together into a coherent topic, like I did. Or perhaps variety is your thing! Maybe your book is about 20 weird, interesting things few people know (I’m looking at all you polymaths out there!)

"But—I hear you again—I just want to share my knowledge freely!"

I get it, and it's commendable, truly. If you can afford to, that is. But what I've found out is that more often than not even those who already are in a very stable financial position, eventually discover they can't write for free as much as they'd want to. There is a finite amount of time and so many things to do with it.

This is a way to make that free writing at least a bit self-supporting. But you can still make 100% of your content free. That's what I'm doing with my graphs book. Everything, including source code, is available for free online. The book is just a convenient packaging with some additional syrup and a couple of cherries on the top—if you can pardon the lousy metaphor.

The point is that you can adapt this model to your interests and values. You can make all or most of the content free, or you can make the book an extended version of your articles. The core of the idea is that 80% or more of the work is already done when you hit publish on Substack. And the remaining 20% could be enough to make the whole thing, if not profitable, at least affordable.

Some final words

Listen, I'm advocating strongly for this business model because I'm rooting for you. I truly believe the vast majority of you technical writers out there have what it takes to make a compelling book on your area of expertise. But I understand this is not for everyone. So here are some reasons why you might not want to do this.

First, it does take some extra effort. The hardest part is, as you might suspect, consistent writing. I waited for more than a year to make sure I'd found the workflow and rhythm that allowed to me write more or less consistently without the rest of my world breaking apart. If you're only a couple of months into technical writing, maybe it's better to wait until you've found your pace.

Second, it does put some extra pressure on you. Once you commit to a topic, you'll have to find a way to stay motivated to write about that same topic for over a year--or as long as it takes to finish the book. You can take some rest here and there, of course. But once you have people paying in advance for something you'll deliver in the near future, some pressure will inevitably build up.

And finally, we all know once a hobby becomes a job, it stops being fun. And there is the risk this model turns your otherwise pleasurable moments of exploration into yet another thing you have to do, instead of a thing you want to do. I don't have any magic potions to fight that, but I've found keeping a healthy variety of topics to write about lets me procrastinate from one while investing in another topic, tricking my primate brain into thinking this is not work.

But all in all, I think this is one of the most underrated business models for technical writers, and there has never been a better time to do it. You have the technology, the platform, and now a community of like-minded writers to support you and help you stay motivated, and sometimes kick you in the butt if we must. Please go ahead and give this idea at least a fair chance, you'd be surprised how much you can enjoy it.

And if you are interested in actually doing this, we at The Tech Writers Stack are building a community of writers to help each other. We proofread each other's works and share tricks and tools, and some of us have become full-time collaborators. Join us now and let's kickstart your indie tech writing career together.

Join The Tech Writers Stack

PS: If there is enough interest, I'm happy to share a few more technical articles on my actual process, from the tools I use to the workflows I follow. Leave a comment if that sounds enticing to you.

Leave a comment

Dive into a world of cutting-edge innovation and thought-provoking perspectives with this issue’s captivating articles. Explore the intricate dance of misinformation, engagement algorithms, and technical challenges in the AI field, and delve into the groundbreaking biology of Michael Levin, who turns cell assembly and morphology on its head.

Discover how AI can revolutionize the writing process and enrich the educational landscape while also addressing existential risks and present-day harms. Witness the power of growth and change in business, and journey back to uncover historical puzzles like the Trojan Horse and the disappearance of 10 days in Europe. Understand the complexities of human-AI interactions, grapple with the concept of success, and reflect on the pressures of perfection.

Tell us if you find this content valuable and what else you want to see in this section.

NOTE: A majority of this content is AI-generated, so although a human editor has read and aproved all of it, inconsistencies and mistakes are still posible. Let us know if you see anything.

If you want to see how this is made, take a look at the source code.

Featured articles

The following are AI-generated summaries of randomly chosen articles writen by members of our community in the previous week.

Why Gemini’s Struggles Aren’t Straightforward

Read more

Logan Thorneloe’s article discusses the misinformation surrounding Gemini’s alignment struggles, which include generating incorrect historical images, refusing to help with C++ code, and having trouble accessing plugin information. Thorneloe attributes these issues to the X algorithm’s need for controversy to drive engagement and revenue, rather than Google being behind in AI or introducing these “features” out of corporate bias. The author explains that these problems are more complex and likely caused by the rapid spread of unfounded claims. Thorneloe notes that many uninformed individuals can quickly become “experts” in AI, inadvertently contributing to the misinformation.

The AI Writing Revolution: Empowering Authors to Embrace Innovation Strategically

Read more

Nick Potkalitsky has written an article presenting a comprehensive guide on integrating AI into writing processes. The article is aimed at students, professionals, researchers, and entrepreneurs. It is divided into two sections, with the first section available for free. The first section discusses when and how to incorporate AI into specific workflows.

Why Alignment is the Hardest Problem in AI

Read more

Alejandro Piad Morffis discusses the greatest challenge in artificial intelligence (AI) development: AI alignment. This problem involves creating AI systems that generate outputs deeply aligned with user preferences rather than just following instructions or optimizing for superficial metrics. The core difficulty lies in accurately describing user preferences. Solving the AI alignment problem is crucial for addressing various AI safety issues, from present-day harms like biases and disinformation to existential risks.

The Psychology of Human-AI Interactions: Part I

Read more

Nat discusses the role of AI in shaping user engagement on TikTok in this article. The AI on TikTok collaboratively influences content consumption, creation, and social networking, resulting in high user engagement through frequent and prolonged platform usage. The platform’s AI fosters niche and fluid communities, allowing users to connect based on shared interests. As artificial intelligence rapidly evolves, it leads to phenomena like virtual companions, highlighting a modern amplification of the timeless human struggle with loneliness.

The Strange Practices at The Broadcaster’s Inn • Broadcasting in NumPy (A NumPy for Numpties article)

Read more

Stephen Gruppetta’s article introduces us to The Broadcaster’s Inn, a peculiar hotel on the outskirts of Nump Town. The hotel has a unique layout, with five identical floors and a grid-like arrangement of rooms. Its staff is a mystery; no one has ever met them outside the hotel. Gruppetta secures an anonymous interview with a staff member, hinting at revelations to come.

What I Learned Comparing ChatGPT & Microsoft Copilot

Read more

Lance Cummings discusses the challenges universities face in keeping up with AI advancements, citing a “suite” mindset that prioritizes all-in-one applications like Office 365 or Google Workspace. He highlights the need for students and tech professionals to experience various ecosystems, as most work environments use a variety of tools, up to 50 in some cases. Cummings points out the limitations of traditional university frameworks for technology procurement and funding, which struggle to adapt to the rapidly evolving tech landscape. The author advocates for a more customized, “boutique” approach to technology and workflow, enabling users to piece together their own app stacks tailored to specific needs.

Could OpenAI’s Sora be a big deal for elementary school kids?

Read more

In his article, Andrew Maynard discusses the potential of OpenAI’s Sora, an AI video engine. He expresses concern about the issues raised by hyper-realistic AI-generated videos, such as deep fakes and disinformation. However, he also highlights the potential of technology as a learning and development tool if used responsibly. Maynard was impressed by a video created by Sora using the prompt “an elephant made of leaves running in the jungle,” noticing its potential for fostering creativity in users who might find it challenging to articulate their ideas.

Understanding Success

Read more

Michael Woudenberg, in his article on Polymathic Being, examines the concept of success and how it is defined. He discusses the discrepancy between societal definitions of success and the outcomes people truly want. Woudenberg highlights the importance of a polymathic approach, which involves integrating insights from diverse fields to gain a more comprehensive understanding of success.

The Pathological Pursuit of Perfection

Read more

Josh Brake discusses his experience of maintaining a perfect 4.0 GPA throughout his undergraduate studies. However, he believes that this achievement should have an asterisk next to it, as it comes with a cautionary tale. Brake started with a strong foundation, having accumulated advanced placement credits in high school. He then sailed through his first year of college, but felt the pressure to maintain his GPA as he entered his sophomore year.

From the Community

The following are AI-generated summaries of the remaining articles published since last digest. The categories were assigned by AI as well.

Do you want to see your own technical blog featured here? Join us!

Join the Tech Writers Stack

In “Michael Levin and the shifting landscape of biological form and function”, Andrew Maynard discusses groundbreaking biologist Michael Levin’s revolutionary work in creating “biological machines” from cells for tissue repair, challenging traditional understanding of cell assembly and morphology.

In “The Art of Leaving Stuff Out (Ep. 15)”, Stephen Gruppetta argues that effective educators know when to omit details, illustrated through an egg-scrambling example distinguishing concise instructions from unnecessary scientific explanations.

In “The Gender-Equality Paradox in STEM”, Steve Stewart-Williams discusses a 2018 paper which found that higher levels of gender equality are associated with a lower percentage of female STEM graduates, challenging the assumption that greater gender equality would lead to more women in STEM fields.

In “Reactions to Research on Sex Differences”, Steve Stewart-Williams discusses his lab’s latest paper on people’s reactions to sex difference research in a radio show and podcast episode, and plans to release a written interview and a new blog post on his nature-nurture newsletter.

In “Change comes at you”, Andrew Sniderman discusses the concept of growth and change in the context of business, using examples such as compound interest and Moore’s Law to illustrate the idea of exponential growth.

In “Trojan Horses”, Andrew Smith recounts the story of King Arthur’s knight, Sir Bedevere, and his clever use of a large wooden rabbit to infiltrate the French castle, drawing parallels to the ancient Trojan Horse tactic from Virgil’s epic poem, The Aeneid.

In “The Great Stink”, Andrew Smith describes the crowded, unsanitary, and diseased city of London during the summer of 1858, focusing on the overpowering stench that filled the streets and even parliament.

In “10 Days That Disappeared”, Andrew Smith discusses how a discrepancy in the calendar in 1582, due to the changing of the seasons and the Church’s need to accurately determine the date of Easter, led to the disappearance of 10 days in Europe.

In “Why I am making all my posts free”, Alejandro Piad Morffis announces that he is removing the paywall from all his posts, having previously restricted access to some content that included opinionated and time-sensitive topics, and shares his pride in the substantial number of total reads his public articles have received.

In “NVIDIA Explained: Origins, GPUs and AI stock bump | EP8”, Viggy Balagopalakrishnan discusses NVIDIA’s past, present, and future, highlighting its origins, the impact of its first GPU, the shift towards AI-focused data centers, and the assumptions that must hold true for its high valuation to be maintained.

In “Backend Biweekly #3: 97 Updates and Resources,” Logan Thorneloe provides an overview of the latest updates in machine learning and AI. He also includes learning resources, with additional benefits for paid supporters.

Cut-off date: 2024-03-29T16:11:19

And that’s all for today! Let us know your thoughts about this format and any suggestions to make it more useful.

Leave a comment

Mastering the art of revising technical documents can be challenging, as most writers dread the revision phase. It's thrilling to let your thoughts flow onto paper, but revisiting your work to correct inconsistencies and errors can feel like a chore rather than a creative exercise.

Many technical writers struggle with revisions for two main reasons. First, it's difficult to balance generating new ideas while simultaneously critiquing your writing. Second, many writers revise their work in an unstructured and unfocused manner, often by simply rereading and making changes until nothing else seems wrong. This approach is far from ideal.

In this article, I'll introduce a more effective revision method that works for me and many successful writers across various genres. Adapted from prolific fantasy author Brandon Sanderson, this technique is applicable to fiction, technical documents, and textbooks alike.

The method revolves around two key principles: decoupling writing from revision and revising with intention.

Principles of effective revisions

By separating the writing and revision processes, you can enter distinct mindsets for each task. This allows you to focus on creativity while writing and critical analysis during the revision phase. When revising with intention, you avoid simply correcting errors as you encounter them. Instead, develop a structured plan that addresses specific issues in your document. Following these principles can help transform the revision process into a more enjoyable and efficient experience for any writer.

Decouple writing from revision

Think of yourself as either the creator or the critic, but not both at the same time.

When in creator mode, focus on writing whatever comes to your mind. Some writers are more structured and prefer a clear outline, while others are less structured and like to let their thoughts flow freely onto the page. Regardless of your approach, when writing, just write. Don't revise or reread what you've written – simply create.

Once you have your first draft, switch to critic mode, but take a break before revising it. It can be a short walk, making coffee, or watching a YouTube video. Or just sleep over it for a couple nights. Give your mind some time to reset from the writing process.

When you’re on critic mode, your goal is to analyze and improve your work. Tackle revisions one step at a time – don't try to fix everything at once. Instead, focus on specific aspects during each revision phase. We will expand on this idea next.

In critic mode, don't make any changes to the document. Instead, go line by line and make comments on sections, highlighting sentences or words that need improvement. There is some nuance here: you can fix minor issues like typos or missing commas –most writing software will catch these errors anyway–, but don’t fix anything that takes, say, more than five seconds of thought. Instead, just leave notes.

After finishing revising the document, take another break to clear your mind. Later, return in creator mode to address the revisions. Although you should focus on fixing the identified problems, don't feel restricted by them. You can disagree with the revision or add new sections inspired by your critique.

Remember to allow yourself creative freedom while addressing the revisions, as this will help improve your writing overall. Perhaps add a dash of excitement and consider differing slightly from the critic's viewpoint. Treat the critic not as a commanding boss, but as a helpful editor offering suggestions to enhance your work.

Now you get the picture, right? Enter creator mode, make adjustments, and then allow your text to rest before revisiting it for further revisions. Continue this back-and-forth until you're pleased with the results. By separating these two roles and being mindful of your objectives during each stage, you'll create a more efficient revision process that allows you to make the most of your writing and editing sessions.

Revise with intentions

Tackle each revision with a concrete plan of what issues to look for.

When revising a document, you may face various issues, from missing commas and weak verbs to unsupported conclusions and major structural problems. Revising with intention means separating your concerns and addressing them from high-level to low-level problems.

First, focus on the document's structure. Is your main claim clear? Do each section and part support that objective? Is the order of arguments and ideas correct? Should anything be explained earlier? Does your conclusion tie everything together, or is it scattered? Is there a strong introduction with a motivating problem or example? Consider the story your writing conveys and assess its coherence, flow, and organization.

Next, address low-level concerns like engagement and clarity. Choose the best words and synonyms to convey your message. Select strong, clear verbs that communicate your intentions effectively. Are you using a passive voice, or is your writing active and engaging?

Mid-level problems involve paragraph structure and clarity. Make sure each paragraph supports your argument effectively and clearly. Can you rearrange the order or words to improve clarity? Consider moving the premise to the beginning and the conclusion to the end.

You can divide the editing process into multiple stages. A simple approach is two stages: one for structure and one for content. For short articles, start by reviewing the overall structure and flow of ideas. Then, thoroughly revise the content to ensure appropriate synonyms, words, verbs, voice, and sentence structure. This is what I do with most of my blog articles.

You can also split it into three phases: 1) high-level story structure, 2) clarity of ideas, and 3) engagement. First address the high-level story, then focus on each argument's explanation and consider adding examples or reordering explanations for better support. Finally, review engagement by examining verb strength, active sentences, and meaningful word choices. This is what I do with longer articles, such as book chapters or scientific papers.

Now, here is the important part. When entering critic mode for revisions, clearly state which phase you're in and focus on detecting specific issues. Before starting the revision process, state your objective and identify the issues you're looking for. Write down general questions that address these problems, such as: Is the structure's order correct? Is the tone active and engaging? Are all verbs strong and meaningful?

As you revise, refer back to these questions and assess the text based on them. When providing criticism, avoid simply saying something is wrong. Instead, explain why it's wrong: The structure isn't right, it's not easily understood, or it doesn't address the claim being made. Be detailed in your critical revision.

However, don't suggest solutions at this stage. Just criticize. Point out if the tone is too casual or formal, if a verb is weak, or if an argument lacks evidence. Leave a focused set of comments for your next creative phase.

Final remarks

Let's end by discussing some caveats to the principles we mentioned earlier. First, the principles themselves are more important than their strict implementation. The key ideas are that you should either be writing or revising, but not both at the same time, and that you should have a clear idea of the issues you're looking for when revising, instead of looking all over the place.

You don't need to be extremely structured with your schedule; some people prefer a looser approach. The important thing is to keep these principles in mind when working on your document.

When revising, take notes and write them down. One common issue with revision is making mental notes of problems and then trying to fix them without writing them down. Instead, put yourself in the shoes of someone who isn't the author and leave thorough notes about the document. Don't overthink these comments – they're for yourself, so focus on addressing one specific issue per note.

Lastly, how long should you revise? Ideally, you would continue until you're satisfied with your work. However, remember that perfection isn't always achievable; focus on creating clear and effective content while adhering to these principles.

For most, the “revise until satisfied" method doesn't work because you'll never be satisfied with your own work. So, what I do is set a fixed number of cycles, like two revisions—one high level and one low level—and then I publish.

Of course, you have some freedom when in creator mode.If you feel the high-level structure is okay during a revision, you can move to the next stage. Alternatively, you may leave a note for your next editing session to do another high-level revision pass. You have the freedom to do this, but working with constraints is important.

Tell yourself you have two or three revisions to fix it, and then hit publish. Otherwise, you may perfect your document forever without ever being satisfied.

Share

Dive into a world where technology and human nature intertwine. Explore the depths of programming with insights from C, understand the power of networks through Metcalfe's Law, and delve into personality traits that shape us. Witness the awe-inspiring capabilities and potential perils of AI, as it generates videos and art and even influences election outcomes.

Grapple with complex terminology in machine learning and consider the future of AI-assisted education. Ponder trust in AI, the value of being 'lost', and Bertrand Russell's wisdom. Witness the rise of the Mongol Empire, the origins of words, and much more.

Tell us if you find this content valuable and what else you want to see in this section.

NOTE: A majority of this content is AI-generated, so although a human editor has read and aproved all of it, inconsistencies and mistakes are still posible. Let us know if you see anything.

If you want to see how this is made, take a look at the source code.

Featured articles

The following are AI-generated summaries of randomly chosen articles writen by members of our community since last digest.

It's Been a Rollercoaster of a Week in AI

Read more

Andrew Maynard discusses recent developments in AI that caught his attention. He talks about OpenAI's new AI video generator, Sora, which can create realistic and captivating videos from text inputs. The author highlights the potential of Sora to enable people to visualize their imagination but also raises concerns about deep fakes, bias, intellectual property, and job displacement. Additionally, Maynard mentions an effort to disrupt the deepfake supply chain, and he encourages readers to consider the implications of such technology becoming widely available.

Why Machine Learning Terminology is So Confusing

Read more

Logan Thorneloe discusses the confusion arising from machine learning terminology. He mentions how his interactions with beginners in the field have inspired him to clarify common misconceptions. Thorneloe distinguishes between Artificial Intelligence (AI) and Machine Learning (ML), stating that AI is a broader field focused on creating intelligent systems, while ML is a subset that involves training machines to learn from data. Unlike traditional AI systems, he highlights that ML systems improve accuracy over time without explicit programming. Thorneloe also points out that the complexity of machine learning terminology is due to the technical nature of the field, which can be challenging to communicate effectively.

Be A Dreamweaver

Read more

Josh Brake discusses the pitfalls of relying too heavily on statistical distributions and personalization in understanding people. He warns that personalization, while useful for targeted advertising, can reduce people to mere shadows of their true selves. With the advent of generative AI, Brake cautions that hyperrealistic personalization will become even more common, potentially leading to widespread deception. He encourages readers to resist the allure of personalization and to strive instead to truly understand and connect with those around them, urging them to become "dreamweavers" who create meaningful relationships. The article is part of a reader-supported guide to human flourishing in a technology-saturated world, with paid subscriptions being the best way to support Brake's work.

The Diminishing Charm of AI: Are Chatbots Losing Their Luster?

Read more

Nat discusses the potential performance degradation of AI models over time, citing sources claiming that some models are becoming less capable. Stanford computer scientist James Zou points out that large language models like GPT-4 experience performance degradation due to user interactions and continuous training efforts, affecting complex reasoning abilities. This performance decline is not uniform and may inadvertently occur as safety measures are implemented. Nat highlights the importance of ongoing monitoring and research to maintain the long-term reliability and effectiveness of AI models. Kevin Roose, a New York Times journalist, shares his firsthand experience with the 'untamed' version of the Bing chatbot, now known as Copilot, further emphasizing these concerns.

Empowering Essays: The Impact of AI on Student Writing Processes

Read more

Nick Potkalitsky, an educator focused on integrating AI in writing curricula, writes about using AI to enhance student essays. He discusses his 9th-grade English class's thematic essay on Bryan Stevenson's "Just Mercy", where students develop and evolve their thesis throughout the unit. Potkalitsky acknowledges the risk of an early thesis overshadowing new ideas but believes introducing AI early can help students refine their initial thesis with deeper reading and analysis. He emphasizes the importance of a community-supported approach to education and encourages readers to engage with his work and share their thoughts.

Don't Trust AI... Entrust It

Read more

Michael Woudenberg discusses the importance of shifting our perspective on trust in AI and autonomous systems. He worked with colleagues at Lockheed Martin to develop a framework called FIDES (Frameworks for the Integrated Design of Entrusted Systems) to analyze these systems with a focus on human advantage and safety. The article emphasizes that instead of trusting AI in general, we should entrust it with specific, well-defined tasks. Woudenberg argues that this shift in perspective can help us navigate the challenges and ethical concerns associated with AI and autonomous systems more effectively. The full draft paper of the framework is available for reference.

Lost and Found

Read more

Andrew Sniderman discusses the excitement of discovering unexpected treasures at lost and found areas as a child, and how getting lost can be liberating as an adult. He then introduces the term "enshittification," coined by Cory Doctorow, which refers to the process of platforms initially being good to their users, then abusing their users for the benefit of business customers, and finally keeping all the value for themselves before ultimately dying. Sniderman relates this to various free internet services that were once amazing but have become less appealing due to excessive ads and algorithms. The article ends with a tweak to Wirepine's business model, which will be revealed to those who continue to read The Wirepine Weekly.

From the Community

The following are AI-generated summaries of the remaining articles published since last digest. The categories were assigned by AI as well.

Do you want to see your own technical blog featured here? Join us!

Join the Tech Writers Stack

Essays

In "To C or not to C", Julio Merino argues that while you don't need to know C to be a good programmer, understanding C can provide valuable insights about programming concepts such as memory management and system calls, which are relevant in many other languages.

In "Metcalfe's Law", Andrew Smith discusses Robert Metcalfe's observation that the value of a telecommunications network is proportional to the square of the number of connected users, highlighting his work on Ethernet at Xerox PARC and its impact on the internet.

In "12 Things Everyone Should Know About Personality", Steve Stewart-Williams discusses various aspects of personality, including its higher-order traits, heritability, and how it differs between men and women.

In "Dunbar's Number", Andrew Smith discusses Robin Dunbar's theory that 150 is the theoretical cognitive limit to the number of stable social relationships one can maintain, using the correlation between primate neocortex size and social group size to support this claim.

In "On Generating Ideas - Leadership & Work", Michał Poczwardowski presents a framework for exploring ideas together with a team, emphasizing the importance of addressing human nature facets like conformity, authority bias, and individual communication preferences to foster quiet idea generation.

In "A Very Bad Way to Die", Andrew Smith discusses the tragic collapse of the meeting hall at Petersberg Citadel in 1184, causing dozens of nobles to fall into a cesspit and meet a gruesome end.

In "AI as a Catalyst for Innovation: An Interview with Dr. Elliot Bendoly", Nick Potkalitsky discusses the potential benefits and risks of generative AI in education, highlighting a research paper that supports the thoughtful implementation of AI to enhance learning.

In "All the Lonely Peoples", Andrew Smith explores the concept of loneliness as solitude through the example of the isolated Sentinelese tribe of India, who choose to remain disconnected from the world, while contrasting it with the paradoxical isolation experienced through constant connection in the digital age.

In "Top 12 Bertrand Russell Quotes", Steve Stewart-Williams compiles and comments on a selection of thought-provoking and humorous quotes from the British philosopher, mathematician, and political activist.

In "Fortnight", Andrew Smith explores the origin of the word, tracing it back to ancient calendars based on lunar cycles and the concept of dividing the sidereal month by two.

In "What Is Going on with AI in K-12 Anyway?", Nick Potkalitsky discusses the varying visions of AI implementation in K-12 education and presents a comprehensive overview of the current state of AI adoption through engaging conversations with a diverse group of educators.

In "Unless You Are the Mongols", Andrew Smith discusses the meteoric rise of the Mongol Empire under Genghis Khan, attributing his success to his mother's teachings on resilience and political alliances.

In "A Dime a Dozen", Andrew Smith discusses how the meaning of the phrase has remained consistent, while the value of what it represents has shifted over time, highlighting examples such as the decreasing cost of sharing information, electronic devices, and learning, and the increasing cost of housing.

News

In "Should We Let AI Art Rewrite History?", Jurgen Gravestein discusses how Google's AI image generation tool, Gemini, was halted due to inaccurate historical depictions, and how its attempt to promote diversity resulted in controversial, historically misleading images.

In "Tech's Pledge To Fight AI Election Interference & Twillio’s woes with Segment | EP 6", Viggy Balagopalakrishnan discusses tech companies' voluntary pledge to combat AI-generated election interference through 2024 and Twillio's challenges with their Segment acquisition.

In "Daily AI Snapshot: Adobe's AI Makes You a PDF Power User", Nat discusses how Adobe's new AI-driven features in Acrobat promise to revolutionize PDF document interaction and management, despite ethical and technical challenges.

Promotions

In "Dive into Adventure: D&D + LLMs", José J. Rodríguez introduces a project combining Dungeons & Dragons with Large Language Models for dynamic storytelling, character creation, and immersive text-based gameplay.

In "Lovelaice, an LLM-powered assistant for hackers without self-regard", Alejandro Piad Morffis presents a personal project of a chatbot that generates and executes code in the terminal, acknowledging its potential risks while emphasizing its educational value and real-world helpfulness.

In "PODCAST: The Ape That Understood the Universe", Steve Stewart-Williams discusses how understanding our "human design" and the differences between men and women can help us make better choices and build value-driven lives.

In "The Hitchhiker's Guide to Graphs - Update #1", Alejandro Piad Morffis announces the availability of the first draft of his book, provides a link for early access, and introduces different subscription options for supporters, including a Patron pass with potential benefits such as a free printed copy.

Tutorials

In "Recording: Live Session on Performance Optimization using 1BRC as a Case Study", Abhinav Upadhyay discusses various performance engineering topics, including system call costs, file reading methods, threading considerations, and data structure choices, with an emphasis on interactivity and Q&A.

In "It's Pointless! Or Isn't It? Python's Ellipsis Has Three ...", Stephen Gruppetta explains how the Ellipsis object in Python can serve as a placeholder in code where functionality will be added later.

In "How to Use Copilot's Notebook to Experiment with Prompt Design," Lance Cummings introduces Notebook, a new feature in Copilot that simplifies prompt design and iteration for Microsoft users in the classroom and workplace settings.

In "SQLCoder-2–7b: How to Reliably Query Data in Natural Language, on Consumer Hardware", Sjoerd Tiemensma explains how to use the SQLCoder-7b language model, LM Studio, and Streamlit to create a local, user-friendly interface for querying data using natural language on consumer hardware.

Cutoff date: 2024-02-26T05:01:29

And that’s all for today! Let us know your thoughts about this new format and any suggestions to make it more useful.

Leave a comment

In this issue, delve into a fascinating world where artificial intelligence (AI) and ancient civilizations intertwine. This issue explores OpenAI's groundbreaking text-to-video AI model, Sora, and its potential impact on various industries. Discover the intricacies of Rome's ancient sanitation system and Constantine's strategic shift of the empire's center.

Grapple with the limitations of AI in replicating human emotions and the importance of authentic communication. Ponder the implications of AI in education and labor market dynamics. Engage with thought-provoking concepts like steelmanning arguments and managing impulsive behavior.

Examine the physics behind everyday smartphone experiences, consider the potential consequences of anti-technology sentiment, and reflect on the significance of the Voyager 1 golden record.

Tell us if you find this content valuable and what else you want to see in this section.

NOTE: A majority of this content is AI-generated, so although a human editor has read and aproved all of it, inconsistencies and mistakes are still posible. Let us know if you see anything.

If you want to see how this is made, take a look at the source code.

Featured articles

The following are AI-generated summaries of randomly chosen articles writen by members of our community since last digest.

Dream Machines

Read article

Jurgen Gravesteen's article discusses OpenAI's new text-to-video model, Sora, which generates high-quality videos up to a minute long. The announcement created excitement, with Sora stealing the limelight from Google's Gemini 1.5 model. Despite its impressive capabilities, Sora shares flaws with language models and image generators. Gravesteen holds off on discussing industry impact, instead highlighting oddities in the Sora-generated videos, suggesting potential issues that warrant further investigation.

AI as a Catalyst for Innovation: An Interview with Dr. Elliot Bendoly

Read article

Nick Potkalitsky discusses the potential of generative AI in education and its risks to critical thinking. He shared his views on LinkedIn, prompting Dr. Elliot Bendoly to share a research paper supporting the thoughtful implementation of AI in classrooms. Potkalitsky advocates for a data-driven approach in AI adoption, and is excited about the emergence of research papers to guide educators. He acknowledges that many educators are pioneering AI integration in isolation, and hopes that comprehensive studies will help in this process.

Steelman

Read article

Michael Woudenberg, in his article on the website "Polymathic Being", discusses how to become a superhero by improving strength and agility, and avoiding conflicts. He introduces the concept of "Steelman", a type of thinker who spans diverse specialties and weaves together insights. Before getting to Steelman, he explains their archnemesis, "Strawman", a personality who misrepresents what you say and uses strawman arguments, an insidious informal fallacy of refuting an argument that is different from the one being discussed. Woudenberg uses the infamous interview between Jordan Peterson and Cathy Newman from the BBC as an example of Strawman.

What's In A Name?

Read article

Stephen Gruppetta explores the relationship between names and objects in Python, using the example of naming a string object "Stephen". He explains that names are not objects, but labels that refer to objects, comparing it to a box analogy where objects are placed in boxes labeled with names. Gruppetta then delves into reference counts, explaining how they work and how they relate to garbage collection in Python. He emphasizes that understanding these concepts can help programmers avoid common mistakes and improve their coding skills. The article serves as an introduction to the intricacies of Python's memory management and object system.

Setting fire to self-driving cars won't help build a better future

Read article

Andrew Maynard writes about his shock and anger at the torching of a driverless Waymo car in San Francisco, and the narratives that have emerged around the incident. He notes the growing sentiment against self-driving cars in the city, but cautions against oversimplifying the issue as a public backlash against new technology. Maynard argues that the incident should be seen as a complex issue, reflecting the challenges of integrating new technologies into society and addressing the concerns of different stakeholders. He emphasizes the need for responsible innovation and engagement with communities to build a better future.

From the Community

The following are AI-generated summaries of the remaining articles published since last digest. The categories were assigned by AI as well.

Essays

In "Doodoo Diligence", Andrew Smith recounts his visit to Rome with Alley, focusing on their fascination with the ancient Roman sanitation system, which is not commonly highlighted among Rome's achievements; he describes how Romans dealt with their waste, using the Cloaca Maxima sewer system, and their communal latrines, which were like stadiums with rows of urinals that caught both urine and feces.

In "From Constantine to Constantine", Andrew Smith discusses how the Roman Emperor Constantine shifted the political and economic center of the Roman Empire from Rome to Byzantium, now Istanbul, due to its strategic location, secure defenses, existing infrastructure, and to distinguish himself from Rome's origin story.

In "But Why?", Andrew Smith explores the physics behind everyday experiences with smartphones, discussing the science behind light, electric fields, wireless communication, and the seemingly solid yet mostly empty atomic structure of matter.

In "How AI can Impact Demand and Supply of Labour(Musings)", Edem Gold discusses the potential influence of artificial intelligence on labor market dynamics, highlighting the increased automation risk in occupations with high minority representation, and the negative impact of AI integration on perceived human expertise in labor demand aspects.

In "Let's stop saying that Data are the new oil", Valentino Zocca discusses the drawbacks of the popular analogy that compares data to oil, highlighting the differences in their utility and scarcity, emphasizing how data is dynamic, subject to rapid obsolescence, and not all data are equally valuable, while also touching upon issues of privacy, security, and bias in the expanding data landscape.

In "Gold Records", Andrew Smith discusses the Voyager 1 spacecraft and its golden record, which includes a collection of sounds, images, and music intended to represent life on Earth and to communicate with any extraterrestrial civilizations that might intercept the spacecraft.

In "How To Tame Your Impulsive Behaviour And Make Healthier Decisions", Zan Tafakari argues that traditional strategies for managing impulses, such as resistance and identity change, are not effective and can even increase suffering; instead, Tafakari suggests a solution focused on understanding and managing impulses.

News

In "Daily AI Snapshot: Meet Sora, a text-to-video AI model", Nat discusses OpenAI's new Sora, a text-to-video AI model that generates photorealistic videos, its capabilities and limitations, the advancement it represents in AI's growth, potential ethical concerns, and its competitive position in the emerging AI-generated media landscape.

In "Daily AI Snapshot: Tech Giants Unite Against AI Election Misuse", Nat discusses how twenty tech companies, including OpenAI, Meta, and Microsoft, have collaborated to create detection tools, run public awareness campaigns, and implement actions against deceptive AI-generated content that could interfere with elections globally.

In "Daily AI Snapshot: Breaking Up with Algorithms: Spot the Artificial Tears", Nat discusses the limitations of AI in replicating human emotional depth in writing, particularly in breakup texts, emphasizing the importance of authentic human communication in personal relationships and raising ethical questions about using AI in sensitive interpersonal matters.

Promotions

In "The Hitchhiker's Guide to Graphs", Alejandro Piad Morffis aims to fill the gap in current graph-related educational materials by providing a book that combines real-life applications, practical algorithms, and the underlying mathematical theory, catering to students, teachers, and professionals alike.

And that’s all for today! Let us know your thoughts about this new format and any suggestions to make it more useful.

Leave a comment

What follows are AI-generated summaries of most articles published in our community last week. Please beware that we are still testing this workflow, so although a human editor has reviewed all summaries, some inconsistencies might still exist with the actual content of the articles. If you spot any, please let us know.

Tell us if you find this kind of content valuable and what else you want to see in this section.

Featured articles

The following are four randomly selected articles from our community, featuring diverse authors and long-form content, and summarized with the help of artificial intelligence.

Make a Customer Service Bot

In "Make a Customer Service Bot", Alejandro Piad Morffis presents a tutorial for creating a chatbot to answer user queries using profile information and a general knowledge base. The article uses the example of a SaaS product with a FAQ guide, where a user's specific situation and plan details can be incorporated into the chatbot's responses. This AI-powered chatbot aims to provide tailored answers to users, reducing their need to search through the entire FAQ guide. The tutorial is somewhat advanced, requiring basic Python and Streamlit knowledge, but does not assume prior experience with language models or building chat-based apps. The source code is available on Github, and the author encourages supporting the effort put into creating these free coding lessons.

Running GNU on DOS with DJGPP

In "Running GNU on DOS with DJGPP", Julio Merino discusses his experience using DJGPP, a distribution of GNU development tools for DOS, before being exposed to Linux. He remembers DJGPP as a strange and bloated tool compared to Microsoft C Compiler and Turbo C++, but he appreciated its complete development environment and the ability to view its source code. Merino dives into the history of DJGPP, explaining how DJ Delorie ported GCC and other tools to DOS despite Richard Stallman's doubts about running a 32-bit compiler on a 16-bit operating system. The article highlights the contortions Delorie went through to make it work and how DJGPP remains an alien development environment for DOS and Windows users.

What A Word Is Worth

In "What A Word Is Worth", Josh Brake discusses a tweet from Sam Altman about OpenAI's 100 billion words generated, highlighting the story behind the numbers and the comparison. Brake raises questions about the alignment of AI-driven success with human flourishing, emphasizing the importance of efficiency in enhancing humanity rather than as an end in itself. He argues that science and technology cannot answer this question, suggesting that philosophical and religious pursuits of knowledge provide valuable perspectives. Brake remains skeptical about the true value of many AI-generated words, suspecting that a significant portion may not contribute to human flourishing as intended.

Neurons to Networks: Bridging Human Cognition and Artificial Intelligence, Part 2

In "Neurons to Networks: Bridging Human Cognition and Artificial Intelligence, Part 2", Nick Potkalitsky discusses the integration and implementation of AI in educational settings, focusing on the distinct structures of the brain and artificial intelligence. He aims to investigate how these unique mechanisms might influence the development of writing curricula that enable students to engage with new technologies effectively, ethically, sustainably, and productively.

From the Tech Writers Community

The following are all the remaining articles published by authors in our community in the last week. If you want to see your articles featured here, join us.

• In "Daily AI Snapshot: SEC Chair Warns Against AI Hype", Nat discusses SEC Chairman Gary Gensler's warning about misleading AI-related disclosures by publicly traded companies, which could violate US securities law and harm investors, while highlighting the growing concern over ethical AI use in business and the need for transparency to prevent fraud and protect consumer rights.

• In "Goodbye Chatbots, Hello AI Agents", Jurgen Gravestein discusses the evolution of conversational AI, highlighting how the emergence of AI agents, powered by generative AI and Language Learning Models (LLMs), surpass the limitations of old chatbots, offering more flexible, capable, and proactive assistants, thus marking a shift towards more exciting and practical applications for the future.

• In "Daily AI Snapshot: US AI Regulations: A Patchwork Emerges", Nat discusses how the growing number of AI-related laws in the US, with 14 out of 190 state bills passed in 2023, impact AI strategy, innovation, and compliance for enterprises and tech vendors, while shaping international AI policies and pushing companies to innovate responsibly within a legal framework.

• In "Living Dinosaurs", Andrew Smith discusses the reign of dinosaurs, their extinction 66 million years ago due to an asteroid impact, and the surprising fact that birds are actually descendants of dinosaurs, with the first clue coming from the discovery of the Archaeopteryx fossil in the 1860s.

• In "Daily AI Snapshot: The Double-Edged Sword of AI Companionship", Nat discusses the growing trend of AI companions as a response to rising loneliness, highlighting the benefits of emotional support while raising concerns about power imbalances, loss of authentic human connections, and moral decay, encouraging responsible use of AI to complement rather than replace genuine human interaction.

• In "Translate Everything with a Single Command", José J. Rodríguez shares a Python tool he created using the OpenAI API to translate his Spanish book on Cryptocurrencies and Blockchain into English, making it accessible to more people, and encourages others to use and customize the code on GitHub.

• In "Writer Highlight: Michał Poczwardowski", Alejandro Piad Morffis features Michał Poczwardowski, an engineering manager and author of the newsletter "Poczwardowski Notes", which shares different perspectives on various topics, including productivity, technical writing, book reviews, and personal experiences, appealing to a wide audience curious about learning and problem-solving.

• In "How AI can Impact Demand and Supply of Labour(Musings)", Edem Gold discusses the potential effects of AI on labor market equilibrium, highlighting the increased automation risk in occupations with high minority representation and the negative impact of AI on perceived human expertise in labor demand.

• In "Atomos", Andrew Smith discusses the history of atomic theory, beginning with the ancient Greek philosopher Democritus's concept of atomos, the indivisible building blocks of matter, and how it was largely forgotten until revived by John Dalton in the 19th century through his experimental and observational studies of gas behavior.

• In "Keeping Time", Andrew Smith discusses the historical evolution of timekeeping, starting from simple observations of the sun's position to the creation of sundials and water clocks, highlighting the significance of accuracy in time measurement and the inventions that improved it, such as Ctesibius' advanced water clock.

• In "But Why?", Andrew Smith explores the physics behind everyday experiences with smartphones, discussing the science behind the photoelectric effect, electric fields, polarized light, wireless communication, and the intriguing properties of atoms that allow us to hold and interact with these devices, despite their seemingly empty and distant components.

• In "Five ways to monetize your technical writing", Alejandro Piad Morffis explores various strategies for making money with technical writing skills beyond the subscription model, including subscriptions, pay-per-article, sponsorships, online courses, and consulting services.

• In "Daily AI Snapshot: Breaking Up with Algorithms: Spot the Artificial Tears", Nat discusses the limitations of AI in replicating human emotional depth, particularly in creative writing and personal relationships, emphasizing the importance of authentic human communication and ethical considerations in using AI for sensitive tasks.

• In "Alignment: Understanding the Multi-Billion Dollar Opportunity within Machine Learning", Logan Thorneloe discusses the importance of alignment in machine learning, which ensures AI systems achieve desired outcomes, align with human values, and are safe and reliable for users, covering the complexity of aligning models throughout the entire machine learning pipeline, and the significant financial incentive for solving this problem.

• In "Instagram limits political content, and Google's consumer play with Gemini", Viggy Balagopalakrishnan discusses Meta's decision to stop recommending political content on their platforms and Google's launch of the Gemini app, analyzing the impact, potential monetization, and competitive advantages of both moves.

• In "Using Lex AI to Enhance Human Writing", Lance Cummings explores how Lex.page, a specialized AI-driven writing environment, supports the creation of original, human-centric content by offering features such as intuitive interface, AI-enhanced writing capabilities, strategic writing methods, customization, personalized feedback, and practical usage tips.

And that’s all for today! Let us know your thoughts about this new format and any suggestions you have to make it more useful for you.

Leave a comment

If you are a technical writer, chances are you have marketable knowledge that many readers would happily pay for. While Substack provides one compelling strategy to monetize this knowledge –paid subscriptions–not all readers can or even want to subscribe to yet another service.

In this article, we'll explore different strategies for making money with your technical writing skills beyond the subscription model. First, we'll look at the most common monetization method that works well with Substack: paid subscriptions. Then, we'll discuss alternative strategies that may not be as easy to implement on the platform but can still be effective with some workarounds.

Strategy #1: Subscriptions

This is the fundamental monetization model on Substack. The idea is that readers pay a monthly or yearly subscription to access your content. This approach is appealing because it provides a steady income, and you know how many people you're writing for at all times. Plus, it's scalable – the same effort and quality of content can reach as many readers as you can attract.

However, one downside is that it can lead to burnout since you might feel pressured to produce content for your subscribers constantly. At the same time, many people are getting subscription fatigue, as the Internet all around us has become a giant subscription model. Plus, readers won’t necessarily care about everything you write. Yet, with a subscription, they commit to reading (or at least paying for) all your content.

Strategy #2: Pay-per-article

Instead of paid subscriptions, consider charging an access fee for individual articles. Readers can preview the beginning of the article and choose to unlock it for a small one-time fee, perhaps as low as $1.

Unfortunately, Substack doesn't currently support this feature, likely due to the small amount of money involved per user after deducting fees. Implementing this would require them to hold to your money and send payouts whenever you reach a significant sum, which complicates matters financially for them, so I don’t see them doing it anytime soon, unfortunately.

But don't worry; you can still implement this strategy using other platforms like Gumroad. To make this work with Gumroad or a similar service, you must create a product for each paid article. The content of the product is simply the secret drat link (that you can find in each article settings page). Then, in the actual article at Substack, just before the paywall, include a custom button linking to your corresponding product checkout page.

This way, you can still benefit from Substack's reach while utilizing alternative monetization methods that suit your needs better. This strategy lets you monetize at a finer level, attracting those who might not want a full subscription but would pay for a specific article. However, it does require managing multiple platforms since it's not integrated into Substack.

You can combine this with a traditional subscription model, allowing regular subscribers to receive everything while others can unlock individual articles. Make sure the total cost of paywalled articles is similar to or greater than a yearly subscription; otherwise, subscribing won't make sense.

Strategy #3: Lifetime subscription

The third strategy is offering a one-time payment for a lifetime subscription. For example, charge two or three times the yearly subscription cost for unlimited access to your content forever.

Many readers experience subscription fatigue and prefer paying a larger amount upfront instead of dealing with recurring payments. The downside is that it requires more money upfront from readers, but some may be willing to do this.

Why this makes sense? It depends on the lifetime value of your readers. Substack and other subscription services have a churn rate – a percentage of paid readers who don't renew their subscriptions. If you’ve been on Substack for long enough, you can calculate an average churn time, but it is usually around two to three years for technical publications.

So, if you charge upfront for lifetime access, you might earn the same or even more than you would from readers who only subscribe for one or two years anyway. For a two-year or three-year rate, you receive the total value of the subscriber upfront.

Substack doesn’t natively support this feature, so you’ll have to do manual work, i.e., comping the corresponding readers forever. Now, you can, of course, set this up with Gumroad, Patreon, or any other platform, but you can also use Substack alone by taking advantage of a less-known feature: the founder’s plan.

To do this in Substack, set up a founder's plan alongside your yearly plan. Make the founder's plan, e.g., three times the yearly rate, and clearly state in the description that it's a one-time payment for a lifetime subscription. Ensure this is clear in your about page, plan benefits, and settings.

When someone purchases the founder's plan, you'll receive an email. You'll need to manually give them a complimentary subscription forever by going to your subscriber's page. Although this requires manual work, it's not a huge burden since you won't receive many such emails daily.

And if you're getting dozens of lifetime subscriptions a day at more than $100 each, that's a great problem to have! You can even hire someone to handle this task.

Strategy #4: Sell digital products

Strategy number four involves monetizing something other than your articles. For example, if you write technical articles or tutorials for a programming language and you have written (or are writing) a technical book, you can use your articles as a free gateway to promote it. Include a link to your Amazon or LeanPub page under all your articles.

You can apply this strategy to finished products, like promoting a complete Python programming book alongside your technical tutorials. Alternatively, you can use it like a Kickstarter campaign. Ask readers to pay a small pre-order fee upfront and let them know they'll receive frequent updates and the full content when the book is completed.

For example, whenever I write a new chapter of my upcoming CS book, I send supporters an updated PDF and EPUB file. This method provides very-needed seed funding for a big project, such as writing a technical book. Again, you can use alternative platforms like Gumroad, Patreon, BuyMeACoffee, or simply provide your PayPal link.

Strategy #5: VIP access

Another way you can monetize your technical blog is by providing paid readers with exclusive access to a community. For example, you could say that all subscribers can read your articles, but paid subscribers can access a Discord server to ask questions, get feedback, and work through problems with your help. You can also use this community to host live workshops or other face-to-face events that offer additional value to paid readers.

This way, everyone can read your content, which helps you grow your reader base, but only paid subscribers receive this extra support from you through office hours or personalized assistance.

Similarly, you could offer additional content to these paid subscribers. For example, while the article may have text explanations and snippets, subscribers could get access to a private GitHub project with the actual source code they can run. This way, you can monetize extra content that's appealing to some readers without taking away the value of the free article for most of your audience.

Conclusions

Substack is a fantastic platform that provides valuable tools to make a business around your writing, if you choose to do so. However, the paid subscription business model is just one of many possibilities to monetize your hard-earned knowledge, time, and effort.

While Substack doesn’t natively support any alternative revenue model, you can, with some work, integrate other platforms –or even manage things fully manually– to accommodate other revenue models that may complement paid subscriptions or replace them altogether.

As Substack matures and grows, I expect its founders to realize there are many alternative models they could support natively. In the meantime, you can use some of the tricks in this article to make one of these models work for you.

Now is your time to share! Do you have any other tricks or ideas to monetize your technical writing?

Leave a comment

Subscribe now

First, tell us a bit about yourself. Who are you, what is your day job, what are your professional interests?

My name is Michał Poczwardowski. I used to work as an Engineering Manager in a software house from Poland. I was responsible for the whole employee life-cycle, and I led 5 different technical units: Ruby on Rails, Java, Cloud, Data Science, and Solution Architects. I have a Master’s Degree in Computer Science; I participated in Google Summer of Code twice and worked as a Senior Ruby Developer before jumping into a managerial role.

Our identities are fluid, and we should not stick to one of them too tightly. Professionally, I can be described as an engineer, an engineering manager, a technical person, a guy who likes computers, and an individual curious about the world who enjoys learning new things and solving problems.

Currently, I don’t have a day job; I’m having my gap year - I wrote an article about that:

Poczwardowski Notes

Filling the gaps in a gap year

In the summer of 2023 I was directly affected by the round of layoffs happening in the tech industry. When all the emotions calmed down I was happy to discover how time off was the gift I needed much more than I had realised. I had many questions from my friends about my decision not to look for a new job. Most of these questions were along the lines of…

Read more

2 years ago · 6 likes · Michał Poczwardowski

Now, tell us about . What is it about? What topics do you cover? Who is your intended audience?

I believe that one of the best things to help us make better decisions is to look through the lenses of different perspectives. I’m sharing different perspectives through my publication.

My notes do not yet have a fully shaped target audience, nor one leading theme. I write book reviews and share my thoughts.

I share my experiences from my engineering manager role like in this post:

Poczwardowski Notes

On Writing at Work

Writing (and then reading) is a transfer of thoughts from one brain to another. That is my definition anyway, a bit grandiose I admit. I do not know who to quote, but the statement “writing is thinking on paper” resonates with me deeply. So, I took it further, where we send our thoughts to others by writing them down…

Read more

2 years ago · 5 likes · Michał Poczwardowski

This post was featured in the SoftwareLeadWeekly newsletter.

How, when, and why did you begin writing about technical topics on the Internet?

I have decided to share my thoughts because creating public notes is a challenging transition from a single-player game to a multiplayer one, so now the content has to be compatible with more than just one brain.

My notes became public in November 2023 - by migrating my local Ghost instance into a Substack account.

What role does technical writing play in your job and life?

Writing shapes our thinking and putting thoughts into words helps us evaluate our understanding. I truly believe that writing is “thinking on paper”. Writing posts helps us to evaluate what we know, a valuable asset when it comes to technical topics.

How is your writing process? How do you organize your writing schedule? How much time does writing take you, on average?

I write about my current interests, or if I have nothing on my mind and inspiration is lacking, I write book reviews as a way to process what I read. Book reviews are how I started publishing and I still have quite a list of reviews to be written. I use a simple Google Doc for drafts, in one large file that I change annually. Sometimes, I take a small notebook and pen with me to write outdoors in a more traditional way.

In terms of time, I aim to write every day for at least 30 minutes. It is not always possible, but this is my priority. The key for me is consistency. We are in charge of how much we publish, so I set a goal of 52 articles in 2024, which means publishing once a week, but not necessarily every week. I am not a native English speaker, so I use the opportunity of writing to work on some of my texts with my English teacher.

What kind of advice could you give people considering or getting started with technical writing?

Sharing technical knowledge with others is the best way to learn something and evaluate your understanding. You will learn a lot, and as a side effect, you can help others.

The best advice is just to start, not overthink it, and not limit yourself to selected topics. Just write and publish when it is good enough.

Write about things that you would like to read about. Look for moments and topics when writing makes the time just pass by without noticing.

Any closing words you’d like to share with the readers of The Tech Writers Stack?

“Which would you rather be?

Someone who hasn’t created anything in years because you’re so busy consuming?

Or someone who hasn’t consumed anything in years because you’re so busy creating?” - How to live, by Derek Sivers:

Poczwardowski Notes

Book Review: "How to Live" by Derek Sivers 5/5

How to Live is an extraordinary book where each and every chapter shows us a different way of how life can be lived. Everything is presented in such a concise way that the book is little more than 115 pages. Each chapter describes one possible way of living, and all of these possible approaches are all-in, whereby we follow them to the letter. The author…

Read more

2 years ago · 6 likes · 2 comments · Michał Poczwardowski

Thanks for reading!

This was The Tech Writers Highlight, a section of the Tech Writers Stack where we recommend new and seasoned writers. Leave a comment or question for to learn more about their writing.

What is the right way to do Substack?

There is an ongoing debate over notes and posts in general, with what seems to be two camps at Substack debating the right way to approach writing on the platform. I call them the pragmatists and the purists —no offense intended with either label. Both sides have compelling reasons to claim their way is the right way.

So, I guess it’s my time to pick a side, right? Well, not exactly. I will share my thoughts on this debate, but keep in mind that my perspective is influenced by my own experiences and motivations, which may not apply to everyone. So here are my two very biased cents.

Pragmatists believe that success on Substack, defined by having many readers and making it profitable, requires giving readers what they want. This often involves choosing a niche, maintaining a consistent schedule, addressing readers' interests, and aligning with a specific mindset or echo chamber. To stand out in the competition, you must write well and create content people want to read. Essentially, this camp suggests optimizing your writing for your audience, treating it like a product designed for a target market.

This is the writing as a business side.

On the other hand, purists argue against this approach, claiming it leads to burnout and misery. They believe that writers should focus on what they truly want to write about and follow their own schedules. This might mean writing five essays in a week or one essay in a month. Eventually, if your writing is genuine and good, readers will come; more than readers, they will be friends.

This is the writing as a calling side.

I think the right way to do Substack is… anything in between. And yes, I know, this is the blandest opinion I could have. But hear me out. I think I have a point to make.

The two extremes, writing as a product and writing as an art, are both valid. The fake dilemma arises when you ask the wrong questions first. Instead of asking what to write about or how to write, start by asking why you're writing. That is, determine your motivations first: for income, curiosity, self-discovery, finding peace, or building a community. Once you know why you're writing, choosing topics, schedule, structure, and niche becomes much easier.

If you want to make a living from your writing and create a business, you must write about topics people will pay to read. In this case, your work may lean towards news digests, explainers, or something more product-oriented.

On the other hand, if your reasons for writing are more personal – connecting with yourself or a community, finding your voice, understanding your emotions, or satisfying your curiosity – then your writing will feel more personal and chaotic, connected to those pursuits.

Now, once you find a why and a what, how is more or less pretty straightforward, good writing advice works across all genres – be it fiction, news, essays, or a scientific paper. Your writing should be engaging and strong, reflect your values, and encourage the reader to ask difficult questions.

You should strive for good, clear, straightforward writing that doesn’t make the reader struggle to understand what you mean. This will always improve your writing, whatever your motivations or topics. Likewise, using personal stories, relating to the reader's experiences, and having a strong voice all contribute to engaging and compelling writing.

Some aspects of the "how" will depend on the "why." For instance, a consistent schedule and structure are more important if you're writing for money because you're creating a product. On the other hand, if you're writing for artistic or personal reasons, having a schedule or consistent structure is less crucial. Instead, it's essential that each piece feels unique and genuine. But most writing advice is general.

So there you go, there is no real dilemma. This discussion might seem like a dichotomy because people disagree on the "why." If you and I are writing for different reasons, it's natural that we'll write about different topics using different techniques.

And here's my strong claim of the day: all motivations for writing are equally valid. No one can tell you why you should write or what motivates you to become a writer. There are no stupid reasons to write.

Why are you writing on Substack? That's something only you can answer. No one else can judge your motivations, no one is on your shoes. Once you know your reason for writing, then we can talk about whether your actions align with those motivations and see if there’s something you could do better. But the why, that’s all on you.

So here is my question for you: why are you writing?

A previous version of this post was first published early last year. This is a revised and slightly extended version that came out of several insightful comments and discussions on the original post.

We’ve all been there. You wrote the perfect blog post for solving that painful problem elegantly. Your readers should be delighted; there’s everything they might want to know. And yet, hardly anyone reads the whole thing. If only they gave the article a chance, they would find out how incredibly useful it is, right? But you find it almost impossible to get readers interested long enough to discover it themselves. Sounds familiar?

I’ve struggled with this issue for years. I’ve written solid papers that reviewers didn’t grok. I’ve given insightful lectures that put listeners to sleep. I’ve pitched exciting business ideas that landed flat in the face of potential investors. I’ve tried every trick to hook the audience, and most don’t work. But I’ve found a remarkably simple strategy that does work.

Convincing your readers about the importance of some topic is the hardest part of technical writing. Doing the research, finding reputable sources, and actually writing and editing is devilishly complex. But it’s nothing compared to getting your readers to care. Ask any technical writer, and they will all tell you the same: it doesn’t matter how good your content is; most people won’t stay long enough to find out. They’ll give you the benefit of a couple of minutes, at most, and decide their time is better spent elsewhere.

Why is this so hard? You are dealing with the quintessential problem of communication: how to hook your audience so they’ll stick long enough to allow you to deliver on that hook? The problem starts with human psychology. You see, we have evolved to prioritize. Things potentially dangerous or that satisfy our basic instincts hijack your brain —that’s how social media keeps you hooked.

What happens is that you’re trying to sell the reader a solution to a problem they don’t care about. It doesn’t matter how elegant, effective, or simple the solution is. If your reader is not invested in the problem, you're preaching to the void. Thus, you must convince the reader that your problem matters to them first, and only then can you show them the answer. Start with Why.

Let’s break it down.

Start with Why

Engagement begins with the Why. Your aim here is to establish three points: the importance, complexity, and solvability of the problem.

Regarding importance, your job is to convince your reader that the problem is relevant and significant to them. You do this by highlighting all the negative consequences of not solving that problem. It could be framed as an undesirable world state your reader wishes to improve or a negative consequence of not taking action.

Then you tackle complexity. You should debunk common but ineffective solutions, showing why they fail to solve the problem, or at least how they fail to solve it in the way that matters in this case. This doesn’t need to be a detailed explanation, but at least show that you’ve done your homework and know the problem isn’t trivial.

Finally, you can introduce the critical insight that supports your solution as a better alternative. The trick is not to spill the beans just yet, but instead say something that hints at the solution, and, ideally, makes something click in the reader's mind. In this post, that insight is the idea that we have evolved to prioritize things we believe are essential.

Punch with What

Next comes the What, a concise statement. The purpose of this claim is to get stuck in your reader’s mind.

Keep it simple yet comprehensive for easy understanding. If they take away anything at all from you, it should be this. So make it easy to remember: use mnemonics and put it in big, bold, centered letters.

To understand your what, consider the following two questions: “what is this article about?”, and “what does it say about it?” Most writers think the answer to the first question is what should stick. But that first answer is often just a promise, a high-level prompt, not an actual answer. You want to incept the second answer in your reader’s mind.

Let’s see in this post:

— What is this article about?

— The best way to structure your content to make it engaging.

— Oh, and what does it say about it?

— That you should answer the Why, What, and How, in that order.

See? That final answer is the What —the thing you want the reader to answer when prompted in detail.

Deliver with How

Finally, you get into the nitty-gritty of How. This is where you’ll spill all the beans, and provide a thorough explanation of the actual solution. At this point, the reader should be invested in the problem, and happily surprised by the hint to the solution that is your What. Now is the time to deliver.

For highly complex solutions, start with a top-down approach. Begin with an outline at a high level of abstraction and then detail the steps to implement the ideas. The purpose is to avoid overwhelming the reader with too many details before they grok the big picture.

An alternative approach is to start explaining the separate components of the solution from the bottom up and then tie them together at the end. This approach is more effective when the overall solution cannot be easily reduced to its parts. With enough time to understand in detail each part, the reader can hopefully see the overall solution emerge naturally.

Whatever approach you pick, remember to make it didactic. The goal is to teach a new skill, so the language and pacing should match the reader's expertise level. If it's too easy, it will be dull and uninteresting; and if it's too challenging, the reader won't learn anything at all.

Finding the right balance

The time apportioned to each of these parts can vary, but as a general rule, you should spend a fair amount of time in the Why, say, no less than 30% of the whole content. The What aspect usually requires the least time since it's an overview that can be displayed through diagrams or short headlines. Then, the How can take up all the remaining space. The exact balance will depend on the type of content and audience you're writing about.

For instructional and educational material, for example, you'll likely spend around 20-30% of your time setting up the problem's context and causes, 10% outlining what the solution is at a high level, and then devote 60-70% on detailed instructions for the solution. This is the typical distribution for a tutorial-like post here in Substack.

In contrast, if you’re preparing something short —e.g., a product pitch with a limited time— focus mainly on the Why. Nearly all your content should explain why an issue needs resolution and convince the audience that this is the most critical problem in their lives (at least while you’re talking). Then, you can briefly introduce your service, product, or idea as the answer and provide simple usage instructions as the How.

These are the two extremes; anything else likely falls in the middle. College courses, for example, are often designed with a combination of lectures and practical classes (or laboratories). In this case, the lecture can cover the Why and What, leaving much room to ensure students get invested in the problem. Then, the practical part takes over the How.

Closing remarks

If you’ve been paying attention, you’ll notice that this article is organized in this fashion. I spent a fair amount of time trying to convince you that engagement is a vital issue that you want to solve, then I pitched a simple high-level solution to you, and finally, I spilled the details. If you’ve read this far, then I’ve succeeded. And now you know the secret: Start with Why.

After a long pause, we're restarting our Tech Writers Highlight series, and we want to feature you!

In this series so far we have interviewed nearly a dozen of the Tech Writers Stack community. It's a chance to show your work in front of nearly 1000 readers and let them discover your writing.

We feature both seasoned and new writers, so whether you have thousands of readers or you're just getting started, consider yourself officially invited.

How to participate

Below you will find a short template with some typical questions we ask all our featured authors.

Just reply to this post or directly email us at techwriters@substack.com and send us your answers.

These questions are just a guide, feel free to add, modify, or remove anything you feel makes your story more compelling.

We're waiting to hear from you!

Interview template

First, tell us a bit about yourself. Who are you, what is your day job, what are your professional interests?

[RESPONSE]

Now tell us about [your publication]. What is it about? What topics do you cover? Who is your intended audience?

[RESPONSE]

How, when, and why did you begin writing about technical topics on the Internet?

[RESPONSE]

What role does technical writing play in your job and life?

[RESPONSE]

How is your writing process? How do you organize your writing schedule? How much time does writing take you, on average?

[RESPONSE]

What kind of advice could you give people considering or getting started with technical writing?

[RESPONSE]

Any closing words you’d like to share with the readers of The Tech Writers Stack?

[RESPONSE]

If you want to get a shout-out, reply in this thread with a short, 200-ish-word summary of what you have achieved this year.

Some ideas about what you can share:

1. How many subscribers you’ve won

2. How many posts you’ve written

3. Your top-3 articles (by whatever metric you prefer)

Don’t forget to include a link to your substack.

And if you still haven’t, consider subscribing to join our community of technical writers, full of free resources and, most importantly, cool people willing to help you grow.

This week the question is the following: what ways are you using/considering to monetize your technical articles?

Please share all your thoughts, even things you haven't tried out but seen others do, etc. Ask questions and engage with the rest of the community.

You can also join the same conversation over at Discord if that's your thing.

Welcome to Wisdom Wednesday, our weekly challenge where you get to share a piece of advice, be it professional or personal, about anything you think can help the rest of the community.

Pick an topic and share article, note, thread, or any other written communication.

Or ask an interesting question and get the rest of the community to think with you.

Link back here your contributions, and make sure to check all others.

In this short post, I will highlight five hugely useful and reasonably easy-to-implement features for technical writers that would elevate Substack to the best online tool for our breed.

I will cover editing, organization, and monetization. Feel free to comment and add any suggestions you think would also be helpful for your writing workflows.

While I have zero leverage with Substack developers, I do hope this post gets in the eye of someone with the power to push for some of these changes. I think it would be a win-win.

#1 - Support for code syntax

This is a must for technical writers in the computer science and software engineering area. It is simply too cumbersome to share code today in Substack. Our best options are either the severely lacking native code block (which is just a monospace font) or embedding a GitHub Gist —or worse, an image.

On the other hand, this is so easy to implement that it is inconceivable that Substack still hasn’t solved it. There are dozens of fancy text editors with support for syntax highlight that could be included in Substack.

One argument I hear a lot is that Substack prioritizes the email experience, and email is very limited in what you can do with CSS. However, possible solutions involve either rendering an image version of the code, or falling back to a less fancy rendering on email with a generated link to the web version for those who want to see the code block in its full splendor.

#2 - Series with custom navigation

Many of us write a series of posts on a given topic. The usual way to organize them is to put something in the title (e.g., “Foundations of CS #1 - The actual title”) and/or to use a custom tag.

However, since there is no notion of an actual series, there is no built-in navigation. So, we have to manually add navigation links, which means we have to edit past posts to add forward navigation. The native navigation links work across your entire publication, so if you’re writing two series simultaneously, the links will get mangled.

An easy solution is for Substack to allow defining an arbitrary tag as a series, which would potentially add native back/forward navigation links among the series' articles. Also, one could optionally define that a given tag lists posts in increasing order (older to newer) instead of the default (newer first) when reading articles in chronological order makes sense.

#3 - Conditional sections

As a software engineer, one of the mantras I live for is DRY — Don’t Repeat Yourself. When writing a piece for non-, free, and paid subscribers, I have to consider how different readers will see my article and add pieces here and there that only make sense for some of them.

Conditional sections would allow us to mark some sections as free-only, paid-only, non-subscribed-only, etc. Right now, the only feature reasonable close is the paywall which basically divides the article into an intro that everyone sees and a full content that only paid subscribers see. However, there is no way to put something only for free subscribers, for example.

Ideally, I would want to make a section conditional on any of the filters they allow on the subscribers page. For example, I could make a section that only appears for first-time readers, or, on the contrary, for my 5-star readers.

#4 - Pay for single posts

This one is a bit harder because it probably messes with the business model that Substack consider optimal —the long term subscriber. While I do live my yearly subscribers, I also recognize that some readers won’t get a full subscription just to read one paywalled article that interests them.

The solution is, of course, to extend the payment mechanisms to allow us to charge for individual posts. Even better, give us a fully customizable tiered system where I can offer different things to different categories of subscribers, as complex as I want.

Right now, we only have three fixed tiers: free, paid, and founders. If I now want to offer, for example, a paid course, I have to either make it accessible to all paid subscribers or manage payment outside Substack. They are leaving a lot of money on the table for the lack of a more full-featured payment system.

5 - Global or category-based tags with search

I love tags, as they allow me to organize my articles in non-disjoint categories (as opposed to sections) and then link to the list of all relevant articles on a given topic by using a /t/ URL. However, unless you decide to put links to your tags, they are invisible to me as a reader. Furthermore, I’m sure several publications use similar tags (e.g., many of us have a programming tag or something similar).

What if, when adding a tag, Substack would suggest similar tags used around the community (category) I’m in so that later readers could find individual articles by tag on the Discover page?

Right now, for the most part, different substacks are different silos. Unless explicitly linked to them, navigating among similar publications or finding relevant articles related to what you just read is almost impossible. While going full automatic recommendation is something I understand they are cautious of —we’re all sick of the algorithms dictating what we consume— searchable tags can give writers and readers the power to find what they want transparently.

That’s it for today. These are just five relatively easy-to-implement features that I believe would elevate Substack to a different level altogether. As a software engineer, I understand that all features need to be balanced in terms of complexity versus the value they provide, but I truly believe these are absolutely worth it.

What do you think? Is there something obvious that Substack doesn’t provide and would make your writing so much easier?

We have a Discord Server now! Join us today to chat about technical writing, share your work, get feedback, and collaborate with others.

Join our Discord Server

Welcome to Wisdom Wednesday, a new weekly challenge where you get to share a piece of advice, be it professional or personal, about anything you think can help the rest of the community.

Pick an topic and share article, note, thread, or any other written communication.

Link back here your contributions, and make sure to check all others.