<?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 Elad Lebovitch on Medium]]></title>
        <description><![CDATA[Stories by Elad Lebovitch on Medium]]></description>
        <link>https://medium.com/@eladleb?source=rss-660bdb5d6997------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*AvIu3uEoByG8XEej.</url>
            <title>Stories by Elad Lebovitch on Medium</title>
            <link>https://medium.com/@eladleb?source=rss-660bdb5d6997------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:39:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eladleb/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[Should Indies Attend Pocket Gamer Connects?]]></title>
            <link>https://medium.com/@eladleb/should-indies-attend-pocket-gamer-connects-b22941153fe6?source=rss-660bdb5d6997------2</link>
            <guid isPermaLink="false">https://medium.com/p/b22941153fe6</guid>
            <category><![CDATA[unity]]></category>
            <category><![CDATA[mobile-games]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Elad Lebovitch]]></dc:creator>
            <pubDate>Thu, 31 May 2018 10:42:36 GMT</pubDate>
            <atom:updated>2018-05-31T10:46:32.899Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently had the opportunity to attend a games conference (thanks to <a href="https://www.facebook.com/groups/IndieGameDevs/">Indie Game Developers</a>).<br>We have a very small indie studio (2 guys) and are about to launch our first mobile game (exciting!).</p><p>Since it’s half way across the world for us (Tel-Aviv to SF), it wasn’t a no-brainer at all, but we figured we had to meet people who are a part of the industry so we went ahead and booked the tickets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*t9pg2cesp0o3P0gc1PNSnA.png" /></figure><p>We actually had a great time so I wanted to share my thoughts and some tips for going to gaming conventions.</p><h3>Who are you going to meet?</h3><p>Gaming conventions have a lot of different people and roles. Publishers, ad-mediation services, developers, designers, gamers, students… Before putting your time and money to attend, you’d best figure out who you’d like to meet and what would make it a successful convention for you.</p><p>For us at Banditos, it was meeting publishers in person and getting feedback on our current version of the game (5 <a href="https://www.facebook.com/5heroes/?ref=medium">Heroes</a>).</p><h3>What should you prepare before going?</h3><p>Your game should come first! That’s what most of the people would like to see (as long as they aren’t trying to sell you something). I’d recommend making a <strong>solid <em>demo</em> version</strong> of your game, where it’s easy to reset the data so every new player gets a fresh and solid experience. We used some in-app debug buttons to reset the game after every play-session and it went well.</p><p>For this convention, we also did the whole branding thing. <br>Branded t-shirts, a rollup with our game on it, business cards. We figured that these will help drive the right message to the people we wanted to meet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*dwv7MBaw4fWs57gtfzb_kw.png" /><figcaption>I was so busy coding and didn’t have a chance to get a haircut before traveling</figcaption></figure><h3>What I loved specifically about Pocket Gamer Connects</h3><p>This specific conference is really indie-friendly. You’ve got a system that helps you set meetings with other attendees. You’ve got a couple of events where you show your game to influencers, industry vets, press and publishers and the team that organizes the event sets a friendly and lovely atmosphere.</p><p>There are other B2B conventions, and there consumer (gamers!) focused and some and even a combination of both businesses and consumers. I’d recommend learning more about a convention by looking into the previous year it was held, which is often the best indicator.</p><h3>So… Should you attend Pocket Gamer Connects?</h3><p>If you are an indie dev and would like to get a little more in-depth feedback than likes and comments on your game, I think it’s a great opportunity to see what’s out there. Tickets are mostly inexpensive and there are events across Europe and the U.S.</p><p>Are you an indie considering attending a conference? I would love to hear your thoughts!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b22941153fe6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenges creating the game of Go on Ethereum]]></title>
            <link>https://medium.com/@eladleb/challenges-creating-the-game-of-go-on-ethereum-part-1-30e8de4ffcda?source=rss-660bdb5d6997------2</link>
            <guid isPermaLink="false">https://medium.com/p/30e8de4ffcda</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[go]]></category>
            <dc:creator><![CDATA[Elad Lebovitch]]></dc:creator>
            <pubDate>Sun, 18 Mar 2018 17:08:31 GMT</pubDate>
            <atom:updated>2018-04-15T11:39:37.833Z</atom:updated>
            <content:encoded><![CDATA[<p>Today we’ve finally launched <a href="https://www.ethernalgo.com/">EthernalGo</a>, our first DAPP (decentralized app) running on Ethereum. This DAPP allows people from around the world to play the simple yet so deep game of Go on the blockchain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oJ4Z-GqeBdifJR1rnAnYFw.jpeg" /><figcaption>Finally launched!</figcaption></figure><p>Since creating the game the way we wanted proved to be quite challenging, I wanted to share a bit of our experience developing this smart contract.</p><h3>Challenge #1 — Getting Started with Ethereum:</h3><p>There are many learning resources out there, but there are a few that I think really stand out. I’ve curated a quick list of the important ones.</p><ul><li><strong>Learning solidity:</strong> <a href="https://cryptozombies.io/">https://cryptozombies.io/</a> is by far the best 1st stop. Just go there and go through all available lessons.</li><li><strong>Actual development environment: </strong>Don’t miss out on <a href="http://truffleframework.com/">truffle</a> to help with most of the day-to-day tasks (starting a development node, migrating your code to different networks). It’s pretty solid and nicely maintained.<br>For us, the most helpful tool was the test framework that comes bundled in with truffle and allows for quick automated testing without any UI development.<br>For writing code we used <a href="https://code.visualstudio.com/">VS code</a>, we love it for its flexibility and being so light-weighted.</li><li><strong>Geth Reference:</strong> Eventually you will want to deploy your contracts to a testnet and then the mainnet. <a href="https://github.com/ethereum/go-ethereum/wiki/geth">geth</a> is the official command line interface that can help you do that. While there are others with nice UI such as parity or ethereum wallet (which uses geth), I believe you must start with basics.</li></ul><h3>Challenge #2 — Building a solid web client:</h3><p>We chose to go with react but that’s just based on previous experience with it. Any web stack can work, the main challenge will be to interact with the web3 (the component that communicates directly with the blockchain) successfully.</p><p>Installing <a href="https://metamask.io/">MetaMask</a> is not only helpful for end-users buying kitties, it’s also very helpful for development as you can see your balance, transactions and work with multiple accounts.</p><p>I’d recommend focusing on a single web3 implementation and ironing out the experience of using it.</p><p>Keep in mind that transactions on the testnet and mainnet take much longer than running on a local environment. Make sure you make the effort to notify your users what’s going on and what are they waiting for exactly. For EthernalGo, we used <a href="https://www.npmjs.com/package/react-notify-toast">toast notifications </a>which did the trick.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*XdBwePga2fTrejFnsgfJ9A.gif" /></figure><h3>Challenge #3 — Getting noticed:</h3><p>The days of creating an app and immediately getting noticed were pretty short. After crypto-kitties there were tons of look-alike dapps and it’s getting harder and harder to stand out. Getting noticed will probably cost time, effort and money.</p><p>At the time of this writing, leading crypto-currency sites ask for anywhere between 200 USD to 5000 USD for promotional pieces so take this into account when creating your budget pie.</p><h3>So what’s next?</h3><p>I would love to hear your thoughts and comments on this post and our game. If it’s interesting, please let me know and I’ll be happy to share more in future posts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30e8de4ffcda" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Tips for running effective recurring meetings with Trello]]></title>
            <link>https://medium.com/@eladleb/3-tips-for-running-effective-recurring-meetings-with-trello-2532311cbf98?source=rss-660bdb5d6997------2</link>
            <guid isPermaLink="false">https://medium.com/p/2532311cbf98</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[trello]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[Elad Lebovitch]]></dc:creator>
            <pubDate>Wed, 29 Mar 2017 12:14:39 GMT</pubDate>
            <atom:updated>2017-03-29T12:14:39.949Z</atom:updated>
            <content:encoded><![CDATA[<p>I think that the only thing people <em>hate</em> more than regular meetings is <strong>recurring meetings</strong>. Well, maybe <em>hate</em> is a strong word, but we’ve all heard opinions on how meetings distract us from getting “actual work” done.</p><p>Both in my current position, running the AutoCAD mobile team for Autodesk, and in my previous position as CEO of for-each LTD (which was acquired by Autodesk in 2013), I’ve had to deal with multiple recurring meetings “cluttering” up my schedule.</p><p>Here is what I do to focus on the right stuff during these meetings:</p><h3>Tip #1: Agenda and action items are shared and visible</h3><p>I have a shared <a href="https://trello.com/b/t5NTxkJM/1-1-example">Trello</a> board for each of the recurring meetings. <br>Whether it’s a 1:1 or a staff meeting, I run it using Trello.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*JpFivdW-Y-Db3fsotkCMiw.png" /><figcaption>Example Trello board for 1:1</figcaption></figure><p>The basics are to have these three columns:</p><ul><li><strong>To talk:</strong> Any new topics that require discussion / updates should be in this column. Any participant can add topics to the meeting prior to it or even during the meeting.</li><li><strong>In Progress:</strong> Anything that we said we will do should be here (usually action items and follow-ups). Items in this column always have assigned team members so it’s clear who owns this action item. They also have more elaborate descriptions and the members on the card comment on it as they make progress. We sometimes even use checklists or attachments where it makes sense.</li><li><strong>Reminders:</strong> Anything we are not dealing with right now should go to this column with a due date for a time we need to revisit this item. When the due date arrives we decide if we want to deal with this task now, “snooze” it to a later date or just archive it.</li></ul><p>Having visible agendas and items helps organize your workgroup, whether it’s a 1:1 or a team meeting - it simply drives more productive meetings.</p><h3>Tip #2: Most important items are at the top, but don’t forget what’s In Progress</h3><p>Our time is the most valuable resource we have so the meeting owner must make sure we discuss the most important items first. It’s also great to have some balance between the “heavy” stuff and a few quick updates so we can get the most out of the meeting. We prioritize by putting the most important item at the top and start discussing them.</p><p>When we are done with the “To Talk” column we go over the “In Progress” column to make sure we are still on track with everything we decided we will do. This is the easiest part to neglect, as I’ve seen teams make decisions and never follow-up on them.</p><p>Keeping a visible list of who owns what helps get s*** done.</p><h3>Tip #3: Use sticky items for recurring mission critical updates</h3><p>Sometimes we just need to get a recurring status update of a key effort and steer the ship accordingly.</p><p>Specifically, our team works with <a href="https://library.gv.com/how-google-sets-goals-okrs-a1f69b0b72c7#.m9xxjgq02">Objectives and Key Results (OKRs)</a> and these are usually the most important items we need to discuss on a weekly basis.</p><p>We list specific key results that we want to discuss and keep them sticky (labeling them differently). The card’s owner knows she is expected to give a quick update about this effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/281/1*JZNxY4xzlcWJw7xKimHTZg.png" /><figcaption>Example for key recurring update</figcaption></figure><h3>Final thoughts</h3><p>I personally believe that 1:1 meetings and small team meetings are very important to keep the business headed in the right direction but unless we are intentional about the agenda and following up on the right things, we can end up discussing the wrong stuff and lose focus on what’s really important.</p><p>I would absolutely love to hear how you manage your meetings and any feedback regarding what I’ve shared here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2532311cbf98" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>