<?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 Tomasz Staniak on Medium]]></title>
        <description><![CDATA[Stories by Tomasz Staniak on Medium]]></description>
        <link>https://medium.com/@nbw?source=rss-493cc09064a5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*HoXzAK4L_pXF7hn_.jpg</url>
            <title>Stories by Tomasz Staniak on Medium</title>
            <link>https://medium.com/@nbw?source=rss-493cc09064a5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:30:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nbw/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[What comes after preservation? On the future of  Amiga]]></title>
            <link>https://medium.com/@nbw/what-comes-after-preservation-on-the-future-of-amiga-3fd51749646b?source=rss-493cc09064a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fd51749646b</guid>
            <dc:creator><![CDATA[Tomasz Staniak]]></dc:creator>
            <pubDate>Wed, 19 Aug 2026 19:47:00 GMT</pubDate>
            <atom:updated>2026-08-19T20:17:26.893Z</atom:updated>
            <content:encoded><![CDATA[<h3>What comes after preservation? On the future of Amiga</h3><p>I love retro computing. I grew up using the Atari 800XL, Amiga 500 and 1200, and early PCs starting with a 286 running DOS in the late 80s and early to mid-90s.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*tVOqAAXWAMlXZlfkDo7iFA.png" /><figcaption>The NEW and refreshed Amiga logo — 2026!</figcaption></figure><p>I have a lot of affection for the Amiga, and one of my dreams is to return to the platform and start making software for it, mostly games. I actually think this is a particularly good time for retro platforms. AI lowers the barrier to entry considerably and could bring a lot of people back to platforms they would otherwise never have the time or technical confidence to develop for while lowering the bar to learn the actual platform if they wish to.</p><p>And there is something slightly incredible about the fact that I can even write about the <strong>future of the Amiga</strong> in 2026. This is a platform that was supposed to have died more than 30 years ago, yet we are still discussing where it should go next, what kind of hardware it should run on, what its operating system should become and what new software could be built for it.</p><p>My interest in retro was reignited by Atari. I started buying Atari shares about two years ago, and I have to say I’ve been impressed by what Wade Rosen has done so far: shedding dead weight, opening the company up to licensing, producing genuinely good apparel, collaborating with decent brands, and, most importantly, making smart acquisitions and repositioning the company around things like Nightdive, Digital Eclipse, and the revival of Infogrames.</p><p>That made me wonder whether something similar could happen with the Amiga.</p><p>I was never particularly interested in Commodore as a brand, so I can’t fully judge whether everything happening on that side makes sense or not. But I did hope that the renewed interest around Commodore would eventually have a positive impact on the Amiga ecosystem.</p><p>I was never particularly interested in Commodore as a brand, so I can’t fully judge whether everything happening on that side makes sense or not. But I did hope that the renewed interest around Commodore would eventually have a positive impact on the Amiga ecosystem.</p><p>So far, it hasn’t.</p><p>Then, a few days ago, Amiga Inc. (Cloanto) and Hyperion finally put their disputes behind them. A lot of people immediately started analysing what this might mean for the ecosystem, for developers, for users and for the future of the platform.</p><p>At the same time, when I look at Reddit or other places where the Amiga community gathers, the thing that often seems to generate the most excitement is the 999th way of running the same old software: another take on the Amiga 500 or 1200, another accelerator, another recreation.</p><p>I sometimes feel like an ecosystem of hackers and dreamers slowly evolved into an ecosystem of preservationists.</p><p>The Amiga community is exceptionally good at preserving the Amiga, but much less comfortable with letting the Amiga evolve into something that stops looking exactly like the Amiga they remember.</p><p>And that brings me to the <a href="https://www.youtube.com/watch?v=lp-NAajrc5Q">almost three-hour interview with Mike Battilana of Cloanto and AmigaBill</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Flp-NAajrc5Q%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dlp-NAajrc5Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Flp-NAajrc5Q%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/04e22f274913d3e702c32c12fead07d5/href">https://medium.com/media/04e22f274913d3e702c32c12fead07d5/href</a></iframe><p>It’s a great interview and a fascinating one for anyone hoping to hear directly from the source about what the recent developments might mean. And I want to be optimistic. Mike is probably one of the people best suited to run the Amiga in what may be its strongest legal position in more than 30 years.</p><p>But I have to say, I came away a little worried.</p><p>Look, I remember the bankruptcy. I remember what led to it, and I remember the years that followed. It was chaos. It was completely FUBAR. But it was also full of interesting ideas.</p><p>AGA, faster CPUs, RTG, PCI, PowerPC, new graphics systems, SMP, modern APIs, further OS evolution.</p><p>Even if some of those ideas turned out to be dead ends, they all had one important thing in common: <strong>they were attempts to move the platform forward.</strong></p><p>And this is where I struggle with the vision being presented today.</p><p>Right now, I see a lot of very capable engineers in the Amiga ecosystem. People who understand the hardware, the OS, compatibility, emulation, FPGA, accelerators and all the strange historical layers that make the platform what it is.</p><p>What I see much less of is vision.</p><p>And by that I do not mean another technical roadmap. I mean somebody with a clear idea of what Amiga should be as a platform five or ten years from now. Someone who can answer not only <em>what hardware should we build?</em> or <em>how do we preserve compatibility?</em>, but also <em>what should people actually do with this platform? Who is it for? Why should developers care? What kind of new software should exist on it?</em></p><p>This is one of the things I find interesting about Wade Rosen’s approach to Atari. Whatever you think about individual products or acquisitions, there is a broader direction behind them. Atari is not treated simply as a box that needs to be recreated. It is treated as a platform and an ecosystem: hardware, games, publishing, remasters, new software, licensing, acquisitions, merchandise and old IP all reinforcing each other.</p><p>I am missing that kind of thinking around the Amiga.</p><p>First, its centre of gravity is still very clearly AmigaOS 3.x and 68k compatibility. There is talk of 8K RTG, future processors and new hardware, but everything is supposed to grow out of a stable, compatible baseline.</p><p>I understand the business logic behind that. Compatibility matters, especially in a small ecosystem where the existing software library is one of the main assets.</p><p>But it is also very easy to end up with a faster machine whose main achievement is running exactly the same software.</p><p>And that, to me, is the difference between thinking about Amiga as a <strong>product</strong> and thinking about Amiga as a <strong>platform</strong>.</p><p>A product can be a beautifully engineered new Amiga that is faster, more convenient and more compatible than anything before it.</p><p>A platform needs something more. It needs reasons for people to build on top of it. It needs tools, distribution, documentation, incentives, new applications and some idea of what kind of ecosystem it wants to create.</p><p>Second, I am not convinced by the hesitation around open source.</p><p>One of the arguments against opening things up seems to be the fear that it would create fragmentation: countless branches, competing versions and, ultimately, anarchy.</p><p>But the uncomfortable part is that <strong>the anarchy already happened, without open source</strong>.</p><p>The post-Commodore history of the Amiga is already a history of forks, parallel evolutions and incompatible ideas about what the platform should become. AmigaOS 3.1, 3.2, 3.9 and the various attempts to continue that line. AmigaOS 4.x. MorphOS. AROS. ScalOS. Directory Opus Magellan as an almost alternative desktop environment in its own right. Different RTG systems, different PPC approaches, different hardware families, different owners, different interpretations of who had the right to develop what.</p><p>We did not avoid fragmentation by keeping the source closed.</p><p>We got fragmentation <strong>plus legal uncertainty, duplicated effort and dependencies on companies that could disappear, change ownership or spend years fighting over licences</strong>.</p><p>That is why pushing open source into some hypothetical third stage worries me. First come free updates, then broader availability, and perhaps truly open code at some later point.</p><p>That still feels like a model where:</p><blockquote><em>the owner gradually allows the community access to more parts of a controlled platform.</em></blockquote><p>What I would find much more compelling is a platform where companies and the community can build together on a stable foundation without having to wonder whether, five years from now, the owner changes again or somebody discovers a new interpretation of a contract signed in the 1990s.</p><p>Open source would not magically remove disagreements. Of course there would be forks. Of course people would disagree about direction. Some branches would die. Others might become successful.</p><p>But that is not necessarily a bug.</p><p>Healthy open-source ecosystems often deal with fragmentation by allowing ideas to compete and successful ones to converge again. The alternative is not automatically unity. In the Amiga’s case, we have already seen what the alternative can look like: multiple closed or semi-closed descendants evolving separately while everybody waits for somebody else’s permission to move.</p><p>After everything that happened to the Amiga, I think that distinction matters.</p><p>Third, there is a lot of language about creating a beautiful environment, preserving compatibility and removing uncertainty, but very little concrete proposition for a new developer.</p><ul><li>What is the SDK?</li><li>What is the toolchain?</li><li>What APIs should I target?</li><li>What is the target hardware?</li><li>How do I distribute an application?</li><li>How do I make money from it?</li></ul><p>And, perhaps most importantly: <strong>why should somebody in 2026 choose to build software for the Amiga?</strong></p><p>That is the question I keep coming back to.</p><p>Because I think there is a fundamental tension in the vision. Mike Battilana appears to want both complete historical continuity and a path toward the future.</p><p>I understand why. Historical continuity is part of the value. It is what makes the Amiga the Amiga.</p><p>But at some point a choice has to be made about what “the future of Amiga” actually means.</p><p>Does it mean a more polished, more accessible and more capable AmigaOS 3.x experience?</p><p>Or does it mean a platform capable of producing things that did not exist before?</p><p>Those are not necessarily mutually exclusive goals. In fact, the best outcome would probably find a way to support both: keep the historical software library accessible while creating a modern development target above it.</p><p>But they are not the same goal either.</p><p>And I think this is where the Amiga ecosystem needs more than good engineering. It needs a stronger answer to the question of <strong>what the platform is supposed to become</strong>.</p><p>And don’t get me wrong: this is probably the most exciting moment I can remember in the Amiga ecosystem in the last 30 years. There is movement again. There is new hardware, renewed interest, legal uncertainty finally being reduced and people willing to invest time and money into the platform.</p><p>That is exactly why I think the question of where it should go next matters now.</p><p>In the meantime, I’ve decided to take a closer look at AROS while I wait and see where the wider Amiga ecosystem goes next. Since much of the software I already work on uses SDL, AROS feels like a relatively accessible way to start targeting the platform without having to reinvent my entire development workflow. Hopefully, I’ll have something small of my own running on it and ready to publish before too long.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IGqCLdcbmSBktlS1-Ip5Qw.png" /><figcaption>First piece of code running on AROS</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zpuM3YvivkqbTkiUNBLDEw.png" /><figcaption>And mandatory vector ball</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fd51749646b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Postreads.co: From 0.18 to 0.27— Smarter, Faster, and More Powerful]]></title>
            <link>https://medium.com/@nbw/postreads-co-from-0-18-to-0-27-smarter-faster-and-more-powerful-4da59ca29731?source=rss-493cc09064a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/4da59ca29731</guid>
            <dc:creator><![CDATA[Tomasz Staniak]]></dc:creator>
            <pubDate>Sat, 15 Nov 2025 00:44:47 GMT</pubDate>
            <atom:updated>2025-11-15T00:44:47.419Z</atom:updated>
            <content:encoded><![CDATA[<p>Since version 0.18, <a href="https://postreads.co/">Postreads.co</a> has been constantly into a feature-rich, user-centric reading platform. Here’s what’s new:</p><p>📚<strong> Personal Library &amp; Reading Experience</strong></p><p>Save any web article with full content extraction, turning links into a distraction-free reading library. Email newsletters now display inline, with optimized formatting and dark mode support. The new “Links in this article” section shows favicons and allows instant copying, making research and sharing effortless.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*_bgFoEewylLew77cp5pS6A.png" /></figure><p><strong>📝 Capture &amp; Organize Your Thoughts</strong></p><p>Highlight, annotate, and tag any text passage with a <strong>annotations</strong>. Choose from four vibrant colors, add personal notes, and find all your insights in the dedicated “My Highlights” view. Search, sort, and jump back to context with a single click — your highlights are always just a tap away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k28n522DauIRLLrnet3R-g.png" /></figure><p><strong>🗂️ Advanced Organization</strong></p><p>Introducing hierarchical folders: drag-and-drop feeds, create unlimited folders, subscribe to entire categories with one click, and let Postreads auto-organize new feeds into smart folders — no duplicates, no clutter.</p><p><strong>🔍 Smarter Discovery &amp; Navigation</strong></p><p>Find content faster with advanced search: filter by date, company mentions, or relevance, and enjoy instant term highlighting. Choose between cards or magazine view for browsing, and access folders directly from the main page. Smart indicators now flag paywalled articles and inactive feeds, helping you curate your reading list with ease.</p><p><strong>🎯 User Control &amp; Polish</strong></p><p>Fine-tune your experience with account management, including email preferences and account deletion. Enjoy polished features like keyboard shortcuts, feed muting, and a streamlined mobile experience.</p><p><strong>💡 Little Touches, Big Impact</strong></p><p>From WebSub protocol detection for real-time feed updates to enhanced entity extraction (now recognizing video games, software, and tech tools), every detail is designed to make reading smarter and more enjoyable.</p><p><a href="https://postreads.co/"><strong>Postreads.co</strong> is more than an RSS reader</a>. It’s your personalized, powerful reading companion.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4da59ca29731" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Postreads: a newspaper-style feed and RSS reader]]></title>
            <link>https://medium.com/@nbw/introducing-postreads-a-newspaper-style-feed-and-rss-reader-178033564f8e?source=rss-493cc09064a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/178033564f8e</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-launch]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Tomasz Staniak]]></dc:creator>
            <pubDate>Mon, 18 Aug 2025 05:47:08 GMT</pubDate>
            <atom:updated>2025-08-18T05:47:08.654Z</atom:updated>
            <content:encoded><![CDATA[<p>What is better than managing products? Building them. Today, I am introducing <a href="https://postreads.co/">Postreads — an RSS reader with a modern take on the retro idea of curated content blended with a newspaper</a>. An outcome of 1.5 years of almost daily work after hours, while managing life and learning how to code.</p><h3>A bit of background</h3><p>I am a millennial, born in the 1980s in Europe. I grew up before the internet and became an adult just as new ideas were taking off. I experienced the “browser wars”, web2.0 and watched technologies emerge that we now take for granted. Most of all, I was fortunate to meet and work with great people.</p><p>An outcome of one of those experiences was <a href="https://web.archive.org/web/20080903161526/http://www.10przykazan.com/">10przykazan.com</a>, a feed aggregator — inspired by <a href="https://technorati.com/">Technorati</a> and <a href="https://9rules.com/">9rules</a> — which was quite popular in Poland around 2006–2008. Our paths later diverged, and the project ended. I tried to revive it a few times, but kept hitting the same wall: skills I lacked. Looking back, I think it had a real shot.</p><p>Two years ago, I returned to coding and stuck with it. <a href="https://postreads.co/">Postreads </a>is my first large build since the <a href="https://tomaszstaniak.com/books">Essential Product Management Books: A Curated Reading List for Leaders,</a> and only the second project I feel ready to share</p><h3>What is it</h3><p>Postreads is a curated feed aggregator that pulls from RSS, YouTube, Bluesky, email newsletters, and podcasts, with more to come. It offers two ways to read:</p><ul><li><strong>Newspaper</strong>: a shared, chronological feed you can personalize when signed in</li><li><strong>Reader</strong>: a classic RSS reader in the spirit of Google Reader</li></ul><p>You can also publish your own curated feed as a public URL. It is a one-person project and my sandbox for learning. I started by cloning 10przykazan, found my old sketches for a Reader mode, and kept going.</p><h3>How does it work</h3><p>Postreads favors signal over noise. <a href="https://postreads.co/discover">It ships with about 70 quality sources</a>, so you can start reading right away. Browse the main feed or the <a href="https://postreads.co/discover">Discover </a>and <a href="https://postreads.co/most-read">Trending </a>sections, then subscribe to anything that interests you. To add more, paste any site or channel URL, and Postreads will try to discover the feed; if needed, you can provide the feed URL. OPML import makes migration easy.</p><p>Every new source is reviewed within 24 to 48 hours for validity, duplicates, and spam; catalog items are available immediately. The goal is quality, not volume, with reliable publications, newsletters, and creator channels. Sources are tagged by language and category, so you can filter your feed and discovery; both will expand over time. You also get background updates, a personal address for newsletter forwarding, channels for organization, bookmarks with notes, and a simple trending view.</p><p>Content creators can also “claim” their feeds for faster updates and access to future features.</p><p>The discovery aspect helps you find quality content you might otherwise miss. You can see what articles are getting genuine engagement from other users, cutting through the noise to surface pieces that are actually worth reading.</p><p>There’s no pricing currently. If you find Postreads useful, you can <a href="https://ko-fi.com/enbewu">buy me a coffee</a>. It is a one-person project powered by curiosity, late nights, and caffeine, not venture capital.</p><h3>Future outlook</h3><p>I am committed to Postreads for the long run and will keep building as time and resources allow. I ship frequent updates and keep a <a href="https://postreads.co/changelog">public changelog</a>. Right now I am smoothing early decisions and improving user flow: better discovery, simpler profiles and settings, and a rebuilt Nuxt.js front end. In parallel, I am moving on to iOS and Android apps, expanding the API, and exploring workflow integrations with <a href="https://n8n.io/">n8n</a>, <a href="https://zapier.com/l/home?utm_source=bing&amp;utm_medium=cpc&amp;utm_campaign=bing-gbl-nua-search-brand-long_tail&amp;utm_term=zapier&amp;utm_content=_pcrid__pkw_zapier_pmt_e_pdv_c_slid__pgrid_1313917899892321_ptaid_kwd-82120685115631:loc-72_&amp;utm_ads_campaign_id=440173813&amp;utm_ads_adset_id=1313917899892321&amp;utm_ads_ad_id=82120167502164&amp;msclkid=b5627590349b1dfe330e1d3264e81a32">Zapier</a>, and <a href="https://ifttt.com/">IFTTT</a>.</p><p>If you care about open discovery and a cleaner reading flow, try it at <a href="https://postreads.co/">postreads.co</a>. I would love your feedback on what would make your daily reading simpler.</p><ul><li><a href="https://bsky.app/profile/postreads.co">Postreads on Bluesky</a></li><li><a href="https://bsky.app/profile/enbewu.bsky.social">Me on Bluesky</a></li></ul><h3>Ready to try it?</h3><ul><li>Go to <a href="https://postreads.co/">Postreads</a></li><li><strong>Create an account:</strong> sign in with <strong>Google</strong> or <strong>email</strong>.</li><li><strong>Browse the Newspaper</strong> (main feed). While logged in, <strong>subscribe</strong> to any feed directly from a story to add it to your <strong>collection</strong>.</li><li><strong>Add more</strong> by pasting RSS or Atom URLs, YouTube channels, newsletters, or Bluesky profiles.</li><li>Read your collection <strong>three ways</strong>:</li><li><strong>Newspaper</strong> — a front-page view of your subscribed sources.</li><li><strong>Reader</strong> — a clean, distraction-free inbox.</li><li><strong>Channel</strong> — publish your collection so others can follow it.</li><li><strong>Optional:</strong> Channels are <strong>private by default</strong>; publish only if you want them discoverable.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=178033564f8e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Product Manager’s Essential Library]]></title>
            <link>https://medium.com/@nbw/the-product-managers-essential-library-8a014ae50d69?source=rss-493cc09064a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a014ae50d69</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Tomasz Staniak]]></dc:creator>
            <pubDate>Sun, 11 May 2025 19:26:20 GMT</pubDate>
            <atom:updated>2025-05-11T19:27:05.691Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gKGV-FKxsb2C9SkF" /></figure><p>After two years of careful curation, I am finally sharing <a href="https://tomaszstaniak.com/books/">my Product Manager’s Essential Library — a collection of the most impactful books for product professionals</a> 📚 at every career stage.<br>This isn’t another ‘top PM books’ list. It’s a <strong>knowledge system</strong> for becoming a complete product leader.</p><p>The library is organized into five interconnected categories that reflect the holistic nature of product leadership:</p><ul><li><strong>Organizational Effectiveness</strong>: Building high-performing teams and scalable systems</li><li><strong>Discovery and Product Development</strong>: Mastering customer research and validation</li><li><strong>Strategy and Leadership</strong>: Developing strategic thinking and decision-making</li><li><strong>Personal and Professional Development</strong>: Enhancing leadership and communication skills</li><li><strong>Curated Collections</strong>: Cross-cutting themes addressing specific challenges</li></ul><p>Beyond technical skills, I’ve included essential wisdom on coaching, mentoring, and leadership that’s often overlooked but critical for true product excellence. For each book, you’ll find insights on “what the most important takeaways are,” “when to read,” and “why you should bother” — elements missing from most other reading lists.</p><h3>The Story Behind This Project</h3><p>I often get questions about book recommendations from fellow product managers, and I’ve participated in several book clubs over the years. While Goodreads reviews are helpful, I felt there was room for a more structured approach to sharing insights from these books.</p><ol><li>Reading actively with note-taking helps me better understand and retain the material, so I wanted to share these structured insights with others.</li><li>This project — the first project I started two years ago — allowed me to combine my interests in product management and software development.</li><li>It helped me prove to myself that I can finish what I start. This project became a test of resilience, pushing me to organize and complete something meaningful despite the odds.</li></ol><p>All of the books I read are available on <a href="https://www.goodreads.com/review/list/48622049?ref=nav_mybooks">my Goodreads profile</a></p><p>If you want to see which books might be available soon (minus all the write-up), check out <a href="https://www.goodreads.com/list/show/197337.Product_Management_and_Leadership">my list of books dedicated to product management.</a></p><p><a href="https://www.goodreads.com/list/show/197337.Product_Management_and_Leadership#top">https://www.goodreads.com/list/show/197337.Product_Management_and_Leadership</a></p><h3>How the library is organized:</h3><h4>Collections</h4><p>The intention behind collections is to create curricula that cut across established categories, providing a more holistic view of common PM challenges. For example, <a href="https://tomaszstaniak.com/books/collections/high-performing-team-structures-designing-for-flow">when you’re facing the challenge of building high-performing teams</a> you’ll find books that cover strategy, team dynamics, and individual psychology, so you can tackle the problem from every angle.</p><h4>Reading path</h4><p>The general library and each category contain a recommended reading path. These paths are carefully structured with specific reasoning behind them. For example, in the Organizational Effectiveness category:</p><blockquote><strong>Read sequentially</strong> — each book builds vocabulary for the next.</blockquote><blockquote><strong>Keep a running “translation” list</strong>: Jot down what every big idea means in <em>your</em> organization.</blockquote><blockquote><strong>Run small experiments after each book</strong> (e.g., try a “psych-safety check-in” after Fearless Organization, or a “team interface canvas” after Team Topologies).</blockquote><blockquote><strong>Circle back</strong> — after you finish, revisit Peopleware’s notes; you’ll see new layers.</blockquote><h4>Categories:</h4><ul><li><a href="https://tomaszstaniak.com/books/organizational-effectiveness">Organizational Effectiveness</a> 🔗<br>Understand how to build and maintain high-performing teams and create systems that scale. Learn to navigate organizational dynamics, improve team collaboration, and implement processes that drive sustainable results.</li><li><a href="https://tomaszstaniak.com/books/discovery-and-product-development">Discovery and Product Development</a> 🔗<br>Learn systematic approaches to understanding customer needs, validating ideas, and building the right products. Master frameworks and practices for continuous discovery, customer research, and product validation that lead to market success.</li><li><a href="https://tomaszstaniak.com/books/strategy-and-leadership">Strategy and Leadership</a> 🔗<br>Develop strategic thinking and learn to make high-impact decisions that drive organizational success. Master the frameworks and principles for effective product leadership and organizational transformation.</li><li><a href="https://tomaszstaniak.com/books/personal-and-professional-development">Personal and Professional Development</a>🔗<br>Focus on individual growth, self-improvement, and essential soft skills. Enhance your leadership abilities, emotional intelligence, and communication skills to become a more effective product manager.</li></ul><h3>What’s next?</h3><p>Moving forward, I plan to:</p><ul><li>I will add more books and occasionally replace some — this library is never finished. But I also don’t want it to grow too big. The aim is not to create an exhaustive list of every book worth reading, but rather the ones that I find the most relevant.</li><li>Add a quarterly changelog listing new titles that have influenced my thinking.</li><li>Extend the themed collections for specific product management challenges.</li><li>Experiment with different formats for sharing insights — newsletter or micro-reviews on LinkedIn, maybe even a podcast? I will definitely look into more practical applications of the content written in the books I recommend.</li></ul><p>“Hey Tomasz, there are plenty of those already!” someone might say. My response: “But none created by me.” Here’s what I’ve learned over the years — nobody will notice unless you create something truly spectacular. Most won’t even click your link, let alone dislike it. Even when they like you. So, stop doing things for popularity. Instead of seeking approval, create because you want to, regardless of others’ opinions. My goal is to bring something “mine” while fighting the most prominent critic of my work: myself.</p><p>Personal curation still matters. We don’t need more generic recommendations — we need thoughtful selections that reflect real experience and practical application. This library represents my small contribution to that ideal. Whether it reaches ten people or ten thousand, its purpose has already been fulfilled: it exists because I wanted to create it and had the resilience to get it done.</p><p>But your engagement with this library would make it even more valuable. Have you read any of these books and drawn different conclusions?</p><p>👉 Tell me which book changed your PM practice and why.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a014ae50d69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Summarising 2024]]></title>
            <link>https://medium.com/@nbw/summarising-2024-1c768019d5dd?source=rss-493cc09064a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c768019d5dd</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Tomasz Staniak]]></dc:creator>
            <pubDate>Sat, 28 Dec 2024 23:20:28 GMT</pubDate>
            <atom:updated>2024-12-28T23:20:28.902Z</atom:updated>
            <content:encoded><![CDATA[<p>While LinkedIn feeds overflow with success stories of promotions, work-life balance victories, and transformative learning experiences, I reflect on a different kind of year. Don’t get me wrong — I love seeing people thrive, and 2023 was that year for me. But 2024?</p><p>The year for me was a constant battle with insomnia, resignation, and depression. Every symptom Matthew Walker described in “Why We Sleep” (read it!) became my daily reality. My confidence crumbled, and I struggled with existential questions about my professional and personal purpose. The experience felt like an emotional pendulum, swinging between states of mania and mental fog.</p><p>Yet, even in this challenging landscape, two commitments I made in 2023 proved to be my anchors:</p><p>1. Learning to program</p><p>2. Reading more consistently</p><p>These goals emerged from long-held aspirations. For years, I’d dreamed of returning to game development. Earlier in 2023, a colleague inspired me to create a resource repository — a curated list of essential reads for product managers and those looking to enhance their product development skills.</p><p>What started as “just a quick webpage” to host this reading list evolved into an 18-month journey rather than the planned six weeks. Here’s where marginal gains showed themselves, though not in the way motivational posts would have you believe. Most weeks, I’d come home from work and become a vegetable on my couch, barely able to walk the dog and falling into that classic revenge bedtime procrastination trap — staying up late playing video games because it felt like the only time that was mine. Yet somehow, I kept returning — finishing work at 6 PM, dragging myself to the desktop PC, and diving back into tutorials and coding. Not from some deep well of discipline, but partly because I was too stubborn to let it go, and partly because when things actually worked — when that code finally ran, or that feature finally clicked into place — it was genuinely fun. Those moments of triumph, however small, made it worth trying again after each setback.</p><p>As we enter 2025, I’ve (almost) achieved both goals. I consistently read 3–4 books monthly, totaling over 70 since making that initial commitment. I’ve mastered enough of Godot to understand its workings, and I can now build prototypes for any web project I envision — especially with AI amplifying these capabilities.</p><p>The year battered me, but it also taught me something fundamental about progress: messy, inconsistent, and rarely Instagram-worthy. You’ll feel under the weather, you’ll question everything, and that’s completely normal. What matters isn’t perfection or consistency — the stubborn decision to return to what matters to you, even after failing. Again and again. Day after day. It’s not about maintaining an unbroken streak; it’s about building the resilience to start over as many times as necessary.</p><p>Michael Jordan once said: “I’ve missed more than 9,000 shots in my career. I’ve lost almost 300 games. Twenty-six times, I’ve been trusted to take the game-winning shot and missed. I’ve failed over and over and over again in my life. And that is why I succeed.” In 2024, I finally understood what he meant. Success isn’t about never missing — it’s about being willing to take another shot, even when you’re bone-tired and your confidence is shot. That’s the real victory.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c768019d5dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A story about points. Story points.]]></title>
            <link>https://medium.com/@nbw/a-story-about-points-story-points-ebf9182a25c3?source=rss-493cc09064a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebf9182a25c3</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Tomasz Staniak]]></dc:creator>
            <pubDate>Sun, 21 Jul 2024 20:54:52 GMT</pubDate>
            <atom:updated>2024-07-21T20:54:52.626Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever felt your Scrum meetings are more about jumping through hoops than getting actual work done? People often hate Scrum because they perceive it as overly rigid and bureaucratic. Its numerous ceremonies and roles can feel like unnecessary overhead that slows down actual work. Additionally, the misapplication of Scrum principles by inexperienced teams or managers can lead to micromanagement, unrealistic expectations, and a focus on process adherence over actual productivity and creativity. But today, let&#39;s focus on one specific aspect: story points.</p><h3>What the Hell Are Story Points?</h3><p>Story points are a unit of measure used in Agile project management, particularly in Scrum, to estimate work items&#39; relative effort, complexity, and uncertainty. Instead of using time-based estimates, teams assign abstract point values to tasks or user stories. This allows for more flexible planning and helps teams focus on delivering value rather than adhering to strict time estimates. Story points typically gauge team velocity and capacity, aiding in sprint planning and project forecasting.</p><p>Many people dislike story points at different stages. Engineers often resent them because they feel like arbitrary numbers are imposed to measure their workload. Managers dislike them because they see them as another constraint on their expectations for maximizing output.</p><h3>Humans. Suck. At. Forecasting (aka: Estimations)</h3><p>Our estimations are off for many reasons: overconfidence, changing environment/circumstances, and focusing on the best-case scenario — to name a few. We also forget that a lot of our work is actually… waiting and waiting for feedback, tests to finish, and approval—the bigger the organization, the more queues. You think the task will take 2 hours, and it will take YOU two hours, but it will take 2 weeks to get to production, yet you promised 2 hours, and someone committed to the customer based on that estimation.</p><h3>Story points. The training wheels some teams need.</h3><p>That&#39;s why we have story points. Everyone understands time, and I may be a fossil, but back in my days, people were held accountable for their estimations: &quot;But you said it would take one day; I sold it already to the customer!&quot;, &quot;Two days?! My nephew did something similar in two hours!&quot;. Time estimation adds pressure from stakeholders because time is universally understandable: &quot;Come on, we need it by the end of this week!&quot;. While intuitive and straightforward, you want to use something other than this in practice.</p><p>It may also add pressure on your teammates — maybe the task is trivial for you and would take you two hours, but it may be a two-day task for someone else. Agreeing that it will take 0.5 days is not a solution, and it leads to imbalanced task assignments and &quot;knowledge islands&quot; (people who know &quot;everything&quot; because they built it all), adding more pressure when they go on vacation or get sick.</p><p>Story points aren&#39;t perfect — far from it. But ditching them just because you don&#39;t understand them? That&#39;s like throwing away your GPS because you can&#39;t read a map. Teams must grow into abandoning points, not out of frustration, but through proper understanding. Otherwise, you&#39;re just trading one set of problems for another, shinier set.</p><h3>How to Work Better with Story Points</h3><h4>Don&#39;t obsess over story point values:</h4><p>The real treasure is the conversations they trigger. Aim for meaningful team discussions about approaching tasks and whether they are necessary. As your team matures, you might naturally phase out formal point assignments, but always maintain the habit of these collaborative talks.</p><h4>Rethink how you use story points:</h4><p>Instead of measuring effort or time (and definitely avoid equating points to days), use them to gauge uncertainty and complexity. The higher the points, the more unknowns in the task. This approach sidesteps time-estimate pitfalls, encourages deeper analysis of challenges, and smooths the onboarding of new team members. It creates an environment where it&#39;s okay for newcomers to assign higher point values as they navigate unfamiliar territory, fostering knowledge sharing and team growth.</p><h3>Final thoughts</h3><p>So next time you&#39;re in a Scrum meeting, and you enter the conversation about using story points — assess the team maturity and the organizational setting, and have a conversation with your stakeholders or managers if needed. Ultimately, it doesn&#39;t matter what unit of measure you and your teams prefer or even if you use one. In the end, it&#39;s not about the points; it&#39;s about delivering value, but if your team is still in the early days and the team members are not so experienced, don&#39;t just ditch something because it feels strange.</p><p>Disclaimer<br>This is my attempt to get back into regular writing. I call this format “short” — it’s not an exhaustive description of a problem, but I wanted to write about it with an approach that “done is better than perfect”. Thanks for any feedback!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebf9182a25c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On my way to the Mendelssohn-Bartholdy’s estate and the old airfield. [Werneuchen Loop]]]></title>
            <link>https://medium.com/@nbw/bike-trip-on-the-way-to-the-mendelssohn-bartholdys-estate-and-the-old-airfield-werneuchen-loop-775432736cc1?source=rss-493cc09064a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/775432736cc1</guid>
            <category><![CDATA[trip]]></category>
            <category><![CDATA[cycling]]></category>
            <category><![CDATA[history]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[sightseeing]]></category>
            <dc:creator><![CDATA[Tomasz Staniak]]></dc:creator>
            <pubDate>Tue, 25 Aug 2020 05:31:02 GMT</pubDate>
            <atom:updated>2020-09-11T11:00:50.855Z</atom:updated>
            <content:encoded><![CDATA[<h3>On my way to the Mendelssohn-Bartholdy’s estate and old airfield. [Werneuchen Loop]</h3><p>I’m looking for a way to go back to writing. It took me years to figure out what I’m interested in sharing — and I figured that I want to start with my trips.</p><p>A couple of months ago, I bought my first decent road bike, and I started to make trips around the city I live: Berlin.<br>Initially short ones, I went on a path to discover what I like about biking. The initial intent was to ride fast, but I quickly figured that’s not what makes me tick as I hate riding loops.</p><p>The distance and ability to see things — this is a pure delight. Since then, I have made over 100 trips already, I’m hitting 3000 km mark, and I figured, I’d like to share this. Maybe someone else will get interested.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_vBUP3GC3T_wyAhyR4mQIA.jpeg" /><figcaption>The bike stands of the pros</figcaption></figure><p>My goals for each trip: to go far and to see something specific — nature, historical buildings, points of interest, etc. Let’s start.<br>The starting point being Berlin and my first destination: the military airfield in Werneuchen. The whole trip distance: 65km.</p><h3>Werneuchen</h3><p>Werneuchen is a small town of nearly 8,000 people located 30km away from Berlin. Reaching it is quite easy, the road quality is good, typical tarmac.<br>There is not much of a history to the town — it was a Wendish settlement, destroyed in the Hussite wars and the 30-years War. It grew significantly after the 1900s. It got connected to the railroad line, which led to subsequential development in the roads and connectivity. It grew in the importance more with the opening of the mentioned first goal of the trip: the airfield in 1937.<br>The airfield was a modern airbase created as a model-airfield for the future German (Nazi) developments — it was very well equipped. The town became the garrison-town for the airfield year later. The airfield took part in the bombing operations during the war against Poland. In the Nazi times, Germans performed here research on the radar technology for the needs of the night fighters.<br>It survived the war without damage, and one of the locals prevented the explosive destruction of the airfield, which shortly after became occupied by the Soviet army.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P7QTYe4NJxTXcd53FWWvFQ.jpeg" /></figure><p>The Soviets were using the airfield as a base for the elite Guard Reconnaissance Air Regiment until Germany’s reunification in the 1990s. Still, little is known about the operations performed in those times as they were kept secret.</p><p>After the Russians left, the airfield became a civilian strip of little importance. Occasionally it can be used for helicopters and lightweight planes. On two occasions in the 2000s, there were two emergency landings on the airfield of larger aircraft with seven injured passengers overall.</p><p>The area is mostly open and freely available, although the few publicly available buildings are in the state of disrepair. Part of the airfield has been filled with solar panels. There is an event location which when I was there held a small techno party. It’s a really cool place to visit if you are into the “urban decay” stuff.<br>I didn’t have much time to go around the whole airstrip, but I encourage highly to do it as it’s empty and feels bigger than Tempelhofer Feld.</p><p>Unfortunately for the trip, the arrival to the airfield was the end of the fun part. After going out of Werneuchen the tarmac became uneven, the terrain quite hilly (it was formed during the Ice Age), and I had the headwind for the next 40km directly in my face. But since “shut up legs,” I arrived at…</p><h3>Schönefeld</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9InBkXLHtkOGf2XyblM_jw.jpeg" /></figure><p>No, not the airfield one.</p><p>I’ve spent a couple of minutes here — the town has a long history, but I stopped here because it’s one of those cute small rural towns with a few large, old abandoned farms and a lovely church.</p><p>Typically next to those town-churches (dorfkirche), there are statues for the fallen in World War 1 (usually: more prominent and decorative) and World War 2 (typically: small plate, somewhere on the back).</p><p>This split is fascinating to observe — on the one hand, paying tribute to the fallen husbands, fathers, sons, and on the other — having this feeling of shame.</p><h3>Börnicke</h3><p>The last point of interest in the trip is the village of Börnicke. It’s again a typical Branderburgish village, with many old farm buildings and the typical rural architecture but two main points stand out:</p><p><strong>The church and the palace.</strong></p><p>The palace was owned by the Mendelssohn-Bartholdy family members until 1935 when Paul von Mendelssohn-Bartholdy has died.</p><p>Swiss Embassy moved for a short time to the palace in 1945 due to the bombings of Berlin. Later it was a field-hospital for the Soviet Army, a holiday house in the ’60s, home for handicapped children and a school until it was finally closed in the ’90s and bought by a private party in 2003. Since then efforts are being made to restore the palace and the park to its former greatness</p><p>The story of the Mendelssohn-Bartholdy’s family is an interesting one as many of its members were Europe’s best traders, bankers, and of course: musicians, composers, and philosophers. Jews in Prussia didn’t have last names — Moses Mendelssohn has picked the last name after his father: Mendel. His son: Abraham, the father of Felix, has added Bartholdy to his last name after his wife once they converted to Christianism. They raised their children in the Christian (protestant) faith.</p><p>Next to the church’s tower, there is the Mendelssohn-Bartholdy’s family tomb. Unfortunately, at the time of writing, I could not enter the cemetery as it’s closed outside of the opening times due to the COVID-19 regulations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ngEWIk47ghxHXcmFuIcxpg.jpeg" /><figcaption>Mendelssohn&#39;s family tomb</figcaption></figure><h3>Trip summary:</h3><p>The distance: 65km, My ride time: 2 hours 23 minutes, I assume that the regular weekend trip along this route will take up to 3.5 hours.<br>The whole route is a different quality of tarmac, mostly flat with a couple of “false-flats” and uphills and relaxing downhills.</p><p>There are a few small restaurants and gas stations where you can grab a bite or a quick coffee. There is no need to prepare anything special, but having something sweet and about 1.5litres of water would be enough for one person to comfortably ride this trip.</p><p>Places passed: Ahrensfelde, Blumberg, Seefeld, Werftpfuhl, Beiersdorf, Schönefeld, Willmersdorf, Börnicke, Birkenhöhe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rr63cd23BlCfnH0luuD3Gw.png" /></figure><h3>Places I’ve missed (for the next trip):</h3><ul><li>Radar tower in Weesow</li><li>The roof-less church in Beiersdorf (a ruin since the 1970s, haven’t found more info yet)</li><li>There are some ruins and remains of the radar towers around Doringsee — I will go there some other time.</li></ul><p>Not sure if such content fits Medium, but maybe someone will find it useful, and I will search for a more suitable place and form as I move on with the next notes.</p><p>Want to get in touch: <a href="https://www.instagram.com/enbewu/"><strong>My Instagram</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=775432736cc1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[O wojnie medialnej. Z innej strony.]]></title>
            <link>https://medium.com/@nbw/o-wojnie-medialnej-z-innej-strony-d779ff8e8072?source=rss-493cc09064a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/d779ff8e8072</guid>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[polityka]]></category>
            <dc:creator><![CDATA[Tomasz Staniak]]></dc:creator>
            <pubDate>Fri, 08 Jan 2016 16:40:26 GMT</pubDate>
            <atom:updated>2016-01-08T16:40:26.150Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Lubię Michała i lubię to, co pisze.</p><p><a href="https://medium.com/@michalsalaban/o-wojnie-medialnej-czyli-dlaczego-obydwu-stronom-%C5%BCycz%C4%99-powodzenia-c905ff67d56f#.qozieawen">Kolejny, bardzo ciekawy, fajnie napisany tekst</a>, z którym mógłbym się zgodzić w całej rozciągłości gdyby nie to, że w mojej ocenie, w walce o media chodzi o coś odrobinę innego.</p><p>Cofnę się o krok i zacznę od podpięcia się pod tekst Michała: “Nie będę się tu rozwodził czy preferuję PiS czy PO, bo byłaby to rozprawa o tym, czy wolę cierpieć na kiłę czy na rzeżączkę”. Dla mnie, to co przedstawił Michał, to bardzo “nasza” perspektywa: ludzi, którzy w zasadzie wychowali się w Internecie.</p><p>Sam nie mam telewizora, od kiedy wyprowadziłem się od rodziców (prawie 13 lat), nie słucham radia poza samochodem. Wszystko co wiem, przynosi mi Internet. <br>Ale kiedy wyjedziesz poza “miasto”, okazuje się, że nawet tam, gdzie jest Internet, sytuacja nie wygląda już tak samo.</p><p>W kręgu moich znajomych, nikt nie słucha Radia Maryja i nie ogląda Telewizji Trwam ale kiedy pojadę w rodzinne strony, ta perspektywa się zmienia i z jej powodu, zacząłem inaczej patrzeć na to zjawisko. Od strony zasięgu i sensownych programów (zapewniam, że są, tylko trzeba cedzić ziarno od plew), te media zasługują na pełen podziw i szacunek. Dlaczego? Bo “dowożą kontent” tam, gdzie nikt inny, do ludzi, którzy z różnych powodów nie uczestniczą w życiu. To są starsi ludzie, często schorowani, mieszkający w miejscach, gdzie największą atrakcją jest niedzielna msza i okazjonalny pogrzeb. Łatwo zgubić tę optykę, kiedy prowadzi się wygodne i dostępne życie w dużym, nowoczesnym mieście ale w Polsce są jeszcze miejsca, gdzie w taki dzień jak dziś, kiedy jest -6 za oknem i od rana sypie śnieg, ludzie po prostu utykają. Fizycznie — nie są w stanie ruszyć się ze swojego domu. I te dwie atrakcje stają się niedostępne — dla nich pozostaje telewizor lub radio. A co ma najlepszy zasięg?</p><p>Kiedy sobie to uświadomiłem, zacząłem też rozumieć dlaczego partia, która odniosła zwycięstwo przede wszystkim w Internecie, deklasując wszystkie inne partie, z PO włącznie, po wygranych wyborach zaczęła… zmieniać to najbardziej klasyczne, przestarzałe medium. I nie, nie ma to związku z tym, że PiS nie rozumie Internetu. Właśnie rozumie — wie, że wygrał w nim jako opozycja i wie, że wygrał bo to medium, którego nie da się kontrolować.<br>Wie również, że tzw. “twardy elektorat”, nigdy nie był odbiorcą Internetu — PiS potrzebował Internetu by zgarnąć te parę punktów procentowych u tych, którzy chcieli dokopać Platformie, ale nie potrzebuje już tych ludzi tak bardzo, by dalej prowadzić swoją narrację. Wie, że ta narracja w Internecie bardzo szybko zostanie rozbita i tzw. “racjonalni” sobie poradzą, wie również, że ich przeciwnicy, tak jak ja, nie oglądają telewizji.</p><p>Musi jednak dotrzeć z tą narracją do ludzi, którzy stanowią wierny, twardy elektorat, a oni — raczej — nie korzystają z Internetu. Dla nich telewizja to jedyne, “natychmiastowe” źródło wiedzy i potrzebują go, by wierzyć, że nadeszła “dobra zmiana”.</p><p>Okej, ale nie taniej byłoby po prostu zmienić nazwę? Jasne, że byłoby taniej, ale tutaj chodzi o możliwość odtrąbienia sukcesu. O propagandę, o “oderwanie świń od koryta”, i czy lepiej nie brzmi stwierdzenie, że “Telewizja jest w końcu Polska!”? Brzmi. I to co cały rwetes.</p><p>Czy telewizja to medium umierające, jak chce Michał… nie, nie sądzę. Niedawno krzyczeliśmy, że papierowe książki umierają, że zabiją je ebooki. Na razie na to się nie zanosi, tak jak i nie zanosi się na śmierć telewizji, głównie ze względu na jej zasięg w mniejszych osadach ludzkich.</p><p>Najważniejsze pozostaje jedno stwierdzenie, pod które również się podepnę: uczcie się czytać ze zrozumieniem. Lub raczej: uczcie się przyswajać wiedzę ze zrozumieniem. To boli, wiem, ale to jedyna opcja, by co “chwila” nie pojawiały się “gadające głowy”, które twierdzą, że one wiedzą lepiej od ciebie, co jest dla ciebie ważne i tobie potrzebne.</p><p>P.S. A tak poza tym, chciałem się przekonać, czy potrafię jeszcze napisać dłuższy tekst, od początku do końca.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d779ff8e8072" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>