<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Adam Czegledi on Medium]]></title>
        <description><![CDATA[Stories by Adam Czegledi on Medium]]></description>
        <link>https://medium.com/@adamczegledi?source=rss-b67cd7adec0a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8prf9l9mGZRuSQ4H.</url>
            <title>Stories by Adam Czegledi on Medium</title>
            <link>https://medium.com/@adamczegledi?source=rss-b67cd7adec0a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:27:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adamczegledi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Learning SwiftUI: Day 2]]></title>
            <link>https://medium.com/learning-swiftui-100-days-of-swift/learning-swiftui-day-2-91feb8c53c4a?source=rss-b67cd7adec0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/91feb8c53c4a</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Adam Czegledi]]></dc:creator>
            <pubDate>Wed, 26 Mar 2025 14:55:26 GMT</pubDate>
            <atom:updated>2025-03-26T15:02:42.317Z</atom:updated>
            <content:encoded><![CDATA[<h4>Slow burn</h4><p>This is Day 2 of my quest to learn SwiftUI and become an iOS app developer (or at least a strong premise). To get the full picture of this challenge, check out <a href="https://medium.com/learning-swiftui-100-days-of-swift/learning-swift-day-0-1c0fcf3ac573">Day 0</a>. I’m following Paul Hudson’s <a href="https://www.hackingwithswift.com/100/swiftui">100 Days of SwiftUI course</a> and posting here for the purposes of note-taking and accountability.</p><p>Check out the previous day, <a href="https://medium.com/learning-swiftui-100-days-of-swift/learning-swiftui-day-1-628d523697f4">Day 1, here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NxHgZh8IKHz1PO1L" /><figcaption>Illustration generated by author with Sora</figcaption></figure><p>And came Day 2, which seemed a bit short in learning material, but I’m okay with that, because I have other things to tackle as well today (bit swamped with work lately).</p><p>So let’s review: Boolean is the remaining data type next to Strings, Int, and Double.</p><h4>Booleans</h4><p>A boolean value is either True or False. Very binary.</p><p>The NOT operator is !, so if let’s say:</p><pre>var thisStatementIs = true</pre><p>Then this:</p><pre>oppositeOpinion = !thisStatementIs<br>print(oppositeOpinion)<br><br>// Will print &quot;False&quot;</pre><p>Another apparently useful method for Booleans is that they are ‘toggleable’ (is this a word?) with a nifty method called <em>toggle():</em></p><pre>thisStatementIs.toggle()<br>// Which basically is the same as:<br>thisStatementIs = !thisStatementIs</pre><p>Though there are no arithmetic operators applicable to Booleans like for Int and Double types, there are logical operators that we can use:</p><h4>AND (&amp;&amp;) and OR (||)</h4><p>These evaluate two Boolean values. They use the so-called <strong>short-circuiting</strong> approach, which means that in the case of AND, if the first one is False, then the other one is not evaluated anymore, and its result is automatically False. Similarly, when applying OR, if the first one is True, then the other one will not be checked, and the result will automatically be True. So as a summary:</p><ul><li>a || b: If a is true, b is <strong>not evaluated</strong>.</li><li>a &amp;&amp; b: If a is false, b is <strong>not evaluated</strong>.</li></ul><h4>String Interpolation</h4><p>This method is very useful for concatenating (joining) strings or inserting values into texts as strings. We could use the classic “string1” + “string2” + “string3” + … way of adding strings together, but this is not an efficient way to do it. Use the <strong>string interpolation </strong>method instead:</p><pre>let string1 = &quot;Hello &quot;<br>let string2 = &quot;World&quot;<br>let string3 = &quot;!&quot;<br><br>// So instead of this:<br>var message = string1 + string2 + string3<br>print(message)<br>// Will print &quot;Hello World!&quot;<br><br>// Use this:<br>var message = &quot;\(string1)\(string2)\(string3)&quot;<br>print(message)<br>// Will also print &quot;Hello World!&quot;<br><br>// Or another example:<br>let name = &quot;Adam&quot;<br>let height = 180<br>var greeting = &quot;Hello, my name is \(name), and I&#39;m \(height)cm tall!&quot;<br>print(greeting)<br>// Will print &quot;Hello, my name is Adam, and I&#39;m 180cm tall!&quot;</pre><p>One important thing about string interpolation, as opposed to classic concatenation, is that <strong>you don’t need to worry about converting Int and Double types to Strings; Swift will do it for you.</strong></p><p>As a checkpoint for getting to know simple data types and learning to use them, a small exercise was due: Create a Celsius to Fahrenheit converter. Does not sound very difficult, so let’s see:</p><pre>//Your goal is to write a Swift playground that:<br>//<br>//Creates a constant holding any temperature in Celsius.<br>//Converts it to Fahrenheit by multiplying by 9, dividing by 5, then adding 32.<br>//Prints the result for the user, showing both the Celsius and Fahrenheit values.<br><br>let celsius = 23<br>var fahr = celsius*9/5+32<br>var message = &quot;\(celsius)C° equals \(fahr) degrees in Fahrenheit.&quot;<br>print(message)<br>// prints &quot;23C° equals 73 degrees in Fahrenheit.&quot;</pre><p>That’s it, folks. I hope we will get crazy on Day 3…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91feb8c53c4a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learning-swiftui-100-days-of-swift/learning-swiftui-day-2-91feb8c53c4a">Learning SwiftUI: Day 2</a> was originally published in <a href="https://medium.com/learning-swiftui-100-days-of-swift">Learning SwiftUI: 100 Days of Swift</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning SwiftUI: Day 1]]></title>
            <link>https://medium.com/learning-swiftui-100-days-of-swift/learning-swiftui-day-1-628d523697f4?source=rss-b67cd7adec0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/628d523697f4</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[programming-languages]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Adam Czegledi]]></dc:creator>
            <pubDate>Mon, 24 Mar 2025 08:32:52 GMT</pubDate>
            <atom:updated>2025-03-26T15:03:11.102Z</atom:updated>
            <content:encoded><![CDATA[<h4>Variables, constants, strings &amp; numbers</h4><p>This is Day 1 of my quest to learn SwiftUI and become an iOS app developer (or at least a strong premise). To get the full picture of this challenge, check out <a href="https://medium.com/learning-swiftui-100-days-of-swift/learning-swift-day-0-1c0fcf3ac573">Day 0</a>. I’m following Paul Hudson’s <a href="https://www.hackingwithswift.com/100/swiftui">100 Days of SwiftUI course</a> and posting here for the purposes of note-taking and accountability.</p><p>I knew the first few days would feel slow because learning about variables would be very similar to learning other languages I’m familiar with, like C# or Python. So, I decided to stay patient and trust the process.</p><p>Once I finish with the fundamentals, which are the basis of any programming language, it will speed up and become more exciting. For now, let’s just enjoy how easy it feels…</p><h4>Opening Playground</h4><p>The first thing was to open Playground within XCode, which is a good way to practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eCwTBR72xfT6nqArZVdUyA.png" /><figcaption>XCode: File &gt; New &gt; Playground — then choose macOS</figcaption></figure><p>Then this is what you see:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*uUjqnbN3AdRWw1Nb4sL6IA.png" /></figure><p>We learned about variables and variable types.</p><h4>Variables</h4><p>So far, Swift seems more like C# than Python, which I expected. Variable declaration has two main types: <em>var</em> and <em>let:</em></p><pre>var x = &quot;First&quot;<br>let y = &quot;Second&quot;</pre><p><strong><em>Var</em></strong> is used to declare any <strong>variable</strong> by <em>type inference</em>. It means that the interpreter will determine the type by looking at the value without the user explicitly defining the type.</p><p>Although, Swift has a way of explicit declaration as well:</p><pre>var x: Int = 5<br>// instead of:<br>var x = 5</pre><p><em>Let</em> is used to declare <strong>constants</strong>. These values are <em>immutable</em>, meaning they cannot be changed.</p><h4>Naming convention</h4><p>Variable names are case sensitive, and similarly to what is used in C#, the convention to name variables is <em>camelCase</em>.</p><h4>Strings</h4><p>There&#39;s not much to discuss here; it&#39;s the same as in other languages: strings are texts. Some basic functions and properties have been discussed:</p><pre>let movie = &quot;Star Wars&quot;<br>print(movie.hasPrefix(&quot;Stars&quot;))<br>print(movie.hasSuffix(&quot;Wars&quot;))<br>// false<br>// true<br><br>var actor = &quot;Bruce Willis&quot;<br>// Number of characters in &#39;actor&#39;:<br>var length = actor.count<br><br>let message = &quot;&quot;&quot;<br>This is a multi-line<br>string in Swift.<br>&quot;&quot;&quot;</pre><p>There are so called escape characters as well, like in many other languages:</p><pre>\n - New line<br>\t - Tab<br>\\ - Backslash<br>\&quot; - Double quote<br>\&#39; - Single quote</pre><h4><strong>Numbers</strong></h4><p>We have <em>doubles</em> or ‘double precision’ <em>floating point </em>numbers and <em>integers</em> (whole numbers). I understand there are others, but these are the main, mostly used number types. What was new to me was that it is allowed to use underscore (_) in numbers to interpret a longer number more easily. For example:</p><pre>let longNumber = 100_000_000_000</pre><h4>Type conversions</h4><p>Swift does not allow operations between different types (i.e. Int and double). To be able to do that, you need to convert the variables:</p><pre>let x = 3.99<br>let y = Int(x)   // y = 3<br><br>let a = 5<br>let b = Double(a)  // b = 5.0</pre><p>Good to know the basics. <a href="https://medium.com/learning-swiftui-100-days-of-swift/learning-swiftui-day-2-91feb8c53c4a">Next, come the booleans</a>. Can’t wait.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=628d523697f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learning-swiftui-100-days-of-swift/learning-swiftui-day-1-628d523697f4">Learning SwiftUI: Day 1</a> was originally published in <a href="https://medium.com/learning-swiftui-100-days-of-swift">Learning SwiftUI: 100 Days of Swift</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning SwiftUI: Day 0]]></title>
            <link>https://medium.com/learning-swiftui-100-days-of-swift/learning-swift-day-0-1c0fcf3ac573?source=rss-b67cd7adec0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c0fcf3ac573</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Adam Czegledi]]></dc:creator>
            <pubDate>Sat, 22 Mar 2025 12:45:02 GMT</pubDate>
            <atom:updated>2025-03-24T09:35:53.723Z</atom:updated>
            <content:encoded><![CDATA[<h3>The humble beginnings</h3><p>This is going to be interesting. Because I’m notorious for starting projects and not finishing them, this will be another challenge, but I’m optimistic.</p><p>So… I recently got a new MacBook, and one of the reasons I bought it was that I finally really want to start learning to develop apps for iOS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-qkCRBJiZhdAVlPb" /><figcaption>Photo by <a href="https://unsplash.com/@rendermouse?utm_source=medium&amp;utm_medium=referral">Andy Makely</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It’s been on my plate forever. About 10 years ago, I bought a Mac Mini because I did not want to invest in a more expensive computer just to learn app development for the iPhone, but that attempt quickly died out. You know, life and stuff… I guess it was not a priority enough. By the way, I do not possess that Mac Mini anymore.</p><p>Anyway. I’m at a different stage in my life now, but as a side project, I still have this urge to be able to build an application from an idea. I mean, when I have it. I mean the idea. And yes, I already have some. But we’ll cross that bridge when I even get to that bridge or even have a bridge to cross. I refer to the knowledge of how to build an app. That’s the bridge. Yeah, you got it.</p><p>I do have some programming experience, mostly with C# and Python. I like using these tools when automating something or building proprietary, simple PC apps. Structural engineers use Windows machines, not Macs, which is another reason why I haven’t started it over for a long time.</p><p>Here we are. I have a Mac now, which was a requirement, so let’s start this.</p><h4>First steps</h4><p>The very first thing I did was ask ChatGPT how I should start. The answer was:</p><blockquote>1. Download and install XCode, Apple’s integrated development environment (IDE).</blockquote><blockquote>2. Learn Swift.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1tVZeSIVmUSbTxzL.jpg" /></figure><p>Okaay. Next question: what resources should I start with?</p><p>One of the materials it recommended besides Apple’s official resources (i.e. <a href="https://www.apple.com/swift/playgrounds/">Swift Playground</a>) was the <a href="https://www.hackingwithswift.com/100/swiftui">100 Days of SwiftUI</a> video series by Paul Hudson, creator of the website <a href="https://www.hackingwithswift.com/">Hacking with Swift</a>. The 100-day challenge sounded intriguing, so I decided to jump right into it. What could go wrong?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hLtnkY28z-X8HxH4i09T3Q.png" /></figure><p>In the introductory to the course, Paul sets two rules:</p><blockquote>1. Every day you spend one hour reading or watching SwiftUI tutorials, or writing SwiftUI code.</blockquote><blockquote>2. Every day you post about your progress to the social media site of your choosing. Tell people!</blockquote><p>So, I decided to post about my progress here. I suspect this would also give me a sort of need for accountability. You are welcome to follow along and comment on my progress so I can learn better.</p><p>Of course, I am planning on looking into other resources as well. My daily progress here will conclude everything I learned that day. I reckon some of my daily posts will be shorter than others, but I will try to learn something new every day. Hopefully, one hour per day will be achievable.</p><p>I was a bit worried about the relevancy of the course since the videos were from several years ago, but under the introductory video on YouTube, Paul responded to someone who had the same thought, just a couple of months ago:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hAKO6Bh7f69eQEUm0NUqvw.png" /></figure><p>Right. I guess that’s my cue. Let’s start; t<a href="https://www.hackingwithswift.com/100/swiftui/0">oday is Day 0.</a></p><h4>Day 0</h4><p>What have I learnt today after watching Paul’s Day 0 video?</p><p>There is a list of so-called ‘core skills’ and ‘extension skills’ that he thinks a Swift iOS developer should possess:</p><p><strong>Core skills</strong>: obviously, the most important core skills are knowing Swift and SwiftUI. Others are working with data, networking (i.e., fetching data, not finding coding buddies), and version control.</p><p><strong>Extension skills</strong> are helpful but not required for Swift development. One such skill is knowledge of UIKit, which is an older framework by Apple that’s been around since 2008. According to Paul, it is not recommended for complete beginners to learn it, especially because it has a steeper learning curve and is not built for Swift (unlike SwiftUI), so there are some problems that can arise. Also, according to Paul, it’s not future-proof, although it&#39;s still relevant for solving complex UI requirements, as SwiftUI has some limitations in that regard.</p><p>I learned about the common mistakes by beginners, which I’m going to try not to make, such as:</p><p><strong>Memorizing everything</strong> — thanks, Paul, but I did not plan to do it. Can you memorize code, anyway…? Who does that? I agree with Paul that understanding the principle first, then knowing where to look, is more important if you don’t remember something. This applies to almost everything. Also, if you get your hands dirty and start writing code, the often-used bits will burn into your brain eventually, and you will remember them anyway. Forgetting, revisiting and then relearning something helps solidify memory and new skills at the beginning.</p><p><strong>Shiny object syndrome</strong> — this is more relevant to me, as I was planning to look at other resources in the meantime, like Codecademy, for which I do have a subscription, but let’s see how this one goes first. Paul mentioned many resources anyway, free ones. He highlights that you should not be mesmerized by a nice-looking new course because it costs many and/or is expensive. Nothing guarantees that it will be better for you or that it’s good at all. There are plenty of free and great resources which you can rely on, stick to that one, and once you have the basics and understand more about it, you can look elsewhere if you really want to. I’ll try to keep this in mind.</p><p><strong>Don’t be a lone wolf. Ask questions</strong>. — Well, in the era of AI assistants, it’s very difficult to stick with asking people if you are stuck. It’s probably easier to ask ChatGPT, Claude, or whichever your go-to AI buddy is than to ask a question in a forum. I understand, though, that the community is great. It would be interesting to see how much that dynamic has changed since AI assistants became publicly available to help with coding. I understand StackOverflow definitely has been suffering because of them.</p><p>Anyway, there are numerous free resources and learning materials made by fantastic people, which you can easily find by searching. Start there.</p><h4>XCode installation</h4><p>The logical next step after watching Paul’s video, was to download XCode from the AppStore and install it with macOS and iOS components:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ev8GrtCCt6IntdwOPR_z8A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hte6v_JOquCZUyGPkYscyQ.png" /></figure><p>Ready for some action, but let’s finish here now. To be continued <a href="https://medium.com/learning-swiftui-100-days-of-swift/learning-swiftui-day-1-628d523697f4">tomorrow.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c0fcf3ac573" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learning-swiftui-100-days-of-swift/learning-swift-day-0-1c0fcf3ac573">Learning SwiftUI: Day 0</a> was originally published in <a href="https://medium.com/learning-swiftui-100-days-of-swift">Learning SwiftUI: 100 Days of Swift</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can AI Replace Creators? — A Personal Perspective]]></title>
            <link>https://medium.com/@adamczegledi/can-ai-replace-creators-a-personal-perspective-952217056a6e?source=rss-b67cd7adec0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/952217056a6e</guid>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[art]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Adam Czegledi]]></dc:creator>
            <pubDate>Wed, 11 Dec 2024 20:52:30 GMT</pubDate>
            <atom:updated>2024-12-11T20:52:30.724Z</atom:updated>
            <content:encoded><![CDATA[<h2>Can AI Replace Creators? — A Personal Perspective</h2><h4>Since the emergence of publicly available AI tools, numerous social media posts and articles have discussed the dangers of AI taking jobs and making people of certain occupations redundant. Some areas mentioned are writing, filmmaking, and art in general. I don’t think it’s a real threat. Yet.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z9Uv5P1K7gYQj6pJ.png" /><figcaption><em>Source: ChatGPT</em>, OpenAI (2024)</figcaption></figure><h4>Fear of AI</h4><p>When it comes to filmmaking, you might have heard of Justine Bateman. I’ve followed her on Instagram for a while now. She is an American filmmaker and writer — and, by the way, the sister of actor Jason Bateman. I didn’t know much about her before, but sometime last year, I came across one of her Instagram posts. I don’t remember the exact post, but it was probably insightful or interesting enough for me to start following her.</p><p>Since then, her Instagram feed has transformed into an annoying series of warnings about the dangers of AI replacing human filmmakers and actors. She seems genuinely afraid that this will happen. I disagree.</p><p>Now, I’m not a filmmaker of any kind. I don’t have the insights to know which areas of filmmaking are truly on the verge of being replaced by AI. However, I love movies and cinema. While I can’t speak for filmmakers, as part of their audience I do have my own perspective on art imitations generated by AI tools.</p><h4>Creation vs. Generation</h4><p>Here’s what I think about AI-generated products labeled as “art”:</p><p><strong>We can call something “art” only if it’s created by humans — or at least heavily influenced by human creativity — and reflects the creator’s thoughts and perspectives.</strong> The keyword here is <em>creation</em>.</p><p>The term “Generative AI” contains the word ‘generation.’ <strong>Generation is not creation.</strong> It is not inherently creative, and becomes boring in the long term.</p><h4>Boring?</h4><p>Yes it’s subjective, but for me, something becomes boring when it doesn’t stimulate me — when it doesn’t make me think or question anything. When it doesn’t entertain, and when it doesn’t add to or improve who I am in any way.</p><p>Generation, as a process, builds outputs based on statistics. It is a computer code using statistical algorithms to produce the most probable and satisfying results based on its training data. It’s not creative; it’s calculated.</p><h4>Human-Created Art Matters</h4><p>AI is an amazing tool with possibilities we cannot even imagine. Yes, it can generate impressive, art-like products. But it is trained on data created by humans. Books, paintings, movies, music — we consume these because they evoke emotions and<em> make us feel something</em>. <strong>That emotional connection comes from the human experiences and emotions infused into these works.</strong></p><p>They make us feel something because the people who made these things most probably felt the same or similar to what they invoke in their audience. They tell a story. A story in which its inspiration originates from human experience of a certain lifetime. That can never be fully replaced by an algorithm.</p><p>An AI — at least with today’s technology — will not be able to tell a story from its own point of view because it has never lived through that story. It can imitate and simulate something similar, but it can never be inspired by a feeling or an experience. It can only recycle and reuse what has already been told.</p><h4>Humans need human influence</h4><p>I will never enjoy a movie or a book made entirely by an AI as much as one created by humans. Humans inject their creations with soul — a quality that arises from the complexity of our minds and emotions, which we still don’t fully understand.</p><p>Movies with AI-generated characters instead of real actors? I wouldn’t be interested in those. Why? Because I’m fascinated by other people. I’m drawn to their emotions and their extraordinary ability to channel anger, joy, or their very essence into a character.</p><p>AI-generated characters will never appear on stage, attend fan conventions, or shake your hands. It will never happen, at least not in our lifetime. (But then we’re talking about self-conscious humanoid AI robots, which leads to a completely different series of problems and dilemmas.)</p><p>The same applies to writing. AI doesn’t have its own style; it merely mimics and statistically imitates the styles of human writers. AI will never write a story inspired by real-life events or connect emotionally with an audience, without genuine experience.</p><h4>AI’s Role in the Process of Human Creation</h4><p>In the long term, AI will undoubtedly be used to create countless things — movies, books, and more — based on prompts from humans — already is. But when its generative capabilities are used to replace human creativity entirely, the value of these products will always be lower than those created by humans. That is unless the content’s purpose is purely informational — like safety instruction videos (in which case, I really don’t care who or what makes them as long as the information is clear). Or, of course, the parts where AI is used for the more laborious, procedural tasks by implementing automation easily.</p><p>To Justine Bateman and others advocating for the outright banning of AI in creative fields: <strong>you’re beating a dead horse.</strong> Your audience will not replace you if your creativity makes them feel special. Because that is real influence, that’s what we long for. AI is here to stay, and you might not know this yet, but eventually, you will also learn how to integrate it effectively into your own life. Instead of resisting it, channel that energy into learning how to live with it. Explore how AI can enhance creativity by streamlining the less imaginative parts of the creative process.</p><h4>Humanity in Creativity Will Always Be Essential</h4><p>We humans will always need the ‘human touch’. We thrive on real feedback and authentic connections. Even if AI-generated content seems exciting and jaw-dropping at first, it will eventually become clear that <strong>if it lacks humanity, it feels empty</strong>. It lacks what makes us <em>us</em>.</p><h4>Final thoughts</h4><p>I’ll end with a quote from Ben Affleck, who was asked during the CNBC Delivering Alpha investor summit in November 2024 whether AI could replace filmmakers. His response begins like this:</p><blockquote>“A: That’s not possible now. B: Will it be possible in the future? Highly unlikely. C: Movies will be one of the last things — if everything gets replaced — to be replaced by AI. AI can write you excellent imitative verse that sounds ‘Elizabethan’. It cannot write you Shakespeare. The function of having two actors, or three, or four actors in a room, and the taste to discern and construct that, is something that currently entirely eludes AI’s capabilities — and I think it will for a meaningful period of time.</blockquote><blockquote>What AI is gonna do is disintermediate the more laborious, less creative, and (…) more costly aspects of filmmaking. That will allow costs to be brought down, lower the barrier to entry, and enable more voices to be heard. It will make it easier for people who want to make ‘<em>Good Will Hunting’s </em>to go out and make it.”</blockquote><p><a href="https://www.youtube.com/watch?v=ypURoMU3P3U">His full response</a> is a gem, and I encourage you to watch it. I think his remarks are educational and spot on.</p><h4>What Do You Think?</h4><p>That’s my current perspective on AI and creativity. Now, I’d love to hear yours.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=952217056a6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Pursuit of Perfection: Lessons from the Myth of a Perfect Email]]></title>
            <link>https://medium.com/@adamczegledi/the-pursuit-of-perfection-lessons-from-the-myth-of-a-perfect-email-7067a1392143?source=rss-b67cd7adec0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7067a1392143</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[email]]></category>
            <category><![CDATA[perfectionism]]></category>
            <category><![CDATA[email-productivity]]></category>
            <dc:creator><![CDATA[Adam Czegledi]]></dc:creator>
            <pubDate>Tue, 03 Dec 2024 16:30:14 GMT</pubDate>
            <atom:updated>2024-12-05T06:04:21.622Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Write the Perfect Email: From Myth to Mastery</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/527/1*5qkX0181y3cqYb38rI9XOQ.png" /><figcaption>Illustration by author</figcaption></figure><p>You hover your mouse over the ‘Send’ button, pausing for one final review: <strong>greeting, content, signature — check</strong>. A last careful scan for grammatical errors and typos. “How about the <strong>tone</strong>? Not too pushy? Not too passive? Professional enough, but not overly formal? Friendly, but not too desperate?” You look at the clock. You’ve been at this for an hour now. Sheesh. With one last tweak, you finally hit ‘<strong>Send</strong>’. Feeling a wave of relief — until a second later, the panic hits: <strong>you made a mistake</strong>. You frantically check the ‘Sent’ folder, but it’s too late: the email is gone, and there isn’t a <strong>damn</strong> thing you can do about it. Sound familiar?</p><p>If you‘ve ever felt like you spend way too much time writing emails to avoid mistakes and ensure everything is perfect, you’re not alone. This short discussion dives into why writing and sending emails can feel so unproductive and stressful for many of us, and offers some practical advice to help you write more effectively and with less anxiety.</p><h4>The Paradox of Brevity</h4><p>To me this is usually the hardest part when writing an email.</p><p>There is a widely known quote that exists in several versions, <a href="https://quoteinvestigator.com/2012/04/28/shorter-letter/">attributed to various famous people</a> from the course of history, with its essence as follows:</p><blockquote>“I apologise for such a long letter — I didn’t have time to write a short one.”</blockquote><p>It highlights the difficulty of achieving <strong>brevity</strong> in communication. Creating a concise message often takes more time and effort than writing a longer one. This highlights the fact that achieving brevity can be more demanding than being verbose.</p><h4>Perfectionists vs. Pragmatists</h4><p>Some people are <strong>perfectionists</strong> when it comes to emails. They agonise over every word, worry about tone, and double-check for typos until the cows come home. Others are <strong>pragmatists</strong>: they aim for “good enough,” hit ‘Send,’ and move on with their lives.</p><p>If you’re a perfectionist, you probably think every email reflects your competence and professionalism. While that’s partly true, striving for perfection often leads to overthinking, stress, and wasted time. Pragmatists, on the other hand, focus on getting their message across effectively without sweating the small stuff.</p><p>So, how can you become a pragmatist?</p><h4>The Perfect Email</h4><p>Before answering this, let’s establish what perfection even means when it comes to emails. Since “perfect” in communication is quite subjective, here is a checklist of features that I believe are required to write a close-to-perfect email:</p><ol><li><strong>Descriptive subject line</strong>: clearly summarises the content while piques the recipient’s interest</li><li><strong>Concise content</strong>: avoids unnecessary details.</li><li><strong>Explicit content: </strong>unambiguous message focusing on the subject.</li><li><strong>Complete information</strong>: contains all necessary details the sender wants to convey to the recipient.</li><li><strong>Appropriate formality: </strong>matches the recipient’s context (i.e. greeting, tone, closing and signature).</li><li><strong>Error-free</strong>: free of grammatical and typographical mistakes.</li><li><strong>Well-formatted</strong>: easy to read and matches the recipient’s context.</li></ol><p>The order of the above list also reflects a hierarchy of importance, starting with the most impactful item regarding the recipient’s engagement, followed by those that support comprehension and professionalism.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e_lxwwRCtN-dA-7NbUbaJg.png" /><figcaption>Image by author</figcaption></figure><h4>The Perfection Trap</h4><p>So, how can you apply all these core qualities without overthinking the process?</p><p>The answer is simple, but you may not like it:</p><ol><li><strong>Practice.</strong></li><li><strong>Good enough should be good enough.</strong></li></ol><p>Yes, that’s right. I’m sure you have already suspected: there is no such thing as the perfect email — or<strong> perfect anything, for that matter — </strong>unless you can clearly measure it with a score. You can aim for perfection to maximise results, but remember: <em>the further you push beyond the ‘good enough’ threshold, the more effort it takes for progressively smaller returns</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0WbQk99ylc_07uvKrtbppw.png" /><figcaption>The principle of diminishing returns in the effort vs. quality relationship (illustration by author)</figcaption></figure><p>The schematic graph above demonstrates this concept. It’s a reminder that perfection might not always be worth the cost, especially when “good enough” already gets the job done.</p><p><strong>The key to effectiveness is to recognise when something is good enough and pursue further improvements only <em>if</em> <em>time and resources allow.</em></strong></p><h4>Still Hesitating?</h4><p>You finished writing an important email but are still anxious about sending it out. Why is that? <strong>Because you don’t want to lose control</strong>. Once you hit ‘Send’, it’s out of your hand. You can’t change it anymore. Even if you realise later you made a big mistake, it is what’s going to be delivered to the recipient.</p><p>So, let’s go over what can cause this anxiety and procrastination:</p><ol><li><strong>Fear of miscommunication: </strong>worrying about being misunderstood.</li><li><strong>Fear of negative feedback: </strong>concern about leaving a bad impression.</li><li><strong>Fear of mistakes: </strong>anxiety over typos or missing information</li><li><strong>Forced decision-making</strong>: pressure to respond quickly</li></ol><p>The main reason behind these fears is that <strong>emails lack non-verbal cues</strong>. It is the same reason why you will more likely get into a fight with someone over text messages than face-to-face. It’s much easier to misinterpret a written text without context provided by tone, facial expressions or gestures. That’s why it is essential to communicate clearly and precisely.</p><p>Considering digital communication’s fast-paced nature, you might also feel pressured to respond quickly, whether this pressure is real or perceived.</p><h4>Defeating Email Anxiety</h4><p>To overcome these fears and become more efficient in emailing, apply the previously detailed <strong>checklist to build a </strong>checking process, that can become your routine.</p><p>Additionally, consider the following useful tips:</p><ul><li>Before writing: <em>create a list</em> to gather all the information you want to include. <em>Prioritising </em>the items can also help with the structure of the email.</li><li>Set a <em>time limit</em>.</li><li>Use <em>templates</em>.</li><li>Seek <em>feedback </em>from colleagues, friends, or family members.</li><li>Use in-built <em>proofreading tools </em>or third-party <em>writing assistants.</em></li><li><em>Consider the recipient’s perspective</em>: before sending the email, review it as if you were the recipient to help spot inconsistencies and mistakes.</li><li><strong><em>And a bonus trick: </em></strong><em>Only add the recipients’ email addresses once you’ve finished your email</em>. This will help avoid accidentally sending an email that is not yet ready.</li></ul><p>Of course, you are free to tweak the above steps depending on the importance of your email</p><h4>Final Thoughts</h4><p>Perfection is a moving target — often subjective and rarely necessary. If it exists at all. Practice recognising when “good enough” is truly enough.</p><p>It’s also important to remember that emails are just tools for communication, not reflections of your worth or competence. Build a solid routine, practice writing, and aim for a pragmatic approach. Strive for your best, but don’t let the myth of perfection debilitate your progression.</p><p>Understand what chasing perfection can cost in the long term for you. Not only in email writing but also in general. Emails are a tiny bit of our life, but they are a good example of understanding the concept of “finishing something”. <strong>It’s never going to be perfect, but at one point it needs to be good enough. </strong><em>And that’s when it’s ready.</em></p><p>‌</p><p>‌</p><p>‌</p><p>‌</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7067a1392143" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mission Possible: a Subscription Website from Scratch]]></title>
            <link>https://medium.com/zero-to-web-application/mission-possible-a-subscription-website-from-scratch-ed8da33b441d?source=rss-b67cd7adec0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed8da33b441d</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-app-development]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[challenge]]></category>
            <category><![CDATA[website-development]]></category>
            <dc:creator><![CDATA[Adam Czegledi]]></dc:creator>
            <pubDate>Sat, 21 Jan 2023 21:32:28 GMT</pubDate>
            <atom:updated>2023-01-21T21:32:28.208Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mission Possible: Building a Subscription Website from Scratch — Introduction</h3><h3>I had this idea..</h3><p>… of building a website. From scratch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HNMLEqKJmLF4Gb8iUfHcQQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@emilep?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Emile Perron</a> on <a href="https://unsplash.com/backgrounds/apps/website?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’m not a software engineer, I’m not a computer scientist, and I’m definitely not familiar with how to build websites <strong>without using any content management systems</strong> (CMS), like WordPress or Wix, nonetheless make it a subscription website, <strong>where users could login</strong>, and see customized content.</p><p>However, I still know some technical basics. What I mean is I have read about what you normally would need to build a website, how you can acquire a domain name (I have done several times), register for hosting (done that too), or build websites with CMS (again, done it as well a couple times) etc. <strong>So nothing fancy, nothing special, just the basic stuff</strong>.</p><p>I also know some Html and CSS, I have tried to build basic functioning one-page websites with React.js a couple years ago, and I’m also familiar with programming in C#, Python and JavaScript.</p><p>But I am still “just” a structural engineer who occasionally applies programming (VBA, C#, Python and visual programming) for engineering design automation.</p><p><strong>Building a standalone, working website</strong> without any content management framework, seems a complex task, and learning how to do it seemed like an <strong>exciting challenge</strong>.</p><p>The reason I’m planning to build one now, is that I have some ideas to create a web application for engineers with online resources like <strong>spreadsheets, tutorials, online, cloud based calculation templates</strong> etc.</p><p>I’m aware of the fact, that there are engineering resources like this on the internet already, and I’m not planning to disrupt this territory. (Yet. )</p><p><strong>For now, I just want to learn how to build one from the ground up, tell its the story, and learn on the go.</strong></p><h3>Q: How/Where to start?</h3><h4>I have started where anyone would have: I <strong>asked the internet</strong>.</h4><p>Of course by this I mean <strong>Google</strong>, and since it’s already 2023, I asked <strong>ChatGPT </strong>several times<strong> </strong>as well.</p><p>During my research, I understood, that <strong>the first step </strong>actually<strong> should be a step <em>backwards</em></strong>, and an attempt to understand the problem as a series of interconnected tasks. <strong>What I knew before jumping into it, was this:</strong></p><blockquote>I wanted to get from a single <strong>idea</strong>, to a <strong>working website:</strong></blockquote><blockquote>A web app for engineers, where users could log in, access custom content and be able to use its resources, based on their subscription tier. For the time being, I do not care about a beautiful user interface, or a paid subscription.</blockquote><p><em>When </em>this goal is achieved, <em>then</em> I can start working on making it pretty, and maybe getting on the path to monetizing it.</p><p>So, a <strong>Step 0 </strong>should be the <em>real</em> first step, which<strong> </strong>is <em>a backward step </em>in order<em> </em>to be able to look at the challenge as a whole, and understand what main tasks need to be planned out to achieve my goal:</p><ol><li>Find and acquire an available <strong>domain name</strong> (1/10)</li><li>* Find a suitable <strong>hosting service and web server</strong> set-up (3/10)</li><li>Design a <strong>mockup </strong>for the website layout (UX, UI) (3/10)</li><li>Set up a <strong>development environment</strong> and a <strong>version control</strong> system (3/10)</li><li>* Select a framework and build the <strong>front-end </strong>(7/10)</li><li>* Build the <strong>back-end </strong>system and implement a database (9/10)</li><li>Implement <strong>access controls</strong> for subscribed users (10/10)</li><li><em>Optional</em>: Implement a <strong>payment gateway </strong>(10/10)</li><li><strong>Security </strong>measures (10/10)</li><li><strong>Test</strong> (7/10)</li><li><strong>Analytics </strong>(7/10)</li></ol><blockquote><em>Note:</em></blockquote><blockquote>*Steps 2, 5 and 6 together basically comprises the so called <strong><em>web development stack.</em></strong></blockquote><blockquote>I also appended to each step a difficulty score out of 10, that reflects <strong>my assumption</strong> of how challenging the task would be, based on my own knowledge and experience. The higher the score is, the more I need to learn to be able to implement it. It will be interesting to see how these scores will change (or not change) as time goes on.</blockquote><p>The order and the actual tasks may change as we go on, and when that happens, I will make a note, and justify the adjustment.</p><p><strong>You are also welcome to give me any advice in the comments, if you think I could benefit from it, and for that I will be really grateful.</strong></p><p>An hopefully, in the end I will have a website along with a complete hands-on tutorial, in case someone else would also like to replicate this process.</p><h3>In the next part:</h3><p>In the next part I will attempt to set up a free web server with hosting where I can start building the site, and find a suitable domain name.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed8da33b441d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zero-to-web-application/mission-possible-a-subscription-website-from-scratch-ed8da33b441d">Mission Possible: a Subscription Website from Scratch</a> was originally published in <a href="https://medium.com/zero-to-web-application">Zero to Web Application</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How writing could help you find order (in life and in your head)]]></title>
            <link>https://medium.com/@adamczegledi/how-writing-could-help-you-find-order-in-life-and-in-your-head-b07a1bae2b3f?source=rss-b67cd7adec0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b07a1bae2b3f</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[inspiration]]></category>
            <category><![CDATA[entropy]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Adam Czegledi]]></dc:creator>
            <pubDate>Tue, 27 Sep 2022 08:51:19 GMT</pubDate>
            <atom:updated>2022-09-27T09:00:25.417Z</atom:updated>
            <content:encoded><![CDATA[<h3>How writing could help you find order (in your head and in life) — My first story on Medium</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XYGGnvWIw_2gNZQbHs2Cbg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Markus Spiske</a> on <a href="https://unsplash.com/s/photos/order?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>About order (in general) and the natural flow of things</strong></h3><p>The truth is, everyone is lazy at heart (at least a bit, admit it). Doing, creating, or just preserving something by definition requires action, and that action requires some kind of energy. Creating something means organizing certain bits and pieces into a recognizable order and make them interconnect with each other, so they would shape something else, something bigger. If we want to maintain or add to this order, we constantly have to fight the second law of thermodynamics: <a href="https://www.sciencedirect.com/topics/earth-and-planetary-sciences/entropy"><strong>entropy</strong></a>.</p><h4>Entropy</h4><blockquote>The level of entropy of a system is used to describe the level of disorder or energy distribution inside that system: the higher the entropy, the higher the level of disorder there is. If the system is closed (no energy transfer in or out), over time it tends towards equilibrium, which is also the highest entropy state: the most probable and most stable state the system can be at (so entropy increases).</blockquote><blockquote>If the system is not closed, an outside influence (energy) can alter its natural behavior, maintaining or even increasing order, thus decreasing the entropy of the system.</blockquote><p>In other words: by nature, <strong>all matter in the universe — including both living and non-living — are continuously trending towards equilibrium</strong>, or the state of the lowest energy and the highest probability (i.e., <a href="https://en.wikipedia.org/wiki/Principle_of_minimum_energy">principle of minimum energy,</a> see above), and they either reach that state by themselves, or some kind of external actor prevents that from happening.</p><p><em>(I hope I managed to phrase it right, as I’m not a physicist and the exact relationship between entropy and energy of a closed or an open system is </em><a href="https://physics.stackexchange.com/questions/534173/why-does-the-minimum-energy-principle-work"><em>not evidently easy</em></a><em> to </em><a href="https://ps.uci.edu/~cyu/p115B/LectureNotes/Lecture13.pdf"><em>wrap your head around</em></a><em>.)</em></p><p>So basically entropy is the reason why you’d rather plop down on the couch after a hard day at work, instead of just to start doing the dishes: your body simply tends towards the lower energy or higher entropy state.</p><h4>The house</h4><p>To better illustrate the concept of entropy in real life, here is a classic example: take an abandoned house, that looks like it’s almost collapsing. Vegetation and wildlife has started taking over inside and out, windows are broken - it’s obvious, that no one has taken care of it for ages. Another couple of decades and sure it will turn into unrecognizable ruins. <em>This is entropy increasing.</em></p><p>Imagine now, that you buy this house and start renovations right away. You basically use yourself as an outside force to fix, to reorder, to rebuild. <em>This is you decreasing the entropy of the house.</em></p><p><strong>But there is a price to be paid.</strong></p><p>Interesting to note, that this increasing entropy causes the opposite process in your own body. After all, construction work requires a lot of energy, it is tiring: your body wears down, you get bruises, sore muscles etc. <em>This is your own body’s entropy increasing</em>.</p><p>Then by replenishing your body with nutrients, its <em>entropy decreases again</em> (using the energy from food), by breaking down the ingredients (increasing entropy) and so on. I’m sure now you see my point.</p><p>Every increase of entropy somewhere requires a decrease of entropy somewhere else, because of it. However, regarding the universe as a system, the overall entropy will always increase, so a local exchange of energy between systems that changes entropy doesn’t mean they will change in equal level.</p><h4><strong>When you just let things happen, it always leads to uncontrolled behavior, randomness, disintegration, and then eventually everything turns to dust</strong>. I mean this both metaphorically and literally.</h4><blockquote>“The sun will last ten billion years and maybe the dwarfs will last two hundred billion for all the good they are. But just give us a trillion years and everything will be dark. Entropy has to increase to maximum, that’s all.” (<a href="https://www.physics.princeton.edu/ph115/LQ.pdf">Asimov: The Last Question</a>)</blockquote><h4>A deck of cards</h4><p>If you throw a deck of cards on the floor, it is highly unlikely they will land perfectly stacked on each other, in order and all faced down. Instead, they will randomly scatter on the carpet, some face up, some face down, and if you want to put them back in their box, you have to pick them up one by one, and organize them. This requires effort. Effort requires work, work requires energy.</p><h4>Not wanting to put in the work and still expecting, that things will work out the way you want, will only take you so far.</h4><p>If you want to avoid the most likely outcome, you need to act. Of course, you can get lucky once or twice, but for most people (like 99.99999999% of people — roughly that’s your chance), not doing anything but hoping for luck will not pay off the long term.</p><p><strong>If you wish to maintain any kind of order regarding anything in your life, you will need to put the work into it.</strong></p><h3><strong>So, what does writing have to do with all this?</strong></h3><p>I am not happy to admit, but I have always struggled with finishing certain things after starting them. I often get enthusiastic about a subject, a project, deciding I will stick with it until I can get something valuable out of it. Then soon I find myself excited about something else again the next day, the next week or next month, and my interest in the previous subject just slowly fades away, I become less and less invested, and this new thing takes its place just to share the same fate a couple of weeks later.</p><p>Writing for me is one of these things.</p><p>When I first moved countries for a longer period, I started a blog, so I should not have to update all my friends and family about my new life one by one. I enjoyed blogging for quite a while, because moving to a new country was really exciting, and I wanted to share that excitement and my new experiences with the people I cared about.</p><p>Then these novel experiences slowly became everyday part of my life, they became my new normal, and I felt I couldn’t share any more new information that I haven’t already shared before. What was left was my private life, and I just didn’t feel I wanted to write about it that regularly any more.</p><p>So I stopped, and haven’t really picked up the habit of putting down words since then. (Writing reports for work does not really count).</p><p>However, writing for me has always been something that I wanted to be able to do consistently and regularly, mainly for the following reasons:</p><ul><li>becoming better at it: either writing in English, as it is not my first language, or in Hungarian (my first language)</li><li>creating an imprint of my thoughts in an organized way, so it can become clear what I am <em>really</em> thinking, being able to draw further ideas from them later, or as I’m going ahead, instead of fishing in the chaos in my head</li><li>being able to create consumable content: like a permanent digital mark, so I can provide value for others, maybe even earning money from it</li></ul><p>I do not consider the third point always as a priority, as sometimes you just need to write down words to organize your thoughts, just for yourself, in a therapeutic way, without showing it to anybody.</p><p>Writing down what’s in your head <em>will</em></p><ul><li>give your thoughts a structure</li><li>inspire further inner discussion about the topic</li><li>help you remember them later.</li></ul><p><strong>If you think your ideas are worth remembering, don’t let them fade away.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NwoJdxBGvOrP8EIzlfp20g.jpeg" /><figcaption>How I imagine what writing can do to your thoughts — Illustration by author</figcaption></figure><p>To illustrate all the above, before I started typing this article, I didn’t have a concrete idea what I wanted to write down exactly. I knew I had all these thoughts about writing, my own difficulties to stick with it, the urge to find out why it’s like that, also I have been always fascinated by the theory and philosophical aspect of entropy as a potential answer for a lot of things around us.</p><p>I had all these sprinkled in my head, I just didn’t know yet how to organize them. So I grabbed my main idea first (an obstacle: my inability to stick with writing), then meticulously reverse engineered where it could come from (human laziness, entropy), and created a connection between them, also as a firm reminder what should be done to overcome that obstacle.</p><p>Eventually it’s become a recursive contemplation about why writing is good for you, why it is difficult, and what’s the first step to get on with it regardless: <strong>to remind yourself of, and understand the first two.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b07a1bae2b3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>