<?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 Allan Wintersieck on Medium]]></title>
        <description><![CDATA[Stories by Allan Wintersieck on Medium]]></description>
        <link>https://medium.com/@wintersieck?source=rss-9c3094df6d8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*y0lXOyxnII1WlgN40x_qJQ.png</url>
            <title>Stories by Allan Wintersieck on Medium</title>
            <link>https://medium.com/@wintersieck?source=rss-9c3094df6d8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:15:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wintersieck/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[Product Manager’s Guide to IoT Security]]></title>
            <link>https://medium.com/swlh/product-managers-guide-to-iot-security-667a23bc1153?source=rss-9c3094df6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/667a23bc1153</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[iot-security]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[Allan Wintersieck]]></dc:creator>
            <pubDate>Mon, 29 Nov 2021 17:55:29 GMT</pubDate>
            <atom:updated>2021-11-30T17:34:02.228Z</atom:updated>
            <content:encoded><![CDATA[<h4>IoT technology is moving fast — don’t let your product’s security fall behind.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*dqH-cBf-HarwmnjJ.jpg" /></figure><p>The world of IoT has come a long way since 1990 when an MIT scientist introduced the world’s first internet-connected toaster. Although the original smart toaster didn’t quite make it in the new millennium, we are currently living in a world that is surrounded by connected devices.</p><p>This brings up an important question: how do we keep it all secure? In this guide for product managers, we’ll touch on the major security risks for IoT products and how to work with your software engineering team to prevent them.</p><h3>Security in IoT</h3><p>IoT is growing fast. Luckily, many IoT platforms (AWS IoT core, Azure IoT, etc.) have security features baked into them. In our experience, however, we’ve seen cases where security either gets bypassed (as companies rush to get a prototype out the door) or goes unaddressed because it doesn’t deliver immediate user value.</p><p>IoT security is not a sexy, user-facing topic, so it usually gets put on the back burner.</p><p>This means that product managers and developers must constantly engage with potential security concerns when building an IoT product.</p><p>IoT is multi-faceted. The many components of IoT offer a wealth of opportunities for data breaches. Each device and network connection can present a unique security risk.</p><p>Data breaches cost money and reputation. Now more than ever, users are concerned about data privacy. A breach will cost both money and public trust.</p><blockquote>IoT security is not a sexy, user-facing topic, so it usually gets put on the back burner.</blockquote><h3>Consumer IoT Security at a Glance</h3><p>You can look at IoT as a four-part data journey from the smart device, through the local network, up to the cloud, down to the companion app, and back again.</p><p>Take this example: your new home security camera detects motion at the front door. The camera captures video footage, then sends it through your home network to the cloud where it is analyzed. After running the video through some algorithms, a notification is sent to your phone telling you that a person walked by.</p><p>Quick definitions:</p><ul><li><strong>Devices</strong>: These are the hardware components of your IoT product — the physical sensors and microprocessors that accompany your smart devices.</li><li><strong>Network</strong>: The network is the collection of devices that communicate with each other. In most home network configurations, devices communicate with other devices on the network via some kind of wireless interface (usually Wi-Fi). Wi-Fi itself is not the network.</li><li><strong>Cloud</strong>: This is where your data is stored and things like real-time analytics occur.</li><li><strong>App</strong>: This is the mobile or web interface where users primarily interact with their devices.</li></ul><p>Each point in the IoT data journey presents its own unique security challenges, so we broke it all down for you below.</p><h3>IoT Device Security</h3><p>Whether it’s a home security camera or a smart faucet, if it has a Wi-Fi network connection, it can be attacked. An IoT device security attack opens the possibility for adversaries to manipulate and exfiltrate data from the device and any data running through the network. Whether the attack is successful depends on your device’s security methods. As a product manager, you can reduce security risks.</p><p>To protect against device-level security threats, start by limiting the number of attack vectors open on your device. Turn off unnecessary application protocols such as Telnet and SSH if your device does not need them during production. When in doubt, a port scanning tool (such as Nessus) can reveal potential threats which may go unnoticed by the development team. When such protocols are necessary to keep on during production, you should always disable the default login credentials.</p><p>Devices should always use secure communication protocols when connecting with the cloud (MQTT, HTTPS, WebSockets, etc.). Secure communication usually requires the device to store a private key in order to authenticate itself with the cloud service. The private key should be stored and used in such a way that it cannot be dumped from the MCU’s flash memory, such as on a cryptographic processor.</p><p>Even with every attempt to make your IoT device perfectly secure the first time, over time, you’ll need to update the device firmware to meet the latest security threats. Having an over-the-air (OTA) update strategy and infrastructure in place is paramount to maintaining device security throughout your product’s lifespan. It is often worthwhile to bring on a security consultant to run a security audit on your devices if you don’t have that expertise in-house. When a vulnerability is identified, make sure to promptly deploy a device firmware update to resolve it.</p><p>To review, product managers should keep these security best practices in mind when designing an IoT device:</p><ul><li>Devices should use a secure communication protocol for interacting with the cloud</li><li>Store private keys on a cryptographic processor instead of the MCU’s flash memory</li><li>Regularly update device firmware to keep up with the latest security concerns</li></ul><h3>IoT Network Security</h3><p>Your IoT devices might use a combination of Bluetooth, Wi-Fi, Zigbee, LoRa, cellular, and even satellite networks to stay connected. It’s critical to understand the common network architectures utilized by your radio access technologies of choice and the best security practices associated with them.</p><p>Since so many consumer IoT devices use Wi-Fi, let’s take a look at Wi-Fi security.</p><p>A common scenario to get your IoT device connected to your user’s home network is to program it to start in access point (AP) mode. This makes it discoverable by your user’s phone so that they can pass along their home Wi-Fi credentials via a mobile app.</p><p>For devices with “optional” IoT capabilities ( <a href="https://www.metrikus.io/blog/10-weirdest-iot-enabled-devices-of-all-time">such as smart litter boxes</a>) which are technically fully operational without being connected to the internet, these devices sometimes never get configured to work with the internet. So that device stays in AP mode. For years. Waiting for a <a href="https://en.wikipedia.org/wiki/Wardriving">wardriver</a> to come along and notice it and (hopefully not) take control of it.</p><p>Granting a hacker the ability to know how often Mr. Whiskers takes a visit to the ol’ sandbox probably isn’t of consequence to anyone. However, giving a hacker access to your device could also lead to <a href="https://www.cnet.com/tech/services-and-software/smart-tea-kettle-home-wi-fi-security-hot-water/">your user’s entire home network being compromised</a>, depending on how seriously your developers have taken network and device security.</p><h3>Cloud Security</h3><p>You are likely to use an enterprise cloud database to run your IoT devices. Major cloud computing platforms like AWS, Google Cloud, and Microsoft Azure offer secure protocols and automatic audits to facilitate the security of your IoT application. However, many of these security features require the nuanced experience of seasoned developers who are familiar with how and when to implement them correctly.</p><p>One cloud security problem we frequently encounter is poorly maintained and overly-lax access control lists (ACLs) for cloud resources. Your ACLs should be maintained in a systematic and sustainable way to make it easy to identify who has which permissions. Use access control groups instead of directly attaching policies whenever possible.</p><p>In addition to configuring user permissions, each IoT device should have limited permissions to only ready &amp; publish data that pertains to itself.</p><h3>IoT App Security</h3><p>Most IoT devices use a mobile or web interface for users to interact with the device. Your app needs the same attention to authentication and security as your device when it comes to interacting with your cloud services.</p><p>Ensure your users use strong passwords and two-factor authentication for account logins. Oftentimes, simply educating users about proper account management can make a major difference in protecting user data. Require capital letters, special symbols, and a minimum length. If possible, use two-factor authentication to verify each new login.</p><h3>Final Thoughts on IoT Security</h3><p>Building an <a href="https://devetry.com/blog/iot-architecture-every-component-you-need-for-your-iot-project/">IoT architecture from scratch</a> can be a daunting task, but trying to maintain and evolve that architecture over time can be even tricker.</p><p>A reliable IoT expert can identify potential vulnerabilities in your IoT architecture, help you take full advantage of security features provided by cloud services, and ensure that your IoT application has safety and security baked into its digital DNA from the beginning, not just hastily tacked on at the end.</p><p><em>Originally published at </em><a href="https://devetry.com/blog/product-managers-guide-to-iot-security/"><em>https://devetry.com</em></a><em> on November 29, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=667a23bc1153" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/product-managers-guide-to-iot-security-667a23bc1153">Product Manager’s Guide to IoT Security</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Monopolization of Tech Talent, & What You Can Do About It]]></title>
            <link>https://wintersieck.medium.com/the-monopolization-of-tech-talent-what-you-can-do-about-it-39d92756da75?source=rss-9c3094df6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/39d92756da75</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[cto]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Allan Wintersieck]]></dc:creator>
            <pubDate>Wed, 13 Oct 2021 16:56:32 GMT</pubDate>
            <atom:updated>2021-10-14T16:29:52.107Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*YxFMNuY1cy0RtkdN.jpg" /></figure><p>The monopolization of products and services has already molded our economy as giant companies disrupt industry after industry (or buy disruptive companies). To no one’s surprise, these large corporations’ success means that they are also starting to monopolize talent.</p><p>Unless you are managing a large company, it is becoming increasingly difficult to attract and retain technical talent. The situation is bound to get worse as these tech giants grow larger and accumulate resources to attract the best talent.</p><h3>Why This Sucks</h3><p>With the big firms having the lion’s share of the job market, the digital economy talent acquisition arena is <a href="https://fortune.com/2018/03/08/privacy-data-collection-facebook-google-amazon-apple-microsoft/">drastically becoming a one-man show</a>. The lack of competition can worsen the inequalities in the labor markets and hinder innovation and entrepreneurial growth. For instance, eCommerce giants like Amazon can strong-arm the formulation of taxation policies and hire the brightest and most competitive tech talent to carry out essential tasks to their business. This only worsens the already-pressing human resource problems for small firms.</p><h3>Can We Do Anything About It?</h3><p>Are we all doomed to lose our brightest software engineers to Amazon and Google?</p><p>I don’t think so.</p><p>But — engineering leaders need to focus on this problem and understand what truly matters to software developers. Continuing the cultures of the past is a sure-fire way to continue losing.</p><p>There are essentially only two ways to overcome the monopolization of tech talent. Both are listed below.</p><h3>Understand How Many Engineers You Need</h3><p>The demand for software engineers currently outweighs the supply. Therefore, you need to keep your custom code base at its minimum to reduce the number of engineers you actually need. Keeping the number of engineers in your company at a minimum makes hiring the ones you actually need more straightforward.</p><p>Use as much off-the-shelf software as possible (e.g. AWS tools and automation). Knowing when to build vs buy is just as important in your organizational strategy as your technology strategy.</p><h3>Attract &amp; Retain Engineers Over Your Competition</h3><p>Easy right?</p><p>Attracting and retaining technical talent over the big monopolies is a multi-step process. You’ve got to look at your current culture, find gaps, figure out what matters most to your current and future team members, message it accurately, and then actually take action to uphold those cultural changes. On top of that, you’ve got to consider essentials like compensation and a remote/hybrid policy. It’s certainly not as simple as, “let’s brag about PTO days.”</p><p>The first two steps (assessing your current culture and finding weaknesses) we can’t help you within this article. But we can help you find out what matters to software engineers, at least generally speaking.</p><p>Two months ago, we conducted a <a href="https://info.devetry.com/software-developer-survey">software developer survey</a> where we asked about compensation, culture, and what matters most. Here are some of the top takeaways.</p><h3>What Matters Most to Developers Today?</h3><p>According to about 500 developers, here are the things that matter most in their careers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OqPgY4Ol9RueFNQPAjYesw.png" /></figure><p>In order of most important to least:</p><ol><li>Compensation</li><li>Flexible work schedule</li><li>Remote options</li><li>Company culture</li><li>Technology</li><li>Impact of product or company</li><li>Industry</li></ol><h3>Different Folks Care About Different Things</h3><p>Unsurprisingly, not all developers rank “compensation” as number one. When asked to rank what matters most, we found three general archetypes for developers.</p><ul><li><strong>True Believers</strong>: Developers who value experience and culture over anything else</li><li><strong>Pure Tech:</strong> Developers who care about frameworks and languages first and foremost</li><li><strong>Flexibility Over Everything</strong>: Developers who value flexible work conditions and remote options.</li></ul><p>We think this is good news. If you’re a product with dated tech who maybe can’t pay as much as Big Tech, you still have hope. Maybe you can provide “flexibility over everything” and attract folks that way.</p><h3>Understand Why People Leave Their Jobs</h3><p>If you know why people leave, you can take action to fix it. When we surveyed developers, we found two interesting points of data:</p><ol><li>Male software developers most often leave their jobs because they have <strong>poor relationships with the management (20% of responders)</strong></li><li>Female engineers leave their posts most often because of a <strong>lack of professional growth opportunities (42% of responders)</strong></li></ol><p>We hear “people quit their bosses” and “women are promoted less often” a lot in the professional world, and it seems it may be true for developers as well. If you’re managing or recruiting a team, address these issues. Is there anything you could be doing better?</p><h3>Burnout is Here to Stay</h3><p>62% of software developers have experienced burnout in 2021. The top reasons being:</p><ol><li>Poor relationship with management</li><li>Lack of interest in work</li><li>Long hours</li></ol><p>Out of the 38% that didn’t report burnout, taking time off and focusing on mental health/wellbeing were the main ways they prevented it.</p><p>Point being: Burnout will affect most of your team members at some point, which can quickly lead to dissatisfaction and turnover. Improving your weak areas can reduce this which is a win for everybody.</p><h3>Download the Developer Survey</h3><p>There is more data and information in the survey, and you can view it all <a href="https://info.devetry.com/software-developer-survey">here.</a></p><p><em>Originally published at </em><a href="https://devetry.com/blog/the-monopolization-of-tech-talent-and-what-you-can-do-about-it/"><em>https://devetry.com</em></a><em> on October 13, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39d92756da75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IoT Architecture: Every Component You Need For Your IoT Project]]></title>
            <link>https://medium.com/swlh/iot-architecture-every-component-you-need-for-your-iot-project-98e5ce09fb1c?source=rss-9c3094df6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/98e5ce09fb1c</guid>
            <category><![CDATA[iot-platform]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[iot-architecture]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[Allan Wintersieck]]></dc:creator>
            <pubDate>Tue, 28 Sep 2021 18:12:38 GMT</pubDate>
            <atom:updated>2021-09-28T20:21:38.584Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*ZxTNNGu9-RqudFWfm_-4BQ.jpeg" /></figure><p>IoT architecture is a beast.</p><p>An IoT ecosystem has the potential of having thousands of sensors, hundreds of microcontrollers, and a handful of gateways before storing the data in your cloud. From the cloud, there are additional considerations before delivering that data to an application so it can be used.</p><p>We are currently building our own IoT product: Devetry’s Office Vitals, a smart system that measures temperature, carbon dioxide, and capacity in our Denver-based office. As we built out the IoT architecture, we realized that getting all the components right the first time is difficult. It requires planning and focus to get your IoT architecture components right.</p><h3>General Architecture of IoT</h3><p>No matter your size or complexity, there are four categories within the larger architecture of any IoT product.</p><ol><li><strong>Application</strong> — How is your consumer going to interact and use this data?</li><li><strong>Embedded</strong> — This is the hardware itself (and the custom software written to run on it). What kind of chips and sensors do you need to collect and send the necessary data?</li><li><strong>Network &amp; Connectivity</strong> — How is the data being sent to the cloud?</li><li><strong>Cloud &amp; Infrastructure</strong> — What kind of cloud infrastructure and database do you need?</li></ol><p>As you start to plan your IoT architecture, these are the four categories you’ll need to figure out as quickly and effectively as possible. Within each of these categories are a series of decisions you need to make, each affecting the other. This is why it’s essential to strategize and plan around your end user.</p><h3>Where to Start — IoT Architecture</h3><p>If you’re starting from scratch or trying to unlock specific data for the first time, start with your application’s architecture. Your final endpoint will shape the rest of your architecture.</p><p>As you think about your app, ask your team these questions:</p><ul><li>Why are we creating this application?</li><li>What kind of data do we need?</li><li>How will we obtain this data?</li><li>What are we doing with this data?</li><li>What might we want to do with this data in the future?</li></ul><p>You need to answer these questions upfront. The rest of your IoT’s architecture depends on it because once you start introducing hardware, it’s difficult to change.</p><p>The one expectation to this is if you already have a board. In that case, start with your embedded architecture components.</p><h3>Application Architecture</h3><p>Imagine a future where you have all the data you need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*zbEc8QiSJAB8LCQF.jpg" /></figure><p>What are you doing with it? Why are you creating this application?</p><p>Then you can start to think about how to deliver the data you need to the user-facing application. Will it be via a web browser, mobile application, smartwatch, or something else? To get a better idea of what to do, include <a href="https://devetry.com/blog/human-centered-design-principles-practices/">human-centered design principles</a> in your strategy.</p><p>Something to consider in this stage is data processing speeds. How quickly your device needs to process data will determine whether you lean on cloud or edge computing.</p><p>Edge computing is ideal for data that needs to be processed very quickly (heart monitors, autonomous vehicle braking system). The downside is that edge computing will increase the cost of the device itself.</p><p>Cloud computing is ideal for things that aren’t as “life or death” (coffee pots, doorbells). With cloud computing, you can also access the device from anywhere because everything runs through the cloud.</p><h3>Embedded/Hardware Architecture</h3><p>There are a lot of decisions you’ll need to make when it comes to embedded systems, the first being your sensors and actuators.</p><p>When selecting sensors, you have some considerations to take into account.</p><ul><li>Operating environment</li><li>Maintainability</li><li>Cost</li><li>Sensing ability</li><li>Sensitivity</li><li>Range of information</li></ul><p>After you’ve selected your sensors, you need to define your sampling method and sampling rate.</p><ul><li><strong>Sampling method</strong>: Will you sample via interruption or polling? I.e., Are you recording data every XX seconds? Or waiting for an event?</li><li><strong>Sampling rate</strong>: If you’re polling, how often will you sample? For this, you’ll need to consider how quickly the data you’re sampling changes. Determining if you need to sample every 1 second or 1 month makes a big difference in how you’ll collect and process that data. Further, depending on how urgently you need to send that data back to the cloud will influence the requisite quality of your network connectivity. If you sample too much, you’ll drive up network costs. Plus it’s wasteful. Generally speaking, you want to sample just enough data to get by.</li></ul><p>After you’ve got the above worked, out, the next piece of your IoT architecture is your microcontroller (MCU).</p><p>Your MCU processes all your IoT data. You’ll need one that does wireless communication. When choosing an MCU, get one that does a bit more than you need because as you develop your product, you’ll probably add features for your users.</p><p>Consider using an RTOS like FreeRTOS or MongooseOS which allows over-the-air (OTA) updates. You’ll be able to add new features and update security as vulnerabilities are found.</p><p>Other things to consider:</p><ul><li><strong>Cost</strong>: Especially for industrial IoT, you might need hundreds of microcontrollers. For consumer devices, you want to keep the cost of production low to maximize profit and make your product more accessible.</li><li><strong>Power</strong>: Your application may require your MCU to run off of a battery instead of being plugged into a power source. You need to understand how long the battery will last and which operating conditions will quickly drain your battery (for example, reading samples from sensors generally takes far less energy than performing wireless communication).</li><li><strong>Memory</strong>: If you need to aggregate large amounts of data for edge processing before sending it off to the cloud, you may quickly run out of memory!</li><li><strong>Gateways</strong>: If you have a low-power microcontroller, you’ll need a gateway. A gateway bridges your embedded architecture with your network.</li><li><strong>Information</strong> <strong>rate</strong>: If your sensors are producing a lot of information quickly, it might affect the MCU you get.</li></ul><p>Popular boards include Raspberry Pi, Arduino, and ESP, and we typically recommend one of these while prototyping. However, once you decide on a system, you will likely design your own board. This selection gives you the control, flexibility, and security that you need for your product.</p><p>Never put a development board into mass-produced/commercial products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*hAg4Xd2JNfQ75V01.jpg" /></figure><h3>Network/Connectivity</h3><p>Your network is how you’ll send data to your cloud. To choose this, you’ll need to know your embedded technology and your sampling rate. Whichever MCU you choose needs to support the networking interface you choose, but the networking interface should be driven by your operating environment.</p><p>Where will your product operate? In a car? In a cornfield? At a school?</p><p>This operating environment plus your sampling rate should give you insight into what kind of network/connectivity you need for your IoT architecture. Here are some popular options:</p><ul><li>Bluetooth (close to mid-range and low energy)</li><li>Wifi (mid to long-range. Wifi takes 10X the power, but is faster and can have a much longer range than Bluetooth)</li><li>Cellular (great for when your device is on the go in urban areas. You don’t need to be tethered to a wifi network or gateway, you just need to make sure you stay within the coverage area of your provider.)</li><li>Satellite (less conventional (read more expensive and harder to find a provider), but enables network connections in rural areas where cellular coverage isn’t available.)</li><li>LoRa (Long Range): Similar to wifi, but it reaches further (up to 10 miles in rural areas).</li></ul><p>The final thing to consider is reliability. Is your network going to be available at all times? If not, you might need to account for storage on your microcontroller or gateway.</p><h3>Cloud and Infrastructure</h3><p>Arguably the biggest decision for your IoT architecture is your database. After you’ve collected and sent all your data, how will you store it? With IoT, you’ll be collecting time-series data (at X time, the value is Y). Here are a few preferred <a href="https://geekflare.com/time-series-database/">time-series databases</a> for IoT.</p><p>If you’re unsure of which cloud provider is suitable for your team, know that each provider allows you to make a free account with a dashboard. So you can always tinker with each before choosing one.</p><p>Although, what will most likely drive your decision is what you’re most familiar with.</p><p>At Devetry, we have other infrastructure in AWS so it makes sense to stay in that ecosystem. AWS’s IoT Core plays well with its other products.</p><h3>Your Top Options for IoT Cloud</h3><ul><li><strong>Google</strong>: Google isn’t a dominant player in IoT right now, but trying to make a push.</li><li><strong>Amazon</strong>: They have everything you need, but, to us, it feels like they’re more focused on industrial IoT. One possible benefit is that Amazon has its own hardware brand called SiteWise. They also have SnowFamily (edge processing).</li><li><strong>Microsoft</strong>: Microsoft seems to be more friendly to consumer products.</li><li><strong>Cisco</strong>: Specifically focused on industrial and smart cities. They also have their own hardware</li></ul><p>To send information to the cloud, you’ll likely use MQTT protocol. For IoT, this has become the industry standard. This protocol keeps messages small.</p><p>To send information to your consumer-facing application or web browser, you’ll probably use protocols like MQTT or HTTP.</p><h3>How to Create your IoT Architecture Plan Quickly</h3><p>If you’ve made it this far, you understand the number of decisions you’ll need to make when creating your entire IoT architecture. Depending on your application, industry, and budget, your final architecture could be one of a hundred combinations. To find the ideal combination, we recommend an architecture sprint.</p><p>You want to make decisions as quickly and efficiently as possible. The quicker you can prototype an IoT, the better. During this one-week sprint, focus on the necessities, don’t worry about high-fidelity prototypes.</p><p>Being able to consult experts who have experience building IoT products will save you a lot of time as well. That’s why we recommend working with an IoT software development partner during your architecture sprint. The time and effort saved during an intensive sprint will save you in the long run.</p><p><em>Originally published at </em><a href="https://devetry.com/blog/iot-architecture-every-component-you-need-for-your-iot-project/"><em>https://devetry.com</em></a><em> on September 28, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98e5ce09fb1c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/iot-architecture-every-component-you-need-for-your-iot-project-98e5ce09fb1c">IoT Architecture: Every Component You Need For Your IoT Project</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We Asked Developers Why They Left Their Last Job. Here Are Their Answers]]></title>
            <link>https://wintersieck.medium.com/we-asked-developers-why-they-left-their-last-job-here-are-their-answers-fdd2c16f1ddd?source=rss-9c3094df6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdd2c16f1ddd</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[talent-acquisition]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[software-developer]]></category>
            <dc:creator><![CDATA[Allan Wintersieck]]></dc:creator>
            <pubDate>Mon, 13 Sep 2021 19:15:13 GMT</pubDate>
            <atom:updated>2021-10-14T17:35:07.712Z</atom:updated>
            <content:encoded><![CDATA[<h4>“Why did you leave your last job?”</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2NyiQKB6TdxLzGQHGHCo7g.jpeg" /></figure><p>This was the question we asked just under 500 developers in a survey meant to shine a light on the retention and attrition of software developers. We asked them a variety of questions, all of which you can view in our <a href="https://info.devetry.com/software-developer-survey">2021 developer survey results</a>.</p><p>One of the responses we were most interested in was the top reasons developers leave their jobs. The findings are not necessarily surprising, but they are insightful.</p><h3>Why did you leave your last job?</h3><ul><li>21.6%: Lack of professional growth opportunities</li><li>20% Poor relationship with management</li><li>18.4% Compensation</li><li>10.8% Burnout</li><li>7% Lack of flexible work options</li><li>6% Layoff (COVID or otherwise)</li><li>2.7% Lack of remote options</li><li>13.5% other</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tIb79x9P0_B2Il80.png" /></figure><p>According to the developers we surveyed, there were three main reasons one would leave their jobs: lack of growth opportunities, poor relationship with management, and compensation.</p><p>Burnout was the fourth reason, and while much less than the top three, 10% is still substantial.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L_AQgNvkExWQ9ubj.png" /></figure><p>The most common response, “lack of professional growth opportunities” was especially true for the female developers we interviewed. Almost 40% of women reported that as their top reason they left.</p><p>For men, the most common reason was a poor relationship with management with about 21% reporting that as their top reason.</p><p>This data aligns with other professions. You may have heard the often-quote “people don’t leave their jobs, they leave their managers.”</p><h3>Download the Full Report</h3><p><a href="https://info.devetry.com/software-developer-survey">Download the software developer results here.</a></p><p><em>Originally published at </em><a href="https://devetry.com/blog/we-asked-developers-why-they-left-their-last-job-here-are-their-answers/"><em>https://devetry.com</em></a><em> on September 13, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdd2c16f1ddd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“What Does Culture Mean to You?” — Software Developers Respond]]></title>
            <link>https://medium.com/swlh/what-does-culture-mean-to-you-software-developers-respond-3acdf170095f?source=rss-9c3094df6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/3acdf170095f</guid>
            <category><![CDATA[software-development-team]]></category>
            <category><![CDATA[tech-companies]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[cto]]></category>
            <dc:creator><![CDATA[Allan Wintersieck]]></dc:creator>
            <pubDate>Thu, 02 Sep 2021 16:32:12 GMT</pubDate>
            <atom:updated>2021-09-14T21:43:42.093Z</atom:updated>
            <content:encoded><![CDATA[<h3>“What Does Culture Mean to You?” — Software Developers Respond</h3><h4><em>Below are surveyed developer’s raw responses to the question, “What does culture mean to you?” While sorting through the data, we found a few buckets in which these responses fell.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lemd9468OtJ1g2gb.jpg" /></figure><p><em>The responses are categorized below. For more insight into developers, </em><a href="https://info.devetry.com/software-developer-survey"><em>download the developer report here</em></a><em>.</em></p><h3>It’s About Leadership</h3><p>“Knowing what kind of decision to make in a tough situation; one that aligns with what the company/founders would do.”</p><p>“To me, it means the philosophy of the leadership in why they do what they do, and why we as a company do what we do.”</p><p>“What the leadership does to ensure a safe, rewarding work environment that maintains high morale and reduces attrition.”</p><p>“What we as an organization choose to work on, build or foster. Whether that be a project, people, or ideas.”</p><h3>It’s About the People</h3><p>“Culture means having people who respect each other and are kind to each, encourage one another. Also, a team that encourages work-life balance. Socially, mostly everyone gets along and cares about one another, but also cares a ton about what they’re working on and how they build it.”</p><p>“The relationship in a team and the things done as a routine inside of the company.”</p><p>“The quality of employees, the amount of flexibility in the work schedule, the quality of work sponsored events, the freedom to work when and where I desire, company morals that align with mine.”</p><p>“Culture applies to the people who work in the company, how they feel about the company and what they expect from their colleagues. To build a challenging but supportive environment in which employees and grow while delivering high-quality products while making money would be ideal for company culture.</p><p>“Culture is all about the people at a company, and how they treat each other. Good culture means people are treated well and not just like resources to management.</p><p>“How co-workers interact with one another and how management interacts with workers. Company social outings, professional growth opportunities.</p><p>“The ‘feeling’ of working with other people. Is it positive, negative, collaborative, etc The culture of the company can be affected by a lot of things, but in the end, it is how everyone feels about being there.</p><p>“A culture where everyone can be uniquely themselves and each person brings something to the team and the team can adapt and grow together. No person left behind.</p><p>“To me, culture means all the myriad ways the people in a workplace treat others. This includes how they collaborate, socialize, respect, and support each other from junior to senior positions.</p><p>“People you work with, the ability to weigh in on arguments, feeling valued for your feedback, mentoring developers.</p><p>“Culture is the social environment of a company. It’s a combination of the attitudes and habits of rank and file employees and the priorities and direction set by leadership.</p><p>“It’s a bond you create with your team, just like a troop of soldiers will bond from being on the front line. When you have that feeling that you’re part of a group that is working together towards 1 goal, you don’t want to let anyone down. You are excited to join your team and start working on a problem. On the opposite end when the team doesn’t gel (or your turnover is so high you never connect with anyone) things grind to a halt and work becomes tedious.”</p><p>“How interaction with team/work looks day-to-day — am I being treated fairly/with respect? Is the work meaningful in some way (learning something new, creating useful/accessible tech…)?”</p><p>“How the employees are treated and treat each other.”</p><p>“Work environment including goals, coworker interactions, leadership, values.”</p><p>“The recognition of each individual, their needs, and the willingness of the company to adapt as needed.”</p><h3>Trust &amp; Autonomy</h3><p>“Too many things to really put into this little text box. It’s a whole bunch of fun words like autonomy and authority and not having to ask for permission because people trust you.</p><p>“The general tone and behavior of leadership have a huge impact on culture. Leadership that treats their employees as robots/children leads to a very dry a boring workplace. Trusting employees to get the work done while also engaging in some unrelated (to the work) distractions from time to time makes for a great culture and a place to work. Fellow colleagues will also impact the quality of the culture, of course.</p><p>“Whether you can trust your peers and management to do a good job, support you when needed, help you understand what you can do better, and help you align your professional goals with company goals.</p><h3>It’s About Values</h3><p>“The overall values of the organization and focus on either getting things done or having a process.</p><p>“What are the values that are upheld by the people at the company? The same way you’d describe how different groups of friends might behave.</p><p>“The values that a group holds and the framework in which they interact with each other and other groups/individuals.</p><p>“The shared values and principles across the people in the leaders and workers of the company, the customs, traditions, viewpoints, and objectives.</p><p>“The values of the company and how that’s reflected in my coworkers’ attitudes. How well people work together, and how willing people are to try new things and continually improve.</p><p>“What behaviors and attitudes are valued, normalized, and rewarded (tangibly or socially).</p><h3>It’s the Bigger Picture</h3><p>“Culture is somewhat intangible to me, but I’d describe it as the overall “feel” of the company and team. Do the connections between employees feel genuine and human or are they forced? Are there actual company traditions that people like to participate in, or are there just cheesy morning lightning questions and awkward happy hours? For me, the companies that actually have that right “feel” to them are the ones with good culture.</p><p>“The accumulation of the views and insights of the entire company (and whether or not the company takes them into account), no matter the position.</p><p>“The culmination of happiness, satisfaction, and general alignment of work among the company.</p><p>“The overall vibe of the company — how people treat each other, how many hours are expected of the team, making sure to keep the work daylight, having fun.</p><p>“The soul of the company.”</p><p>“How you foster the development and happiness of your employees, how you present yourself to the public, what you prioritize with company funding/revenue</p><p>“The talk becomes the walk. “We have a good work/life balance” becomes “hey why are you submitting code at night?”</p><p>“The collective personalities surrounding the mission of the company.</p><p>“The unspoken habits of a collective of individuals that drives how.</p><p>“Culture is the intangible atmosphere of how the company operates. It is the attitude all the workers have about the company and the expectations management has for the workers.</p><p>“The ability to grow and improve as an organization. Having fun. Respecting people without getting wrapped up in faux diversity.</p><p>“Culture is the intangibles of a team. A culture of fear is vastly different than a culture of support.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*JuUywDls_7ii4tvYxdXezw.jpeg" /></figure><h3>What do you Want in Company Culture?</h3><p><em>The following are some of the best responses to what developers are looking for in company culture.</em></p><ul><li>Engineering — Making technology choices that reduce risk, based on merit and empirical evidence.</li><li>Employees — Enthusiastic people working together. Constructive criticism is welcomed.</li><li>Teams — Build teams that need minimal oversight; give them freedom and responsibility.</li><li>Company — Compensates employees well. Recognizes the employees getting work done and rewards with pay raise. Flexible hours. Not looking to squeeze extra overtime hours out of its employees.</li><li>Social — Let’s play some yard games to give our brains a break from that cognitive load, so we’re recharged when we sit back down at a keyboard.</li><li>Environmental — Commitment to values aligning with minimizing climate change. Let’s shorten those commute times.</li></ul><p>“A place you can be yourself, be wrong, learn from it and it’s okay.”</p><p>“As a remote worker, most of my interactions are over Slack and Zoom. For me, culture is… Having lively, interesting Slack channels on professional and non-professional subjects. Supporting people in new/difficult roles.”</p><p>“Work/life balance, and a fun light-hearted atmosphere in the office.</p><p>“Caring about people — empathetic policies and practices that promote inclusion, equity, and health in the workplace.</p><p>“I really want to be meeting goals and growing as a person with my time, and the right balance of challenge and psychological safety creates a culture where a company can enable employees to do both — grow and thrive.</p><p>“Being trusted that I am knowledgeable and competent and given autonomy to build/figure out things on my own.</p><p>“Good management fostering clear direction and clear leadership. Friendly, accepting coworkers that want us all to succeed and progress in our careers.</p><p>“A good environment where people remember you are human.</p><p>“People that care about the quality of the software — from devs to management. And management that cares about their team members and has realistic goals. Harsh deadlines are the absolute worst.</p><p>“Team bonding activities, paired programming, employees making an effort to help and mentor.</p><p>“A place where I feel good at and comfortable in my own skin, I work with people who challenge me, are kind, and care about the work they do.</p><p>“Strong management but not overbearing. Friendly and nice people to work with and have a passion for getting things right.</p><p>“Healthy work environment. I enjoy going to work, I don’t dread it or wish for something to be different. No bad co-workers.</p><p>“A sense of community among coworkers, where everyone is respectful and open to hearing others’ opinions.</p><p>“Getting along with my teammates and feeling like we are actually working together vs competing with each other. A good manager who cares about me, how I’m doing, the amount of work I have to deal with.</p><p>“A company that represents itself from a community standpoint and embodies servitude leadership.</p><p>“An environment that is separate from the tasks at hand. The relationships and experiences that are shared outside work.</p><p>“I feel comfortable going to anyone on my team or at my company with questions or problems. I enjoy being with my coworkers outside of work and we are honest with each other about things we like and dislike about our work. The company is transparent (where it can be).</p><p>“Coworkers look out for each other, consider each other’s feelings, and look for opportunities to help each other improve.</p><p>“Good culture means that my values, thoughts, and what I find to be important, are also upheld by others.</p><p>“A community of people who share values. In the tech world, to me, this means people who value education and continued learning, a supportive community willing to share knowledge and experiences, a camaraderie amongst peers both in and outside of the workplace, and an opportunity to grow professionally within the company.</p><p>“Working with a group of people that care about doing a good job at whatever they’re working on.</p><p>“The people I work with and management — how they approach problems and conflict. A good culture has a good diversity of thought and is open to unexpected ideas and will evaluate them fairly.”</p><h4>More Insight</h4><p>These responses are part of a survey project, where we asked software developers about their work, culture, and compensation preferences. Download it below.</p><p><a href="https://info.devetry.com/software-developer-survey">Download the 2021 Developer Survey Report</a></p><p><em>Originally published at </em><a href="https://devetry.com/blog/what-does-culture-mean-to-you-software-developers-respond/"><em>https://devetry.com</em></a><em> on September 2, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3acdf170095f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/what-does-culture-mean-to-you-software-developers-respond-3acdf170095f">“What Does Culture Mean to You?” — Software Developers Respond</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Most Common Problems in Software Development]]></title>
            <link>https://medium.com/swlh/the-most-common-problems-in-software-development-b26360775c3?source=rss-9c3094df6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b26360775c3</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[cto]]></category>
            <dc:creator><![CDATA[Allan Wintersieck]]></dc:creator>
            <pubDate>Wed, 02 Jun 2021 20:22:39 GMT</pubDate>
            <atom:updated>2021-06-16T17:33:57.987Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“If an application crashes, it didn’t go down because of a bug. It went down because <strong>a junior developer</strong> checked in code <strong>without going through code review</strong> in an area of the codebase that <strong>wasn’t covered by unit tests</strong> because the project was <strong>running late </strong>because it had been <strong>under scoped</strong> from the beginning.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ILvBtc9_aLS4BoDW.jpg" /></figure><p>If you’ve worked on a digital product, whether as a product manager, engineering manager, or business leader, you know that the most common problems in software development are rarely as straightforward as “bugs.”</p><p>While the surface-level problem might be something like a bug, the root of the problem is closer to the story told in the quotes above.</p><p>My team and I have worked on hundreds of digital products, and we’ve seen all the common (and not so common) problems that plague software teams. To save your project from a similar fate, we’ve decided to share them with you so you can avoid common pitfalls and have a great product with less time, money, and headaches.</p><p>The good news is that because these issues are so common, they also have solutions that are relatively simple to implement. The bad news is that simple does not equal easy. Many of these solutions are difficult to implement when considering budget and resource constraints. Regardless, we’ll lay it out.</p><p>Here are the most common surface-level problems in software development, and typically why they happen.</p><h3>Problem: Bugs, Broken Code, &amp; Technical Debt</h3><p><strong>Why It Happens</strong>: Under-Scoping</p><p>Under-scoping is most often the cause of bugs during software development.</p><p>If the project wasn’t properly scoped from the outset, with an appropriate amount of time allotted for each stage, then your developers may start to cut corners and work in a rush to keep from falling behind schedule.</p><p>This is when semicolons start to go missing from the code or code gets checked in without undergoing the required code review, leading to application crashes and bugs galore.</p><h4>Solution: Plan Realistically, Not Optimistically</h4><p>A lean development approach is typically helpful. Set short, achievable milestones, and validate that you’re going in the right direction. Then iterate. This approach makes it harder to put together a complete plan, but you can be more confident in the accuracy of your estimates in the short term.</p><p>Another way is identifying up front which features are only “nice to have” and can be cut if you’re running up against a deadline.</p><p>Keep in mind that the “slow” way is often the fastest and most efficient way since hastiness invariably leads to a technical debt that will have to be made up later on.</p><p>Treating a problem at the source is much more effective than addressing a symptom. Take the time to consider what the root of the problem is-whether it’s a lack of time, skill, or oversight. This will yield huge savings in time and effort over simply hiring more developers.</p><h3>Problem: Premature Optimization</h3><p><strong>Why It Happens:</strong> Lack of strong code review process</p><p>Speed is too often treated as the highest good when it comes to code, at the expense of code that is clean or legible. It’s a common pitfall for developers to focus on writing optimized code that runs fast rather than code that can be read, understood, and maintained over the long term.</p><p>Hard-to-read code can slow your team down, particularly when engineers come and go. If an engineer comes in and can’t decipher code, you’ve suddenly got a big problem.</p><p>Premature optimization most commonly happens when there isn’t a strong code review process. Without this essential step, things get messy and cause problems down the road.</p><h4>Solution: Have a strong code review process</h4><p>A good code review process will ensure that the code is understandable, follows guidelines, and can be tested/debugged.</p><p>As for optimization, don’t worry about optimizing all of your code. Keep in mind that an application generally spends 90% of its time running 10% of the code. Once you know which 10% of the code that will be, you can focus your optimization efforts and prioritize legibility over speed in the rest of the code.</p><h3>Problem: Stuck With Complicated New Technologies</h3><p><strong>Why it Happens:</strong> Lack of Senior Leadership</p><p>It’s no surprise. Developers are drawn to hot new technologies. It’s no surprise. Tools such as AWS Lambda (that promise increased efficiency and flexibility) are exciting!</p><p>They can be great once you’re proficient with them, but it takes time to learn how to set up and test these new technologies. Plus, it’s like learning a new language. Once you progress past the basics, a little more nuance is required, and that can be time-consuming and challenging to navigate. An area where this issue plays out frequently is databases.</p><p>The root problem behind this is typically <a href="https://devetry.com/blog/what-happens-when-you-lack-senior-engineering-leadership/">a lack of senior leadership </a>. Software teams need engineers with experience. Those who know that new isn’t necessarily better.</p><h4>Solution: Prioritize Senior Leaders</h4><p>Senior leaders can mentor your less experienced engineers and encourage them to stick with proven tech (at least for now). They’ll be more likely to recommend familiar tools such as PostgreSQL or MYSQL. These are predictable entities that get the job done.</p><p>Whatever feature in a NoSQL database that caught your attention is probably not essential to your project. It’s a nice-to-have, not a need-to-have, and it probably has some limitations that you’re unaware of.</p><h3>Problem: Too Much (or Not Enough) Abstraction</h3><p><strong>Why it Happens</strong>: Either not understanding the problem domain or you’re paying developers by the line of code</p><p>Running your entire application out of a 10,000 line index.js file is a recipe for disaster, but going to the other end of the spectrum with 10,000 one-line files is also a bad idea.</p><h4>Solution: Find a happy medium</h4><p>Striking a balance is the way to resolve the abstraction issue. You want to aim for an approach that prioritizes code that is understandable and maintainable.</p><h3>Problem: Overlooking the Little Things</h3><p><strong>Why this happens</strong>: Again, underscoping</p><p>Let us reiterate. Underscoping a software project is one of the most common and detrimental mistakes people make.</p><p>Some of these little, overlooked things is a failure to cache or CDN static assets. Another is not adding the appropriate indexes to your database. These whoopsies can have huge performance implications, and they almost always come down to scoping problems from months prior.</p><h4>Solution: Scope Properly</h4><p>Here are three tips for better scoping:</p><ol><li>Involve a senior developer in the project scoping process. They’re more likely to remember all the little details than a PM or PO (who will be focused on features).</li><li>Keep track of what was missed in your last project. Use that list as a checklist for your next one.</li><li>Understand that a project doesn’t end when it is “released.”</li></ol><p>One silver lining to all the little things we overlook is that they’re usually not a part of the “core” of the project. A cache or a database index can always be added later, and budgeting to keep a developer engaged with a project after a release is a good way to clean up all the little details.</p><p>Bumps in the road are inevitable when you’re building a digital product, but knowing the common pitfalls and the steps to prevent them can help.</p><p>If you have already fallen to one of the common software mistakes, our advice to you is to take your time getting back on track. Trying to increase velocity when behind schedule is a <a href="https://devetry.com/blog/two-software-development-truths-vps-need-to-hear/">recipe for disaster</a>.</p><p><em>Originally published at </em><a href="https://devetry.com/blog/the-most-common-problems-in-software-development-2021/"><em>https://devetry.com</em></a><em> on June 2, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b26360775c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/the-most-common-problems-in-software-development-b26360775c3">The Most Common Problems in Software Development</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Two Software Development Truths VPs Need to Hear]]></title>
            <link>https://wintersieck.medium.com/two-software-development-truths-vps-need-to-hear-8e450e9343f4?source=rss-9c3094df6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e450e9343f4</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[cto]]></category>
            <dc:creator><![CDATA[Allan Wintersieck]]></dc:creator>
            <pubDate>Fri, 14 May 2021 14:09:07 GMT</pubDate>
            <atom:updated>2021-05-20T19:10:18.966Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*USkfvoVm_a7k5ybNCZImXQ.jpeg" /></figure><p>As a CTO, I’ve worked with a number of businesses. Some are creating their first MVP and some are well-established technology leaders.</p><p>Working with these kinds of organizations, it’s shocking how often the realities of software development are ignored. These realities tend to revolve around money and time.</p><p>If you’re tasked with overseeing a software product, and things start to get hectic, you need to remember two things:</p><ol><li>Software costs what it costs</li><li>Software takes a while to build</li></ol><p><em>You might think these truths are obvious, but in my experience, they are almost always forgotten about in times of stress.</em></p><p>I’m diving into these two ideas so the people in power of resourcing can see a developer’s point of view on money and time involved in creating software.</p><h3>Software Development Costs What it Costs</h3><p>When a project starts to go over with budget, business leaders try to get creative with their teams to save money. They’ll try to replace a senior engineer with two junior ones, or replace their front-end team with an outsourced team. But at the end of the day, no matter the “creative” makeup of your team, you’re not going to save that much money.</p><p>Two juniors take more time than a senior. An outsourced team needs to be managed more than an onshore resource. These tradeoffs are true for pretty much all team structures you’ve tried.</p><p>Here’s the truth. Software is expensive.</p><p>Look at the most successful software companies (the ones you want to emulate). Twitter employs over <a href="https://www.linkedin.com/company/twitter/people/?facetCurrentFunction=8">2,000 developers</a> globally. Asana has about <a href="https://www.linkedin.com/company/asana/people/?facetCurrentFunction=8">350 full-time developers</a>. Shutterfly? About <a href="https://www.linkedin.com/company/shutterfly/people/?facetCurrentFunction=8">590 software developers</a>.</p><p>My point is this: if your goal is to create enterprise software, you’re going to eventually need an enterprise team. Starting responsibly is of course the way to go, but once proven successful, it’s no longer worth cutting corners with complicated salary math.</p><p>A basic progressive web apps cost $100–120,000 to build. Native apps cost $200–250,000. Expect to pay 10–20% per year in maintenance. If you’re trying to improve your software and expand features and verticals, it’s much, much higher.</p><p>That’s what software costs. You might be able to save a little money with odd people combinations, but in the end, it costs what it costs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*y5e2tPxhDTKLIUtl.jpg" /></figure><h3>Software Development Takes More Time Than You Want</h3><p>Similar to cost, software development takes time, and there’s no amount of Agile or scrum that will change this fact.</p><p>In our experience, many business leaders will either create incentives or obsess over processes in the name of “velocity.”</p><p>The truth is that if your software development project falls off the rails, tough luck. You can’t quick-fix projects that are behind schedule.</p><p>Creating incentives only encourages developers to be hasty, which results in technical debt later on. This phenomenon has a name: the <a href="https://www.thekguy.com/the-cobra-effect.html">Cobra effect</a> (which is basically: too many cobras, government pays for dead cobras, people start breeding cobras, now cobra problem is worse). This snake problem can be compared to software bugs or tickets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uJFhGsUHyQJvkhqW.gif" /></figure><p>Another common effort is to hire more developers, but onboarding new team members takes time and will only delay the project further. This phenomenon also has a name: Brooks Law which states, “ <a href="https://en.wikipedia.org/wiki/Brooks%27s_law">adding manpower to a late software project makes it later.</a> “ It was coined in 1975, but teams still run into this issue today.</p><p>At the end of the day, you can’t rush technical solutions that only happen after a developer has lived in the code. Unfortunately, the best solutions don’t make themselves apparent on a leader’s schedule. It takes time to work through problems.</p><p>If you can be realistic about both money and time, your project will run smoother. You’ll have a better product, less technical debt, and be positioned to iterate and create more value in the future. All it requires is an internalization of the two truths mentioned above.</p><p><em>Originally published at </em><a href="https://devetry.com/blog/two-software-development-truths-vps-need-to-hear/"><em>https://devetry.com</em></a><em> on May 14, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e450e9343f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Managers Guide to C++]]></title>
            <link>https://wintersieck.medium.com/product-managers-guide-to-c-bca48e73db55?source=rss-9c3094df6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/bca48e73db55</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[c]]></category>
            <category><![CDATA[aspiring-product-managers]]></category>
            <dc:creator><![CDATA[Allan Wintersieck]]></dc:creator>
            <pubDate>Wed, 07 Apr 2021 09:27:31 GMT</pubDate>
            <atom:updated>2021-04-09T16:35:28.427Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LJmPQ3iV504jyMMeXgiutw.jpeg" /></figure><p>Yes, C++ is an old programming language. But don’t conflate age with the ability to get stuff done. A powerful language, C++ has many benefits in the right situations.</p><p>In this quick C++ 101 guide, created by Devetry senior software engineers, we’re going to share what product managers should know and understand about C++. Knowing “just enough to be dangerous” can help you communicate with your development team and optimize your roadmaps.</p><h3>C++ 101</h3><ul><li>C++ is an extension of C. It’s C but with some extras (hence the ++)</li><li>C++ is better for systems that run apps — not necessarily apps themselves</li><li>Software that uses C++ include Adobe Photoshop, Microsoft Office, and YouTube</li></ul><p>What makes C++ valuable is that it’s a low overhead language, meaning you don’t pay for what you don’t use. This allows developers to create fast, efficient programs but can lead to lines and lines of code for simple tasks. These lines and lines of code make it incredibly tedious to work on, which makes it difficult to understand or find errors unless you’ve got a strong, experienced background.</p><p>But what makes it obnoxious for humans is what makes it so great for machines. A machine can read C++ and process requests in a fraction of the time compared to other languages. This speed and execution ability are some of the biggest reasons why it’s incredibly valuable for certain products.</p><h3>When Your Products Need C++</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*d_IXChUi1hgvz95T.jpg" /></figure><p>Three examples where C++ is an ideal choice include</p><ol><li>Apps and systems that require heavy processing</li><li>Software that needs to work across many different devices and platforms</li><li>Embedded software (sensors and connected devices) that rely on batteries</li></ol><h3>Systems That Require Heavy Processing</h3><p>C++ is great for cross-platform applications that require a lot of processing.</p><p>To understand what we mean, let’s consider a music streaming product (like Spotify or similar).</p><p>Any streaming product like this must store terabytes of music files in their library. When you search for a <a href="https://www.youtube.com/watch?v=9Ht5RZpzPqw">throwback</a> and click “play,” it gets the request, sends the file to your device, and turns it into the sound you hear.</p><p>Sending a multi-megabyte file within a second requires a good amount of processing. Now multiple this act by Spotify’s <a href="https://www.theverge.com/2021/2/3/22262508/spotify-q4-2020-earnings-subscriber-numbers-users-podcasts-audiobooks">345 million monthly active users</a>. That’s a lot of on-demand processing power.</p><p>To ensure that these files get sent quickly and without consuming <a href="https://www.rollingstone.com/music/music-features/environmental-impact-streaming-music-835220/">an insane amount of energy</a>, a language with low overhead (that a machine can quickly understand) is ideal.</p><p>C++ is that language. C++ gives your developers the power to create a system that efficiently uses energy, all while providing the processing power so you can listen to songs on the fly.</p><p>Without C++, your next jam sesh would be slower and more expensive.</p><h3>Cross-Platform Software</h3><p>What’s also great about C++ is that it’s portable. That means it can run on pretty much any operating system and any device. Our music streaming example works here too.</p><p>People pull up music apps on their phones (iOS, Android), computers (Windows apps, Chrome browsers) fitness trackers (iWatch), and TVs (Roku, Fire TV Stick). With C++, they have a set of libraries all of these different clients can utilize.</p><h3>Embedded Software/ IoT</h3><p>For this example, we’re revisiting energy consumption. If you’re running a device that requires a battery to operate, you are constrained by processing power and energy usage.</p><p>You need something fast and powerful, yet lightweight enough not to drain a battery.</p><p>An example might be a health monitor. The sensor needs to collect and process your data and then send it to your application rapid-fire to alert you in case of an emergency. You can’t risk slow speeds in a life-saving device.</p><p>Languages like Python, C#, and Java would be contenders, but they all have too much overhead (requirements to keep them running).</p><h3>What C++ Looks Like</h3><p>Here are two examples of C++ code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/0*wjH-Xr33Xn0ZQljw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/0*APoLgpzR8DjyiP6P.png" /></figure><p>To reiterate, many software developers have difficulty reading C++, so as a product manager, you’re not going to have much luck. And that’s okay. Staying in your lane while understanding why your development team uses C++ is the important thing.</p><p><strong>Want more technical knowledge?</strong> I’ve written 101s for a number of languages including:</p><ul><li><a href="https://devetry.com/blog/sql-101-for-product-managers/">SQL 101</a></li><li><a href="https://devetry.com/blog/python-101-for-product-managers/">Python 101</a></li><li><a href="https://devetry.com/blog/what-product-managers-should-know-about-software-architecture/">What Product Managers Should Know About Architecture</a></li><li><a href="https://devetry.com/blog/5-things-every-product-manager-should-know-about-software-development/">What Product Managers Should Know About Development</a></li><li><a href="https://devetry.com/blog/things-product-managers-know-qa-testing/">What Product Managers Should Know About QA &amp; Testing</a></li></ul><p>You can also download our <a href="https://info.devetry.com/pms-guide-roadmaps">eBook: Guide to Product Roadmaps</a></p><p><em>Originally published at </em><a href="https://devetry.com/blog/c-101-guide-to-c-for-product-managers/"><em>https://devetry.com</em></a><em> on April 7, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bca48e73db55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tech Trends Every Business Leader Should Know — April 2021]]></title>
            <link>https://wintersieck.medium.com/tech-trends-every-business-leader-should-know-april-2021-b3de9d402c69?source=rss-9c3094df6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3de9d402c69</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[tech-trends]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cto]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Allan Wintersieck]]></dc:creator>
            <pubDate>Wed, 31 Mar 2021 21:50:22 GMT</pubDate>
            <atom:updated>2021-04-05T16:13:35.278Z</atom:updated>
            <content:encoded><![CDATA[<h3>Tech Trends Every Business Leader Should Know — April 2021</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kbyl51TOXLvQrnKKNWcLIg.jpeg" /></figure><p>Technology and trends evolve so quickly, it’s hard to keep up with everything that could potentially affect your business. To help, the Devetry team sat down with Allan Wintersieck to ask him his unfiltered thoughts regarding today’s opportunities and threats to business--both internal and external.</p><p>What we ended up with is below: a quick guide to technology trends for the first half of 2021. These trends are the things every CTO, CIO, or techy CEO needs to have on their radar this quarter.</p><h3>“What are the biggest opportunities for tech companies right now?”</h3><p>In general, remote work. This past year has been an experiment in regards to remote work, but we’re finally approaching a realistic end to this pandemic. Everyone needs to start making these policies.</p><p>According to <a href="https://www.pwc.com/us/en/library/covid-19/us-remote-work-survey.html">surveys</a>, <a href="https://www.nbcnews.com/business/business-news/just-1-10-companies-expect-all-employees-return-office-n1255589">reports</a>, and <a href="https://www.linkedin.com/pulse/remote-work-sweeps-us-55-say-can-succeed-industry-george-anders/">conversations</a>, it’s clear across the tech industry. People don’t want to go back to the office.</p><p>If you demand five days back in the office without flexibility, you’re going to have attrition. However, if most of your team didn’t sign on to work remotely, they probably want some office interaction. Based on these team preferences, a hybrid approach is probably the right move (and probably what your industry is doing).</p><p>If you do go ahead with remote work, your team will probably be all over the place. Why not have your team be even more all over the place? There is talent across the US, in low cost of living areas which could provide benefits.</p><p>If you go ahead with a hybrid approach, you’re going to want to figure out logistics ASAP. There’s no point in having a 100-person office space if only 50 will be in at a time. But that means you might need a schedule. Maybe flexible space (community co-working space). Maybe you need it every other week. You know what’s best for your team, but I encourage all to start thinking about this.</p><p>Another opportunity I see lies in junior developers. Right now, there’s a desire to hire only senior talent, but this is creating scarcity and delaying progress on a lot of software products.</p><p>To hiring managers, I would say this: consider hiring a developer that’s more junior than you want. Maybe they’ll be slower and things will take longer, but they’ll get it and add value to your organization, especially if you have roles that align with boot camp curriculums (for example, frontend-only React work).</p><h3>“What’s the biggest challenge you see?”</h3><p>It’s the hardest it’s ever been to hire senior people. Everyone is ramping up, with a focus on the future, and it’s hard. Everyone’s trajectory is the same. I don’t have great advice here other than <a href="https://devetry.com/blog/what-to-look-for-when-hiring-a-software-developer-in-2021/">focus on hiring</a>.</p><p>To no one’s surprise, compensation is also a challenge. So many Bay-area companies have committed to remote and their teams have settled in low-cost locations. If you’re a business in these small markets, you might have some challenges down the line.</p><h3>“What product do you think needs to be built right now?”</h3><p>Despite all the tools for infrastructure and cloud, it never gets any <em>easier to set these up</em>. These newer options offer a variety of benefits for medium/larger teams, but they aren’t saving time to set up. Things are just as hard as Heroku days (arguably even harder!). So I’d like to see something that makes it easy to set up infrastructure.</p><h3>“What technology are you investing in right now?”</h3><p>At a macro level, augmented and virtual reality. Both of these technologies have had so many ups and downs but now are finally being commoditized. It’s now almost economical to make an AR or VR app. I predict a lot of interesting technology leveraging AR/VR-things like remote learning and training via AR products.</p><p>As a CTO, I’m interested in the next development technology. If you look at historical technology life cycles, the three biggest front-end technologies (React, Vue, Angular) may very well already be on the downhill. React has been around for almost eight years. Its peak may have already passed. So what’s the next cool thing for front-end technology?</p><p>My advice is to be open to these inevitable new things, even if it’s just little parts of your front end. Failure to evolve is exactly how you become “that company” with obsolete tech.</p><p><em>End interview</em></p><p>Keep these items on your radar so you can create a strategy and leverage them properly when the time comes.</p><p><em>Originally published at </em><a href="https://devetry.com/blog/cto-perspectives-april-2021-technology-trends/"><em>https://devetry.com</em></a><em> on March 31, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3de9d402c69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Product Managers Should Know About Software Architecture]]></title>
            <link>https://medium.com/swlh/what-product-managers-should-know-about-software-architecture-aec718a1445c?source=rss-9c3094df6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/aec718a1445c</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[Allan Wintersieck]]></dc:creator>
            <pubDate>Thu, 21 Jan 2021 22:20:53 GMT</pubDate>
            <atom:updated>2021-01-28T21:56:54.456Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rp25xiJ6F7HKqB3d5l9b2g.jpeg" /></figure><p>There is a reason why technologists borrowed the word “architecture” from buildings and blueprints. Software architecture lays out <em>what</em> goes <em>where</em> and <em>how</em> it’s all connected.</p><p>While software architecture is designed by systems architects and maintained by engineers, there are some arguments for product managers knowing the basics of software architecture.</p><p>Improved communication between product managers and engineers, better product road mapping, and useful insight into time and budget are some of the reasons why a product manager should know a bit about this subject.</p><p>Here is our team’s perspective on what product managers should know about software architecture.</p><h3>How Software Architecture Affects Product Experience</h3><p>At the very least, product managers should understand why software architecture is vital to a successful product.</p><p>Summarized, a strategic software architecture ensures your product’s:</p><ul><li><strong>Availability</strong>: Can users access your product when they need it?</li><li><strong>Scalability</strong>: Can your product scale as your userbase grows?</li><li><strong>Performance</strong>: Speed, uploads, APIs-is your product doing its job?</li><li><strong>Maintainability</strong>: Can your engineering team maintain your product as technology evolves?</li></ul><p>Issues with architecture can create bottlenecks, which can dissatisfy users, slow implementation, or increase costs. Therefore, having a software architecture that supports your product’s functionality is essential.</p><h3>Behavioral vs. Structural Changes</h3><p>Within a system, there are two types of product updates.</p><ol><li>An update that changes the behavior of a function (on click:do this)</li><li>An update that changes the structure of the system (both elements and the relationships between them)</li></ol><p>In the product world, time is always scarce. There’s never enough time to do everything you want to, so product managers typically push for the changes they care about. That means structural changes are unpopular since they don’t change external behavior. In other words, if product managers can’t see the change, they don’t care about it as much.</p><p>However, software architecture is all about change. If engineers anticipate maintaining a program, there must be structural (nonvisible to product managers) changes. When these structural changes occur, they’re acting on a belief about how a system may change in the future.</p><p>Here’s a common analogy:</p><p><em>You want to install granite countertops (build a new feature into your application). Unfortunately, your existing cupboards are only rated for laminate, and can’t support the weight of the new granite.</em></p><p><em>In order to make granite countertops happen, you need to spend a month reinforcing the underlying structure.</em></p><p><em>You could have built granite-supporting countertops from the start, but that would waste money and time if you never put in granite.</em></p><p>Non-visible ≠ less valuable.</p><h3>You Can’t Retroactively Collect Data</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DGtQmz5C_iGkWA82.jpg" /></figure><p>When planning products, it’s essential that product managers thoroughly understand all the types of data they need to collect.</p><p>That’s because systems have strict rules about communicating with one another. If your back end never requests a specific metric, it’s can’t collect it.</p><p>We sometimes see product teams forget about internal metrics. For example, many organizations have public promises around response times, so an example metric might be logging data (who did what, when).</p><p>If these metric requests are late in the development phase, functionality will need to be rewritten, costing time and additional resources. Worse, if v1 goes out, you may never be able to go back and get it. This kind of metric is easy to miss because there are “defaults” within databases. It’s the product manager’s responsibility to know the full scope of data collection.</p><h3>There Are Two Main Types of Architectures</h3><p>There is a range of architectural designs, with two limits on either side: monolithic and microservices.</p><p>A monolithic architecture is a single “stack,” where your front end, back end, and database share one server to suit all of the application needs.</p><p>With <a href="https://devetry.com/blog/think-you-need-microservices-think-again/">microservices</a>, there are many servers (or serverless functions) that serve a particular purpose.</p><p>For example, let’s imagine we want to make a video streaming platform.</p><p>We will likely start with one server that will process logins and video streams. That means if there are too many people streaming video at once it could slow down the login workflow! Since we don’t want users to have a slow login experience, we break our monolithic server into two dedicated services: one for processing video streams and one for everything else (logging in, liking, commenting, etc.). This divided structure is microservices.</p><p>There are drawbacks to monoliths and microservices, but you should be able to understand why your software architect selected one over another. Think back to Conway’s law. It doesn’t make sense to have more microservices than teams maintaining them. For small teams, monoliths are much more beneficial.</p><p>When solving for speed and function, it’s helpful to understand these technical tradeoffs.</p><h3>Final Thoughts</h3><p>Ideally, when planning product updates and optimization initiatives, your architect should be involved. Since they know the current and future state of the architecture, they can give you instant feedback on the feasibility, timeline, and budget of any update which can be a massive time-saver for product managers.</p><h3>More Knowledge for Product Managers</h3><ul><li><a href="https://devetry.com/blog/python-101-for-product-managers/">Python 101 for Product Managers</a></li><li><a href="https://devetry.com/blog/sql-101-for-product-managers/">SQL 101 for Product Managers</a></li><li><a href="https://info.devetry.com/pms-guide-roadmaps">The Product Manager’s Guide to Roadmaps</a></li></ul><p><em>Originally published at </em><a href="https://devetry.com/blog/what-product-managers-should-know-about-software-architecture/"><em>https://devetry.com</em></a><em> on January 21, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aec718a1445c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/what-product-managers-should-know-about-software-architecture-aec718a1445c">What Product Managers Should Know About Software Architecture</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>