<?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 Alexander Yumashev on Medium]]></title>
        <description><![CDATA[Stories by Alexander Yumashev on Medium]]></description>
        <link>https://medium.com/@jitbit?source=rss-cb5ee64ea3dc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*psSE3-DjJefUFl-6.jpeg</url>
            <title>Stories by Alexander Yumashev on Medium</title>
            <link>https://medium.com/@jitbit?source=rss-cb5ee64ea3dc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 08:21:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jitbit/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 switch to remote in 1 day]]></title>
            <link>https://medium.com/@jitbit/how-to-switch-to-remote-in-1-day-88395ea17059?source=rss-cb5ee64ea3dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/88395ea17059</guid>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Alexander Yumashev]]></dc:creator>
            <pubDate>Mon, 23 Mar 2020 00:00:00 GMT</pubDate>
            <atom:updated>2020-03-23T17:58:13.230Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/889/1*YacFcDWAI9uGAQFoAYJFZg.jpeg" /></figure><p>Most remote work guides I see during these days of COVID-19, are all about <em>optimizing</em> for remote work in a remote company where everyone will keep working remotely forever. I haven’t yet seen any realistic, simple, unsexy and “down to earth” guides on how to <strong>urgently switch a “traditional” old-school corporation to remote in 1 day</strong>.</p><p>Ages ago I worked at a company, whose office building had to be urgently evacuated and closed down for 2 weeks — we literally had to switch to remote within <em>hours</em>. Now, my “enterprisey” tech skills are probably outdated, but this is what we’ve done. Forget all the fancy Slack/Trello/Zoom/timetracking tips, here’s what you need to start with:</p><ol><li><strong>Set up a VPN at your office</strong> and write very simple instructions for everyone. Make it VERY short and non-technical, and optionally save it as an image (!) so people can forward it to each other via WhatsApp etc.</li><li><strong>Use a <em>simple</em> protocol for your VPN</strong> no time to show off your technical skills and use Shadowsocks or whatever. Use something that’s already included with Windows. This way you’ll be able to set up a VPN connection with <a href="https://stackoverflow.com/a/30546103/56621">one line of PowerShell</a>.</li><li>The simplest way to start working is <strong>Remote-Desktopping to office workstations</strong> I know it sounds very, very ugly, but if you only have one day — you’re out of options. As far as I remember, allowing RDP connections for all office workstations at once <a href="https://community.spiceworks.com/topic/96392-what-is-the-best-way-to-enable-remote-desktop-on-all-of-my-domain-computers">can be done</a> via Active Directory group policy.</li></ol><p>Once you’re done with this part and people can begin trying to learn how to access their office files, emails and documents move on to the next step:</p><ul><li><strong>Making your internal services accessible via Web</strong> — kudos if they already are. Moving away from RDPing means gradually making your services available online. Your internal email, project &amp; task management, file storage, databases, code repos etc.</li><li><strong>Make office phones work via VoIP/SIP software</strong> your office PBX system probably <em>already</em> supports that. This way when someone calls a person’s office number — the call is routed to their home computer, where they answer it using a headset. Later move on to installing a SIP client on their smartphones so they can answer calls on the go. Or simply use call-forwarding if that sounds too complicated.</li><li><strong>Install chat software</strong> yes, finally we got to the Slack part. Chances are you’re already using it. Just make sure everyone keeps their “away/afk/on a meeting” statuses accurate. Make sure everyone has it installed on their phones, so you can “@-username” them in case something goes down, and they will get vibration in their pockets. And don’t rush into creating more “rooms”, “channels”, tags and threads — keep it simple and stupid.</li><li><strong>Use SSO</strong> — when choosing a new SaaS tool to help with your remote work, make sure it supports “Single Sign On” via SAML or a similar protocol with your existing users catalog. This will allow people to keep using their existing corporate usernames/passwords instead of creating new accounts (most chat software including Slack and MS Teams already support that).</li><li><strong>Set up an ongoing “everyone in” Zoom call</strong> — which is a very nice hack at the beginning. Start a call, invite everyone (from your team/department, not company-wide obviously) switch it to “gallery mode” and simply keep this call on the background with the “mute” button pressed. Whenever you want to say something — unmute yourself and say it ;) This way you don’t feel lonely and can actually see other people going through similar mess. It sounds silly but not being alone is a huge motivational bonus.</li></ul><p>If you have any other simple tips please tweet me at <a href="https://twitter.com/jitbit">@jitbit</a> I’ll add those to the post, keeping your name/link to original.</p><p><em>Originally published at </em><a href="https://www.jitbit.com/alexblog/287-how-to-switch-to-remote-in-1-day/"><em>https://www.jitbit.com</em></a><em> on March 23, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88395ea17059" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Managers Make more Money than Engineers]]></title>
            <link>https://medium.com/@jitbit/why-managers-make-more-money-than-engineers-35c9888b6630?source=rss-cb5ee64ea3dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/35c9888b6630</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[compensation]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Alexander Yumashev]]></dc:creator>
            <pubDate>Wed, 11 Mar 2020 00:00:00 GMT</pubDate>
            <atom:updated>2020-03-11T16:13:34.632Z</atom:updated>
            <content:encoded><![CDATA[<p>Programmers often wonder, why executives make more money than developers. How come “John the manager” gets paid more than me, who’s doing all the work?!</p><p>The answer to the big question comes from this little story I read, by Robert Sapolsky, a professor of biology at Stanford.</p><h3>The Naked Mole Rat</h3><p>There’s this weird African specie, a rodent called “the naked mole rat”, that lives in cooperative groups, mostly underground. While studying their behavior scientists soon began to realize there are two types of species in their colonies: the one that’s skinny and hardworking, doing all the work, the other types were lazy, fat and were just sitting around doing nothing all day, simply eating all the food brought by the hardworking types.</p><p>It was really puzzling since it contradicted all known behavioral studies and theories. Until it turned out, that you just needed to watch the colony long enough to realize what’s really going on.</p><p>Turns out when the rainy season comes, these fat guys who have been sitting around doing nothing all year long eating tons of food — they go up, turn around and plug their butts into the tunnel entrances. Protecting everyone from snakes, coyotes <em>and</em> preventing water from flooding the tunnels.</p><p>Literally covering everyone’s asses with their own.</p><p>P.S. Here’s <a href="https://youtu.be/Y0Oa4Lp5fLE?t=4324">a video</a> of Robert’s lecture (link points to the timecode where he tells a version of this story)</p><p><em>Originally published at </em><a href="https://www.jitbit.com/alexblog/285-why-managers-make-more-money-than-engineers/"><em>https://www.jitbit.com</em></a><em> on March 11, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35c9888b6630" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we send 22000 emails every hour]]></title>
            <link>https://medium.com/@jitbit/how-we-send-22000-emails-every-hour-ab9769122c69?source=rss-cb5ee64ea3dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab9769122c69</guid>
            <category><![CDATA[system-architecture]]></category>
            <category><![CDATA[email]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[sysadmin]]></category>
            <dc:creator><![CDATA[Alexander Yumashev]]></dc:creator>
            <pubDate>Mon, 29 Jul 2019 00:00:00 GMT</pubDate>
            <atom:updated>2019-07-30T08:19:00.195Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*67eUHHh5GSUrJK8tcjABxw.png" /></figure><p>Our app sends and receives about 22,000 (22 thousand) emails per hour.</p><p>That’s more than <strong>half a million</strong> emails every day.</p><p>During US daytime it peaks to 25–30 emails <em>per second</em> and goes down to almost zero on a late Sunday evening — but only for 1–2 hours <em>because Australians</em>.</p><blockquote><em>Here’s a cute completely irrelevant story, feel free to skip. The phrase “Because Australians!” has actually become an inside joke/catchphrase in our company. See, Aussies and Kiwis (New Zealanders) wake up before everyone else (even before Japan). Basically Australians are the reason SaaS businesses don’t have an outage/maintenance window. And a couple of times when we were about to put a server down for maintenance on a late Sunday evening (EU time), someone would shout “Wait! Don’t do that!” — “What… Why?” — “Because Australians!”</em></blockquote><blockquote><em>So after 4 or 5 times this phrase is now used as an ultimate “42” answer why everything has to be up and running 24/7. I even have a tiny map of Australia in my office. I (nor anyone from the team) have never been to Australia or New Zealand, but hey, we’re always thinking about you mates [wink]</em></blockquote><p>Anyway, back to our enormous amounts of email. Half a million per day.</p><p>We looked at paid PaaS providers like Mailgun, Sendgrid, Amazon SES… And all of them would cost <em>several thousand a month</em> at this scale. And since we’re not a sexy funded startup from California, but a boring customer-funded business, we can’t afford this bill.</p><h3>The boring solution</h3><p>That is why we finally settled on a… <strong>tiny AWS instance running </strong><a href="http://www.postfix.org/"><strong>Postfix</strong></a><strong> under Ubuntu. It has 2 Gigs of memory, priced around $9/month and the CPU load rarely goes beyond 15%.</strong></p><p>But we had to learn everything about email. Every damn bit.</p><p>SMTP, relays, MX-records, SPF verification, DKIM signatures, spam filtering, reverse-DNS, blacklisting, “Internet Message Format”, throttling, MIME-encoding, email-antiviruses, bounces, headers, log-parsing, rate-limiting, greylisting, RFC standards (and that no one follows them)… And of course — about IP address reputation (more on that later).</p><p>Our Postfix installation handles both inbound and outbound emails.</p><h3>Outbound email</h3><p>Our ticketing app sends an outbound message whenever “something happens” — like when a new support ticket arrives, it notifies helpdesk agents. Or notifies a user whenever an agent has responded to their ticket. Etc.</p><p>Our set up is pretty straightforward — the Postfix machine simply acts as an SMTP server, that listens for incoming connections from the web-app on port 587 (black arrows on the diagram). Connections are allowed form within our internal VPC-network only (“Virtual Private Cloud”) and additionally protected by a username/password, just in case. After receiving an email, Postfix <a href="https://support.google.com/transparencyreport/answer/7381230">encrypts the message via TLS</a> and forwards it “into the wild”.</p><h3>Inbound email</h3><p>In addition to sending email out, we handle a lot of inbound email. All our customers are provided with a xxx@xxx.jitbit.com mailbox, with an option to add their own mailboxes via IMAP/POP/EWS (yeah, more acronyms). Our Postfix machine&#39;s IP-address is listed as a wildcard MX-record for our domain and listens to all emails sent to *@*.jitbit.com on port 25.</p><p>The inbound emails are then routed to a local PHP script (yes, THAT unsexy) because that’s the only way Postfix can “execute something” when an email arrives. The PHP script then does some basic parsing and feeds the messages to the web app via an internal http/REST endpoint (blue arrows on the diagram).</p><p>But before that the inbound email is scanned for viruses (ClamAV), spam-filtered (SpamAssassin), checked against blacklists (SpamHaus), SPF-verified, FQDN-verified, throttled (if abusive) etc. etc. etc.</p><h3>Monitoring</h3><p>We use:</p><ul><li>Postfix’s built-in logging system and cat, zcat, grep to navigate the logs</li><li>qshape for reviewing the mail queue and bottleneck analysis</li><li>AWS’s built-in alerts whenever the server slows down, like when the CPU load goes higher than X% for more than a minute or when the disk usage jumps abnormally (I think it’s called “CloudWatch Alarms” or something, Amazon is terrible with names) — which usually means someone’s flooding or spamming</li><li>An in-house developed watchdog that simply sends a dummy email to a disposable Mailinator mailbox every 5 minutes to check that things still work. If not — it sends a message to admins via SMS, Telegram, WhatsApp and Slack saying (quote) “email is fucking down”. It also tries to “fix” things on its own by restarting some daemons, “recycling” web-application pools on Windows-powered machines etc. — until a human shows up.</li><li>Another in-house developed watchdog that periodically queries the database for things like “incoming tickets rate per user” and “email rate per company account” etc. You can’t even begin to imagine the amounts of inbound and outbound spam we’re dealing with (yes, outbound too — people register trial accounts and find creative ways to <a href="https://www.jitbit.com/alexblog/259-your-saas-app-is-an-attack-target/">abuse it</a>).</li></ul><h3>IP reputation</h3><p>Now this is a tricky part. You can’t just launch a new server and start sending hundreds of thousands of messages out of the blue — your IP will be blocked. You have to <em>build up reputation gradually</em> otherwise Gmail, Outlook.com, Hotmail, Yahoo (still exists yeah), Apple, AOL, ProtonMail etc. will simply ban your IP for good.</p><p>This is not documented anywhere, but this is a de-facto standard email-admins don’t tell anyone about. Gradually build up your volume. Start by sending internal error alerts to your team. Then move some of your email marketing campaigns. Then some system messages. And so on.</p><p>You will probably have to contact your hosting provider too (AWS, Azure, DigitalOcean etc) to let them know you’re about to send massive amounts of emails (otherwise — ban), and ask them to add a “reverse-DNS” record for your IP (otherwise — ban).</p><h3>Build vs Buy</h3><p>This is a classic “make vs buy” problem. With one exception that you’re not actually writing any new software, you’re just setting up the existing one. It takes some time, but the field is pretty well documented. Email has been around for decades. There’s plenty of information out there (although some websites look like they’re from the 90s — that’s because they are — and at times I feel the docs are intentionally cryptic, no offense).</p><p>Setting it all up is a one-time expense, it can take hours, days or even weeks to get it working, but this is knowledge that stays with you (and the company) forever. After that it’s pretty low maintenance and with super-cheap operating cost (the “$9 a month” mentioned above).</p><p>The “make” option drawbacks can be minimized by being hosted in the <em>cloud</em>. Like, even if your server goes down you can spawn a replica within seconds and switch the IP address to the cloned machine with just a couple of clicks — and then take your time to investigate what happened.</p><p>The “buy” route is much more expensive but provides the blessing of ignorance. Everything is being managed for you. You don’t have to learn or do anything just sit back, relax and prey.</p><p><em>Originally published at </em><a href="https://www.jitbit.com/news/email-architecture/"><em>https://www.jitbit.com</em></a><em> on July 29, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab9769122c69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Legal Stuff They Don’t Tell You About Remote Work]]></title>
            <link>https://medium.com/@jitbit/legal-stuff-they-dont-tell-you-about-remote-work-5b24b6762659?source=rss-cb5ee64ea3dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b24b6762659</guid>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Alexander Yumashev]]></dc:creator>
            <pubDate>Mon, 24 Jun 2019 00:00:00 GMT</pubDate>
            <atom:updated>2019-06-28T15:09:26.353Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iaIyorSr5mdpDU33oO_XeA.png" /></figure><p>My company — <a href="https://www.jitbit.com/">Jitbit </a>— is an all remote company. We are 100% distributed, we don’t have an office and our teammates literally work from around the globe (currently it’s the UK, the US, Latvia, Israel and Turkey).</p><p>So it might seem strange for me to warn people against remote work. But let’s have a look from the <em>employee’s angle</em>.</p><p><strong>This is what you need to know when you’re about to work for someone remotely and <em>internationally</em>.</strong></p><h3>You’re a CONTRACTOR now</h3><p>This part is crucial and all the other points more or less come out of this one, so let me stress every sentence in this paragraph:</p><p>You’re not officially employed any more. Legally you’re <em>self-employed</em> now.</p><p>You’re not protected by employment law and/or your country’s labor authorities.</p><p>“Employee rights”, benefits, labor unions, regulations — do not apply to you anymore.</p><p>You’re on your own.</p><p>The only thing that regulates your work is <em>your contract</em>.</p><h3>Your CONTRACT is super important</h3><p>The above mentioned issues make your contract crucial. It is the only thing that protects you. Once you become a contractor — as opposed to an employee — your country’s <em>employment law</em> (very strict in most European countries) just stops working. No more minimum wages, no wrongful terminations, your new employer can fire you any moment and get away with that.</p><p>This is why your contract needs to cover <em>everything</em>, even the parts that seemed “obvious” when you were working in the office. Everything. Employee benefits, medical insurance costs, layoff procedures, holidays and vacations, promotions and — of course — compensation. Lawyer up! (just kidding… although, it’s never a bad idea to have legal help).</p><h3>You probably need to register as “self-employed”, “sole proprietor”, “individual entrepreneur” or similar</h3><p>In most countries it’s illegal to perform “business activities” without actually registering a “business”. And since you’re now a contractor doing business with the remote company, you will need a <em>legal entity</em>. There’s no need to register a whole big ass company, since most countries offer “self employed” registration of some sort. Sometimes called “sole proprietorship”, “individual entrepreneur” or a simpler “self-employed” form (although registering an actual company might be a good idea, more on that later). This “entity” will then sign the contract with your employer, receive the money and pay taxes.</p><p>You will also need a bank account for this entity (obviously). And in some rare cases your bank, your country’s tax office or even the company your work for might also ask you to issue an <em>invoice</em> for every monthly payment your receive. Don’t let this freak you out, this is totally normal, and the invoice will just mention “Monthly web-development services for June 2019 — q-ty: 1” or something, nothing too complicated.</p><h3>Exception #1 — Authorship</h3><p>In some cases you can get away without registering a business and get your paycheck as an “authorship royalty”. Like, you’re the “author” of the source code, who “licenses” that code — to the remote company. And the company pays you “royalty”. This way you’re not in a “buyer-seller” relationship, you’re in an “author-publisher” relationship, and this usually does not require registering a legal entity. But this might involve more paperwork and more lawyers (duh).</p><h3>Exception #2 — PEO</h3><p>Another way to be hired remotely without registering any business is through an “employer of record” service, which acts as a proxy between the remote company and an employee such as yourself. Here’s how it works: a global company like ShieldGeo (not affiliated) which has local legal entities in many many different countries, becomes the official “employer of record” for tax purposes and paperwork only. This way you are officially employed and can simply skip the rest of this article. Ask the remote company if they use a service like this (called “professional employer organization” — PEO) or even suggest using one — why not!</p><h3>You’re doing your own taxes now *</h3><p>In many countries taxes are “done for you” by the employer and companies even publish job descriptions with “after tax” salaries. Employees sometimes do not even know how much would they earn “before tax” and in some countries (believe it or not) people are not even aware of the current tax rates.</p><blockquote><em>&lt;Political nerd mode on&gt; Actually there’s a pretty clear correlation between how “free” a country is, and whether people do their own taxes or not. Turns out, countries where people know their taxes are more liberal and civilly active (because you actually see how much money you give away every month), while countries where taxes are “done for you” tend to be politically indifferent and often end up in some form of authoritarianism.&lt;/off&gt;</em></blockquote><p>Anyways. If your taxes were done for you by the employer in the past, well, that’s going to end. You will have to report to your Tax Office, file the tax return and actually pay taxes in the end.</p><p>You will probably need an accountant too. They will advise you on how to save on taxes, which expenses are deductible, whether registering a company is better than “self-employment” (might also help save some taxes), and generally save you a lot of time and headache. It shouldn’t be very expensive either, I pay my accountant approximately 100 Euro a month ($120).</p><h3>Benefits and other stuff to negotiate with your remote employer</h3><p>Here at Jitbit we cover: medical bills, insurance costs, some of the taxes (in countries where being “self-employed” results in bigger taxes than being employed “normally”), work expenses (like a new laptop allowance etc). We even provide <em>0-interest dateless loans</em> to our employees — since we do realize that it’s harder to get a mortgage when you’re “self-employed”. By the way, that’s another reason to register a company, rather than “sole proprietorship”, because “a company” always looks better for your bank (and your grandma too).</p><p>Anyway, you will have to negotiate all that after getting the job offer. Don’t be shy, it never hurts to ask. Also, their reaction is a good way to tell the good guys from shady outsourcers who simply want cheap workforce (and then they eff-up Hertz website ;).</p><p>On the other hand, do remember, that this whole “remote” thing is still very new. Some companies are only trying these waters for the first time, they might simply not know what to offer and how to pay. Give us a chance, we’re still learning.</p><p>Further reading:</p><ul><li><a href="https://open.buffer.com/international-pay/">How We Pay Remote Employees</a> by Buffer</li><li><a href="https://about.gitlab.com/handbook/people-operations/global-compensation/">Global Compensation</a> by Gitlab</li><li><a href="https://doist.com/blog/mental-health-and-remote-work/">What Most Remote Companies Don’t Tell You About Remote Work</a></li></ul><p>If you know more good posts on the topic do let me know in the comments, I’ll add the links.</p><p><em>Originally published at </em><a href="https://www.jitbit.com/news/3308-legal-stuff-they-dont-tell-you-about-remote-work/"><em>https://www.jitbit.com</em></a><em> on June 24, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b24b6762659" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 important lessons CEOs can learn by answering customer support tickets personally]]></title>
            <link>https://medium.com/startup-grind/3-important-lessons-ceos-can-learn-by-answering-customer-support-tickets-personally-fa629820769c?source=rss-cb5ee64ea3dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa629820769c</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[customer-service]]></category>
            <dc:creator><![CDATA[Alexander Yumashev]]></dc:creator>
            <pubDate>Thu, 13 Jun 2019 15:01:00 GMT</pubDate>
            <atom:updated>2019-06-16T17:03:29.225Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*KOtlP7yWp5qGAPuq" /></figure><p><em>By </em><a href="https://www.linkedin.com/in/jitbit"><em>Alexander Yumashev</em></a><em>, CEO, and Founder at </em><a href="https://www.jitbit.com/"><em>Jitbit Software</em></a></p><p>I am the CEO of a customer support software company. Oh, and I answer support tickets from my clients personally, just like the rest of my team. Don’t laugh — I’m totally frigging serious.</p><p>I do this at least once a day. Also, all requests are cc’ed to my personal inbox, so I basically review them all. Yeah, I get it — <em>a CEO shouldn’t be answering support tickets personally</em>. Well, that’s what <em>you</em> think. I answer tickets to stay in touch with the realities of my business and the level of service we provide. When you think about it, what better way is there to know how things are going rather than personally addressing the issues of your customers?</p><p>Apart from the reactions that never get old when I tell the customers that they are speaking to the CEO of the company, speaking to customers daily teaches me a lot of things about the way my business works. This is especially important nowadays since I seem to always come across business owners who have no idea what their business is really about. Here are three important lessons I learned from answering customer support tickets personally.</p><p><strong>Lesson 1: An inspiration to pivot to a more successful product scheme</strong></p><p>You might be surprised to hear that at least a dozen times, I’ve found myself revising our whole roadmap or marketing position based on one single support ticket. You see, customers can tell you a lot about your product, and if you listen, you could end up hitting the sweet spot.</p><p>Take Tote, for example. Originally, Tote was designed as an <a href="https://www.fastcompany.com/3001984/pinterest-pivot">online shopping platform by Ben Silbermann</a>. The app allowed people to mark their favorite items and sent out notifications when clothing went on sale, as well as pointing out physical store locations close by. The problem with the app was that paying for the items was a hassle. This was back in 2009 when quick payment methods weren’t as advanced as they are now. Thus, few purchases were being made and Tote wasn’t as successful as predicted.</p><p>What Silbermann noticed, however, was the massive amount of Tote users who would share their collections of saved items with friends on social media. Using this valuable information, he quickly switched gears and designed a new app which focused on shareable picture collections for the masses. The new app is called Pinterest, and in 2017 was <a href="https://techcrunch.com/2017/06/06/pinterest-raises-150m-at-a-12-3b-valuation-as-it-makes-a-full-press-into-visual-search/">valued at $12.3 billion</a>.</p><p>For me, keeping an eye on the support queue is similar to how Silbermann was conscious of his audience’s desires. One of the most convenient features in our app — auto-detecting companies from incoming email domains — was actually suggested by one of our customers. Assigning one or more “domains” to a company and then automatically assigning users to these companies when an email arrives makes our app act more as a customer relationship management tool, and not just a customer service app. This was a huge leap forward. People can track previous interactions with a company, not just a person.</p><p><strong>Lesson 2: A window into your business structure</strong></p><p>Like I said before — I’m baffled at how many clueless people have a business. If I ask the right questions, it doesn’t take long for the truth to emerge: they have no idea what their business is about. Answering your own support tickets is like taking a crash course on how your own business operates, and whether its existing structure is efficient or not.</p><p>For example, you can tell if your UI is clean and self-explaining or not at all, like seeing a checkbox and asking yourself “what the heck does this do?” Here are some other questions you might end up asking:</p><ul><li>Is my pricing competitive or not?</li><li>Am I targeting the right audience (look at the people who write you — how big are their companies, what is their position)?</li><li>How good is my onboarding?</li><li>How complicated is my product for less technical people?</li><li>How efficient is my ordering process?</li></ul><p>Keep in mind that these questions mostly work for B2B because customer support volumes in B2C are simply too high for founders. If your business is B2C, then there are other ways to analyze your business to better understand it. Things, like conducting a consumer analysis and a competitive analysis, as well as taking into account your indirect competitors, are all <a href="https://blog.marketresearch.com/6-tips-for-understanding-your-customer-and-your-business-competition">factors which contribute</a> to a better general understanding of what your business is.</p><p><strong>Lesson 3: Your own worst critic is who?</strong></p><p>Call me cliche for saying it, but yes, we are our own worst critics. This is common knowledge, but what isn’t common knowledge, is how do we learn to become better leaders? Instead of criticizing ourselves, how do we build a relationship with our customers?</p><p>You guessed it — answering support tickets can teach you valuable skills that no school or wise mentor could have so that you can become a more well-rounded leader for your business. Empathy, for example, is arguably the most important skill for customer service. Speaking to more customers on a daily basis about their concerns with your product or service can help you relate more to their situation, instead of hearing about it as feedback from your own employees.</p><p>As a CEO, training your empathy muscle helps a lot in other areas too, like with your family and friends. Also, in a small, 100% remote company, where you don’t get to talk to other people a lot, this is a great way to maintain your social skills. Satya Nadella, the CEO of Microsoft <a href="https://www.morningfuture.com/en/article/2018/06/18/microsoft-satya-nadella-empathy-business-management/337/">said it best</a> himself:</p><blockquote>“The value that I really learned to appreciate deeply and which I talk about a great deal is empathy. I don’t think it is simply a “nice to have” but I believe it is at the centre of the agenda for innovation here at Microsoft. Our core business is connected with the customers’ needs and we will not be able to satisfy them if we don’t have a deep sense of empathy”</blockquote><p>Emails from actual customers are usually filled with emotions. With real-life stories like “we’ve just missed a very important deadline with our biggest client because we had trouble exporting the report data, so John had to stay up till 1am doing manual exports”. An email like that triggers more empathy, emotions and feeling of responsibility than a brief line like “June 2018: customer satisfaction is 57%”.</p><p>And finally here’s some free advice. As a founder or CEO, you probably read a lot about “customer development,” “client surveys,” “net promoter scores,” and “focus groups.” Well, before diving into all that stuff just spend a day or two answering support emails. And make sure everyone in your company — developers, marketers, even the executives — spend a portion of their time talking to customers directly.</p><p>Too many founders and CEOs are hooked on metrics, data dashboards, reports, and graphs. But data is tricky. Without knowing the basics of statistics and without enough data, it’s very easy to make the wrong decision. Spend more time talking to people instead of using metrics to guess what they actually think. With a better understanding of your product, business structure, and more focus on your skills as a leader, you’ll become the role model that your employees look up to.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa629820769c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startup-grind/3-important-lessons-ceos-can-learn-by-answering-customer-support-tickets-personally-fa629820769c">3 important lessons CEOs can learn by answering customer support tickets personally</a> was originally published in <a href="https://medium.com/startup-grind">Startup Grind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts on Tech Stacks for Bootstrapped Startups]]></title>
            <link>https://medium.com/@jitbit/thoughts-on-tech-stacks-for-bootstrapped-startups-f3c8f2525837?source=rss-cb5ee64ea3dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3c8f2525837</guid>
            <category><![CDATA[bootstrapping]]></category>
            <category><![CDATA[tech-stack]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[solopreneur]]></category>
            <dc:creator><![CDATA[Alexander Yumashev]]></dc:creator>
            <pubDate>Wed, 30 Jan 2019 23:26:38 GMT</pubDate>
            <atom:updated>2019-02-05T17:07:49.779Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1YgYJPaEDftPQvDx.jpg" /></figure><p>So you’re starting a bootstrapped web-based business and you’re deciding on the tech stack. After running a software startup with zero funding for 13 years, here’s what I have to say about this.</p><p><em>Warning: highly opinionated bald statements ahead.</em></p><h3>Choosing your stack</h3><p>There’s a lot of (valid) reasons on why you should choose one stack (framework, programming language) over another. Like “check the ecosystem” or “think about future hires”.</p><p>There’s also a lot of shitty and meaningless advice like “put users before technology” or “always go with opensource”.</p><p>But the most crucial, the number one criteria is <strong>the ability to move fast</strong>. Period.</p><p>There once was a term — “RAD: Rapid Application Development” — which is rarely used these days (and has zero connection to our topic), but that’s what you’ll be doing — hopefully — for the next decade.</p><p><em>RAPID development</em>.</p><p>Lightning fast changes. Quick pivoting. Redesigning your whole dashboard in one day. Locating a critical bug without looking at your code — because the whole codebase fits in your head. And fixing the bug using your mobile phone while riding the subway (welcome to the solo founder’s life).</p><p>That’s why the only working advice here is <em>go with what you already know</em>. Preferably something monolithic. Something that’s been around for a while. With minimum abstractions and minimum hype. But most importantly <em>something you know best</em>.</p><h3>Why the “speed” obsession?</h3><p>To minimize the time spent on “technical” challenges.</p><p>You will have plenty of “non-coding” stuff on your plate. Researching the market, validating your idea, interviewing potential customers, getting your first paying users, then scaling the customer acquisition technique, then pivot, then pivot again, and then again — until you get to the product market fit…</p><h3>Joel Test — the bootstrapped version</h3><p>There’s hardly anyone left who hasn’t heard about <a href="https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/">Joel Test</a> these days.</p><p>Here’s the Joel’s original list (you’re supposed to answer “yes” to all of these):</p><ol><li><em>Do you use source control?</em></li><li><em>Can you make a build in one step?</em></li><li><em>Do you make daily builds?</em></li><li><em>Do you have a bug database?</em></li><li><em>Do you fix bugs before writing new code?</em></li><li><em>Do you have an up-to-date schedule?</em></li><li><em>Do you have a spec?</em></li><li><em>Do programmers have quiet working conditions?</em></li><li><em>Do you use the best tools money can buy?</em></li><li><em>Do you have testers?</em></li><li><em>Do new candidates write code during their interview?</em></li><li><em>Do you do hallway usability testing?</em></li></ol><p>Here’s an edited list, considering you’re (1) bootstrapping, (2) you’re a team of 1–3 people and (3) it’s freaking 2019 out there</p><ol><li><em>Do you use s̶o̶u̶r̶c̶e̶ ̶c̶o̶n̶t̶r̶o̶l̶ GitHub, GitLab or Bitbucket?</em></li><li><em>Can you m̶a̶k̶e̶ ̶a̶ ̶b̶u̶i̶l̶d̶ run unit tests, make a build and deploy everything in one step?</em></li><li><em>Do you m̶a̶k̶e̶ ̶d̶a̶i̶l̶y̶ ̶b̶u̶i̶l̶d̶s̶ use CD/CI? It’s OK if you’re not, don’t obsess over this one.</em></li><li><em>D̶o̶ ̶y̶o̶u̶ ̶h̶a̶v̶e̶ ̶a̶ ̶b̶u̶g̶ ̶d̶a̶t̶a̶b̶a̶s̶e̶? You probably do, see #1</em></li><li><em>Do you fix bugs before writing new code?</em></li><li><em>Do you have a̶n̶ ̶u̶p̶-̶t̶o̶-̶d̶a̶t̶e̶ ̶s̶c̶h̶e̶d̶u̶l̶e̶ a roadmap?</em></li><li><em>D̶o̶ ̶y̶o̶u̶ ̶h̶a̶v̶e̶ ̶a̶ ̶s̶p̶e̶c̶? (you obviously don’t)</em></li><li><em>Do programmers have quiet working conditions? (AKA “work remotely”)</em></li><li><em>Do you use the best tools m̶o̶n̶e̶y̶ ̶c̶a̶n̶ ̶b̶u̶y̶?</em></li><li><em>D̶o̶ ̶y̶o̶u̶ ̶h̶a̶v̶e̶ ̶t̶e̶s̶t̶e̶r̶s̶? Do you have both </em><strong><em>unit tests</em></strong><em> and </em><strong><em>UI-tests </em></strong><em>via Selenium, Phantom JS or a similar technology?</em></li><li><em>Do new candidates write code during their interview?</em></li><li><em>Do you do hallway usability testing? AKA do UX audits or simply show the app to your spouse</em></li></ol><h3>No microservices</h3><p><em>(told you it’s going to be opinionated)</em></p><p>Breaking down your app into smaller pieces looks so tempting. Hey, it worked for Google, Amazon and Facebook, it must work for you too! Except it won’t.</p><p>The reason Google and Amazon are doing this is because when you reach a certain scale there’s simply <em>no other way</em> to keep it all coordinated. It was a necessity, not a choice.</p><p>Do the exact opposite: avoid splitting your app into smaller objects for as long as you can. Unless you want your code to become an “un-unit-testable”, “un-deployable”, “un-monitorable” messy nightmare.</p><h3>No JS frameworks</h3><p><em>(unless it’s what you already know best)</em></p><p>JS-frameworks are the new “Java Server Pages”. JS-frameworks are the new “ASP.NET Web Forms”. JS-frameworks are the new “BizTalk server”, the new “JavaBeans”.</p><p>You’re probably too young to remember what are those anyway. I’m 42, so trust me. I’ve seen this before. Have a look at this code:</p><pre>&lt;div&gt;<br>  &lt;ex:Hello&gt;<br>    This is message body<br>  &lt;/ex:Hello&gt;<br>  &lt;c:if test=&quot;${myVar &gt; 2000}&quot;&gt;<br>    &lt;p&gt;The variable is: &lt;c:out value=&quot;${myVar}&quot;/&gt;&lt;p&gt;<br>  &lt;/c:if&gt;<br>&lt;/div&gt;</pre><p>Hey, you can even say the code is kinda readable! It even looks like some fancy modern framework, right?</p><p>Except it’s not. It’s JSP. <strong>Released back in fucking 1999</strong>.</p><p>Or this:</p><pre>&lt;div&gt;<br> &lt;asp:DataGrid ID=&quot;Grid&quot; runat=&quot;server&quot; ForeColor=&quot;#333333&quot;&gt;<br>  &lt;Columns&gt;<br>   &lt;asp:BoundColumn HeaderText=&quot;EmpId&quot; DataField=&quot;EmpId&quot;&gt; &lt;/asp:BoundColumn&gt;<br>   &lt;asp:BoundColumn HeaderText=&quot;F_Name&quot; DataField=&quot;F_Name&quot;&gt; &lt;/asp:BoundColumn&gt;<br>   &lt;asp:BoundColumn HeaderText=&quot;L_Name&quot; DataField=&quot;L_Name&quot;&gt; &lt;/asp:BoundColumn&gt;<br>  &lt;/Columns&gt;<br>  &lt;FooterStyle BackColor=&quot;#990000&quot; Font-Bold=&quot;True&quot; ForeColor=&quot;White&quot; /&gt;<br> &lt;/asp:DataGrid&gt;<br>&lt;/div&gt;</pre><p>This is “ASP.NET Web Forms”, kids. Again, <strong>back from 2001</strong></p><p>All these frameworks were started with good intentions, but ended up as shitty abstractions with their own “tags”, their own “attributes”, hidden logic and layers of “API” you had to fight your way through.</p><p>Things that were once trivial in HTML suddenly became messy workarounds. If — god forbid — you need to render anything that’s not part of the framework — you’re stuck with hacks and spaghetti-code.</p><p>That is why once the “normal” lightweight frameworks came along — like “ASP.NET MVC”, “Ruby on Rails” and “Laravel” — everyone dumped the monstrous behemoths and never looked back.</p><p>The JS world is simply undergoing the same cycle right now. And we — the old farts — are finding this all very familiar.</p><p>So, yeah, no fancy JS frameworks. You can add an “invisible” frictionless JS-layer that plays nicely with your existing code (like Stimulus or even Vue). But <em>server-side rendered HTML</em> (with sprinkles of JavaScript) will always be — as @DHH has coined it — “a throwback to when a single programmer could make rapacious progress without getting stuck in layers of indirection” <a href="https://m.signalvnoise.com/stimulus-1-0-a-modest-javascript-framework-for-the-html-you-already-have/">in this post</a>.</p><p>If it’s good enough for GitHub and Basecamp, it’s good enough for you.</p><p><em>(UPD: just to be clear, by “JS frameworks” I mean libraries like Angular, Ember, React and other behemoths, not the lightweight ones, and not jQuery. And let me reiterate: if you are an expert in a JS-framework — go for it. Just don’t “try it out because everyone else does”)</em></p><h3>“2.0” is always a bad idea</h3><p>Now back to Joel. Rewriting your app from scratch is always a bad idea. It’s one of the <a href="https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/">things you should never do</a>. A rewrite won’t magically solve any of your problems. But it <em>will</em> introduce the new ones <em>and</em> scare your existing users away.</p><p>Unless you’re a funded startup of course, and you need to justify the new hires to the investors (in which case, the JS frameworks are a <em>great</em> idea).</p><h3>Monitoring and handling bugs</h3><p><strong>Write tests after fixing bugs</strong>. If something’s truly a critical and complex bug — it’s something you don’t want to ever see again. Write a test to prevent it.</p><p><strong>Prioritize bugs</strong> and fix the ones that might hurt conversions first. Write a UI test that signs up for your SaaS app trial.</p><p><strong>Track feature usage</strong>. I love killing features. If a feature is used by less than 0.5% of your users, we hide it from the UI to unclutter the app — we simply don’t show the checkbox if the checkbox is “off”.</p><p><strong>Monitor exceptions and downtimes</strong>. Handling server-side exceptions and sending an email notification is generally easy. Handling client-side errors can be trickier, I’d recommend using a tool like <a href="https://sentry.io/">Sentry</a> (has a free entry plan).</p><h3>Avoid the hype</h3><p>As a general rule, don’t chase the hype. Don’t use Go, because it’s the new cool thing. Don’t use a NoSQL cluster <a href="https://www.youtube.com/watch?v=HdnDXsqiPYo">because it’s web scale</a>, a relational database might work <em>just fine</em>. Being a cool kid is tempting (and using a cool technology can be a <em>very</em> important component of staying motivated), but there are other ways of keeping yourself excited (devops to name one).</p><p>As a startup your top priority is getting to market <em>fast</em>. Keep that in mind whenever you’re making a decision and set realistic goals and milestones. <em>Getting things done FAST</em> is what you’re looking for. Not “Facebook-scale”.</p><p><em>Originally published at </em><a href="https://www.jitbit.com/alexblog/276-thoughts-on-tech-stacks-for-bootstrapped-startups/"><em>www.jitbit.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3c8f2525837" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fix The Damn Docs]]></title>
            <link>https://medium.com/@jitbit/fix-the-damn-docs-f71ecaf04b94?source=rss-cb5ee64ea3dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/f71ecaf04b94</guid>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Alexander Yumashev]]></dc:creator>
            <pubDate>Mon, 07 Jan 2019 14:52:27 GMT</pubDate>
            <atom:updated>2019-01-07T14:52:27.633Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*N6s1Jt66t2wKbiTu.jpg" /></figure><p>I blog a lot about customer service here.</p><p>Best practices, useful metrics, “how X helps with this” and “how Y helps with that”, blah-blah, yada-yada…</p><p>But wanna hear the best customer service advice ever?</p><p>The one that will cut your costs, boost conversions, close more sales and improve [<em>insert whatever buzzwordy metric here</em>] by friggin 99%?</p><p>There you go:</p><blockquote><strong><em>Go Fix Your Docs</em></strong></blockquote><p>No, seriously, it amazes me how companies are investing millions in fancy customer service gimmicks, like building rule-based chatbots, hacking cloud-based AI-backed NLP-powered FAQ-suggestions engines or some neural-network-backed phone answering machines…</p><p>Instead of simply fixing their half-assed user manual or updating the outdated API docs first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/419/0*lpmopaldEK2ypcEO" /><figcaption>* here and onward — actual screenshots of faulty docs posted by Redditors.</figcaption></figure><p>Docs shouldn’t be an afterthought. After all, <em>better help documentation means fewer support emails</em>. Fewer support emails means less distraction for your team. And your team can concentrate on moving your product forward instead of explaining how a basic feature works for the 1000th time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/0*cQHTDjt_LKrpTG-t" /></figure><p>According to Forrester research, <a href="https://go.forrester.com/blogs/16-01-28-online_self_service_dominates_yet_again_why_its_an_effortless_way_to_get_to_your_answers/">self-service is on the rise</a>. Not only customers search for answers online, they actually <em>prefer</em> to use self-service instead of talking to a person. Especially if your product is for developers or sysadmins. We’re introverts FFS, please don’t make us call you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/419/0*4hC-P14YJSSO0VL4" /></figure><p>Documentation never sleeps. It’s available 24/7. It needs no salary. And properly organizing and categorizing it helps people learn about unfamiliar features, making them <em>use your product even more</em> and discover new use-cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/0*CKt3X9WeVvsXHs7l" /></figure><p>But still so many companies are ignoring this. Docs are being written on the fly, after an app has already been launched. Or not written at all. Because docs are for pussies, right? Let’s measure “customer happiness” instead. Let’s send out a ridiculous survey to find out if they are “extremely satisfied”, “somewhat satisfied” or “somewhat dissatisfied”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*o9d3KKlw8gv6_56M" /></figure><p>I don’t want to point any fingers, but… well, I actually do want to point fingers. I’m talking about you, Salesforce. I’m talking about you, Microsoft. I’m talking about you, Atlassian. I’m talking about you, Facebook. And many many others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*YGZFUIfJALIcsI0Y" /></figure><p>I’m talking about all the companies who decided they’re all “agile” now and should release a new version every week — just without updating the docs.</p><p>I’m talking about all the companies who decided that “the old uncool API” should be deprecated but “the new cool API” barely has any documentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/0*jdZSMCBTjWwrORgX" /></figure><h3>Bad habit?</h3><p>Maybe it’s all coming from the non-digital age, when most sales were “one time”. Here’s my favorite picture from <a href="https://en.wikipedia.org/wiki/Kathy_Sierra">Kathy Sierra</a> to illustrate this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/477/0*TqeX2adWizw6vkUp" /></figure><p>We cant afford that any more. These days <em>everything is software</em>. Everything is becoming a SaaS — a subscription service of some sort. Even the old-school traditional stuff you’d never thought of.</p><p>Like, cars.</p><p>Last year Volvo’s “on call” network went down in Europe, making it impossible to pre-heat your car using the mobile app (which is a pretty huge deal if you live in northern Europe where winters are long, dark and cold). Hundreds of customers started tweeting at Volvo… And you know what Vovlo’s response was? “Please contact your local dealership”. No, Volvo, you’re a software company now. Join the club. I’m paying extra for this service, so you’re literally a SaaS provider now.</p><p>But enough with the rant.</p><h3>Handy tools to help build great docs</h3><p>Here are some tools that help build great docs (we’re not affiliated in any way):</p><p><a href="http://ricostacruz.com/flatdoc/">http://ricostacruz.com/flatdoc/</a> — a tiny JS file that renders beautiful documentation pages from markdown files.</p><p><a href="https://readthedocs.org/">https://readthedocs.org/</a> — a nice doc hosting option, can import from git/mercurial repos etc.</p><p><a href="https://docusaurus.io/">https://docusaurus.io/</a> — self-hosted Node-based docs engine</p><p><a href="https://en.wikipedia.org/wiki/Comparison_of_documentation_generators">https://en.wikipedia.org/wiki/Comparison_of_documentation_generators</a> — Wikipedia list of documentation generators (from source codes)</p><p><a href="https://docsify.js.org/">https://docsify.js.org/</a> — another self-hosted help site generator</p><p><a href="https://www.gitbook.com/">https://www.gitbook.com/</a> — paid (freemium) tool for docs authoring and hosting</p><blockquote>(please share your favorite tools in the comments, I will add them to the post)</blockquote><h3>P.S. A note about open source projects</h3><p>I’m mostly talking about commercial software. Open source is different in its altruistic nature. We should be grateful to people who decided to spent their free time building a software tool that we get to use for free.</p><p>So I’m more or less OK with this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*mF1uERfi9OCIvhjO.png" /></figure><p><em>Unless</em> the project is backed by Facebook, Google or Microsoft though, which makes it a whole different story. Corporations are backing open source for a reason. Which can be marketing, attracting talent, reshaping the market shares, hooking devs on their stack. “If something is free means you are the product” — and I’m totally OK with that.</p><p>But darn it, Microsoft, why are the ML.NET docs always a couple of releases behind?!</p><p><em>Originally published at </em><a href="https://www.jitbit.com/news/3301-fix-the-damn-docs/"><em>www.jitbit.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f71ecaf04b94" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customer Support by Founders]]></title>
            <link>https://medium.com/@jitbit/customer-support-by-founders-1f6f76bfdcdb?source=rss-cb5ee64ea3dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f6f76bfdcdb</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[founder-stories]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[customer-success]]></category>
            <dc:creator><![CDATA[Alexander Yumashev]]></dc:creator>
            <pubDate>Mon, 17 Dec 2018 23:10:48 GMT</pubDate>
            <atom:updated>2018-12-18T17:56:52.427Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Dkzp6JQ0SZQ7hatx.jpg" /></figure><p>I love answering support tickets. And — even though my team hates this — I try to do that every day. No, really, ask our customers. Nothing gives me a better understanding of how things are going, than spending an hour or two talking to our clients.</p><p>But the most frequent reaction to a “CEO” in my signature is:</p><blockquote><em>“CEO”, really? </em><strong><em>Wait, how big is your company exactly?</em></strong></blockquote><p>I get it — not everyone’s happy to buy from a “one-man-band” company. I even tried removing the “CEO” from my signature for a while — pretending I’m just an “Alex from techsupport” — to stop freaking people out, but then restored it back.</p><p>Look at this differently — the only reason people freak out is because a CEO/founder’s reply to a ticket <em>is very uncommon</em>. In fact, it’s so uncommon, they jump to a very sad conclusion “they must be really small and desperate”. That’s how low the bar is in customer service.</p><p>But once you address that first objection it’s nothing but a smooth ride from there. Here are the “pros” of founders involved in support (I’ll cover the “cons” in another post):</p><p><strong>Dogfooding on steroids</strong> — you’re not just using your own product, you’re in constant contact with people who use your product in ways you wouldn’t imagine. And that stupid design decision you made last week? Here, have some frigging feedback in your face right away.</p><p><strong>Authority</strong> — people are more… uhm… sensible when they know they’re talking to a founder. Helps a lot when dealing with angry feedback or when you’re about to say “no” to a feature request.</p><p><strong>Helps with churn</strong> — nothing helps you win a loyal customer better than a founder willing to solve their problem.</p><p><strong>Vision aware</strong> — you, as a founder, know your product (and where it’s going) better than anyone else. You know when to say “no” to a customer, but also — when to say “yes” and maybe even shift your whole vision of the product. A dozen times I found myself revising our whole roadmap or marketing positioning based on <em>one support ticket</em>.</p><p><strong>Quality</strong> — a founder typically provides better support. Even if the founder actually hates doing it. As a founder, you, of all people, know exactly that providing good customer service is not just about getting a “5 star/smiley face” rating after closing a ticket.</p><p><strong>And finally</strong> here’s a free advice. As a founder/CEO you probably read a lot about “customer development”, “client surveys”, “net promoter scores” and “focus groups”. <em>Well, before diving into all that crap just spend a day or two answering frigging support emails.</em> And make sure everyone in your company — developers, marketers, even the executives —spend a portion of their time talking to customers directly.</p><h3>It’s not for everyone though</h3><p><strong>Once it stops being fun — hand it over to a professional</strong></p><p>Support can be annoying. Customers can be irritating. If you find yourself cringing when you think about all the unanswered tickets waiting for you — it’s time to hand it over to a dedicated support person (or your co-founder).</p><p>I admit, a founder is way overqualified for this job, if it’s just a job<em> </em>to you. And since the quality of customer support <a href="https://www.jitbit.com/news/189-great-customer-support-improves-metrics-the-numbers/">is directly correlated with your revenue</a> a founders burnout can and will have a negative impact on your business.</p><p>It’s time to hand it over when it becomes a burden - if it becomes one.</p><p><em>Originally published at </em><a href="https://www.jitbit.com/news/3300-customer-support-by-founders/"><em>www.jitbit.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f6f76bfdcdb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The REAL reasons to be concerned about AI]]></title>
            <link>https://medium.com/@jitbit/the-real-reasons-to-be-concerned-about-ai-c933fd2e31df?source=rss-cb5ee64ea3dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/c933fd2e31df</guid>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Alexander Yumashev]]></dc:creator>
            <pubDate>Tue, 30 Oct 2018 22:11:30 GMT</pubDate>
            <atom:updated>2018-11-01T22:03:35.154Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EL7Gs4-f26sHfsMX.jpg" /></figure><p>Everyone’s being paranoid about AI these days. And the less people are familiar with the subject, the more concerned they are. Even some of my tech friends, even — believe it or not — <em>software engineers</em>, the ones who have a very vague idea of how AI/ML works, are expressing their concerns.</p><p>“The singularity is just around the corner!”</p><p>“AI is gonna take all our jobs!”</p><p>“Beware the almighty Machina!”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UmMYG9RxKCL2quDQ.jpg" /></figure><p>Here are my 2 cents on this. Actually, <em>my 3 cents</em> to be precise.</p><h3>1. The math behind AI is well known and has been for centuries</h3><p>Vector machines in multi-dimensional spaces, function approximation, regression etc. — all these things have been known and used for hundreds of years. Even the great and terrible her majesty Neural Network has been around <a href="http://www.psych.utoronto.ca/users/reingold/courses/ai/cache/neural4.html">since 1943</a>.</p><p>The majority of ML stuff is based around very basic math. Not even the advanced stuff like, I don’t know, differential equations, or tensors, or “string theory”, or some other complicated shit… It’s based on a thing called “linear algebra” which is studied in the first year of every engineering college in the world.</p><h3>2. CPU progress is about to plateau</h3><p>Remember the 90s? The “386” CPU came out and it was 2x faster than the “286”. But wait, in just a couple of years we got the “486” and it was even faster! Hold on, another 2 years pass and — holy shit — we have a Pentium now. Then a Pentium Pro/Pentium II. Followed by Pentium III… And don’t forget, we also jumped from 32bit to 64bit architecture at some point I don’t even remember when… And every time it was a <em>huge</em> leap forward.</p><p>Now we have reached the point, where increasing performance through transistor size is getting really tricky. Simply because it’s hard to build a stable production process that allows for massive quantities of chips. With 15 million of tiny microscopic transistors shoved into <a href="https://en.wikipedia.org/wiki/Transistor_count">1 square millimeter</a> it is statistically impossible to keep the error rate at zero.</p><p>That is the reason the “per-thread” performance is plateauing.</p><p>And the quantum computers are still 10–20 years away from mass production.</p><h3>3. But if CPUs are the same and the math is old — why the AI boom? WHY NOW?!</h3><p>One word. <em>The DATA</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hoEMuJLUTH4SXcN1.jpg" /></figure><p>Because for the first time in the history of humanity we have access to enormous amounts of data. Thanks to the Internet, “the Cloud” and the social networks. Thanks to the millions of pictures we post, thanks to the terabytes of content we generate, thanks to the <a href="https://www.statista.com/statistics/456500/daily-number-of-e-mails-worldwide/">281 billion emails sent every day</a>. Even in a small company like ours — we store tens of millions of support tickets in the <a href="https://www.jitbit.com/hosted-helpdesk/">help desk app</a> we host for our clients.</p><p>We, the humanity, finally have the means to analyze all that data. Forget analysing — for the first time in history we finally have a way to actually <em>store</em> all the l̵o̵a̵d̵s̵ ̵o̵f̵ ̵c̵r̵a̵p̵ massive amounts of data we generate. And it’s not even that expensive. Just think about it: my S3 monthly bill for all the file attachments in the above mentioned <a href="https://www.jitbit.com/hosted-helpdesk/">SaaS app</a> is somewhat around $20 a month. That’s millions of files attached to support tickets of all our clients in 10 years — for the price of three pints in a pub.</p><p>We can finally play with all that data, pairing it with the math we already have. And that’s what 90% of ML researchers are doing these days. They throw some random data at some random AI algorithm to see what comes out.</p><p>That’s why.</p><h3>P.S. But wait, you said there’s still a reason to be scared</h3><p>Yes. Well, kinda.</p><p>Since <em>DATA</em> becomes the most valuable asset (because algorithms are well-known and CPUs can be rented). The one who has more data — wins. And the more data you have — the more efficient you are — the more revenue you generate — the more access you have to EVEN MORE DATA</p><p>.</p><p>This is a vicious circle. Actually, more of a flywheel. <strong>Companies that already have the unfair advantage will keep increasing this unfair advantage</strong>. And AI speeds this flywheel up enormously.</p><p>Thus, it’s not the “singularity” we should be afraid of, it’s the dark cyberpunk reality where everything is controlled by huge AI-powered corporations and everyone’s being watched.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*NrXfO9PiIiPURdeh.jpg" /></figure><p><em>Originally published at </em><a href="https://www.jitbit.com/alexblog/274-the-real-reasons-to-be-concerned-about-ai/"><em>www.jitbit.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c933fd2e31df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cool Regex performance hacks I bumped into]]></title>
            <link>https://medium.com/@jitbit/cool-regex-performance-hacks-i-bumped-into-83c9fdd1976b?source=rss-cb5ee64ea3dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/83c9fdd1976b</guid>
            <category><![CDATA[regex]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Alexander Yumashev]]></dc:creator>
            <pubDate>Tue, 06 Mar 2018 12:13:28 GMT</pubDate>
            <atom:updated>2018-03-12T12:03:52.830Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ux1p85rV4Hp6rZBTPbGXCw.png" /></figure><p>The first part of this post applies only if you run ASP.NET on Windows, you can simply <a href="#3148">skip to the regex</a> hack if not interested, but I strongly recommend you read the whole post.</p><h3>Debugging ASP.NET CPU spikes</h3><p>About three weeks ago we started seeing unusual CPU load spikes on our <a href="https://www.jitbit.com/helpdesk/">customer service app</a> production server (the cloud-hosted version). We do have a super useful <a href="https://github.com/jitbit/cpu-analyzer">tool</a> (originally written by mister <a href="https://samsaffron.com/">Sam Saffron</a> who kindly allowed me to modify it a little bit and whom I’d like to thank here: sir, this little gem of yours continues to be a life saver in my little company) showing the exact call stacks that use up all the CPU ticks</p><p>But the problem is you have to “attach” this tool to the process at the exact moment the CPU load spikes up. And “catching” that moment can be… uhm… hard.</p><p>Even though we’ve set up AWS to text us when CPU load gets higher than 75% and stays there for 5 consecutive minutes (a must have for anyone who runs a business-critical SaaS app by the way) the time it takes to run to my laptop, remote-login to the sever, get to the command-line, attach to the overloaded process etc etc… CPU load gets back to normal. Darn.</p><p>Luckily my cofounder has written a short Windows .BAT script that does this automatically — if the CPU load gets higher than 75% the script finds the web-application process ID, launches the tool, attaches it to the PID and dumps the call-stack data to a text file (if you’re going to use the script, change the “OurApplicationPool” to the actual user account that runs your app pool).</p><pre>@Echo OFF<br>SET /A &quot;MAXUSAGE=75&quot;<br>For /F %%P in (&#39;wmic cpu get loadpercentage ^| FINDSTR &quot;[0-9]&quot;&#39;) do (<br>  echo %%P<br>  IF %%P GTR %MAXUSAGE% (<br>    for /f &quot;tokens=1,2 delims= &quot; %%A in (&#39;tasklist /FI &quot;USERNAME eq OurApplicationPool&quot; /fo table /nh&#39;) do cpu-analyzer.exe %%B &gt;&gt; log_%date:~-4,4%%date:~-7,2%%date:~-10,2%.txt<br>  )<br>)</pre><p>Then we have simply set up a job in Windows Task Scheduler that runs every 5 minutes (I know, but we needed a quick and dirty solution).</p><h3>In our case — it was Regex</h3><p>After some digging through the logs and call stacks it turned out most of the CPU ticks were spent on Regex.Search. Our helpdesk app uses <em>A LOT</em> of regular expressions both on the back and front ends. For example, when converting markdown and &quot;BbCode&quot; (used for internal storage) to &quot;normal&quot; HTML (used for UI and emails).</p><p>Long story short, after hours of blindly trying different regex patterns, testing and benchmarking here’s what I found:</p><p>If you want to match a rule that goes “<em>something is not preceded with an ‘A’ ”</em> don’t ever use code like this: (^|[^a])something (the first group basically says &quot;it&#39;s either the beginning of the text OR not the letter A&quot;). Most people find it more readable compared to a &quot;regex lookbehind&quot; (including myself, I keep forgetting the syntax).</p><p>But it turns out <strong>regex &quot;lookbehinds&quot; and &quot;lookaheads&quot; are almost 3-4 times faster than patterns involving &quot;beginning/end of string&quot;</strong> especially when working with large stings. In our case replacing (^|[^a]) with an (?&lt;!a) (which literally means &quot;not preceded with&quot;) has made our code 3 times faster. I wrote a quick benchmark test that does 10000 search-replace iterations in both .NET and JavaScript regex engines (we use both) and the results were:</p><pre>╔════════════════════════╦═══════════════╗<br>║ (^|[^a])something      ║  1346ms (avg) ║<br>╠════════════════════════╬═══════════════╣<br>║ (?&lt;!a)something        ║  389ms (avg)  ║<br>╚════════════════════════╩═══════════════╝</pre><p>Whoa, that’s more than 3 times faster! Obviously, the longer the input text you have, the bigger the impact.</p><h3>Wait, there’s more</h3><p>Cool. But can we improve it even further? Is there a way to make <em>a “not preceded with an A”</em> rule even faster?</p><p>Turns out there is! Unfortunately there are not many regex performance analysis on the net, so (again) I was on my own here… But fortunately I somehow remembered reading a cool <a href="https://news.ycombinator.com/item?id=10282121">HackerNews post</a> couple of years ago that suggests a great way to optimize rules like “not preceded with” or “not surrounded with” or “not ends with” and similar. Basically the trick goes like this:</p><p>asomething|(something)</p><p>Nice, huh? If you want to match “something not preceded with an A” simply MATCH WHAT YOU DON’T WANT and then ignore overall matches, looking only at “Group 1”! The benchmarks:</p><pre>╔════════════════════════╦══════════════╗<br>║ (?&lt;!a)something        ║  389ms (avg) ║<br>╠════════════════════════╬══════════════╣<br>║ asomething|(something) ║  16ms (avg)  ║<br>╚════════════════════════╩══════════════╝</pre><p>Holy sh*t! That’s almost a hundred times faster than my original code!</p><p>The only downside that I discovered is that this trick works only on relatively simple patterns. When you start replacing something with more complex subqueries, the performance gain disappears, getting pretty close to the 2nd variant — the (?&lt;!a)</p><p><em>Originally published at </em><a href="https://www.jitbit.com/alexblog/272-cool-regex-performance-hacks-i-bumped-into/"><em>www.jitbit.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83c9fdd1976b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>