<?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 Steven Gripshover on Medium]]></title>
        <description><![CDATA[Stories by Steven Gripshover on Medium]]></description>
        <link>https://medium.com/@gripshos?source=rss-4d859b411adc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nkt-Umzjupq8CrfNVLHCzw.jpeg</url>
            <title>Stories by Steven Gripshover on Medium</title>
            <link>https://medium.com/@gripshos?source=rss-4d859b411adc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 21:13:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gripshos/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[Lessons in Vibe-Coding as a PM]]></title>
            <link>https://medium.com/hybrid-cloud-engineering/lessons-in-vibe-coding-as-a-pm-393dd2d90d71?source=rss-4d859b411adc------2</link>
            <guid isPermaLink="false">https://medium.com/p/393dd2d90d71</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-product-management]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Steven Gripshover]]></dc:creator>
            <pubDate>Wed, 25 Mar 2026 20:55:44 GMT</pubDate>
            <atom:updated>2026-03-25T20:55:44.731Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*affPl7xMNKrSOtEsOSf0Ug.png" /></figure><h4>Back in 2016 when I was a sophomore in college I attended a local hackathon and had a funny idea</h4><p><em>Editor’s note: Besides being an excellent article on the acceleration of innovation using AI, this is also a reminder to all of us that developers love to explore and learn. In AI Enterprise Engineering, our hope is that you see how to excite your developers while creating the guardrails that Steven highlights: proper architectural thinking, proper security, focusing on the best user experience while adhering to enterprise policy. Enjoy!!</em></p><p>What if there were an app like Tinder where the user was looking for chicken tenders instead of their next close friend? The idea was fun, but wasn’t quite compelling enough to devote a lot of attention to. Our team (shout-out to Wade and Matt) built out a barely functioning prototype, drove back to our home college and didn’t think about it again for a decade.</p><p>Flash forward to January 2026, I’m in the middle of the holiday season and looking for something to think about between late night bottles with my few-months-old daughter when I see people posting about the power of the latest AI dev tools. I realized this was the perfect opportunity to get hands-on experience in some of the AI tools and take advantage of my skillsets, a dev background who’s relatively fresh into product management. Then came the hard part, what is the right thing to build? Well, Tendrrr was the perfect fit! I had the stub of the idea and knew it was feasible, so I whipped open the Macbook and got to building.</p><p>What I came out with on the other side was not just a published app in the app store in less than a month, but a realization of just how much the world of software development has changed since my last role in the job in 2024. I also have come to realize the incredibly valuable experience these tools have given me in my role as PM in the AI space: this stuff is really impressive! Come along with me as I break down what I built, what I learned, and how even as a PM I learned valuable skills on how AI is building the future (and where there’s still a ways to go).</p><h3>The Idea (5 Minutes)</h3><p>The concept was simple: a Tinder-style swipe interface for discovering nearby chicken tender restaurants. Swipe right to save a spot to your favorites. Swipe left to skip. That’s it.</p><p>Part parody, part genuinely useful. The “hot tenders in your area” energy was intentional — I wanted something that would make people laugh but also actually could be used.</p><p><strong>PM Insight #1:</strong> Constraints make decisions easier. By picking a single, hyper-specific use case (chicken tenders, not “food”), I eliminated hundreds of feature debates before they started. Every design choice had a clear filter: does this help someone find chicken tenders faster?</p><h3>The Architecture Phase (Days 1–4)</h3><p>My first instinct was to just start coding. But I’d been a PM long enough to know that’s how you end up with a 600-line Object that does everything poorly.</p><p>Instead, I started with a Product Decision Record: a lightweight doc capturing:</p><ul><li>Core user flow (discover → swipe → save → navigate)</li><li>Technical decisions (SwiftUI, local-first data, Yelp API)</li><li>What’s in scope vs. out of scope</li></ul><p>Then I sketched an architecture before writing any code. The initial codebase had everything crammed into one file — business logic mixed with UI, no separation of concerns. I refactored into a clean MVVM pattern with distinct layers: Models, Services, Repositories, and Features.</p><p>The result of this step was a simple markdown PDR that drove development for Tendrrrr via Claude’s project feature to give context. This was relatively bare-bones, but allowed for me to get prompt creation tips directly from the system on how to best get what I wanted from the AI at each step.</p><figure><img alt="Tendrrr’s PDR" src="https://cdn-images-1.medium.com/max/788/1*4rY-JnZEV11KgMMbiFqrMQ.png" /><figcaption>While it’s hardly readable to me, the agent was able to take this and run.</figcaption></figure><p><strong>PM Insight #2:</strong> Technical debt is a product decision. My “quick prototype” would have worked fine for a demo. But I wanted to ship a real product and learn what that takes. The extra day spent on architecture saved me at least a week of debugging later.</p><h3>The API Decision (Day 5)</h3><p>I needed restaurant data. The options:</p><ul><li><strong>MapKit (Apple):</strong> Free but limited — no photos, no reviews, basic metadata</li><li><strong>Yelp Fusion:</strong> Rich data, great images, 5,000 free API calls per day</li><li><strong>Google Places:</strong> Most comprehensive, but expensive and overkill</li></ul><p>I went with Yelp. The free tier was more than enough for launch, and the image quality made the swipe experience feel polished. MapKit stayed as a fallback.</p><p><strong>PM Insight #3:</strong> Free tiers exist for a reason. For a side project validating a concept, I didn’t need the enterprise plan. Yelp’s 5,000 daily calls would support thousands of users before I’d need to worry about scaling. Build for where you are, not where you hope to be.</p><h3>The Security Oops (Day 10)</h3><p>I pushed my code to GitHub. Public repo, nice README, felt good about sharing my work.</p><p>Then I realized: my Yelp API key was hardcoded in Config.swift and visible to anyone who looked.</p><p>The fix:</p><ol><li>Immediately rotated the API key (the old one was compromised)</li><li>Added Config.swift to .gitignore</li><li>Created a Config.swift.example template for anyone cloning the repo</li><li>Made the main repo private</li></ol><p>Since GitHub’s free tier doesn’t support Pages on private repos, I created a separate public repo just for the support site and privacy policy. More work, but no monthly cost.</p><p><strong>PM Insight #4:</strong> Security isn’t a feature — it’s a baseline. In a professional setting, there’d be a security review. Solo, I had to catch my own mistakes. Build security into your workflow: never commit credentials, always use environment variables or config files that stay local.</p><h3>The App Store Gauntlet (Days 12–18)</h3><p>Submitting to the App Store for the first time felt like filling out tax forms in a foreign language. Here’s what actually mattered:</p><p><strong>Required before you can submit:</strong></p><ul><li>Apple Developer account ($99/year — no way around it)</li><li>Privacy policy URL (I used a free generator and hosted on GitHub Pages)</li><li>App icon (1024×1024, no transparency)</li><li>Screenshots for multiple device sizes</li></ul><p><strong>Things that seemed easy but weren’t automatic:</strong></p><ul><li>Age rating questionnaire (took 5 minutes but was mandatory)</li><li>Support URL (pointed to my GitHub Pages support site)</li><li>Clear description of what data you collect</li></ul><p><strong>Things I worried about that didn’t matter:</strong></p><ul><li>Fancy app preview video (didn’t need one)</li><li>Elaborate onboarding (kept it simple)</li><li>Perfect copy (they approved my first draft)</li></ul><p>I was able to leverage AI to build the required pages for the app quickly without needing to start what felt like a full project within a project:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/1*de5bmswiQraasOBk0I3P4Q.png" /><figcaption>This isn’t going to win any design rewards…</figcaption></figure><p><strong>PM Insight #5:</strong> The App Store review process is predictable if you follow the rules. Apple publishes their guidelines. Read them. Most rejections happen because people skip steps, not because Apple is capricious. My submission was approved in under 48 hours.</p><h3>The Monetization Question (Ongoing)</h3><p>For a novelty app with maybe a few hundred users, ads would generate about $3–12/month after integrating an SDK, handling consent flows, and dealing with review headaches. Not worth it.</p><p>Instead, I added a simple tip jar — three tiers ($0.99, $4.99, $9.99) using StoreKit 2. Non-invasive, tucked away in Settings, no guilt-tripping copy. If people love the app, they can support it. If not, no friction.</p><p><strong>PM Insight #6:</strong> Monetization should match your goals. My goal wasn’t revenue — it was learning. A tip jar lets fans contribute without compromising the experience. If the app takes off, I can revisit monetization with real data.</p><h3>What I’d Do Differently</h3><p><strong>Draft first: </strong>In my other projects I’m working on now, I’ve realized a paradigm shift for how to manage the product. I’d been focused on getting user interviews and product concept feedback early, but in this era of AI development speed, why not build out the prototype and get feedback on <em>that</em> early on. It’s so much more powerful to have something tangible to discuss, even if it’s ugly.</p><p><strong>Build the support infrastructure earlier.</strong> Privacy policy, support page, and App Store metadata felt like afterthoughts, but they’re required work that is less fun late in the game. Front-loading this work would have made submission smoother.</p><p><strong>Test on real devices sooner.</strong> The simulator is great for iteration, but location services behave differently on actual hardware. I found bugs in the last 48 hours that should have surfaced earlier.</p><h3>The Product Manager Perspective</h3><p>Building Tendrrr reminded me why I moved from engineering to product in the first place: the interesting problems aren’t the technical ones for me — they’re about understanding what matters.</p><p>Should I add filters? Probably not — that’s scope creep for a novelty app. Should I support delivery ordering? Maybe — but not until I validate that people actually use the app. Should I spend a week on animations? No — ship the core experience first.</p><p>Every feature request I generated for myself went through the same filter: <em>does this help someone find chicken tenders faster?</em> If not, it went on the backlog.</p><p>The hardest part wasn’t code. It was deciding what not to build.</p><h3>What’s Next</h3><p>Tendrrr is live. I’m tracking basic metrics (downloads, daily active users) to see if anyone besides me wants this to exist. If there’s genuine interest, I’ll add features based on actual feedback rather than my assumptions.</p><p>If not? I shipped an app to the App Store. I learned SwiftUI, wrestled with App Store Connect, made trademark mistakes, fixed security holes, and remembered what it feels like to build something from scratch.</p><p>That was the point.</p><p><em>Tendrrr is free on the iOS App Store. It finds chicken tender restaurants near you.</em></p><p><a href="https://apps.apple.com/us/app/tendrrr/id6757625385"><em>Download now!</em></a></p><h3>Key Takeaways for PMs Building Side Projects</h3><ol><li><strong>Constraints are your friend.</strong> A hyper-specific use case eliminates decisions.</li><li><strong>Architecture isn’t overhead.</strong> A little structure saves a lot of debugging.</li><li><strong>Free tiers exist.</strong> Use them until you have a problem worth paying to solve.</li><li><strong>Security is baseline.</strong> Never commit credentials. Rotate keys if you do.</li><li><strong>App Store review is predictable.</strong> Follow the guidelines, and you’ll be fine.</li><li><strong>Ship the core experience first.</strong> Polish is earned, not assumed.</li></ol><p>Most importantly, I think every product manager should try to build out at least one idea with tools like IBM Bob, Claude code, or another similar tool. This technology is hard to believe until you try it yourself. Make something small, improve your workflow, build an app that doesn’t exist and only you would use, <em>because now you can</em>.</p><p><em>Have questions about the process? Find me on </em><a href="https://www.linkedin.com/in/steven-gripshover/"><em>LinkedIn</em></a><em> or check out the w</em><a href="https://gripshos.github.io/tendrrr-site/"><em>ebpage for the app</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=393dd2d90d71" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hybrid-cloud-engineering/lessons-in-vibe-coding-as-a-pm-393dd2d90d71">Lessons in Vibe-Coding as a PM</a> was originally published in <a href="https://medium.com/hybrid-cloud-engineering">AI Enterprise Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Generative AI?]]></title>
            <link>https://medium.com/hybrid-cloud-engineering/what-is-generative-ai-6fc8e9004390?source=rss-4d859b411adc------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fc8e9004390</guid>
            <category><![CDATA[watsonx]]></category>
            <category><![CDATA[introduction-to-ai]]></category>
            <category><![CDATA[generative-model]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Steven Gripshover]]></dc:creator>
            <pubDate>Mon, 14 Aug 2023 18:54:54 GMT</pubDate>
            <atom:updated>2023-08-14T18:54:54.677Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Abw_WZpMv4FN_OcGljxn6A.jpeg" /></figure><p>In the world of technology there always seems to be something new to learn. While this is part of what makes being a software engineer so fun and exciting, it can be overwhelming to keep up with the latest and greatest new tools. The latest example of this for me has been the concept of Generative AI. It’s something we are seeing pop up more and more, but few understand the fundamentals well enough to describe how it works. Even fewer understand why it’s unique and worth investing in (other than the hype, that is).</p><p>Generative AI has a lot of promising use cases. Everything from writing scripts for movies to conducting medical research could use generative models to further progress in their industry. Students are using the technology to complete their essays and write programming assignments in the classroom, much to the chagrin of their teachers. Between the good and the bad, one thing is for certain: this new type of AI is fundamentally changing how work gets done in many ways. For those leading organizations, how can you be sure your business won’t be left behind?</p><p>In this video, I work to demystify the generative AI technology powering tools like ChatGPT, Google’s Bard, and IBM’s WatsonX. These tools are easy to get started with as an end user or customer, but how did they become so sophisticated? What makes an AI generative rather than some other type of AI? I hope you’ll take some time to listen as I teach back what I’ve learned so far on this exciting new domain. In addition, I’d love to discuss my perspective and hear what I may have missed!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F6feRoOfwTYU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D6feRoOfwTYU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F6feRoOfwTYU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/60d69a82941395bd5344fb6d6f7cc9a9/href">https://medium.com/media/60d69a82941395bd5344fb6d6f7cc9a9/href</a></iframe><p>This video is just the beginning. As the world around generative AI continues to evolve, more concepts and norms will begin to solidify. After this brief introduction, take some time to investigate these demos and tools for yourself. Try out some prompt engineering in the publicly accessible tools like ChatGPT and Bard. As this technology grows and changes, stay tuned for both introductions to new terminology as well as deep dives into the latest advancements!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fc8e9004390" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hybrid-cloud-engineering/what-is-generative-ai-6fc8e9004390">What is Generative AI?</a> was originally published in <a href="https://medium.com/hybrid-cloud-engineering">AI Enterprise Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Quirks of Development in a Secure Enterprise]]></title>
            <link>https://medium.com/hybrid-cloud-engineering/the-quirks-of-development-in-a-secure-enterprise-6842ed4ed3cb?source=rss-4d859b411adc------2</link>
            <guid isPermaLink="false">https://medium.com/p/6842ed4ed3cb</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[secure-development]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Steven Gripshover]]></dc:creator>
            <pubDate>Fri, 09 Jun 2023 20:11:43 GMT</pubDate>
            <atom:updated>2023-06-09T20:11:43.704Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rKqyyJIyke4d-EjbOIUaaQ.jpeg" /></figure><p>As a new IBMer coming from the world of high security software development, there have been many differences that I’ve noticed between these two worlds. Sure, much of the work mechanically is the same; still using languages C and Python with relatively modern IDEs to solve complex problems in interesting domains. However, there are several important and unique nuances that come with working in a secure environment that is required in the Defense industry. In this first blog, I’d like to go over some of the requirements and quirks that developers in these environment’s face. These requirements fundamentally change how developers work and get things complete. After reading this post, you will better understand how the environment required for secure development effects the way software is built.</p><p>Before digging in, it’s important to note that these points are based on personal experience, but given the variety of companies, teams, programs, and more there are certainly cases where these rules are less applicable. I will not be discussing anything sensitive in this blog and the views expressed here are my own and do not reflect those of any organization.</p><h3>1. Requirements</h3><p>The first important quirk to remember is that those of us who have worked on the “high side” have had to meet many requirements to be granted access. These can vary depending on the type of work, the sensitivity of the work, and more, but what they all have in common is that no one gets access to begin working until they’ve met all the closed area workspaces’ necessary certifications. For example, all these workspaces will require at least some form of clearance. This process alone can take upwards of a year for a complete investigation. Even when given the appropriate clearance, most of these closed areas still require specific permissions to be granted by the government entity in charge of funding the project. That step too can take months. Finally, even after all permissions are granted, each person on the program may have further requirements to fulfill like in-house security training and additional third-party certifications. Personally, I had to complete the CompTIA Security+ certification to be granted access to an account with any elevated privileges.</p><p>Takeaway: These organizations spend months and sometimes years getting individuals up to speed and working inside programs.</p><h3>2. Program Startup</h3><p>In my stint at one of these defense companies I was lucky enough to work on some very new research projects that we had won. These programs are usually only a few months long and were usually very controlled. By joining these programs, I was able to learn another crucial quirk of working in these spaces, programs take a LONG time to get started.</p><p>Programs would be awarded over a few months of application and competition between contractors. Then, once awarded, security paperwork would begin. This process includes finding a space to perform the work, getting it up to date with required security protocol, getting a secure network online, and then finally getting folks approved to work the program. These steps alone were likely to take months, sometimes a year or more. Finally, even when everyone is approved and a kickoff meeting was scheduled, it was not uncommon for things to delay even further as every necessary piece of technology that we needed to bring into the lab had its own process to be approved. In extreme cases this could take months for complex items like computers or other physical hardware while cloud options are rarely given any consideration. Clearly, these programs require a large monetary and time budget to progress to the point of beginning work. There is little motivation to pay for and approve third party applications on programs of smaller sizes, so most of the developed tools would be made in house to avoid the lengthy approval needed for something that may be more relevant and useful.</p><p>Takeaway: There is a large investment of time and resources into getting these programs up in running in a physical location. Even when things are running, slowdowns are not uncommon.</p><h3>3. The work itself</h3><p>Now things are going to be very generic as nothing about any specific programs is open to discussion. What I can expand on, though, are some of the restrictions that developers have in high security environments. These labs do not have any external access to devices or work done in an unclassified environment. There are occasionally some computers that were designated as “google machines” to get relevant information researched within the lab, but no work can be done on those machines. The computers where work is done are entirely separate from any public network, do not have internet access, and no external data can be added to them without specific approval. Development is frequently done from scratch, despite some relevant solution existing externally, simply because the process of getting technology approved may be longer than it takes to make a version yourself. Even if some work had been completed on another equivalently secure network, moving between those networks also takes a similar approval process that is to be avoided in most cases. There were other limitations like having no personal devices like smartphones or smart watches, generally having no external windows, and time recording requirements that made these workspaces a bit more challenging.</p><p>Takeaway: The development itself is more complex than traditional software engineering given the physical restrictions to the space it takes place in.</p><h3>4. Why does this matter?</h3><p>The above notes may seem to be negative, but that is not the most important takeaway. Things may sometimes move slower in these regulated and secure environments, but the nature of the work demands the sensitivity and care. The work being done in these areas is critical and incredibly interesting. The engineers and scientists adapt to these challenges and overcome them to produce remarkable products and results for their customers. When IBM considers partnering and developing solutions in an industry regulated as tightly as defense, the environment where these engineers and scientists work should be considered. In my personal experiences, there were no cloud offerings in use by these programs and limited application of containers like Docker. While these were not banned or even discouraged, they weren’t properly explored as solutions because most folks I worked with didn’t consider them to be secure enough. The security hurdles listed above seemed to outweigh the benefits. The difficulty isn’t in proving that the solutions would work, it’s proving that they are secure, fit government standards for compliance, and don’t take longer to install and maintain than making something in house. That’s a tall order.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6842ed4ed3cb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hybrid-cloud-engineering/the-quirks-of-development-in-a-secure-enterprise-6842ed4ed3cb">The Quirks of Development in a Secure Enterprise</a> was originally published in <a href="https://medium.com/hybrid-cloud-engineering">AI Enterprise Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>