<?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 Chris Loughnane on Medium]]></title>
        <description><![CDATA[Stories by Chris Loughnane on Medium]]></description>
        <link>https://medium.com/@pchrisl?source=rss-50b869a62a57------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*xQkf3r_YqKcjMFwO.jpeg</url>
            <title>Stories by Chris Loughnane on Medium</title>
            <link>https://medium.com/@pchrisl?source=rss-50b869a62a57------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:13:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pchrisl/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[Hack: Getting Onshape Comment Notifications in Slack]]></title>
            <link>https://medium.com/pdnotebook/hack-getting-onshape-comment-notifications-in-slack-1a7f7fda6133?source=rss-50b869a62a57------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a7f7fda6133</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[hacks]]></category>
            <category><![CDATA[onshape]]></category>
            <dc:creator><![CDATA[Chris Loughnane]]></dc:creator>
            <pubDate>Thu, 10 May 2018 12:32:18 GMT</pubDate>
            <atom:updated>2018-05-10T12:32:18.157Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/841/1*bNXQGG2RtpxnOzFACW5tkg.png" /></figure><p>I love Slack and Onshape, but for now the two don’t talk together. With everything else going through slack, often those comments get lost. I’ve come up with a workaround that works great for us until Onshape opens up their comment API.</p><p>Spending 10min writing this post… so all you get is an outline :)</p><ol><li>Create an additional free Onshape account. (Onshape only sends comment emails when the user requesting the comments is not in Onshape, so to get all the emails you need to have a user who is <strong>never</strong> in Onshape). We’ll refer to this account as the “BOT” account.</li><li>Add “Email” slack integration</li><li>Add the <em>@xxxx.slack.com</em> email address to your BOT account and make it the primary email address</li><li>Select a channel for the notifications to be sent to (we use a separate “bot” channel to collect hardware-related content from various web tools)</li><li>In your original Onshape account share a document with the BOT account</li><li>In your BOT account check the “Receive comment email notifications checkbox”</li><li>Close out of your BOT account</li></ol><p>Now whenever <em>anyone</em> comments in that document:</p><ol><li>Onshape will check to see if the BOT account is logged in (it won’t be)</li><li>It will send an email to the the primary email address on the BOT account (the email address from the “Email” slack integration)</li><li>Slack will pipe that email to the channel of your choosing.</li></ol><p>Tada. Onshape comments in Slack!</p><p>Hopefully soon this functionality will be more properly implemented.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a7f7fda6133" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pdnotebook/hack-getting-onshape-comment-notifications-in-slack-1a7f7fda6133">Hack: Getting Onshape Comment Notifications in Slack</a> was originally published in <a href="https://medium.com/pdnotebook">Product Development Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hardware startup mechanical starter pack]]></title>
            <link>https://medium.com/pdnotebook/hardware-startup-mechanical-starter-pack-e43eaf059a6e?source=rss-50b869a62a57------2</link>
            <guid isPermaLink="false">https://medium.com/p/e43eaf059a6e</guid>
            <category><![CDATA[mechanical-engineering]]></category>
            <category><![CDATA[hardware-startup]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[hardware]]></category>
            <dc:creator><![CDATA[Chris Loughnane]]></dc:creator>
            <pubDate>Mon, 18 Sep 2017 18:01:01 GMT</pubDate>
            <atom:updated>2017-09-18T19:44:44.520Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*k1xILcp1c6QuAo1mDLAHnQ.jpeg" /></figure><p>Twice now (when building the mechanical team here at Empatica as well as when I was at Quanttus) I have jumped into a startup with no supplies on the mechanical side.</p><p>In both cases I stocked the “lab” (sometimes just a small desk) as best I could based on what I could recall from more proper labs (at Farm and Continuum).</p><p>And of course sometimes I didn’t realize what I didn’t have until I needed it, resulting in rush Amazon/Mcmaster orders or a quick run over to RadioShack or Blick Art Supplies.</p><p>It’s frustrating having an engineer held up because they lack a $25 item, so I started to keep track of everything I ordered. Some of them were specialty items (specific to wearables firms), but most I think are necessary for any practicing mechanical engineer to be fully productive.</p><p>Below is the list I made for you. You might not need some of the items (though I bet you need most) and you might need to adjust the parameters on others. Still, take a run through and see if there is anything you’re missing… especially if you’re just getting started.</p><p>A few quick notes before the list.</p><ul><li>Everything is linked to Amazon. Surprisingly it was better than Mcmaster for general stocking. Here is a <a href="http://amzn.to/2wKFa0z">complete Amazon shopping cart</a>.</li><li>There is no capital equipment (drill press, Bridgeport, etc.) on this list with the assumption that if you’re just starting out you probably don’t have the space for such tools.</li></ul><p>With that said… here we go.</p><h3>Hand Tools</h3><ul><li>Your fingers are too big. Make sure you have a set of <a href="http://amzn.to/2wgxAaZ">tweezers</a>.</li><li>For detailed assembly, a <a href="http://amzn.to/2wgQG0u">set of picks</a> (like your dentist has) is a must.</li><li>Wiha is the one who makes the drivers (<a href="http://amzn.to/2viqk0F">Torx</a> as well as <a href="http://amzn.to/2w9DUSR">slotted and philips</a>) driver sets you love.</li><li>Even if you don’t have a drill press on hand, you’ll want a <a href="http://amzn.to/2w9Tcaq">pin vice with some drill bits</a> for fine work on SLAs and aluminum parts.</li></ul><h3>Cutting/shaping tools</h3><ul><li>At some point you’re going to have some machined protolabs (remember FirstCut?) parts in your hands and realize you need some <a href="http://amzn.to/2w9Cxnj">tap handles</a>, set of taps (these <a href="http://amzn.to/2xpa6R8">ones</a> from Merlin tools worked just fine for us), and maybe some <a href="http://amzn.to/2xoI5ch">tap magic</a> just to be safe.</li><li>Don’t go back to scissors, <a href="http://amzn.to/2wAAWYK">X-Acto knives</a> and <a href="http://amzn.to/2wB82YF">replacement blades</a> should always be on hand. While you’re at it, pick up a <a href="http://amzn.to/2vitXUG">cutting board</a></li><li>Prototypes come in wrong. Be sure to have a <a href="http://amzn.to/2wgkJFv">set of files</a> on hand to set them right.</li><li>If things come in really wrong, it’s good to have a <a href="http://amzn.to/2wKr7YX">Dremel</a> on hand :)</li></ul><h3>Electrical</h3><ul><li>I actually got pretty far without a <a href="http://amzn.to/2wgtPCp">power supply</a> until the day I couldn’t power up an LED.</li><li>A <a href="http://amzn.to/2vim55D">fluke multimeter</a> (and <a href="http://amzn.to/2vj6z9l">test lead kit)</a>… because even mechanical enginers to check connectivity and resistance :).</li><li>Your going to need a soldering iron. <a href="http://amzn.to/2iyRqL2">Weller</a> feels like home.</li><li>No sense in having a soldering iron without <a href="http://amzn.to/2xEmKuG">solder</a>, <a href="http://amzn.to/2viSOHP">solder paste</a>, <a href="http://amzn.to/2xEonbR">flux</a>, and a <a href="http://amzn.to/2viET4H">tip cleaner</a>.</li></ul><h3>Organization</h3><ul><li>Unless you want <em>everything</em> all over your desk, get at least a few <a href="http://amzn.to/2wKwpDH">craft cabinets</a> and <a href="http://amzn.to/2vi9Sh4">adhesive labels</a>.</li><li>Various sizes of <a href="http://amzn.to/2viSLvI">jewelery box organizer</a> for kitting assemblies. Particularly useful for packaging prototypes (and it’s critical contingencies) for travel.</li><li>Various sizes of <a href="http://amzn.to/2xoQ88K">clean plastic zip baggies</a>, for keeping less structured things organized.</li></ul><h3>Fixturing</h3><ul><li>When you can’t drill a vice into the tabletop, a <a href="http://amzn.to/2xEJACC">vacuum base vise</a> is the next best thing</li><li>Sometimes you need to <a href="http://amzn.to/2viWj0W">(abror) press</a> things together. Hard.</li><li>Whether you’re soldering adhering, or just trying to keep things in place, everyone can use a set of <a href="http://amzn.to/2warWIV">helping hands</a></li></ul><h3>Measurement Tools</h3><ul><li>Calipers are great until you want to accurately measure Z. Get yourself a <a href="http://amzn.to/2xoBy16">Drop indicator</a>, <a href="http://amzn.to/2wgx0Kl">set of tips</a>, and <a href="http://amzn.to/2w9PXQq">stand plate</a>.</li><li>Everyone should have a pair of <a href="http://amzn.to/2w9CKXu">Mitutoyo Calipers</a>.</li><li>Also <a href="http://amzn.to/2wC3RYe">micrometers</a></li><li>Can’t measure a hole with a set of calipers. Better get Gage pins. (<a href="http://amzn.to/2wKyD5I">0.061&quot;-0.250&quot;</a> and <a href="http://amzn.to/2wAEDh4">0.011&quot;-0.60&quot;</a>)</li><li>A <a href="http://amzn.to/2xomQY9">feeler gauge</a> for gap measurement</li><li>Words can’t describe how amazing a value <a href="http://amzn.to/2w9fWXV">this $35 USB Microscope</a> is. It doesn’t replace a proper <a href="http://amzn.to/2xopi0P">boom microscope</a>, but dollar-for-dollar it can’t be beat.</li><li>You might think you can get away with a force gauge, until you realize you can’t (at least with good engineering conscience). Depending on your resolution needs you might be able to get away <a href="http://amzn.to/2wK1IhP">cheap</a> (like this) or have to shell out for something <a href="http://amzn.to/2wB75PQ">more expensive</a>)</li></ul><h3>Functional Test</h3><ul><li>Not every startup is trying to make something water resistant… but most are. Get a <a href="http://amzn.to/2viR9Cg">water resistance tester</a></li></ul><h3>Adhesives</h3><ul><li><a href="http://amzn.to/2iALJMY">Loctite 40340</a> bonds to most everything and is low odor and low bloom (critical for when gluing together last minute beauty models for investors)</li><li>Using “whatever tape is lying around” for electrical insulation doesn’t feel good. <a href="http://amzn.to/2iASoXr">Electrical tape</a> feels good.</li></ul><h3>Other Consumables</h3><ul><li>Your hands are gross. Use <a href="http://amzn.to/2vioMnn">nitrile gloves</a>.</li><li>You forget how bad you need <a href="http://amzn.to/2vjh9gN">low-lint wipes</a> until paper napkins make everything look gross and sloppy.</li><li>Adhesive is going to get everywhere you if you don’t use <a href="http://amzn.to/2xp096f">dispensing needles</a></li><li>An assortment of <a href="http://amzn.to/2wfRUsR">plastic shim stock</a> for making sure that prototypes fit <em>just</em> right</li><li>Compressed Air</li></ul><p>That’s it. All the general stuff we need to stay productive. If any of you have any additions (or recommendations on better deals re: price or quality) please let me know and I’ll update the list.</p><p>Happy building :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e43eaf059a6e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pdnotebook/hardware-startup-mechanical-starter-pack-e43eaf059a6e">Hardware startup mechanical starter pack</a> was originally published in <a href="https://medium.com/pdnotebook">Product Development Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Thoughts on Fitbit Iconic + Flyer]]></title>
            <link>https://medium.com/pdnotebook/quick-thoughts-on-fitbit-iconic-flyer-e433690f506d?source=rss-50b869a62a57------2</link>
            <guid isPermaLink="false">https://medium.com/p/e433690f506d</guid>
            <category><![CDATA[ionic]]></category>
            <category><![CDATA[wearable-technology]]></category>
            <category><![CDATA[fitbit]]></category>
            <category><![CDATA[wearables]]></category>
            <category><![CDATA[apple-watch]]></category>
            <dc:creator><![CDATA[Chris Loughnane]]></dc:creator>
            <pubDate>Tue, 29 Aug 2017 19:49:26 GMT</pubDate>
            <atom:updated>2017-08-29T19:49:26.024Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dlxCX3oqF_PxSns_.jpg" /></figure><p>On Monday Fitbit announced the launch of their first-ever proper smart watch, the <a href="https://www.fitbit.com/ionic">Fitbit Iconic</a>, along with a set of wireless headphones they call the <a href="https://www.fitbit.com/flyer">Fitbit Flyer</a>.</p><p><a href="https://medium.com/u/1318e3329733">Cherlynn Low</a> has a <a href="https://www.engadget.com/2017/08/28/fitbit-ionic-smartwatch-hands-on/">great writeup</a> over at Engadget that dives into all the details. In looking through it and then sitting back</p><h3>Background</h3><p>Fitbit’s been losing market share to Apple and Xiaomi for some time, and their stock price has dropped ~80% over the past 2 years. Fitbit clearly felt they needed to do something to push back.</p><p>Then they shipped this. Let’s break it down.</p><h3>What I like</h3><h4><strong>4 days battery life</strong></h4><p>(or 10 hours w/ GPS) is nothing to scoff at. Though looking at the bulk of the device I might have opted for 3 days in exchange for a smaller battery.</p><h4>SpO2 sensor</h4><p>It’s pretty sweet that they put an <strong>SpO2 sensor</strong> in there to measure oxygen levels in the blood. They’re only claiming to make “relative” measurements (probably due to the inherent difficulty of SpO2 at the wrist, though the poor fit of the device and resulting light noise probably doesn’t help either)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hh1dPuW2JrJIqzq_LX5rag.png" /></figure><h4>Nanomolding!</h4><p>Arguably Fitbit probably could have made device that gives identical value to it’s users <em>without </em>leveraging nanomolding… but it’s just so cool.</p><p>Nanomolding allows plastic to bond to metal during overmolding… but with incredible strength. Check out this old video to see what I’m talking about.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FKxsJpp8_aNk%3Fstart%3D32%26feature%3Doembed%26start%3D32&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DKxsJpp8_aNk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FKxsJpp8_aNk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6f0620e8079fddc2d4bc4e4a4a971110/href">https://medium.com/media/6f0620e8079fddc2d4bc4e4a4a971110/href</a></iframe><h4>Fitbit Pay</h4><p>Fitbit Pay will work wherever MasterCard, VISA, or Amex contactless payments are accepted.</p><p>This <a href="https://9to5mac.com/2016/05/19/fitbit-apple-watch-apple-pay-competitor/">had been expected</a>, but it’s still good to see it come out. It’s not going to rock the world, but for Fitbit to try to make a stand payments are an obvious choice.</p><p>That said I think they’ll have to push payments into some of their lower end devices (read: most of their units sold) soon in order to have a shot at it taking off.</p><h4>The Headphones</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/0*Bw2F3a-VY3dEv-tn.png" /></figure><p>I like that Fitbit even tried to make headphones. They’re a fitness wearable company and everyone wear’s headphones when they work out, so why not make your own and make the pairing experience seamless?</p><p>We’ll see how it all plays out (comfort and interaction are huge for something like headphones), but if it works out nicely, then good.</p><p>I don’t see any mention of optical or inertial sensors in the headphones (as <a href="https://support.apple.com/kb/SP750?locale=en_US">are present in Apple’s Airpods</a>), which seems like a missed opportunity there’s a lot going on up there to sense :).</p><p>It’s all the more glaring an omission considering they <em>do</em> have SpO2 in the Ionic. Hopefully a teardown will show it’s packing more than it seems.</p><h3>What I don’t like</h3><h4>The fit</h4><p>As I mentioned above the fit doesn’t look very good and hints toward poor optical performance.</p><h4>No cellular</h4><p>Especially on a device this large and with so much battery capacity, to not have cellular feels like a big miss.</p><p>This is even more pronounced by the <a href="https://9to5mac.com/2017/08/28/september-12-apple-event/">likely announcement of a cellular Apple Watch only a few weeks away</a>.</p><h4>Too edgy</h4><p>There’s no accounting for taste, and I’m sure none of the edges on the device cause pain, but it just looks too sharp for my tastes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*msf5FdY4Z6cEzrGE9zjGZg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oC9NaFGDm7e7Hr9iG8GD9g.png" /></figure><h4>Looks like a commodity</h4><p>It just doesn’t look special.</p><ul><li>The fits aren’t clean (though that will probably get a little better)</li><li>The bezel feels old school (likely because they used an LCD instead of AMOLED… maybe due to sourcing issues?)</li><li>My god, that logo. I like to imagine they could have put their <a href="https://images.duckduckgo.com/iu/?u=https%3A%2F%2Fstatic1.fitbit.com%2Fsimple.b-cssdisabled-png.he127ee977213a60001f4edd507132981.pack%3Fitems%3D%2Fcontent%2Fassets%2Fonezip%2Fimages%2Fdevices%2Fapp-icon-2x.png&amp;f=1">dot-matrix logo </a>somewhere more subtle. Although, to be fair, without it it might be difficult to tell this is a Fitbit… which just means they need a better design language.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uwVxm_Act_1DBhT4L-oQKQ.png" /></figure><h3>Conclusion</h3><p>I think it’s good that they made a few steps forward (SpO2, payments, headphones) but a bit disappointed that they didn’t go further (cellular, more sensors in the headphones) and at the overall design of the watch.</p><p>Honestly for me the biggest differentiator is SpO2. If the next Apple Watch doesn’t launch with it that could give Fitbit some time to create real value around in that space(though their optical design isn’t doing them any favors). However if Apple does have SpO2 (and likely cellular) it’s tough for me to see who would prefer the Ionic instead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e433690f506d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pdnotebook/quick-thoughts-on-fitbit-iconic-flyer-e433690f506d">Quick Thoughts on Fitbit Iconic + Flyer</a> was originally published in <a href="https://medium.com/pdnotebook">Product Development Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our experience w/ Onshape: Part 1]]></title>
            <link>https://medium.com/pdnotebook/our-experience-w-onshape-part-1-6ece7d40f100?source=rss-50b869a62a57------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ece7d40f100</guid>
            <category><![CDATA[hardware-startup]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[onshape]]></category>
            <category><![CDATA[cad]]></category>
            <dc:creator><![CDATA[Chris Loughnane]]></dc:creator>
            <pubDate>Thu, 24 Aug 2017 17:08:40 GMT</pubDate>
            <atom:updated>2017-08-24T17:08:40.339Z</atom:updated>
            <content:encoded><![CDATA[<p>A few weeks ago I <a href="https://www.linkedin.com/feed/update/urn:li:activity:6298531196116697088/">announced</a> that we were taking the plunge to Onshape for our production CAD needs. A few weeks in I’m clear on two things:</p><ol><li>Onshape has a lot of work ahead of them.</li><li>Even today, I don’t ever want to go back.</li></ol><p>Let me tell you why.</p><h3>Background</h3><p><em>skip this section if you just want the list of good/bad/annoying/TBD features</em></p><p>Having grown up in design consulting at <a href="http://www.farmpd.com/">Farm</a> (and later spending time at <a href="https://www.continuuminnovation.com/">Continuum</a>), clients dictated CAD tools. As a result, I spent a lot of time (and consider myself a pretty advanced user of ) both Pro|Engineer (now <a href="https://www.ptc.com/en/cad/creo">Creo</a>) &amp; <a href="http://www.solidworks.com/">SolidWorks</a>.</p><p>In recent years I’ve led the mechanical teams at two startups, putting me in a position to specify a CAD tool. I’ve historically preferred Creo for its control and raw power, but have chosen SolidWorks on both occasions due to its low cost and wider user base.</p><p>And it was fine. SolidWorks was fine. Just fine. It was fine.</p><p>Onshape came on my radar (thanks to <a href="https://medium.com/u/b8703acd0870">Scott Mackie</a>) back in 2015. I got excited about the philosophy of (SolidWorks + Google Docs + Git), took part in the beta, played around with it a bit, but still felt that it wasn’t ready for prime time.</p><p>I then moved on with my life until I saw <a href="https://twitter.com/jhirschtick/status/885939455458193408">this tweet</a> from <a href="https://medium.com/u/4bea51d63f70">Jon Hirschtick</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Q3dudZynlRxCQMOYYrdrw.png" /></figure><p>You see, for me, the N-sided fill is a safety net. I don’t use it a lot, but sometimes sweeps and lofts just won’t do. Sometimes you need a patch.</p><p>Also, some time had passed, and I was curious to see if/how Onshape had progressed.</p><p>Furthermore, I was now part of a team that had EE/FW in Milan, mechanical/manufacturing and manufacturing operations in Korea. The remote nature and time zone difference meant that sometimes simple questions like “what is the distance between those parts”, could mean a 24-hour turnaround.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z73ZFI1imhqy75kicsdYjg.png" /><figcaption>Boston — Milan is a 6-hour time difference</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/199/1*jxkcXXvBsSoxsvvWZk7AIA.png" /><figcaption>Our Git flow. Pre-OnShape</figcaption></figure><p>What’s interesting is that we were successfully using git/GitHub for a low-overhead version control of our SolidWorks database, so a combination of git/GitHub/edrawings would allow anyone to pull measurements as they could with Onshape.</p><p>This never actually happened though. Maybe it was unfamiliarity with git for some or an eDrawings issue with Mac on another, but in the end, it was a tool chain that set up barriers that would only be jumped in the most critical circumstances (i.e., still slowed down development).</p><p>Anyway, I followed up with Jon and got a trial. We did some diligence to prove to ourselves that our SolidWorks design was also buildable in Onshape.</p><p>It could (though my spline construction had to change), and we decided to make the switch.</p><p>Since the switch, I’ve tracked things I consider notable. They fall into three categories: the good, the bad, the annoying, and the TBD.</p><h3>The good</h3><h4>Branching/Merging</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/343/0*u1QvG_NUaoHHzC9o.png" /></figure><p>A huge value proposition of Onshape is its ability to <a href="https://www.onshape.com/videos/branching">branch and merge</a>. This lets me explore other designs without polluting the CAD database of record, but then merge back in that exploration if it turns into the database of record.</p><p>The first time I branched (to explore an alternate configuration of a circuit board) I did so with reckless abandon: I made unrelated changes, added/deleted features, changed sketch dimensions and variable names, added folders, appended PDFs, and probably some other things.</p><p>I then went to merge… and it didn’t work. I got an error saying:</p><p><em>“Failed to merge V12 into current workspace dev. An internal error has occurred; support code ef5064da1450….”</em></p><p>Naturally, I wasn’t pleased. However within the day, I had several back and forths with support, and it had been identified as a bug. Within a week the bug was fixed, and I merged everything successfully back into my main branch.</p><p>So, yes, there was a bug. I was fortunate that we didn’t have a release in that week as there was work happening on multiple branches. That said, such a speedy response (and the ultimate AMAZING ability for such an array of changes to be merged) deserves props.</p><h4><strong>Keyboard shortcuts</strong></h4><p>I’m not a monster. <em>Of course</em> I used keyboard shortcuts in other CAD programs. Still, I found Onshape’s out-of-the-box to be pretty good. In anticipation of switching I changed my SolidWorks shortcuts to match and noticed productivity even then.</p><p>So not a tech advantage, but a design element that was well-considered (that’ll be a theme)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ielzUQvktAq7wvHNEDAF8w.png" /></figure><h4>Support</h4><p>This can’t be overstated. Onshape clearly knows that the people paying for this (free unless you want public docs, then $1500/year. <a href="https://www.onshape.com/cad-pricing">details</a>) are using it as a critical element in their professional workflow. Support is crazy responsive. Just a few comments on that:</p><ul><li>The followups are usually same-day</li><li>I’ve had several back-and-forths within a day.</li><li>I had a proper bug and it was fixed within a few days</li><li>The support is just as good as a customer as it while they were selling me.</li><li>Also, the <a href="https://forum.onshape.com/">forums</a> are lively (with Onshape employees and users)</li></ul><h4>Sharing</h4><p>Working simultaneously with other contributors has been great. The experience with viewers has certainly been better than the git/GitHub/edrawings, but not as good as I’ve hoped. I suspect familiarity and the breaking down of initial barriers such as improper permission settings will help.</p><h4>Featurescript</h4><p><a href="https://www.onshape.com/featurescript">Featurescript</a> is the language Onshape uses to write it’s own features. They open it up so that users can write their own first-class features for use in the model tree.</p><p>Admittedly this is a pretty nerdy element, but it did let me create a measurement feature that helped me workaround that isn’t there yet.</p><h4>Folders</h4><p>Not a huge deal, but in the short time I’ve had access to it I’ve gotten used to keeping data sheets for components in the same Onshape folders as the CAD itself. Feels neat</p><h4>Semantic cleanliness</h4><p>Working in Onshape I get the feeling that there are a lot of CAD software engineers who were crazy excited to start from scratch. There are a bunch of examples of this but I think the extrude dialog is the best one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*9cVGb2PD2ymFbgq7YBiJAQ.gif" /></figure><h3>The bad</h3><h4>Lag</h4><p>Most of the time there is no issue. However sometimes it takes a few seconds for dialog boxes to close, which is awful. On balance it’s OK, but I’d love to see improvements on this.</p><h4>The merge issue</h4><p>Mentioned above. It was bad, but ultimately painless in my case and the support response was incredible. YMMV.</p><h4>FEA</h4><p>There are a few FEA tools on the Onshape store. I’m sure they have some capability, but the one I tried had an issue importing my master and so I jumped ship and used SimulationXpress on my SolidWorks seat for a basic FEA.</p><p>I’ll try out the options again when I have more time, but for now I’m jumping back into SolidWorks.</p><h4>Bezier Curves</h4><p>SolidWorks and Creo both have Bezier curves (SW calls them “Style Splines”, where Creo refers to them as having a “control polygon”).</p><p>Onshape doesn’t. It has has vanilla B-splines, which are fine, but less controllable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/303/0*0oyZrjZqjZCrOFUW." /><figcaption>Bezier curves (aka Style Splines) in SolidWorks.</figcaption></figure><h3>The annoying</h3><p>These are things that aren’t really a big deal, but I wish were better.</p><ul><li>The default line weight/zoom on drawings is too thick. It’s fine when you zoom in or export, but dumb otherwise.</li><li>I can’t customize keyboard shortcuts (thought I’ve submitted a request for SHIFT+X to give my a cross section… for now I’m stuck with a two-handed SHIFT+8)</li><li>If I change a variable name I need to change it everywhere it is used, which is impractical. Mid-way I switched from under_scores to CamelCase and it’s driving me crazy.</li><li>I can’t keep curvature combs on while I drag a spline, so I have to guess and check my curvature (exacerbated by the lack of Bezier curves mentioned above)</li><li>When you merge a branch, the graphic doesn’t show it as merged, there is just a note.</li></ul><h3>The TBD</h3><p>There are a few elements that I am sure I will have an opinion on, but haven’t put in enough time to make even a preliminary judgment.</p><h4>BOM</h4><p>To date our development BOM has been managed in spreadsheets and we haven’t swayed much from that. I’m very interested in checking out some of the options in the Onshape store, including OpenBOM and an app that pipes to google sheets (where our dev BOM currently lives)</p><h4>Release strategy</h4><p>In relation to the BOM above, the ability to keep track of which part is released when, what version of the master is being piped to a given part, etc. is a critical ingredient of sanity during production release. This certainly is possible with Onshape, but I will have more detailed thoughts later.</p><h4>Sharing/Viewing</h4><p>Similar to the release strategy, I think this will be better discussed after we’ve gone through some more cycles.</p><h4>FEA and Rendering</h4><p>There are a handful of apps in the OnShape store that might be good. Will have to check them out.</p><h4>Large databases</h4><p>Our database is relatively small (we make wearables, not space shuttles), so it’s possible that Onshape may become unwieldly for large projects. I don’t think I’ll be addressing this any time soon, but I want to call it out lest someone from Boeing advocates a switch.</p><h3>Bonus: Graphics Cards</h3><p>My team currently uses <a href="https://www.amazon.com/gp/product/B06XTNZ75G/ref=as_li_tl?ie=UTF8&amp;tag=pdnotebook0b-20&amp;camp=1789&amp;creative=9325&amp;linkCode=as2&amp;creativeASIN=B06XTNZ75G&amp;linkId=95923334e16f60e43d97239729951f91">Microsoft Surface Book with a Performance Base i7</a>. These have a detachable display with an integrated graphics card in the tablet section, and a higher performance graphics card in the the base (keyboard) section.</p><p>You can set various programs to default to use either graphics card. In the example below I set Firefox to use the performance graphics card and Chrome to use the integrated graphics.</p><p>The performance (as measured by <a href="http://cad.onshape.com/check">cad.onshape.com/check</a>) is nearly an order of magnitude using the higher performing graphics card. This makes a world of difference in graphic responsiveness (though saving features can still seem laggy on a slow WiFi connection)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1sE-aluoksOZ-A6HIbCfig.png" /></figure><h3>Conclusion</h3><p>Clearly Onshape isn’t without it’s warts, but it’s excellent data management &amp; sharing features, adequate geometric ability, crisp feel, and open approach (feature script!) makes it a great fit for the kind of work we do.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ece7d40f100" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pdnotebook/our-experience-w-onshape-part-1-6ece7d40f100">Our experience w/ Onshape: Part 1</a> was originally published in <a href="https://medium.com/pdnotebook">Product Development Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[posts being migrated from wordpress…]]></title>
            <link>https://medium.com/@pchrisl/test-c587b233a15c?source=rss-50b869a62a57------2</link>
            <guid isPermaLink="false">https://medium.com/p/c587b233a15c</guid>
            <dc:creator><![CDATA[Chris Loughnane]]></dc:creator>
            <pubDate>Sat, 07 Jan 2017 21:45:11 GMT</pubDate>
            <atom:updated>2017-01-16T14:42:48.678Z</atom:updated>
            <content:encoded><![CDATA[<p>we’ll be back up soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c587b233a15c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migrating to medium]]></title>
            <link>https://medium.com/pdnotebook/migrating-to-medium-675886971106?source=rss-50b869a62a57------2</link>
            <guid isPermaLink="false">https://medium.com/p/675886971106</guid>
            <category><![CDATA[self]]></category>
            <dc:creator><![CDATA[Chris Loughnane]]></dc:creator>
            <pubDate>Sat, 07 Jan 2017 20:10:34 GMT</pubDate>
            <atom:updated>2017-03-11T20:18:46.963Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*mVDMRqnCIUuhZinMT7I8hw.png" /></figure><p>After over 7 years on wordpress I’m migrating pdnotebook to medium.</p><p>Wordpress has been great, but over the past 2 years much of my online content has been posted in more vibrant communities such as quora, twitter, etc. My hope is that by migrating to a more dynamic platform that I can wrangle a lot of that dispersed content back onto pdnotebook.</p><p>There might be some hiccups… but just bear with me :)</p><p>-Chris</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=675886971106" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pdnotebook/migrating-to-medium-675886971106">Migrating to medium</a> was originally published in <a href="https://medium.com/pdnotebook">Product Development Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google can beat apple on hardware]]></title>
            <link>https://medium.com/pdnotebook/google-can-beat-apple-on-hardware-46cc2aeed90f?source=rss-50b869a62a57------2</link>
            <guid isPermaLink="false">https://medium.com/p/46cc2aeed90f</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Chris Loughnane]]></dc:creator>
            <pubDate>Wed, 05 Oct 2016 18:07:53 GMT</pubDate>
            <atom:updated>2017-03-11T20:11:43.369Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*tEebCehAqtYPF0YaQ3F7Lg.png" /><figcaption>Google’s new hardware lineup</figcaption></figure><p>This response was prompted by Onny Chatterjee in our internal Slack channel at Continuum posting the question:</p><blockquote>Any thoughts [on impact to Apple] on the Google announcements from yesterday?</blockquote><p>I responded</p><blockquote>I think it’s great. the stuff that apple is good at (making excellent hardware) is increasingly becoming commoditized. There are still things only they can do considering their supply chain prowess, but I don’t think that is what moves the needle for many consumers.</blockquote><blockquote>I think the big game changer here is AI (machine learning in particular). in the last few years accuracy of voice and image recognition has improved to near-human levels. This is going to change the way and frequency with we interact with technology and our expectations of it. Google is on the cutting edge of this from a technology standpoint, and this looks like they are pushing to take that lead from a product standpoint.</blockquote><blockquote>Without looking back, they are taking on, at least Apple (devices) Starry (Modular Wi-Fi… which is exciting beyond just getting better service), the slew of VR companies, and Amazon Echo. it’s really audacious, but when I think of the google services I already use (Maps, Inbox, Chrome, Drive, Photo, Youtube, Google Analytics) I think, why not? Isn’t it great that the cutting edge AI firm already knows how I live (creepy yes, but definitely convenient.)</blockquote><blockquote>My biggest cynicism would be that they would fuck it up. Google has historically has been really shitty at building consumer hardware. Glass was way way way overbudget (granted the concept was a reach) and their Nexus phones, while good, get lost in the mix of the wide world of android. However this lineup, at a glance, seems well-balanced and presumably ready to launch.</blockquote><blockquote>I’ve gone from Android (nerd cred… first android device the Tmobile G1) to iPhone to android and currently am back on iPhone. For me the best thing about Apple is that it’s UI is really really slick. The voice controls from headphones, the ‘delivered’ in imessage and a bunch of other little things just make it feel more polished.</blockquote><blockquote>But at the end of the day I really don’t think it’s that hard to duplicate, particularly if Google takes ownership of the device in a big way (which the appear to be doing) to solve the fragmentation problem. And in any case, AI advances are, as I said above, going to change the way I interact with tech, so perhaps some of the polish I like about iOS becomes moot quickly.</blockquote><blockquote>Will be really interesting to watch. If Google can scale smoothly and avoid any big supply chain or hardware problems I think apple might be in some trouble.</blockquote><p>What do you think?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46cc2aeed90f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pdnotebook/google-can-beat-apple-on-hardware-46cc2aeed90f">Google can beat apple on hardware</a> was originally published in <a href="https://medium.com/pdnotebook">Product Development Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visualizing error]]></title>
            <link>https://medium.com/pdnotebook/visualizing-error-16e1b91e2fbd?source=rss-50b869a62a57------2</link>
            <guid isPermaLink="false">https://medium.com/p/16e1b91e2fbd</guid>
            <category><![CDATA[statistics]]></category>
            <category><![CDATA[tolerance-analysis]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[d3js]]></category>
            <dc:creator><![CDATA[Chris Loughnane]]></dc:creator>
            <pubDate>Sun, 17 Jul 2016 22:17:28 GMT</pubDate>
            <atom:updated>2017-03-11T20:08:39.218Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*9kt5wNJwqXs78-Y1wnIYUQ.gif" /></figure><p>I’ve been thinking a lot lately about visualizing error. Standard methods like error bars, or shading a range don’t quite seem to capture it… I find that many people mentally draw a line right down the middle and putting less importance on the error.</p><p>So here is a pass at a different way of visualizing time series data. This dataset shows 3 trials with identical conditions run sequentially. I find that the motion of the points speaks to the variation and the shading in the back provides a good context.</p><p>You can see the code and a live demo <a href="http://bl.ocks.org/loughnane/5929d9a8520eaba7a292c416a83bd45d">here</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16e1b91e2fbd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pdnotebook/visualizing-error-16e1b91e2fbd">Visualizing error</a> was originally published in <a href="https://medium.com/pdnotebook">Product Development Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Notes from WEAR 2016]]></title>
            <link>https://medium.com/pdnotebook/notes-from-wear-2016-415dfda3eeb9?source=rss-50b869a62a57------2</link>
            <guid isPermaLink="false">https://medium.com/p/415dfda3eeb9</guid>
            <category><![CDATA[wearables]]></category>
            <dc:creator><![CDATA[Chris Loughnane]]></dc:creator>
            <pubDate>Mon, 27 Jun 2016 01:34:37 GMT</pubDate>
            <atom:updated>2017-02-22T02:57:46.454Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*a0rQpoqXAP60Qx89LF6F9A.jpeg" /></figure><p>I recently went to WEAR 2016.</p><p>The big thing that I’m thinking about now is how wearable tech might become more and more mainstream as voice UIs start to replace screen UIs in some contexts. Not needing a screen is a huge game-changer, but that’s a topic for another pos</p><p>Anyway, I took a few notes on some cool things from the conference. Enjoy!</p><p><a href="http://slides.com/chrisloughnane/deck-8/embed">WEAR CONFERENCE: Slides</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=415dfda3eeb9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pdnotebook/notes-from-wear-2016-415dfda3eeb9">Notes from WEAR 2016</a> was originally published in <a href="https://medium.com/pdnotebook">Product Development Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[prototyping is oxygen for hardware teams]]></title>
            <link>https://medium.com/pdnotebook/prototyping-is-oxygen-for-hardware-teams-beed11305c60?source=rss-50b869a62a57------2</link>
            <guid isPermaLink="false">https://medium.com/p/beed11305c60</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Chris Loughnane]]></dc:creator>
            <pubDate>Sun, 22 May 2016 17:16:27 GMT</pubDate>
            <atom:updated>2017-03-11T20:17:13.143Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*KWlTsM5BPEw3j8N6Cpdatw.png" /></figure><p>About 5 years ago I wrote a piece on the <a href="http://www.pdnotebook.com/2011/02/five-phases-of-done-ness/">five phases of done-ness</a>. So you don’t need to click through, the phases were:</p><ul><li>to be decided <em>(should we do a thing?)</em></li><li>to be changed <em>(have we done the thing?)</em></li><li>to be reviewed <em>(have we checked the thing?)</em></li><li>to be prototyped <em>(have we proved the thing?)</em></li><li>done <em>(let’s stop thinking about the thing)</em></li></ul><p>It was loosely inspired from David Allen’s Getting Things Done (GTD) and it served me well at the time. However as I started managing projects and managing other peoples tasks I found that it was too prescriptive.</p><p>The issue I found was in the <strong>to be reviewed</strong> column. By having it as an explicit phase right before the <strong>prototyping</strong> phase it was perceived that <em>everything should be reviewed before being prototyped</em>.</p><p>Which is bad. Really bad.</p><p>It’s bad because prototyping is like oxygen to a hardware development team; in order to operate efficiently they need sufficient supply (though a surplus has diminishing returns). If it is scarce then operation quickly becomes inefficient.</p><p>By putting a gate between engineers on the team and prototyping I was effectively making the development team ask permission to breathe.</p><p>So I tweaked the process. It looks something like this</p><ul><li>Won’t do <em>(we’ve chosen not to do this)</em></li><li>Might do <em>(we might do this)</em></li><li>Will do <em>(we’ll get to this)</em></li><li>Doing <em>(we’re doing this)</em></li><li>Done <em>(we’ve done this)</em></li></ul><p>So what was previously<strong> changed</strong>/<strong>review</strong>/<strong>prototype</strong> is now lumped all under <strong>Doing</strong>. This lets your awesome people not have to worry about identifying something for review (which they’ll do anyway’) before sending it out for prototype.</p><p>Not to say that reviews aren’t important, but I’ve found they’re better addressed by weekly task reviews or bi-weekly/monthly design reviews rather than by having them as an explicit part of a task management process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=beed11305c60" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pdnotebook/prototyping-is-oxygen-for-hardware-teams-beed11305c60">prototyping is oxygen for hardware teams</a> was originally published in <a href="https://medium.com/pdnotebook">Product Development Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>