<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dave Horan</title>
    <description>The latest articles on DEV Community by Dave Horan (@davehoran).</description>
    <link>https://dev.to/davehoran</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F175696%2F9226ca9d-57ef-4a21-8937-9ad4eb75be72.png</url>
      <title>DEV Community: Dave Horan</title>
      <link>https://dev.to/davehoran</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/davehoran"/>
    <language>en</language>
    <item>
      <title>Do you know WebRTC?</title>
      <dc:creator>Dave Horan</dc:creator>
      <pubDate>Tue, 25 Aug 2020 16:49:54 +0000</pubDate>
      <link>https://dev.to/davehoran/do-you-know-webrtc-2hg9</link>
      <guid>https://dev.to/davehoran/do-you-know-webrtc-2hg9</guid>
      <description>&lt;p&gt;Are you sick of bad web conferencing? Feeling the "zoom fatigue"? Be a part of the SOLUTION!&lt;/p&gt;

&lt;p&gt;We have a USA-based developer/tester opening at Immersitech (&lt;a href="https://immersitech.io"&gt;https://immersitech.io&lt;/a&gt;). We have developed a next generation spatial (3D) sound engine for web conferencing, distance learning, and gaming. This is a local (Rochester, NY) or remote USA-based position. &lt;/p&gt;

&lt;p&gt;This role will involve working on client-side WebRTC and SIP applications that interact with a wide variety of host collaboration applications, as well as creating adapters to host systems to interact with our sound engine. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;WebRTC/OPUS, SIP, VoIP&lt;/li&gt;
&lt;li&gt;JavaScript, ES6+, Typescript, Python, HTML5 with embedded media, JSON, XML&lt;/li&gt;
&lt;li&gt;Experience with C/C++&lt;/li&gt;
&lt;li&gt;React/Hooks, JSX, RxJS, Node, Meteor, Electron, Angular&lt;/li&gt;
&lt;li&gt;OS experience with Linux/Ubuntu, Android, iOS, MacOS, Windows and associated browsers - Chrome, Firefox, Safari, Edge&lt;/li&gt;
&lt;li&gt;Git, GitHub&lt;/li&gt;
&lt;li&gt;Using and developing secure REST-based APIs and secure websocket applications&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Other skills:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Audio software engineering experience a plus&lt;/li&gt;
&lt;li&gt;Additional consideration for development experience with communications platforms such as (but not limited to) Freeswitch, Slack, WebEx, Zoom, MS Teams, Big Blue Button, Blackboard, Twillio supporting multi-party collaboration/learning.&lt;/li&gt;
&lt;li&gt;Strong documentation and communication skills&lt;/li&gt;
&lt;li&gt;Experience with automated testing platforms&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you think you have the skills, and want to be a part of a growing startup, let us know! Email us at &lt;a href="mailto:hiring@immersitech.net"&gt;hiring@immersitech.net&lt;/a&gt;&lt;/p&gt;

</description>
      <category>career</category>
      <category>freeswitch</category>
      <category>webtrc</category>
      <category>remote</category>
    </item>
    <item>
      <title>Dear Younger Me</title>
      <dc:creator>Dave Horan</dc:creator>
      <pubDate>Wed, 22 Apr 2020 00:40:46 +0000</pubDate>
      <link>https://dev.to/davehoran/dear-younger-me-3cf1</link>
      <guid>https://dev.to/davehoran/dear-younger-me-3cf1</guid>
      <description>&lt;p&gt;Many of us (especially older developers) have been in this game a long time. We remember the days before the internet...yes, there were a lot of computers then too. As everyone grows in their career, you think back to what you have learned and from where. &lt;/p&gt;

&lt;p&gt;If you could send a letter (or email) to your past self, what advice would you give about your career? What to focus on? What work patterns (not design patterns) or ways of attacking problems would you gift to your past self?&lt;/p&gt;

&lt;p&gt;Thoughts?&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>career</category>
    </item>
    <item>
      <title>Will AR be the gateway drug for VR?</title>
      <dc:creator>Dave Horan</dc:creator>
      <pubDate>Tue, 26 Nov 2019 13:26:53 +0000</pubDate>
      <link>https://dev.to/davehoran/will-ar-be-the-gateway-drug-for-vr-4310</link>
      <guid>https://dev.to/davehoran/will-ar-be-the-gateway-drug-for-vr-4310</guid>
      <description>&lt;p&gt;With several companies now abandoning their virtual reality efforts, will augmented reality get better traction, and then lead to a resurgence of VR? What are you thoughts?&lt;/p&gt;

</description>
      <category>discuss</category>
    </item>
    <item>
      <title>What I learned selling a website</title>
      <dc:creator>Dave Horan</dc:creator>
      <pubDate>Mon, 18 Nov 2019 21:27:57 +0000</pubDate>
      <link>https://dev.to/davehoran/what-i-learned-selling-a-website-4pd3</link>
      <guid>https://dev.to/davehoran/what-i-learned-selling-a-website-4pd3</guid>
      <description>&lt;p&gt;I originally posted this on my blog in 2017. However, I've spoken with several developers who had dreams of creating a new community site or app they could sell. So, I figured it might be applicable here as well. &lt;/p&gt;

&lt;p&gt;[2017] I did it. I finally sold a small website. Can I quit my job and live on an exotic island, far from it. However, I did learn a lot from the process and am much better prepared to make the next site project easier to manage and sell. Although not a complete list, here are some general things I learned from this experience:&lt;/p&gt;

&lt;h3&gt;
  
  
  1. HAVE YOUR NUMBERS ORGANIZED
&lt;/h3&gt;

&lt;p&gt;The first thing people will ask for are the site numbers. This includes things like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Site traffic&lt;/li&gt;
&lt;li&gt;E-commerce sales&lt;/li&gt;
&lt;li&gt;Affiliate program commissions&lt;/li&gt;
&lt;li&gt;Hosting costs&lt;/li&gt;
&lt;li&gt;Recurring costs for third party products required to run the site&lt;/li&gt;
&lt;li&gt;Number of subscribers on your mailing list&lt;/li&gt;
&lt;li&gt;Number of followers on various social media accounts&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You basically will want to track and list any income and expenses for the site…like a business. In addition, potential buyers will want to know the audience they will be buying with the site. So any metrics related to social media and site traffic is essential. If you also have something like a discussion board, the system you use may provide some interesting statistics around the activity if the users. These will all be used in your sales listing to support the price you are asking for the site (and related assets.)&lt;/p&gt;

&lt;h3&gt;
  
  
  2. BE CLEAR IN YOUR SALES LISTING WHAT IS, AND IS NOT INCLUDED IN THE SALE.
&lt;/h3&gt;

&lt;p&gt;Be clear about what you are including in the sale of the site. Some people assume that “everything goes”, but that is not always the case. If you have social media accounts that your site auto-posts to, list them out specifically if you are selling them as part of the package. If there are accounts for third party social media management tools, email list tools, etc that you use, list those out, or explicitly state that they buyer will need to get their own tools to support these functions.&lt;br&gt;
People looking to buy a site often have a vision in their mind of what they are looking for. Noting what is included will help them determine where the “holes” are between their vision and your site. This will help weed out potential problem buyers up front.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. HAVE THE SITE ACCOUNTS AND RELATED SOCIAL MEDIA ACCOUNTS ORGANIZED
&lt;/h3&gt;

&lt;p&gt;If you use auto-posting tools, you may not always remember the passwords. If you run multiple sites, you may not remember what accounts are used by what sites. If this is the case.. get your record keeping in order! Seriously, make sure you have the right accounts that go with the site. A prospective buyer will certainly want to check out the public face of these accounts if they can. Also, if your site is a “closed” community, be prepared to create self-expiring guest accounts for prospective buyers.  &lt;/p&gt;

&lt;h3&gt;
  
  
  4. EXPORT YOUR MAILING LIST.
&lt;/h3&gt;

&lt;p&gt;One of the mainstays of any site is their email subscriber list. Don’t assume that someone will be using the same system that you are. If you are selling the list, prepare to get an export of your list. As these sometimes are activities that are batch processed through your mail list management provider, allow time for them to get you the data.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. KNOW YOUR DOMAIN TRANSFER PROCESS
&lt;/h3&gt;

&lt;p&gt;No transfer is without quirks. So, know the process that your registrar uses for domain transfers. The overall process is essentially the same, but each one has some “special” features that you sometimes don’t find out until you go to actually execute the transfer. You can save yourself, and your buyer, a lot of grief if you know the process for your registrar up front. There will be similar quirks with the destination register, so don’t expect this to be an automagical process.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. HAVE A PLAN FOR HOW YOU ARE GOING TO TRANSFER OWNERSHIP
&lt;/h3&gt;

&lt;p&gt;There are a lot of little details between domain transfer, actual site data transfer, mailing lists, social media accounts, and third party subscription accounts. If you think through this before you list the site, you’ll be in a better position to answer questions from a potential buyer as well as executing the process after the sale. Be flexible with this plan, as a lot will be determined by the technical savvy of the buyer.&lt;/p&gt;

&lt;h3&gt;
  
  
  7. YOUR SITE MAY NOT BE WORTH THE SAME TO YOU AS IT IS TO OTHERS.
&lt;/h3&gt;

&lt;p&gt;Presumably you created the site from scratch. It’s your baby. You’ve built it, nurtured an audience, added content, and have done your best to drive affiliate traffic and sales. You have a lot of time and energy invested. However, a potential buyer is looking at this as a business; as an investment. They will be objective, point out defects in your sites, tell you that your pet project site is ugly. Don’t take it personally. A buyer wants to “buy low and sell high”, so they will always give you a lower price than you would expect. This is where your data can show the value of the site, mailing list, etc. Don’t be disappointed if you eventually sell for something less than you initially wanted. This is not to say give up and sell out. Rather look objectively and see what the market is willing to pay for your site. Staying firm on a high price will often times defeat the original purpose…to sell the site.&lt;/p&gt;

&lt;h3&gt;
  
  
  Summary
&lt;/h3&gt;

&lt;p&gt;As the author Stephen Covey said, “Begin with the end in mind.” Now that I’ve been through the process, I know what records to keep and how to maintain the site if the end goal is to sell it. This also has shown me how to better build a site so it is “packaged” well for sale. Having a lot of paid (recurring) plugins, unsupported modules, and other loose ends can make the site unattractive to some buyers. I hope you’ve found this helpful. Now, go out and sell a site!&lt;/p&gt;

</description>
      <category>business</category>
      <category>startup</category>
    </item>
    <item>
      <title>Mint + Firebase</title>
      <dc:creator>Dave Horan</dc:creator>
      <pubDate>Thu, 06 Jun 2019 20:28:38 +0000</pubDate>
      <link>https://dev.to/davehoran/mint-firebase-48pd</link>
      <guid>https://dev.to/davehoran/mint-firebase-48pd</guid>
      <description>&lt;p&gt;I recently discovered Mint, and it looks like fun. Are there any existing examples of setting up Stores to connect with Firebase/Firestone?&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>mintlang</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
