<?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 Julien Balmont on Medium]]></title>
        <description><![CDATA[Stories by Julien Balmont on Medium]]></description>
        <link>https://medium.com/@julienbalmont?source=rss-ddafa05f3323------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*mMoZ1psdXVmgdT_X.jpg</url>
            <title>Stories by Julien Balmont on Medium</title>
            <link>https://medium.com/@julienbalmont?source=rss-ddafa05f3323------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:49:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@julienbalmont/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[How to generate a PKCE challenge with PHP ?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/zenchef-tech-and-product/how-to-generate-a-pkce-challenge-with-php-fbee1fa29379?source=rss-ddafa05f3323------2"><img src="https://cdn-images-1.medium.com/max/600/1*ArAmP1Tl1MguQdLGrY0Btw.png" width="600"></a></p><p class="medium-feed-snippet">When you do not use the right functions, PKCE (Proof Key for Code Exchange) can sometimes be a real pain and can result in OAUTH2 attempts&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/zenchef-tech-and-product/how-to-generate-a-pkce-challenge-with-php-fbee1fa29379?source=rss-ddafa05f3323------2">Continue reading on Zenchef’s Tech and Product Blog »</a></p></div>]]></description>
            <link>https://medium.com/zenchef-tech-and-product/how-to-generate-a-pkce-challenge-with-php-fbee1fa29379?source=rss-ddafa05f3323------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbee1fa29379</guid>
            <category><![CDATA[oauth2]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[pkce]]></category>
            <dc:creator><![CDATA[Julien Balmont]]></dc:creator>
            <pubDate>Tue, 15 Oct 2019 06:58:38 GMT</pubDate>
            <atom:updated>2019-10-15T07:08:53.860Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to identify what is listening on port 80 on MacOS]]></title>
            <link>https://medium.com/zenchef-tech-and-product/how-to-identify-what-is-listening-on-port-80-on-macos-88a2129508d1?source=rss-ddafa05f3323------2</link>
            <guid isPermaLink="false">https://medium.com/p/88a2129508d1</guid>
            <category><![CDATA[web-server]]></category>
            <category><![CDATA[command-line]]></category>
            <category><![CDATA[80-port]]></category>
            <category><![CDATA[macos]]></category>
            <category><![CDATA[macos-sierra]]></category>
            <dc:creator><![CDATA[Julien Balmont]]></dc:creator>
            <pubDate>Tue, 26 Dec 2017 13:16:18 GMT</pubDate>
            <atom:updated>2017-12-26T13:16:18.445Z</atom:updated>
            <content:encoded><![CDATA[<p>You may want to launch Apache or Nginx on your MacOS, butn sometimes, port 80 is busy, and your web server won’t server since another application is already listening on it.</p><p>To find the culprit, try on of those three commands, depending on your version of MacOS or the kind of port you’re trying to search for.</p><pre>lsof -n -i4TCP:80 | grep LISTEN<br>lsof -n -iTCP:80 | grep LISTEN<br>lsof -n -i:80 | grep LISTEN</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88a2129508d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zenchef-tech-and-product/how-to-identify-what-is-listening-on-port-80-on-macos-88a2129508d1">How to identify what is listening on port 80 on MacOS</a> was originally published in <a href="https://medium.com/zenchef-tech-and-product">Zenchef’s Tech and Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to kill and restart the Touch Bar / Control Strip on the new MacBook Pro ?]]></title>
            <link>https://medium.com/zenchef-tech-and-product/how-to-kill-and-restart-the-touch-bar-control-strip-on-the-new-macbook-pro-b77e97c11d03?source=rss-ddafa05f3323------2</link>
            <guid isPermaLink="false">https://medium.com/p/b77e97c11d03</guid>
            <category><![CDATA[terminal]]></category>
            <category><![CDATA[touch-bar]]></category>
            <category><![CDATA[pkill]]></category>
            <category><![CDATA[macbook-pro]]></category>
            <category><![CDATA[controlstrip]]></category>
            <dc:creator><![CDATA[Julien Balmont]]></dc:creator>
            <pubDate>Tue, 12 Sep 2017 10:42:15 GMT</pubDate>
            <atom:updated>2024-09-16T13:28:50.098Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*GC1BvOSkEE6NkEltNNxbZg.png" /></figure><p>If ever your Control Strip starts to bug / fail, there’s an easy way to restart it</p><p>Open your terminal, and copy paste the following :</p><pre>pkill &quot;Touch bar agent&quot;;<br>killall &quot;ControlStrip&quot;;</pre><p>You may have to sudo the command, in this case :</p><pre>sudo pkill &quot;Touch bar agent&quot;;<br>sudo killall &quot;ControlStrip&quot;;</pre><p>For more recent versions of MacOS (Sonoma, Ventura)</p><pre>sudo pkill TouchBarServer;<br>sudo killall &quot;ControlStrip&quot;;</pre><p>You’re good to go now :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b77e97c11d03" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zenchef-tech-and-product/how-to-kill-and-restart-the-touch-bar-control-strip-on-the-new-macbook-pro-b77e97c11d03">How to kill and restart the Touch Bar / Control Strip on the new MacBook Pro ?</a> was originally published in <a href="https://medium.com/zenchef-tech-and-product">Zenchef’s Tech and Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to upgrade your version of PHP to 7.0 on macOS Sierra]]></title>
            <link>https://medium.com/zenchef-tech-and-product/how-to-upgrade-your-version-of-php-to-7-0-on-macos-sierra-e1bfdea55a63?source=rss-ddafa05f3323------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1bfdea55a63</guid>
            <category><![CDATA[php7]]></category>
            <category><![CDATA[homebrew]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[macos-sierra]]></category>
            <dc:creator><![CDATA[Julien Balmont]]></dc:creator>
            <pubDate>Mon, 16 Jan 2017 08:40:48 GMT</pubDate>
            <atom:updated>2017-11-17T08:24:59.571Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*W6E46H-EJJP-PNExdWEaXQ.gif" /></figure><p>Usually, with a fresh version of macOS Sierra, you get a PHP 5.6 installed.</p><p>You’ve got two options: <strong>brew</strong> or <strong>curl</strong> install</p><h3>Brew</h3><pre>brew update &amp;&amp; brew upgrade<br>brew tap homebrew/dupes<br>brew tap homebrew/versions<br>brew tap homebrew/homebrew-php<br>brew unlink php56 <br>brew install php70</pre><pre>You might get an error if PHP 5.6 has not been installed by brew previously, but don&#39;t worry, you can simply continue</pre><h3>CURL</h3><pre>curl -s http://php-osx.liip.ch/install.sh | bash -s 7.0</pre><p>You can replace 7.0 by 7.1 in the command above to get version 7.1 of PHP</p><p>If the output of php -v still doesn’t echoes the version 7, simply type this command to update your path, it should do the magic, as stated on <a href="https://php-osx.liip.ch/#faq">php-osx.liip.ch website</a></p><pre>export PATH=/usr/local/php5/bin:$PATH</pre><p>Apparently, the env var might have changed depending on your environment.</p><p>If the one above doesn’t work, you may try (thanks <a href="https://medium.com/u/4786e820c907">Robert Borghesi</a> for your comment) :</p><pre>export PATH=”$(brew — prefix homebrew/php/php70)/bin:$PATH”</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1bfdea55a63" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zenchef-tech-and-product/how-to-upgrade-your-version-of-php-to-7-0-on-macos-sierra-e1bfdea55a63">How to upgrade your version of PHP to 7.0 on macOS Sierra</a> was originally published in <a href="https://medium.com/zenchef-tech-and-product">Zenchef’s Tech and Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to improve your productivity on Slack with the ALL UNREADS button]]></title>
            <link>https://medium.com/zenchef-tech-and-product/how-to-improve-your-productivity-on-slack-with-the-all-unreads-button-be1fc72430fe?source=rss-ddafa05f3323------2</link>
            <guid isPermaLink="false">https://medium.com/p/be1fc72430fe</guid>
            <category><![CDATA[zenchef]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Julien Balmont]]></dc:creator>
            <pubDate>Thu, 12 Jan 2017 10:17:32 GMT</pubDate>
            <atom:updated>2017-01-12T10:17:32.079Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t_RpJHG-_8rW7gv0HgeYWA.gif" /></figure><p>Slack is in my humble opinion the best tool ever built to communicate with your colleagues.</p><p>But sometimes, you may feel like you’re being spammed by thousand of messages, and it can be a real pain in the a.. to go from one channel to another, from one person to another to read all you newly received messages.</p><p>FORTUNATELY, there’s a solution on the desktop version of Slack. All you have to do is activate the <strong><em>ALL UNREADS</em></strong> button.</p><p>If you don’t see the ALL UNREADS button at the top of your sidebar, just go to <em>Preferences</em> &gt; <em>Advanced</em> &gt; <em>Channel List</em> &gt; <em>Turn on All Unreads</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/1*peV1Izn89rtUvbtcAAwvjA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be1fc72430fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zenchef-tech-and-product/how-to-improve-your-productivity-on-slack-with-the-all-unreads-button-be1fc72430fe">How to improve your productivity on Slack with the ALL UNREADS button</a> was originally published in <a href="https://medium.com/zenchef-tech-and-product">Zenchef’s Tech and Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create a code block in Medium]]></title>
            <link>https://medium.com/zenchef-tech-and-product/how-to-create-a-code-block-in-medium-81112785a15d?source=rss-ddafa05f3323------2</link>
            <guid isPermaLink="false">https://medium.com/p/81112785a15d</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[code-block]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Julien Balmont]]></dc:creator>
            <pubDate>Wed, 04 Jan 2017 13:36:31 GMT</pubDate>
            <atom:updated>2017-01-04T13:38:49.441Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eAMST-LMWJBaKEiGTCqhxw.gif" /></figure><p>Since Medium documentation “Hints and keyboard shortcuts” is not correct about creating a code block, I’ve made some research and finally found how to create a code block. Thought it would be good to share it here.</p><h3>On Mac OS:</h3><ol><li>You can highlight some text, and press Cmd + Alt + 6. This will wrap the whole paragraph into a code block</li><li>Or, you can start a new paragraph, and press Cmd + Alt + 6. This will start an empty code block.</li></ol><h3>On Windows:</h3><ol><li>You can highlight some text, and press Ctrl + Alt + 6. This will wrap the whole paragraph into a code block</li><li>Or, you can start a new paragraph, and press Ctrl + Alt + 6. This will start an empty code block.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81112785a15d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zenchef-tech-and-product/how-to-create-a-code-block-in-medium-81112785a15d">How to create a code block in Medium</a> was originally published in <a href="https://medium.com/zenchef-tech-and-product">Zenchef’s Tech and Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to fix the composer update failure asking you to update a package and unable to remove it ?]]></title>
            <link>https://medium.com/zenchef-tech-and-product/how-to-fix-the-composer-update-failure-asking-you-to-update-a-package-and-unable-to-remove-it-8677af7730c?source=rss-ddafa05f3323------2</link>
            <guid isPermaLink="false">https://medium.com/p/8677af7730c</guid>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[zenchef]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[composer]]></category>
            <category><![CDATA[bugs]]></category>
            <dc:creator><![CDATA[Julien Balmont]]></dc:creator>
            <pubDate>Tue, 27 Dec 2016 10:02:27 GMT</pubDate>
            <atom:updated>2017-01-12T10:53:15.253Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*cGrvS-KhQG5J0gzXCXCXaA.gif" /></figure><p>From time to time, when you try to update you dependencies using</p><blockquote>composer update</blockquote><p>You might be asked the following annoying question</p><blockquote>Would you like to try reinstalling the package instead [yes]?</blockquote><p>In this case, whether you answer yes or no, the command line just doesn’t matter and fails.<br>For example:</p><blockquote>Dependency resolution completed in 0.005 seconds<br> — Removing guzzlehttp/promises (1.2.0)<br> Update failed (Could not delete vendor/guzzlehttp/promises/tests/AggregateExceptionTest.php: )<br> Would you like to try reinstalling the package instead [yes]? yes<br>[RuntimeException]<br> Could not delete vendor/guzzlehttp/promises/tests/AggregateExceptionTest.php…</blockquote><p>The answer is as simple as deleting the offending package from your vendor folder (here, guzzlehttp), and cleaning the composer cache</p><blockquote>rm -rf vendor/guzzlehttp</blockquote><blockquote>composer clearcache</blockquote><p>Try again your composer update</p><p>If it’s still complaining, it means that you might have a permission issue (probably because at some point you ran a composer update in sudo mode or made a modification directly in your vendor directlory).</p><p>The easiest solution is to remove your vendor directory and install from scratch all your dependencies</p><blockquote>rm -rf vendor<br>composer install -vvv</blockquote><p>It should work now :) Enjoy your code !<br>Thanks <a href="https://medium.com/u/947d98b7d60d">Alex Lombry</a> For the solution :p</p><p>Edit: Thanks to the reddit user “<a href="https://www.reddit.com/user/xroni">xroni</a>” for the comment, the article has been updated consequently.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8677af7730c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zenchef-tech-and-product/how-to-fix-the-composer-update-failure-asking-you-to-update-a-package-and-unable-to-remove-it-8677af7730c">How to fix the composer update failure asking you to update a package and unable to remove it ?</a> was originally published in <a href="https://medium.com/zenchef-tech-and-product">Zenchef’s Tech and Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons learned from rebuilding an entire tech platform from scratch]]></title>
            <link>https://medium.com/unexpected-token/lessons-learned-from-rebuilding-an-entire-tech-platform-from-scratch-6d05d0117774?source=rss-ddafa05f3323------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d05d0117774</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Julien Balmont]]></dc:creator>
            <pubDate>Fri, 10 Apr 2015 09:29:28 GMT</pubDate>
            <atom:updated>2015-04-16T07:56:09.169Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/749/1*jj4zbFoxJRG_9Hk3JdGCLQ.png" /></figure><p>I am Julien Balmont, co-founder and CTO of <a href="http://1001menus.com/en/">1001menus</a>, a marketing tool dedicated to restaurants’ online visibility. Today, I’m very proud of our tool, but it wasn’t always the case. Here the story of how we rebuilt our entire platform from scratch.</p><p>September 2013, 10pm, while having a drink at the office (ok, while having <em>several</em> drinks at the office):</p><blockquote>CEO: I have to tell you something … Hard to admit it but, DAMN, I can’t stand our product anymore! Customers don’t want to use it, Support keep complaining about it, you keep saying it’s hard to maintain and don’t get me started on the design…</blockquote><blockquote>ME : Dude, tell me about it …</blockquote><blockquote>CEO : So let’s make a new version!</blockquote><blockquote>ME : Hmm … NOPE.</blockquote><blockquote>CEO : … (try to picture him with a mix between puss in boots eyes and a puppy asking for a candy)</blockquote><blockquote>ME : Well, you know me, I always say no for the sake of it</blockquote><blockquote>CEO : … (this time, picture a kid in front of Santa himself)</blockquote><blockquote>CEO : So … we’re doing it??</blockquote><blockquote>ME: Fine, let’s make a new version!</blockquote><blockquote>CEO : Cool. The baby will be here in 9 months!</blockquote><blockquote>ME : …</blockquote><p>This is how the conversation sounded like or at least how I remember it. And trust me, I had no clue that would be the beginning of the tragedy… We should have had a meeting (or several) with the team, get some feedbacks, third opinions, and more importantly, an estimate of the time needed. But you know, we were tired of our product and wanted to change to something new. NOW. For developers, “new version” means newer technologies, brand new code, brand new database. And I love challenges…</p><p>I could say this was a difficult project, but it really was not. Launching a V2 does require a little bit of structure, preparation, and motivation. By sharing my experience on this, I hope you won’t make the same mistakes and just take some time to plan everything…</p><h3>Motivation is key for a long-term project</h3><h4>1/ The development team has to know “winter is coming”</h4><p>Depending on the product and the volume of code, a new version can take weeks, or months (or even years?) For us, it’s been <strong>months of rush</strong> and <strong>loads of stress</strong> that comes with it.</p><p>In a startup life, the development team who worked on the original product (interns, first employees, etc.) has usually changed when comes the new version. You may know what’s coming… but the newcomers don’t. And you need to prepare them.</p><p>You absolutely need to find a way to prepare and motivate the whole team, before, during and after the project.</p><p><strong>Mistake #1: </strong>Let’s be soft with myself and say that I didn’t master this rule ;) Caught up in the stress of the project and the need to deliver in time, I didn’t take the time to brief the team, show them what they will face and do what a manager should do: make them believe everything was gonna be ok…</p><h4>2/ Step by step (ooooh baby)</h4><p>It’s in our DNA to produce fast, fix some bugs, have many small tasks accomplished in one day. V2 is different. It’s a long-term project, but you need to cut this big cake. One part at a time, one task, one objective. I didn’t do this. I didn’t congratulate my team, show what they created already, brief them on the next step, etc. The only meetings I managed to do were to put more pressure on them. Not a smart move…</p><p><strong>Mistake #2:</strong> There is a reason why Scrum has been created. Agree with it or not, respect the rules 100% or not. You need to cut the project in small parts. It’s the only way to keep the motivation and end up with a better product.</p><h4>3/ Listen to your team</h4><p>During my whole career, — and that’s how I’ve been taught development during my first real job — I’ve always developed a sort of extremely AGILE way. You don’t write anything, you don’t prepare anything, but you make little steps working hand in hand with the product team. And until then, it always worked for me in small teams and small projects.</p><p>Meetings with my developer team? While the team was working on the new version, I was working extinguishing fires, on the old version, and all the other projects, trying to fix everything and keep things going. So I just decided I didn’t have time to do meetings and I just skipped them. My team asked me so many times to have some specifications for each new functionality, to write down at least some information. But no. They had to figure out by themselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*TlMsJfOvC2qshouKQKKqMw.png" /></figure><p>A little bit of communication within the team would have led to sharing some good ideas and bits of code and could have saved so many times…</p><p><strong>Mistake #3: </strong>I’ve been the stubborn guy and didn’t listen to the team. If they ask for meetings and information, take some time to meet their need.</p><h3>Better choose wisely what you don’t control (technology &amp; third part)</h3><h4>1/ Prepare to face new IT challenges</h4><p>New version means new technology. And what is better than one developer looking for the best option? Many developers looking for the best option! I decided to involve the whole team to make this choice. It did include some meetings and long discussion, but it was totally worth it. This challenge became their challenge and not an order coming from their +1. Were we talking about motivation? This is a great tool to boost your team.</p><p><strong>Smart Move #1: </strong>Make this decision as a team. Train the team. Learn from each other while you build this V2</p><p>For us, it’s been a brand new PHP framework. We’ve changed from Zend Framework 1.12 (I knew it inside out so easy to work with but let’s face it: totally outdated) to LARAVEL 4.3.</p><p>By the way, a few words for those who think PHP is outdated / so 2005 to try this framework out. The best PHP libraries have been used, rewrote, extended and gathered together as long as namespaces, closures, interfaces, a RESTful route system and so many wonderful things… In one word, AMAZING ! To try it is to love it.</p><p><strong>Smart move #2: </strong>Being able to rely on a good framework, with a large and active community is comforting.</p><h4>2/ Outsource design? Not such a good idea</h4><p>Without any designer and front-end developer, we had to work with a web design agency to help us on the product UX/UI, and integration of the Javascript. We wanted a good JS base to rely on so decided not to do it internally.</p><p>Skills of the agency we worked with aside, we already knew what we wanted, but they kept pushing in another direction. They persisted in a wrong way with the UI, thinking their point of view was the best one. It’s true it is their expertise but we knew our customers. And they wouldn’t have been able to use this. After weeks and weeks of discussions, phone calls and back and forth, final new design has been sent to their integration team and the full package with JS/CSS/HTML delivered few weeks later. The result? it was incompletely done, there were missing parts, we ended up rewriting and refactoring most of the Javascript and we were already 2 months late on the original timing.</p><p><strong>Mistake #4: </strong>Using an agency instead of internal resources. They are experts but if you don’t have time to guide them, structure them and harass them, you will end up with a “so so” result .. And late!</p><h3>Go live no matter what? NO!</h3><p>This is the worst decision we made about this project. And the more I think about it, the less I understand how we made such a decision.</p><p>We lost 2 months because of design issue but we still decided to go live with the new version on the D-day. Why? Because we chose this date 9 months ago. The reality? We were not ready at all. 70% of the new version was ready. Consequences? Change of plan. We had to make an incremental version upgrade, and keep using the old version. Because our customers had to go from V1 to V2, we had no other choice but modify all the V1 code to fit the new database scheme. What a waste of time!</p><p><strong>Mistake #5: </strong>I should have put my foot down. Refused to launch the product. Said we were not ready and that the risk was too high. But I kept quiet. Because I didn’t want to admit we screwed up the deadline? Because I didn’t want to tell everyone I wasn’t Santa? Or maybe because I’m a real optimistic person and believe a unicorn will fix everything. Not sure why I shut up. But it happened.</p><p><strong>Rule #1: </strong>If a project delivered with a little bit late will not put the company in a difficult position, a product delivered with bugs can make you customers leave and lead to an intricate situation.</p><h3>What a day this D-day</h3><p>To sum up the situation: 70% of the new version was ready. Old version was also ready. Bridge between both versions was ready too.</p><p>Finally the day of the migration came. Well, actually, the night of the migration. That night, I decided to take care of this all by myself. Me &amp; My MacBook. Confident. It went surprisingly well. I tested everything, some data migration scripts took longer than planned, but no big deal</p><p>But the next morning…</p><p>Clients calling from everywhere:</p><blockquote>- « I can’t find my pictures! »</blockquote><blockquote>- « I don’t understand sh*t with your new design »</blockquote><blockquote>- « I can’t login anymore »</blockquote><blockquote>- « I can’t manage my bookings anymore »</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*O8EBhuC6bcpgFgtVGMSg9A.png" /></figure><p>Even worth, complains arrived from our customer support team himself. Not because of the amount of calls, but because of the new product, not working, not handy…</p><p><strong>Mistake #6:</strong> Not having the new product tested by the support team. Their feedbacks would have avoided so many problems, bad customers opinion on the company. And I’m not talking about the frustration it created on the support team. Clearly not what we call a great management decision…</p><p>So, here we are. V2 is online. Customers are complaining. We need to work well and fast. This, I can do. And so does all my team actually. But you need to make sure everyone who worked on the project is available and ready to help testing and fixing latest bugs.</p><p><strong>Smart Move #4:</strong> Applause to my team who kept their cool and managed the stress of all the other departments of the company…</p><h3>Consequences of this decision?</h3><p><strong>We spent the next two months debugging and finishing the new product</strong>. That’s why, at the beginning of this article, I said the developer team should be prepared for the after project.</p><p>After this, we decided to adjust developments, to plan better and safer.</p><p>We had a meeting with the product and the developer teams, to debrief and identify what we could have done to avoid all of this… It was THE moment to talk honestly, to accept being criticized.</p><p>We decided to use SCRUM. Not all of it, as I still have issues with the daily meetings. We still have a small team, and with all the projects we have to deal with, I believe daily meetings would only be a waste of time. But we are in the right track, we can feel it!</p><p>All the issues we’ve met may sound obvious to some of you. Or not. But if my feedbacks help at least one of you, developer, CTO, product manager, then I consider it worths it. We’re now 7 months after the launch, and looking back, this is one of best experience I had. We’ve learned so many things! It structured the team and the way we approach every project we have to start from now on. As i’m writing those lines, we’ve just launched a V2.5. A fresh new design on top of the V2. And a huge code optimization. And you know what? everything went fine ☺ 5 minutes deployment, no bug… So proud of all the team!</p><blockquote>This article is part of the publication <a href="https://medium.com/unexpected-token">Unexpected Token</a> powered by eFounders — startup studio. All eFounders’ startups are built by extraordinary CTOs. If you feel like it could be you, <a href="http://efounders.co/cto">apply here</a>.</blockquote><blockquote>You like? Hit “Recommend” and subscribe to our collection!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d05d0117774" width="1" height="1" alt=""><hr><p><a href="https://medium.com/unexpected-token/lessons-learned-from-rebuilding-an-entire-tech-platform-from-scratch-6d05d0117774">Lessons learned from rebuilding an entire tech platform from scratch</a> was originally published in <a href="https://medium.com/unexpected-token">Unexpected Token</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>