<?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 SaaS Idea on Medium]]></title>
        <description><![CDATA[Stories by SaaS Idea on Medium]]></description>
        <link>https://medium.com/@info_34911?source=rss-c2dad4f52e45------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*E5xOO_ND8gDK6rsNSsDDAg.png</url>
            <title>Stories by SaaS Idea on Medium</title>
            <link>https://medium.com/@info_34911?source=rss-c2dad4f52e45------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:45:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@info_34911/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[Interview with undercover SaaS expert: before you start writing a line of code]]></title>
            <link>https://medium.com/@info_34911/interview-with-undercover-saas-expert-before-you-start-writing-a-line-of-code-d1ddd09f676a?source=rss-c2dad4f52e45------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1ddd09f676a</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[SaaS Idea]]></dc:creator>
            <pubDate>Mon, 01 Oct 2018 19:15:24 GMT</pubDate>
            <atom:updated>2018-10-01T19:15:24.962Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oieb5QfLQyyonXc5ycuvvg.png" /></figure><p>Our special correspondent, <strong>Christin Right</strong>, interviewed <strong>Jim Hill</strong>, the undercover SaaS expert who told us about the best practice and typical mistakes that all (well, most of) SaaS founders/developers do.</p><p><strong>Christin: First of all, thanks for the interview! Can you please tell us a little bit about your work, is it dangerous?</strong></p><p><strong>Jim Hill</strong>: Sometimes, yes. But more often it’s just frustrating.</p><p><strong>Christin</strong>: <strong>Is your name real?</strong></p><p><strong>Jim Hill</strong>: It doesn’t matter.</p><p><strong>Christin: Okay, let’s move on. Tell us what frustrates you most?</strong></p><p><strong>Jim Hill</strong>: Well… I saw different developers, of different levels and knowledge doing the same mistakes… especially when they even didn’t start writing any line of code.</p><p><strong>Christin: Do the take bad decisions? Or it’s about some mistakes related with design, planning?</strong></p><p><strong>Jim Hill</strong>: I’m talking about their reluctance to use solution that already exist, written by someone else.</p><p><strong>Christin: Can you give us some example?</strong></p><p><strong>Jim Hill</strong>: For example in one company I worked undercover, young, very talented developer was responsible for the architecture of a huge SaaS. He works in Facebook or Google these days, by the way — just for you to understand how clever he is. But he refused to use existing frameworks, he didn’t trust them for some reason. He and his colleague created a giant framework from the scratch — it included web interface, event and errors handling, everything. It worked pretty fast and worked okay.</p><p>The problem came when this guy stopped working in the company. He decided to finish the university so he started spending more time on it. Anyway, he could not work full time in the company anymore. He left the company in the very difficult situation. Try to guess how much documentation did his framework have?</p><p><strong>Christin</strong>:<strong> I guess, not too much. Couple of pages?</strong></p><p><strong>Jim Hill</strong>: You are very close. Actually zero. He didn’t like writing documentation, he didn’t like many boring things that nevertheless make your code sort of eternal. For example he didn’t use “self-talking” variable names. As a result, most of variables in his code were just one letter and other developers had to guess what means magic “c” or “m”.</p><p><strong>Christin</strong>: <strong>So, how did the story end?</strong></p><p><strong>Jim Hill</strong>: The management decided to rewrite the whole framework from the scratch. The reason why they did it were slightly different than wise, but other developers were happy anyway because they just felt tired to work with non-documented code filled with magic variables and other surprises. The two-years-work has gone.</p><p><strong>Christin</strong>: <strong>Is there any other consequences than wasting time that such decision could lead to?</strong></p><p><strong>Jim Hill</strong>: Yes, definitely. It’s security things, for example. In one company the whole team, including manager, didn’t want to use existing solutions for user authentication. They wasted several weeks to produce non-reliable code filled with bugs that could be used by bad guys as back doors. When some of the developers, before they started coding, asked quietly why wouldn’t use the existing solution he was asked back to shut up.</p><p><strong>Christin: So, what was the problem? Why didn’t they hear that developer?</strong></p><p><strong>Jim Hill</strong>: Because of two reasons: first is — they thought people shouldn’t doubt about other’s competence. They thought it made more friendly, united team (although it’s opposite in the reality).That question apparently exposed some doubts. The second was the subordination — ordinary developers should not doubt about correctness of their manager. Both reasons grown up from the corporate culture and killed many good initiatives, projects, companies, products. People want to be “politically correct” and don’t know that is the path to nowhere.</p><p><strong>Christin: So, what is the solution?</strong></p><p><strong>Jim Hill</strong>: Conflicts, doubts, arguments — everything like that can help to create better product, healthier companies and culture, and, as a consequence — earn more money.</p><p><strong>Christin: Conflicts? Are you sure?</strong></p><p><strong>Jim Hill</strong>: Absolutely. Conflict — in the finest sense of the word. Not yelling or bullying but just the opportunity to express an opinion without perspective to be asked to shut up, or even to be fired. It’s not a joke. I worked undercover in the company when management fired people that tried to argue. And, by the way, the lead designer there refused to use the well known, reliable HTML framework and invented his own — just because he didn’t like the default indents. Can you imagine? The whole developers team had to torture with his own “framework” instead of just using what millions other developers use.</p><p>So, don’t make this mistake — trust others, listen to colleagues, save your own and your company’s time and money. Don’t think that your product (even if it’s a SaaS) is very unique, that’s not right. Most of such systems have the same set of functional blocks, or components, so try to find the most fitting and use it.</p><p><strong>Christin: Thanks a lot for the interview. Hope, now people will think twice before starting coding their own framework.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1ddd09f676a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>