<?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 James Marks on Medium]]></title>
        <description><![CDATA[Stories by James Marks on Medium]]></description>
        <link>https://medium.com/@dynamicdynamics?source=rss-b2c510d8fb84------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*xhCvM7QaORJwSq5B.jpeg</url>
            <title>Stories by James Marks on Medium</title>
            <link>https://medium.com/@dynamicdynamics?source=rss-b2c510d8fb84------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:15:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dynamicdynamics/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[The 4-letter words that define me]]></title>
            <link>https://dynamicdynamics.medium.com/the-4-letter-words-that-define-me-f9a7ed83b81c?source=rss-b2c510d8fb84------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9a7ed83b81c</guid>
            <dc:creator><![CDATA[James Marks]]></dc:creator>
            <pubDate>Thu, 25 Mar 2021 16:58:50 GMT</pubDate>
            <atom:updated>2021-03-25T16:58:50.797Z</atom:updated>
            <content:encoded><![CDATA[<p>I want to be more deliberate about how I spend my time. I’ve lost months of my life focusing too deeply on any one activity, this is a list of activities I’d like to balance my time across. What am I missing?</p><h3>code.</h3><p>I like to interact with the strictly logical world of code, and it feels fun to have that immediate, tangible impact. A hard to trace bug is like being the protagonist in a mystery thriller. I can easily spend too much time here, but always want to spend some.</p><h3>talk.</h3><p>I love connecting with people, hearing their stories and telling my own. I love Listening (capital L) to pick up the need-behind-the-stated-need and patterns across different perspectives.</p><h3>help.</h3><p>It’s easy to take for granted what I’ve learned over the years. Sharing this with people earlier in their journey helps me appreciate what I’ve accomplished, and it feels good to make someone else feel better.</p><h3>sell.</h3><p>There’s something addictive about hustling, whether it’s pitching a new idea to a familiar face or spending 20 minutes crafting the perfect cold-call email to make it through someone’s noise filters.</p><h3>draw.</h3><p>Drawings of a complex idea might take 5 minutes, but they can generate years worth of direction for a project. The drawing becomes the reason to grow the team, to find faster ways to make it real.</p><h3>plan.</h3><p>Once oriented around a goal, I love breaking it down into logical steps and milestones. That blend of math, people, money and logistics fit together like a puzzle and it’s fun to move the pieces around until you see a version that looks plausible.</p><h3>read.</h3><p>I read a ton of sci-fi and fantasy. In part to turn my brain off at the end of the day, but I also see value in immersing myself in realistic visions of the future. I like orienting myself around what <em>could be</em> when so much of our default experience is <em>what is</em>.</p><h3>play.</h3><p>This has been the biggest challenge for me. I’ve gotten better at it the more I’ve seen that ephiphanies come when I look away from a problem I’m stuck on. Another 5 hours staring at it, or 5 months, isn’t always the fastest way to the solution.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9a7ed83b81c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Trivially easy: my beef with programming today.]]></title>
            <link>https://dynamicdynamics.medium.com/trivially-easy-my-beef-with-programming-today-95d68299c870?source=rss-b2c510d8fb84------2</link>
            <guid isPermaLink="false">https://medium.com/p/95d68299c870</guid>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[James Marks]]></dc:creator>
            <pubDate>Wed, 20 Jan 2021 02:42:03 GMT</pubDate>
            <atom:updated>2021-01-20T04:25:38.340Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EogJIjQLzDxMFQoT" /><figcaption>Photo by <a href="https://unsplash.com/@jefflssantos?utm_source=medium&amp;utm_medium=referral">Jefferson Santos</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Culturally, we web developers have a bad habit of selling things by telling you they’re easy — <em>just</em> follow these steps. <em>Simply</em> do x, y and z. From the beginning, it’s been driving me crazy.</p><p>Nothing about programming has ever been simple or easy for me. In fact, it’s been a struggle every step of the way. Is it me?</p><blockquote><strong><em>Just</em>, <em>simply</em> and my personal (least) favorite programming descriptor — <em>trivial — </em>are presumptive, tone-deaf, very frequently wrong.</strong></blockquote><p>What’s missing here are the qualifiers: <em>Trivially</em> easy… if you have a decade of programming experience. <em>Simply</em> follow these steps… assuming your environment mirrors the one I was using the day I wrote this. <em>Just</em> type this command to install this library… if you know what a package installer is, don’t have any permissions issues, and the OS didn’t change an unlisted dependency<em>.</em></p><p>All signs point to an <a href="https://techcrunch.com/2015/11/27/software-developers-growing-elitism-problem/">insidious programming elitism problem</a>, as DevMountain founder Cahlan Sharp writes for TechCrunch. If there were anything trivial about developing software, why would we be flocking to Stack Overflow in search of answers? If things are really so simple and easy, why do web developers pull down six figures and product roadmaps stretch off into the distance?</p><blockquote><strong>Because programming is not easy.</strong></blockquote><p>The fact is, programming is hard. It takes a lot of time, forethought, and experience to do well. Learning the syntax of the language (no small feat) is just the beginning. Large, complex ecosystems (not to mention personal fortunes) have been built around simplifying each step of the process; new founders with new promises of how easy their service will make things. It’s why coding boot camps were a <a href="https://careerkarma.com/blog/bootcamp-market-report-2020/">$460 million dollar industry in 2019</a>.</p><blockquote><strong>Ironically, the result of all of this simplicity is a mess of complexity.</strong></blockquote><p>Sometimes, these so-called miracle solutions only create more programming headaches. Sure, fewer of us are configuring Linux servers — that was awful, I had no idea what I was doing, and I appreciate not having to do it anymore.</p><p>But more of us than ever are trying to figure out why the CI choked on the latest build. If we’re being DOSed by bad actors, one of our API customers, or (more likely) one of our own services. Why the BI dashboard doesn’t match the same stat we’re displaying to users.</p><p>If it were just me who struggles to manage this complexity, why do most companies have the same answer when VCs ask what they’re raising money for? The response is so common we can almost recite it in unison: <em>to scale engineering</em>. There’s a good reason for that answer, beyond a lack of creativity: organizations face a long and expensive list of solvable-but-time-consuming software problems, and we all know it.</p><blockquote><strong>If it’s all so simple, why is it so expensive?</strong></blockquote><ul><li>Because the “trivial” things take days instead of hours.</li><li>Because builds come back missing features that were trickier than we realized once we dug into them.</li><li>Because the deliverable is useless without the feature that got cut.</li><li>Because the product team didn’t understand what actually would have been feasible for devs, if anyone had thought to frame the problem that way.</li><li>Because we hit a wall on a bug, and it tooks hours to track down.</li></ul><p>To help non-developers make sense of the mess, we build platforms based on templates. Shopify, Wix, Wordpress and the rest are trying to solve the same problem — put the code into the background, or hide it altogether.</p><p>Sell templates with simple, aesthetic photography and design. Make app stores to fill in all the esoteria that didn’t make the 80/20 cut. Create buttons and menus to force templates into new configurations, and hope it does what you need. If you can afford it, invest a small fortune to have it customized.</p><p>But the amazing thing about code — the reason we stomach the chaos and pay the high fees — is its incredible power. Even poorly written code, anchored to the physics of processors and the internet itself, is a thousand times more powerful than no code.</p><blockquote><strong>But true power lies in the holy grail: well-written code.</strong></blockquote><p>Good code is like poetry, expressing complex ideas in a simple, elegant way. Stripping an idea down to its most pure, most authentic self, able to communicate both with machines and humans.</p><p>In our complexity, we’re leaving people on the sidelines and preventing them from ever experiencing that beauty and power. Because they aren’t smart enough? I don’t think so. I find it far more likely that they’re being left out because they don’t have years to invest in learning the syntax, acclimating to the environment, and uncovering the <em>gotchas</em> one painful hour at a time, with a dribble of productivity in the early stages, if they’re lucky.</p><p>My vision? A programming environment for the people who dabbled in Python or Javascript out of curiosity and walked away when they stared up at the sheer cliff face between what they knew and what it takes to build a real app.</p><blockquote><strong>I’m creating a place where no developer of any skill level gets left behind — and I’m calling it Trivial as a permanent reminder of the trap we must not fall into.</strong></blockquote><p>Trivial is a place where you can learn to write software as you go, getting immediate value out of the time you’re investing. Trivial is a place where the steps are intuitive, the examples work when you try them, and anyone can build a bot in minutes without a decade of experience.</p><p>Trivial puts code in the foreground, because that’s where the real power is. I don’t want to hide it behind buttons, subjugate it to some dusty corner where you can write 200-line nightmarish global functions, or require you to build and maintain a local environment.</p><p>Rather, my goal for Trivial is to make code understandable and enjoyable for everyone who wants to learn. We’ll strip away the complexity <em>around</em> code that turns so many people away. To create an environment that doesn’t just teach you how the code works, but how to do incredible things with it.</p><blockquote><strong>How to get more out of your time, and how to access the joy that comes from having control over your environment.</strong></blockquote><p>At the end of the day, code is a tool. It’s a bit unwieldy for everyone but the pros, and it too often seems like magic to the naked eye.</p><p>Trivial is a new place to write and publish the snippets of code that augment our lives. A place for the Javascript or Python amateurs to put that knowledge to work. A place where product managers, project leaders, designers, customer support, and the rest of the software team can see and interact with the code that defines our digital reality.</p><blockquote><strong>And yes, a place for developers.</strong></blockquote><p>After years of struggle, and despite our tone-deaf promises of ease, we too deserve a place where things JFW.</p><p>We’re currently looking for pre-release users of all skill levels. Sign up at <a href="https://www.withtrivial.com/">withTrivial.com</a> and help us build the platform we wish we’d had to learn on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95d68299c870" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[In times of great uncertainty]]></title>
            <link>https://dynamicdynamics.medium.com/in-times-of-great-uncertainty-d086d81f5e19?source=rss-b2c510d8fb84------2</link>
            <guid isPermaLink="false">https://medium.com/p/d086d81f5e19</guid>
            <category><![CDATA[pandemic]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[leadership-development]]></category>
            <dc:creator><![CDATA[James Marks]]></dc:creator>
            <pubDate>Sat, 21 Mar 2020 20:36:27 GMT</pubDate>
            <atom:updated>2020-03-22T17:25:35.812Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s been a difficult week, and I want to give the people around me a clear insight into how I’m thinking about the events unfolding around us. Some concepts that are on my mind:</p><h4>Focus on the things you can control</h4><p>It feels terrible to feel so out of control from all the things we see happening in the world. Everyone processes events in their own way; personally, I clean. When the world feels chaotic and overwhelming, I can at least organize my small little corner of the world. Maybe it’s my work area, or my inbox. Clean that smudge on the door that I haven’t bothered with, or dust under the couch where I haven’t been. I’m talking to a sewing factory to see if they can make masks from e-commerce defects. I’m placing orders with small businesses that I love who’s revenue has been cut off. Will any of it matter? Maybe not. Is it an over reaction? I hope so. But one thing is <em>certain. </em>It makes me feel better, and more able to face each day and support those around me.</p><h4>Think Long Term</h4><p>Using specific time frames for when things will return to normal is not helpful. If you tell yourself, “this will be over in two weeks”, you’re setting yourself up for a new level of disappointment and fear if the situation isn’t improved or continuing to worsen. The mindset you want is one of acknowledgment, short term pessimistic realism, and long term optimism. “Yes, this is painful. We don’t know when it will end. It may get worse before it gets better. But it <em>will</em> get better”. For POWs, this shift in mindset has been described as the difference between life and death. When the promised “this will be over by…” dates come and go, prisoners give up hope and simply stop trying to survive. We don’t know when, or how bad it will get first. But it <em>will</em> get better eventually. Your attitude plays a big role in your outcome.</p><h4>Find the small pleasures</h4><p>We all know that life is fragile, and change comes swiftly when it does. In the midst of all that is terrible or uncertain, I will try to enjoy the moments of beauty that I am fortunate enough to have access to. There is a breeze coming through the window as I type this, and it is true, and good.</p><h4>Terrible things can have unexpected positive results</h4><p>I once had an employee who was miserable. They were diligent and put in strong effort, but their results were middling at best, the work was just not a match for them. Worse, they were prone to angry outbursts that were dragging moral down for our 8 person team. They would be shouting in another room, and the whole office would go uncomfortably quiet, like children of a bad marriage. When I fired them, it was emotionally charged, dramatic, and terrible.</p><p>I ran into them a year later, and approached them warily to say hello. They laughed, “getting fired that day was the best thing that ever happened to me.” They’d been stuck in a rut and unable to see a way out; they were working for me out of momentum and a sense of obligation. Once the cycle was broken, they’d restarted their career on a different path and were doing work they loved, and were good at.</p><p>Neither of us could have predicted it, but it turned out surprisingly well. That’s happened to me a couple of times, actually.</p><p>I’m not suggesting that lost jobs are a good thing, but I will attempt to remain open to the fact that the future is truly unknowable, and that works equally for things that seem immediately bad and good.</p><h4>The world is particularly open to ideas right now</h4><p>People close to me already know my belief that everything is negotiable. That is true to a magnificent degree right now, where we’re seeing monthly payments forgiven on mortgages, barriers lowered<em> </em>for loans, and hospitals accepting donations of home-sewn masks (and sterilizing them before use, I’m relieved to learn).</p><p>The world is especially open to radical ideas in times like these, when things are obviously breaking or broken. People have less to lose, because so much is already being lost. The world is reorganizing itself, and there will absolutely be people who pitch in to help (not profiteer) and establish themselves in the new configuration. Personally, I would like to be one of them.</p><p>Good people will be out of work through factors outside of their control. Some of them will join startups and go on to change the world. It will be the most rewarding experience of their professional lives, and this will be part of the founding story they tell for the next ten years.</p><p>That’s what’s on my mind. Long term optimism, near-term realism. Focus on what you can control. Find the beauty between the lines, and find out how you can help.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d086d81f5e19" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Projecting Revenue]]></title>
            <link>https://dynamicdynamics.medium.com/projecting-revenue-3f7545d5c888?source=rss-b2c510d8fb84------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f7545d5c888</guid>
            <category><![CDATA[investing]]></category>
            <category><![CDATA[predictions]]></category>
            <category><![CDATA[revenge]]></category>
            <dc:creator><![CDATA[James Marks]]></dc:creator>
            <pubDate>Thu, 20 Sep 2018 18:45:31 GMT</pubDate>
            <atom:updated>2018-09-20T18:45:31.589Z</atom:updated>
            <content:encoded><![CDATA[<p>Everyone wants to predict future sales, but there isn’t general consensus on the techniques that should be used. Because there’s generally a seasonal curve to the businesses I’ve run, I’ve developed a habit of using the portion of the period that’s already complete, coupled with data from the previous period and how that period ended. Let’s call this the <em>Proportional Method</em>, and it works like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*oZkYYli0zNzMNPZJMqFDoQ.png" /></figure><p>By cross-multiplying, we come up with a formula as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kVbCWLAmN8DMF3lQQsVmRA.png" /></figure><p>So if, at the end of Q1 we want to predict sales for the year, our formula would look like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/1*2ljdDWHF4_WTWjZYZ_L_Lw.png" /></figure><p>And our cross-multiplication gives us this to solve:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*jsiS7eIwnX4gt-_UtSjiRA.png" /></figure><p>So, if you’re Q1 2016 sales were $1.5M and 2016 Total sales were $9.3M, and Q1 2017 sales were $2.8M, you’d get the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*dkHTYZ1tlQ6oDluVIBorFw.png" /></figure><p>Again, by cross-multiplying, we get this problem to solve:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*KceCHLQxGKRIL_fZBKdPWw.png" /></figure><p>So, in this case, our projection for 2017 would be $17,131,579, or $17.1M.</p><p>Of course, the larger the sample period, the more accurate the projection is going to be. In January, with 11 months of the year unknown, small variances will have an outsized effect. Let’s take a look and see how the projection becomes more accurate as the sample size increases. The following are projections based on available data at the time:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*LfRRM_Wj6c4qnY2OaCs73g.png" /></figure><p>As you can see, projections made in the first half of the year are +/- 50%, but projections made in the 2nd half of the year are generally within about 10%.</p><p>The question is, is there another variable we can introduce that accurately predicts the deviation of this model? I haven’t found it yet, but I’m definitely on the lookout.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f7545d5c888" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Run the mountain, not the hill.]]></title>
            <link>https://medium.com/james-marks-on-life-and-business/run-the-mountain-not-the-hill-c2b269249c89?source=rss-b2c510d8fb84------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2b269249c89</guid>
            <category><![CDATA[determination]]></category>
            <category><![CDATA[running]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[James Marks]]></dc:creator>
            <pubDate>Mon, 08 May 2017 23:18:21 GMT</pubDate>
            <atom:updated>2017-05-09T00:14:15.093Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*w_yWoCx0fX67_W48y01GUw.jpeg" /><figcaption>Modified from<a href="https://www.dkngstudios.com/store/el-pulpo"> DKNG’s El Pulpo art print.</a></figcaption></figure><p>If I had one word to describe my emotional state at VGKids between 2002 and 2007 it would be <em>desolation</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/1*7mbubwN2cbuHSPmZw0ODig.png" /></figure><p>As long as I am being melodramatic, let me say that the 2nd definition really speaks to me, “<em>anguished misery or loneliness</em>”. I was young and inexperienced. 40% year-over-year growth meant I was continually in over my head. Every day felt like a new but inevitable disaster. I was learning, but the staggering mountain of what I didn’t know made the business feel like quicksand, where every step to advance the company took us further into the pit.</p><p>Of course, VGKids wasn’t dying, and neither was I. Both myself and VGKids are alive and healthy ten years later. But it did <strong><em>feel</em></strong> that way sometimes, and it felt that way often enough that it colors my memory of the era.</p><p>Here is a scene that captures its essence: On a sweltering, humid Michigan summer day, we are standing next to a 500º conveyor oven that dries t-shirt ink. A team of three has been working flat-out for eight hours, printing hundreds of two sided t-shirts for a local fair. The fronts are done and look good, and we are just finishing the backs. For the printers out there, it’s black shirts with white-flash-white-flash-red, which means the shirts are on press for three rotations and we are standing around 1/3 of the time. It is agonizingly slow work, but we are almost done, barely scraping in under the deadline. The festival is starting the next morning.</p><p>As the last shirt comes off the conveyor, sweat soaking through our clothes, we pause to look at the last shirt closely and relish in the pride of a job well done. Why is it that we paused at the <em>last</em> shirt, and not the first? We stand back to take it all in, and someone says, “That’s not how you spell <em>experience</em>”.</p><p>Goodbye, profit.</p><p>Goodbye, reputation.</p><p>Goodbye, morale.</p><p>You know how the last 100 miles of a roadtrip seem to stretch on forever? It’s because our attention is focusing on the goal. We are fixating on being stuck in the car and have a heightened awareness of every pain, every discomfort we are experiencing, fixating on the fact that we are <em>here</em> and not <em>there</em>. Goals are good, but not if they are making us miserable because we are in the process of achieving them. If you are on the freeway barreling towards home, what is gained by our anticipation and impatience? Why were we not this uncomfortable the entire time?</p><h4>The difference between the first 2,900 miles and the last 100 is our mindset.</h4><p>On the first 2,900 miles, we have an expectation of driving for days on end, so we let our attention wander. For the last 100, we have razor sharp focus on getting home. In these moments, that focus is exactly what makes our pain accute.</p><p>In the roadtrip of running a business, that fixation on the goal can cause so much misery that we quit under the pressure. It is a shame, because there is not a correlation between difficulty and success. If anything, difficulty tracks positively with success. Your business is making you miserable because at least some part of the business is working. If customers are angry, that’s proof that you can <em>get</em> customers!</p><p>I never put it together that my mindset was creating at least some of my misery at VGKids. I figured it out years later while I was running up a mile-long hill that my body thought was<em> total bullshit</em>.</p><p>I would try to run this hill regularly, and what I eventually figured out was that if I focused on running up the hill, I’d quit partway up. It was just too hard. The trick that worked for me was imagining the top of the hill to be a magnitude farther away than it actually was. I would pretend I was not running to the top of the hill by my house, instead I was running to the opposite coast. I was crossing the Rocky Mountains. I was running Kilimanjaro. The hill I was on right now was just a foothill on the path I was actually running. So when I got to the top of this mile-long climb, well hell. That was <em>easy</em> compared to what I was bracing myself for.</p><p>I’ve heard from other distance athletes that it doesn’t matter too much what you actually think about. The thing that makes the trick work is thinking about literally anything other than the finish line<em>. </em>You have to put yourself in a mental state of acceptance. You have to be at peace with the fact that this hard thing you are doing is going to be happening for a long time, so settle in.</p><p>And that “settle in” mentality needs to be matched by a strong belief that you <strong><em>will</em></strong> complete the task in the end. Not soon, so let’s not think of it. But someday, we will achieve our goal.</p><p>The people with this mindset, the people who are running a mountain so ignore the hill; those are the ones that make it.</p><p>And if you are running a mountain, the hill of redoing the monster pile of shirts you just finished ruining doesn’t seem like that big of a deal.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2b269249c89" width="1" height="1" alt=""><hr><p><a href="https://medium.com/james-marks-on-life-and-business/run-the-mountain-not-the-hill-c2b269249c89">Run the mountain, not the hill.</a> was originally published in <a href="https://medium.com/james-marks-on-life-and-business">The Twelve-Year Overnight Success</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My father.]]></title>
            <link>https://dynamicdynamics.medium.com/my-father-4be6bad78db3?source=rss-b2c510d8fb84------2</link>
            <guid isPermaLink="false">https://medium.com/p/4be6bad78db3</guid>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[James Marks]]></dc:creator>
            <pubDate>Fri, 21 Apr 2017 16:54:44 GMT</pubDate>
            <atom:updated>2017-04-21T16:54:44.713Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve spent most of my life thinking my father and I didn’t have that much in common, and only recently realized how wrong I was.</p><p>What I’ll remember my father for is his patience over the course of years. His kindness and generosity. His steadiness and loyalty.</p><p>Those qualities created the fabric of my youth. Houses, towns, and characters came in and out of frame, but my father was constant.</p><p>And the qualities I strive for myself- kindness, equality, patience, loyalty; I inherited those largely from him.</p><p>I’ve spent most of my life thinking my father and I didn’t have anything in common, but now I know that we had <em>everything</em> in common.</p><p>Everything that matters, anyway.</p><p>If he were here today, I would tell him thank you. For raising me. For teaching me morals. For making me strive to do great things. And just for being there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4be6bad78db3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Value of Now]]></title>
            <link>https://dynamicdynamics.medium.com/the-value-of-now-f04810e18b21?source=rss-b2c510d8fb84------2</link>
            <guid isPermaLink="false">https://medium.com/p/f04810e18b21</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[James Marks]]></dc:creator>
            <pubDate>Tue, 29 Nov 2016 22:55:24 GMT</pubDate>
            <atom:updated>2016-11-29T22:55:24.158Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/885/1*jaIif1jzU3trSWKFlnWOqQ.jpeg" /><figcaption>Modified from <a href="http://www.dkngstudios.com/blog/2012/10/09/the-black-keys-phoenix-az-poster/">DKNG’s poster for Black Keys</a></figcaption></figure><p>When I started writing earlier this year, it was supposed to be a kind of therapy. Yes, I had also hoped to raise my profile, help others, and ultimately benefit my businesses (<a href="https://entrepreneurs.maqtoob.com/two-places-at-once-double-your-time-double-your-potentia-70edebe6f0a4#.y1uap9jd8">one motion, many actions!</a>), but personally, I had hoped it would help me process what I was experiencing.</p><p>I spent the first handful of years at Whiplash re-treading ground I had covered before– getting from Zero to $1M annual revenue. That didn’t make it easy, but it was familiar. Whiplash is somewhere else now– we’re on track for nearly $7M in 2016 and while that’s not huge, it’s new for me. We have different types of problems. Different types of stress. Different requirements placed on us.</p><p>As a writer, one thing I’ve learned is that it’s easier to write about the past than the present. Safer. The participants get less squeamish to have the spotlight swing their way, myself included. But by focusing on the past, the value for me personally is lower. Writing has become a chore, something I do for others. So let’s try writing about this week. The intimidating and ever-evasive <strong><em>Now</em></strong>. Or at least now<em>-ish</em>.</p><h3>Diving Deep</h3><p>I’ve been consumed for the past several days getting a feature to work. We’ve got a button in Whiplash called, “Publish Inventory”, and it updates the inventory level on a webstore for a group of items to include product that’s on it’s way to the warehouse, but hasn’t arrived yet. It’s critical for allowing pre-orders, which means it’s critical for some of our largest clients. At some point a few months ago, it stopped working for a single store. Some items would be updated, and some wouldn’t. And no matter how many times you hit “Publish Inventory”, the items that originally wouldn’t update, would <strong><em>never</em></strong> update. Support handles emails about it regularly, where they (ok, <em>me</em>) go in and update the items one at a time, which works.</p><p>It’s taken months to not-fix because the issue lies somewhere between Whiplash and the store. Whiplash developers are pretty sure it’s a problem with the store. The webstore’s developers are pretty sure it’s a problem with Whiplash. So we grind to a standstill, because actually proving where the problem is takes developer resources, which are in high demand on both sides. And if you’re pretty sure it’s the other guys fault, you’re in no rush to put those hours in.</p><p>The user, who has a clearly defined problem, gets stuck in the crossfire of the two teams.</p><p>The bug is valid, but here’s a question: why am I letting this consume my days? This has been &gt; 85% of my time for something like 4 business days. Is that a job for the CEO? Once the customer described the problem, why didn’t I hand it over to the dev team? The answer is a blend of my strongest personality traits:</p><ul><li>controlling (micro-managing the fix)</li><li>tenacious (I come back to it hour after hour, day after day)</li><li>empathetic (I relate with the customer to have it “just work”)</li><li>narrowing focus during times of stress (Q4 in eCommerce is nuts; working an elusive bug takes my mind off it)</li></ul><p>I make no claim that those traits are positive, although I think some of them probably are. In the last few days, and countless other similar episodes, they’ve combined in a way that’s a hindrence. I can’t really defend spending such a huge amount of time on the problem, and at the expense of other activities. What’s become clear is that we’re at a scale where we need to hire someone to ensure software quality.</p><p>But we haven’t hired that person yet, so I’m doing what I’ve always done:</p><ul><li>Fumble through doing a task myself</li><li>Automate as much of it out of existence as I can</li><li>For what’s left, make a process I can hire and train someone to do.</li></ul><p>That pattern has defined my career, and I’m outgrowing it. To be honest, the tasks I’m fumbling through are just plain harder than before, and they require specialists. They are nuanced, and they take <em>time</em>.</p><p>I don’t write my own legal docs (anymore). I don’t do my own bookkeeping (anymore). I don’t run our sales desk (anymore). I don’t train warehouse staff (anymore). And soon, I won’t be our quality assurance engineer.</p><p>But rather than performing those tasks myself and then handing someone a task that I understand better than anyone, in the future, it will be the other way around. I’ll be hiring specialists, and they’ll be teaching me how to evaluate their work.</p><p>It scares the hell out of me, and leaves me feeling hollow.</p><p>But intellectually, I know that hollow feeling is the vacuum created from a purge. And I know that vacuum will attract a new wave of tasks that are currently going undone. The tasks that are born from the vacuum– or rather <em>hiring</em> the people who will perform them– are what will take us where we want to be.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f04810e18b21" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Two Places at Once: Double Your Time, Double Your Potential]]></title>
            <link>https://dynamicdynamics.medium.com/two-places-at-once-double-your-time-double-your-potentia-70edebe6f0a4?source=rss-b2c510d8fb84------2</link>
            <guid isPermaLink="false">https://medium.com/p/70edebe6f0a4</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[James Marks]]></dc:creator>
            <pubDate>Wed, 26 Oct 2016 21:06:31 GMT</pubDate>
            <atom:updated>2016-10-27T16:06:47.534Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*uJdjZb6O--QFoVtZ4AJ94g.jpeg" /><figcaption><a href="http://mariannaraskin.com/">Modified Tame Impala poster by Marianna Raskin</a></figcaption></figure><h3>At some point, there’s a hard limit on what we can accomplish in life, purely through the time it takes to master a skill compared to our time on earth.</h3><p>If we’re going to accomplish the things we want, we don’t have time to dedicate to each task in isolation. Some things are obvious: taking a call while walking to work. Hanging out with a friend while working out. Folding laundry while watching a show.</p><p>For the same reason we multi-task throughout the day, we have to align our life goals so we’re multi-tasking in the big picture, too. Time should never be spent working on a task that doesn’t satisfy at least two goals, preferably three or even 4.</p><p>Being an entrepreneur lends itself to this: even at the dullest moment, you aren’t just answering email, you’re answering email <em>while building equity</em>. But that’s setting the bar too low! Better would be: writing<em> documentation</em> to respond to a customer in a way that will prevent future emails while building equity.</p><p>One step further: <em>training someone</em> to write documentation so <em>they</em> can respond to an email while <em>you</em> build equity. That’s how you get ahead.</p><p>On one hand, it’s hard and slow. It’s <strong>absolutely</strong> more work up front. This is a sacrifice-now-win-later situation. It takes time to start seeing the efficiency gains. But I promise those benefits are real.</p><p>Do you need to be an entrepreneur for big picture multi-tasking? No way.</p><p>Whatever you spend your time doing, you should be making something. Maybe it’s a game you want to make that’s also getting turned in as a school project. Maybe it’s song lyrics that satisfy your english requirement. Or if you’re like me, building equity in a company while writing mountains of support emails. All three of those people are doing the same thing: building <strong>assets</strong> <em>at the same time</em> as performing the task at hand.</p><p>An asset is defined as:</p><blockquote>property owned by a person or company, regarded as having value and available to meet debts, commitments, or legacies</blockquote><p>When I read that, my mind goes straight to physical objects for some reason– real estate, cars, etc. Let’s make sure we’re thinking about <em>intellectual</em> property also, and not just physical property. Promotional material that lands sales. Training videos that increase customer satisfaction and efficiency. Software to prevent anyone from having to perform whatever-the-hell task it is again.</p><p>Successful people have figured this out. They know that to get ahead, they must accomplish <em>many actions with one motion</em>. The beautiful thing is this: it’s your life and you get to pick the goals. Picking goals that compliment each other is part of the game.</p><p>When I was in my early 20&#39;s and VG could barely pay its own rent let alone mine, I needed to work a regular job. Total pain, but there it was. I was broke and living in my girlfriend’s house. I was building the company, but I couldn’t just coast off my girlfriend’s 9–5 while I played “business guy” all day at a company with zero employees, zero capital, and a similar amount of revenue. At the very least, I was going to pay my share of the bills. I got a job monitoring alarm systems, which I’d heard about as having a ton of free time. I couldn’t believe it was real, it was so perfect: I was making $10 an hour (that was alot at the time… ) and an average 8 hour shift included no less than 5 hours of waiting for something to happen. Three things happened the year I worked there:</p><ul><li>I taught myself JavaScript from online tutorials, which later evolved to becoming a programmer full time.</li><li>I did sales and marketing for VGKids, which eventually got big enough I had to quit the alarm company.</li><li>I beat Tony Hawk’s Pro Skater 2.</li></ul><p>I was hustling hard, but because of the “day job” I had chosen to pay the bills, I had So. Much. Time. Too much, in fact. Because my goals were in alignment, I was screwing around with the <em>extra</em> time I had playing video games. To this day, Tony Hawk’s Pro Skater 2 is the only video game I’ve ever beaten, and it happened while I was building a company that would later have 15 employees and do $1.5M a year in sales.</p><p>Hell, because of the work I put into VGKids, stemming from those early days at the alarm company, I even got to meet Tony Hawk last year. (he tolerated my lame small talk with a cool charm I’d be happy to achieve 10% of).</p><p>To be fair, I think the PC I was playing on had a glitch and the game was easier than it should have been<em>. </em>But still, I put <em>hours</em> into that game. While learning JavaScript. While building a company. While getting paid a decent wage.</p><p>I asked my brother, Adam, years ago why his life seemed easier than mine, and he gave me a simple answer that’s stayed with me ever since: One Motion, Many Actions.</p><p>Thankfully I got the advice when I did, and not a moment too soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70edebe6f0a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working on What Matters: 20% Today]]></title>
            <link>https://medium.com/james-marks-on-life-and-business/80-best-possible-future-705686981675?source=rss-b2c510d8fb84------2</link>
            <guid isPermaLink="false">https://medium.com/p/705686981675</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[self-employment]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[self-employed]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[James Marks]]></dc:creator>
            <pubDate>Fri, 21 Oct 2016 21:45:48 GMT</pubDate>
            <atom:updated>2016-10-26T21:00:24.221Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*E537wHu3ArDh1wIErrDczQ.jpeg" /><figcaption><a href="http://www.dkngstudios.com/work/gig-posters/">Modified from DKNG’s Jack White gig poster</a></figcaption></figure><h4>Part 1: Defining What Matters</h4><p>As professionals, we have quite a bit of latitude in how we spend our time. Sure, we’re “working” during work hours. But is the time we spend moving us closer to our goals in the most efficient means possible? Simply having <em>worked</em> is not the goal– but it’s easy to get caught in a trap of treating it that way. You rarely get extra credit for how hard you worked– what matters is what you <em>accomplished</em>.</p><p>Let’s assume for a moment, that the goal itself is clear. Let’s use a metaphor of marbles in a box– our goal is to move all of the marbles from one box into a second box.</p><p>We could spend our work hours in any variety of time-filling ways:</p><ul><li>Moving marbles one a time</li><li>Looking for a container to scoop multiple marbles at once</li><li>Taking each marble out, cataloging its position in the box, and organizing into a series of bins for later placement in the second box</li><li>Picking the box up and pouring it into the second box</li></ul><p>Anyone in the middle of this operation, when asked what they were doing, would reply with a variation of the same answer: “moving the marbles into the 2nd box”. When they go home at the end of the day, they’ll all have worked hard.</p><p>Each of the marble moving techniques has its pro’s and con’s, and what it comes down to is A) their understanding of <em>why</em> they are tasked with moving the marbles, and B) their comfort with risk. Maybe the person cataloging each marble is a time-waster, or maybe, because they don’t know <em>why</em> they’re moving marbles, they’re taking every precaution not to screw the project up. They have a good imagination (“what?! you don’t know where each marble was originally?!”) and a low comfort with risk, and it will take them all day to get the task done.</p><p>On the other hand, the person who just picks the box up, dumps it, and breaks the box down for recycling, they sure got the job done quickly. But did they know the marbles scratch easily and are now ruined? Depending on the context, they could be a master of efficiency or a master marble-ruiner.</p><p>They both have excellent intentions, and they are both hard workers.</p><p>As we learn a new job, one of the things we’re doing is building a mental model of the <em>context</em> of the job. What <strong><em>matters</em></strong> about this job? Speed? Quality? Not interrupting the boss? Great organizations clearly define what matters, so you’re not left guessing. In any of the hundreds of decisions you make each day, you know what matters to your boss, and you can make sure you hit the organization’s priorities.</p><p>Bosses that <em>don’t</em> clearly define what matters are left shocked and confused at their employee’s actions. “They spent <em>how</em> long moving those marbles?! Those idiots! I just wanted the box they were in!”</p><h4>Part 2: Urgent vs. Important</h4><p>Assuming that we know what matters about our job, we’re still not out of the woods. We have a myriad of tasks placed on us, and an equal number of paths available to accomplish those goals. To help us navigate our options, Eisenhower created a Decision Matrix. It looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*Lr8EU2UxjWB0cmK8ZO-tfg.png" /></figure><p>The more time we spend on Quadrant 1, the less time we have available to spend in Quantrant 2. When I look back on the time I’ve spent at Whiplash and VGKids, it’s almost <em>exclusively</em> Quadrant 1, with quick gulps of air in Quadrant 2. Many of us live in what’s called the Tyranny of Urgent, and it won’t stop until we decide to stop it, and spend our time in Quandrant 2 instead.</p><p>So far I’ve worked in small companies where Quadrant 3 isn’t as much of an issue, but if the popularity of Dilbert is any indicator, there’s a massive amount of time being lost there worldwide.</p><p>As I fight my way through this myself, I found a new lense to look through:</p><blockquote>Optimize for the best possible future while continually improving the present.</blockquote><p>We can’t shorten that to just, “Best Possible Future”, because if we don’t respect today’s needs, we won’t be here tomorrow. But we can’t ignore the future, or we’ll just be skipping from one emergency to the next in our own work-version of Dante’s Inferno. So how do we balance those needs?</p><p>I propose a bastardization of the 80/20 Rule:</p><p>20% of our energy should be dedicated to today’s crisis, while 80% of our time should be spent on ensuring the best possible future. If we can keep today’s <em>and</em> tomorrow’s needs in balance, the life we want to lead will come into place around us.</p><figure><a href="http://eepurl.com/b3ejrL"><img alt="" src="https://cdn-images-1.medium.com/max/900/1*Jr38rJkqo4VmWxXUCmE9Wg.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=705686981675" width="1" height="1" alt=""><hr><p><a href="https://medium.com/james-marks-on-life-and-business/80-best-possible-future-705686981675">Working on What Matters: 20% Today</a> was originally published in <a href="https://medium.com/james-marks-on-life-and-business">The Twelve-Year Overnight Success</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Silent Assumption Destroying My Business]]></title>
            <link>https://dynamicdynamics.medium.com/a-very-dangerous-assumption-26a7fd6e95b8?source=rss-b2c510d8fb84------2</link>
            <guid isPermaLink="false">https://medium.com/p/26a7fd6e95b8</guid>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[James Marks]]></dc:creator>
            <pubDate>Thu, 11 Aug 2016 00:11:14 GMT</pubDate>
            <atom:updated>2016-10-26T21:06:57.022Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*_LUMacmYfIZxNu2oB56_-g.jpeg" /><figcaption><a href="http://insidetherockposterframe.blogspot.com/2015/09/ryan-mowry-chelsea-wolfe-wovenhand.html">Modified from Ryan Mowry’s art for Chelsea Wolfe &amp; Wovenhand</a></figcaption></figure><p>When Sean and I started Whiplash, we generally put off as many things until later as we could. We knew we’d eventually use barcodes to scan all of the items as they shipped to ensure accuracy, but it could wait. We knew we’d bill for storage based off the dimensions of products. But to start, we could just count pallets. And, we knew we would have an automated billing system. But when we had 2 clients and the Whiplash app was just a script to print invoices, we needed a quick &amp; dirty way to get paid.</p><p>That turned out to be Net 30, where we’d just create a generic invoice in Quickbooks. We’d summarize what we’d done for the client, they’d send us a check, and we could “kick the can” of automated billing down the road a little further.</p><p>Part way through the first month, we discovered a flaw with that plan: we buy postage immediately as we ship. With postage making up more than half of what we invoice the client, for us to bill the client $100 at the end of the month, we had to spend $50 of our own money leading up to that. Lending the company $50 wasn’t bad, but it wasn’t long before those loans were a few thousand dollars, and it started getting painful. We were starting a business in the first place because we needed to make money, and here we were actually <strong><em>lending</em></strong> money.</p><p>To keep up with the postage, first we exhausted our own meager bank accounts. Then, we started borrowing money from friends and family. As the company started growing, the problem just got bigger and bigger. We’d borrowed $15k when we maxed out our friends, and suddenly we had a very real problem. Even though we were mildly profitable, we literally could not afford to operate the business we’d started. Traditional lines of credit were out– we’d finally started growing quickly, and didn’t have the history banks want to see.</p><p>I can tell you, it’s a hard spot to be in when you’ve poured your energy into something for a couple of years, pivoted to a model where it’s finally (finally!) showing signs of succeeding, and your bank balance keeps going negative while you scramble to borrow more money or get a client’s check into the bank. Co-founders worry. Spouses worry. Even though you tell everyone it’s ok and show them why you still believe, you worry, too.</p><p>So there was already plenty of stress in the air when our bank balance finally went below zero, and we didn’t have the money to bring it back positive. I remember waking up, seeing the negative balance, knowing we couldn’t do anything about it, and just feeling blank inside. I didn’t tell anyone, I just closed my laptop and took a shower to start my day, wondering what the hell I was going to do. We had a little bit of room on a credit card we could buy postage from. That would buy us a few more days, but then that would be maxed out, too. We wouldn’t be able to buy postage, which means orders would stop shipping. Customers would be affected. And then payroll would come due. And then rent.</p><p>The unrecoverable spiral, where you fail despite still desparately wanting to succeed, was in sight.</p><p>Fundamentally, something was out of whack. Our clients were charging shipping and handling at the time of the sale, so the money existed– the problem was that it was in our client’s bank account, and not ours. Somehow we had to change the flow of money so that we weren’t financing our customers’ businesses.</p><p>By the time I finished my shower, Sean had noticed the empty bank account, too. We got on a call and came to the conclusion that customers would have to pre-pay for their services. We’d have them put a credit card on file, and we’d charge an average week’s worth of services. We’d write the basics of the billing automation, which would spend a client’s account down as we shipped orders for them, and when the client’s account hit zero, we’d automatically bill their credit card for another week. I hammered out the basics of how I saw it working, and Mark jumped in to refine my work and make my prototyped code sane. All the while, as we scrambled to get the programming done, I was convinced that our customers, who were used to having this ‘float’ of shipping charges in their bank account, would freak.</p><p>In fact, I prepared myself for the eventutallity that our customers would leave in droves. I accepted that we’d build the customer base up from scratch again; this time with a group of people who took the new pre-pay style as normal. It was a bitter pill, but we literally could not continue to operate the way we were.</p><p>As the week ended and the billing features were nearly ready for release, we sent an email to customers notifying them that the change would take effect in a few days, at the start of the new month. Since we couldn’t actually survive that long, I reached out to a couple of our larger clients and asked for an advance payment against the invoice they’d be receiving in a few days. Thankfully, we’d built up enough trust by then that they were willing to keep us afloat.</p><p>So with some fumes to live on, the announcement email went out. The one I was pretty sure would cause everyone to leave. The unanimity of the response shook me, and it still does.</p><p>Every single customer was fine with the advance payment. One customer– <em>one</em>– asked if they could be delayed a few months, which we gladly allowed. As the pre-payments started coming in, our bank balance recovered over the course of the week. Plenty of things were still wrong with our company, but we were distinctly alive and viable.</p><p>I had made an assumption. I <strong><em>assumed</em></strong> I knew how our customers would react, and I represented that assumption to myself and others as truth. As a result, we put off solving the billing problem for months and endangered our company. I can’t stress that enough: <em>Do not confuse assumptions with the truth</em>. We have to recognize assumptions for what they are and convert an <em>opinion</em> into a <strong>hypothesis</strong>. A hypothesis recognizes the unknown nature of our situation inherently; a hypotheses begs to be tested for <strong>the</strong> truth, not just the emotional truth inside our head. A hypothesis reforms our statement as a query, and gives us the opportunity to objectively inspect, confirm, or deny. When we are driven by what we’ve learned over over what we think we know, that’s when the path to success has the opportunity to be revealed.</p><p>The path to success is not paved with stones that say, “I think…”, but uncovered with strokes of a broom, each of which start with the words, “I wonder…”.</p><p>And the path may not look at all like we thought it would.</p><figure><a href="http://eepurl.com/bXAzCL"><img alt="" src="https://cdn-images-1.medium.com/max/900/1*KY0DFN3pyqX0BevSQVlL9w.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26a7fd6e95b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>