<?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 Bruno Ribeiro on Medium]]></title>
        <description><![CDATA[Stories by Bruno Ribeiro on Medium]]></description>
        <link>https://medium.com/@brunz36?source=rss-d95b2ffc6b7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Faz8zX6EAe6FE1GyODjv6A.jpeg</url>
            <title>Stories by Bruno Ribeiro on Medium</title>
            <link>https://medium.com/@brunz36?source=rss-d95b2ffc6b7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:14:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brunz36/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[From Ideation to Warranty: Where AI Actually Changes Software Delivery]]></title>
            <link>https://medium.com/@brunz36/from-ideation-to-warranty-where-ai-actually-changes-software-delivery-7a8f9974b741?source=rss-d95b2ffc6b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a8f9974b741</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Bruno Ribeiro]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 01:22:57 GMT</pubDate>
            <atom:updated>2026-04-07T01:22:57.405Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vHB2r0EzOyR5YKQU1oGbtg.png" /><figcaption>The gap is widening between software teams that simply use AI for autocomplete and those genuinely transforming their entire delivery capabilities, from design to production support.</figcaption></figure><p><em>Everyone is talking about AI writing code faster. That’s a narrow slice of a much larger story.</em></p><p>I’ve been watching technology transform industries for a while. Fifteen years ago, I watched 3D modeling disrupt jewelry manufacturing — the businesses that thrived weren’t the ones that just bought the software, they were the ones that redesigned their core services around it. Today, generative AI is forcing a similar transition in software engineering. The seismic shift has many parallels.</p><p>In less than three years, generative AI moved from a curiosity to a daily instrument — used by 79% of software developers as of early 2026. But widespread adoption isn’t the same as effective adoption. The gap between teams that are genuinely transforming their delivery capabilities and those that have simply added an AI autocomplete to their IDE is wide — and widening.</p><p>I spent time researching this and writing it up properly. This post is the distilled version. The full white paper is linked at the end.</p><h4><strong>AI’s impact is not a rising tide</strong></h4><p>This is the thing most AI commentary gets wrong: AI doesn’t accelerate the Software Delivery Lifecycle uniformly. Its impact varies sharply by phase. Some phases are already being transformed. Others are underutilized not because AI can’t help, but because teams haven’t figured out how yet. And a few carry risks that are easy to miss until the damage is done.</p><p>Let me go phase by phase.</p><h4><strong>Planning &amp; Ideation: lowest impact today, highest ceiling</strong></h4><p>Only 18% of developers rate AI’s impact on planning as high. Among senior engineers with ten or more years of experience, that number drops to just 5%.</p><p>At first glance, this looks like a verdict. It isn’t.</p><p>Planning is the most context-dependent phase in the entire lifecycle. AI’s ability to contribute here is directly proportional to how much of the right context it can access — prior architectural decisions, historical sprint data, stakeholder constraints, domain documentation, organizational priorities. Most teams haven’t built that contextual infrastructure yet. The low numbers reflect current practice, not the ceiling.</p><p>There is one real limitation here that won’t be solved by more context: AI’s output is derivative by nature. It recombines what it was trained on, not what has never been tried. Early-stage ideation — the divergent thinking that generates genuinely new directions — remains a human-led activity. Use AI to pressure-test and structure ideas, not to generate them from scratch.</p><h4><strong>Requirements &amp; Design: where the biggest unrecognized opportunity lives</strong></h4><p>Requirements analysis sits at 43% perceived benefit — moderate, and rising. This is the phase where AI’s potential is most widely misunderstood.</p><p>The surface value is straightforward: AI can generate user stories, elaborate acceptance criteria, identify inconsistencies, and surface edge cases that human authors miss under time pressure. On the design side, AI can propose solution approaches, evaluate trade-offs between patterns, and flag technical constraints early — before design decisions harden into implementation assumptions.</p><p>The deeper opportunity, not yet widely captured: AI as a requirements analyst with full project context. When an AI assistant can reference the existing codebase, past sprint outcomes, known technical constraints, and the product roadmap simultaneously, it can surface gaps that might otherwise go unnoticed until refinement — giving business analysts a stronger starting point, not replacing their judgment.</p><p>The risk here is specific and expensive: hallucinated requirements. AI generating a requirement or design pattern that’s incompatible with the existing system is a particularly costly failure mode. It encodes assumptions as facts and propagates them downstream before anyone catches them. Human review at this phase is not optional — it’s the quality gate that makes AI-assisted output safe to build on.</p><h4><strong>Implementation: the one everyone knows about</strong></h4><p>85% of developers rank implementation as the highest-utility phase for AI assistance. 72% report at least a 50% reduction in time spent on boilerplate code. 37% say writing new code now takes roughly 75% of the time it used to.</p><p>This one is real. The productivity numbers are significant, and the tooling — GitHub Copilot, Cursor, Claude, ChatGPT, JetBrains AI Assistant — has matured rapidly.</p><p>The more sophisticated practitioners have moved beyond autocomplete into what some are calling Chat-Oriented Programming: iterative, dialogue-driven development where implementation emerges through multi-turn conversation with AI rather than manual line-by-line authoring. The developer specifies intent, reviews output, refines through follow-up prompts, and iterates. It’s a fundamentally different workflow — and it integrates naturally with TDD.</p><p>Here’s the trade-off I’d flag: speed without judgment creates what practitioners call “house of cards code” — software that appears to work under controlled conditions and collapses under real-world load, edge cases, or security scrutiny. AI-generated code requires the same review standard as human-written code, applied with awareness of AI’s specific failure modes: incompatible library suggestions, missing organizational context, security vulnerabilities that pass syntax checks but fail under adversarial conditions.</p><p>The productivity gain is real. The verification responsibility doesn’t go away.</p><h4><strong>Testing: growing fast, but coverage can be an illusion</strong></h4><p>AI can generate unit tests, integration test scaffolding, end-to-end test cases, mock objects, and synthetic test data — and it can identify coverage gaps that human authors routinely miss under time pressure. 37% of practitioners rate testing as a high-benefit phase, and the teams getting the most value are those using AI not just to write tests but to interrogate coverage: asking AI to identify what isn’t being tested, and why.</p><p>The risk worth naming: AI-generated tests can encode the same assumptions as the code they test. A test suite generated alongside the implementation rather than against a specification is measuring conformance, not correctness. Coverage that’s broad on paper and shallow in practice is worse than you think — it gives you false confidence.</p><p>The best use of AI in testing is within a human-guided strategy: humans define the approach, scope, and acceptance criteria; AI expands coverage and surfaces edge cases. What to test and why remains a human judgment call.</p><h4><strong>Warranty &amp; Production Support: the most underestimated phase</strong></h4><p>If there’s one phase where AI’s potential is most underestimated relative to its demonstrated value, it’s this one.</p><p>75% of practitioners rate operations and maintenance as a high-benefit area — the second highest rating across the entire lifecycle. 29% report that understanding legacy code now takes less than 25% of the time it used to. 69% report documentation tasks taking half the time.</p><p>Production support has historically been one of the most expensive and unpredictable phases of the lifecycle. Systems accumulate complexity over time. Documentation drifts from reality. The engineers who built the original system move on. Runbooks go stale. A production incident at 2am means someone is reading code they didn’t write, in a system they don’t fully understand, under pressure.</p><p>AI changes this materially. Log analysis and trace correlation — tasks that previously required deep familiarity with a system — can now be accelerated significantly. Incident triage, historically dependent on tribal knowledge, becomes more accessible to engineers newer to the system.</p><p>Perhaps the most underappreciated capability: AI’s ability to navigate old, fragmented, poorly organized documentation. Every engineering organization has it — architecture decisions recorded in a Confluence page nobody has updated since 2019, runbooks scattered across wikis and shared drives, institutional knowledge that lives entirely in the heads of two senior engineers. AI can synthesize across these fragmented sources in a way that simply wasn’t possible before.</p><p>The danger: AI can misdiagnose production incidents with the same confidence it projects when it’s correct. Blind trust in AI-generated root cause analysis creates new failure modes — teams acting on a plausible but incorrect diagnosis while the real cause continues to compound. Human verification remains the final gate, especially in high-stakes production environments.</p><h4><strong>The shifting developer role</strong></h4><p>The most consequential change AI is bringing isn’t any specific productivity metric. It’s a fundamental shift in what it means to be a software engineer.</p><p>The developer role is moving from code author to AI orchestrator, problem formulator, and quality arbiter. Syntax mastery is giving way to prompt engineering and system design. Individual craftsmanship is evolving into a collaborative mindset that treats AI as a capable but imperfect partner requiring active oversight.</p><p>None of this deprecates engineering fundamentals — if anything, it raises the bar. The developers who will be most effective in an AI-augmented environment are those with deep fundamentals, because they’re the ones equipped to know when AI output is wrong, and why.</p><p><strong>What’s happening by experience level</strong></p><p>AI is not impacting all developers equally.</p><p>Junior developers get disproportionate productivity benefits — tasks that would take a novice hours are dramatically accelerated. AI functions as a force multiplier on smaller baselines. The risk: the struggle that builds deep understanding gets bypassed. Developers who learn primarily through AI-assisted output may advance faster in the short term while developing shallower foundations.</p><p>Senior developers face a different dynamic. Their productivity gains are real but smaller in relative terms — they were already fast. What they face is a more insidious risk: skill atrophy. In one study, 21 out of 22 practitioners reported code quality degradation associated with over-reliance on AI tools.</p><p>The model that works best is the one most teams already use: juniors draft, seniors review. AI doesn’t change the structure — it changes the speed and quality of what the junior produces on the first pass, while the senior’s review remains the learning opportunity that builds long-term capabilities.</p><p>The risk isn’t that juniors use AI first. It’s that the senior interaction disappears entirely.</p><h4><strong>The governance gap most organizations aren’t addressing</strong></h4><p>34% of organizations have no AI policy at all. 20% of developers don’t know if one exists at their company.</p><p>This isn’t just a compliance risk — it’s a consistency risk. When individuals make independent decisions about which AI tools to use, what data to share with them, and how much to trust their output, the results are unpredictable. Teams in the same organization can be operating with fundamentally different standards, creating inconsistency and friction when they need to collaborate.</p><p>The biggest blocker to effective AI adoption, per a survey of 120+ practitioners: not compliance, but capability. 78.6% cited lack of prompting skills and best practices as their top challenge. Prompting isn’t a soft skill. It’s the interface between human intent and AI output — and the gap between a developer who constructs effective, context-rich prompts and one who types a vague question and accepts whatever comes back is measurable in output quality, verification time, and rework rate.</p><p>Computing expenditure is also a real constraint that’s often invisible at the pilot stage. Computing costs rose 89% between 2023 and 2025, largely driven by GenAI workloads. Organizations that fail to model this economic reality early find that AI investments can consume more than they return.</p><h4><strong>The bottom line</strong></h4><p>AI is not a uniform accelerant. It’s a capability shift that demands intentional adoption — governance, literacy, mentorship design, and human accountability at every phase.</p><p>The organizations that will lead are those that look at the full lifecycle — not just implementation — invest in the developer role that’s emerging, and resist measuring success by adoption rate alone.</p><p>Speed is easy to see. Capability erosion is not — until it’s too late to reverse.</p><p><em>I wrote this up in full as a white paper: “From Ideation to Warranty: How AI Is Reshaping the Software Delivery Lifecycle.” If you want the complete analysis, citations, and governance recommendations, the link is in the comments.</em></p><p><em>I’m a Principal Engineer with a background in healthcare software and fifteen years prior as an entrepreneur in manufacturing. I write about software delivery, engineering leadership, and the pragmatics of building in the real world.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a8f9974b741" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The detour into JS]]></title>
            <link>https://medium.com/@brunz36/the-detour-into-js-7a0c09d57a51?source=rss-d95b2ffc6b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a0c09d57a51</guid>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Bruno Ribeiro]]></dc:creator>
            <pubDate>Thu, 27 Apr 2017 03:59:26 GMT</pubDate>
            <atom:updated>2017-04-27T03:59:26.496Z</atom:updated>
            <content:encoded><![CDATA[<p>My journey at the The Iron Yard has been an exhausting and exciting one so far. We are at the week 7 mark and we have come full circle back to front-end web-development. Today we were introduced to JavaScipt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*MIDz0JDZ-rlb173aSeD-jQ.png" /><figcaption>Skimming the surface of Front-End</figcaption></figure><p>This language syntax seems very different than the Ruby we have been using for the last seven weeks. I’ve done some coding in Python and Java before I started at TIY so the syntax didn’t seem so foreign but it does feel very clunky after really getting to know Ruby a lot a better. I think this seems like a very fun language to learn because of the power it has in the Front and Back end of web-development. It seems I won’t have to use iterator loops with JS these days but just the idea makes me shudder. While I’m not thrilled at the idea of having to write all those curly brackets and making sure every line is properly closed, this is trivial. The ability to write a line and use proper indentation was the reason I decided to use SLIM as a template language when using Rails. But I’m truly excited to take this tangent to learn a small amount of JS to give me the tools to be able to learn this extremely powerful language on my own. I will become a Full Stack Engineer one day and JS will be one the many tools in my toolbox.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a0c09d57a51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s not easy to be Slim]]></title>
            <link>https://medium.com/@brunz36/its-not-easy-to-be-slim-acaeb33c906a?source=rss-d95b2ffc6b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/acaeb33c906a</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[junior-developer]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[slim]]></category>
            <category><![CDATA[the-iron-yard]]></category>
            <dc:creator><![CDATA[Bruno Ribeiro]]></dc:creator>
            <pubDate>Mon, 17 Apr 2017 23:30:12 GMT</pubDate>
            <atom:updated>2017-04-18T03:57:16.510Z</atom:updated>
            <content:encoded><![CDATA[<p>The Rails train stops for no one. That is how I felt this weekend. This week my classmates and I learned different bootstrap tricks and methods, authentication methods, image processing and general Ruby on Rails best practices. But the icing on the cake was at the end of the week…Slim Template Engine. We already have been working with the ERB engine but our instructor introduced us to HAML and SLIM.</p><p>He made it clear towards the end of the week that this was an optional method to learn but we could be asked to use one of these templates in our jobs. So, a few of my classmates and I decided to take on this challenge for the weekend’s homework, creating a Zillow.com clone…@^#%!!!</p><p>Our instructor gave us the parameters to create the site. Have a landing page that appeals to the user to visit the site and search for homes, an index page, show page, form page and search functions. Straight forward enough but not easy, we covered much of this and class and Gavin has shown us where to search for the answers. But, as previously stated…some of my classmates and I like shiny new things.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*rOjuBMXQPQ0mYrcXYI0IIQ.gif" /></figure><p>SQUIRREL!!! So, I decide to do the weekend lab in this new template. After spending the most of the first day creating wireframes, different design templates and rails functionality. I started to code, or at least attempt to. This felt like I was learning everything over again, where do I put classes and types??? I poured over more Slim docs over the weekend than Rails docs it felt like.</p><blockquote>This was an extremely frustrating lab, at one time I decided to switch over to ERB. But I went for a walk, calmed myself down and kept on working the problem.</blockquote><p>The basic parts were easy enough, use a period for classes and indent but as soon as I got to form, navbars collapsing and linked buttons…I wanted to punch a kitten. After many hurdles, I started to chip away at the problem, understanding little by little how to code in Slim. This was a very gratifying feeling, to learn something new and powerful. I love the way Slim looks in Atom. It’s so easy to read and a lot more compact. But it’s not without it’s pitfalls, one wrong indentation and your code comes crashing down. In the end, I was able to finish my site on Sunday and make it look semi decent in the process. With homework turned in I can look back fondly at my crippling frustration. From day one The Iron Yard said there would be days like these…or weekends. This was my toughest weekend so far, culminating with the fact that I was on campus while my family had Easter Sunday without me. I can’t thank them enough for being so understanding during this very demanding school…Like me they understand the juice is worth the squeeze.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acaeb33c906a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Off the rails…then back on]]></title>
            <link>https://medium.com/@brunz36/off-the-rails-then-back-on-f0c29aa2f1f8?source=rss-d95b2ffc6b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0c29aa2f1f8</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Bruno Ribeiro]]></dc:creator>
            <pubDate>Mon, 10 Apr 2017 18:55:42 GMT</pubDate>
            <atom:updated>2017-04-10T18:55:42.503Z</atom:updated>
            <content:encoded><![CDATA[<p>At the end of our 4th week at The Iron Yard we were introduced to the Rails framework. At first glance it was a bit frustrating to see how simple it was to get a basic site up and running. But for me it was also very helpful to somewhat understand what Rails is doing in the background. My weekend homework started off great I was understanding the concepts and I could visualize how the app was running and sending information back and forth. So, I was feeling pretty good about myself. I wasn’t getting too cute and trying to do too much, just focused on the what the instructions at hand. Then came the vaunted Epic Mode, it <strong>seemed</strong> straight forward…add the ability to have comments on your page. While I read every literature that was provided to us and a few others, no dice. I took some time to spend with my family and friends but this problem was at the forefront of my thoughts all weekend. I read some more, started to watch some YouTube videos(picked up some great tips but nothing to understand why my code was broken). I couldn’t get the primary key of the story table to match the story_id of the comment table. I was extremely frustrated because something so simple was blocking my completion of the weekends homework. So that night I went to sleep watching YouTube videos that were leading to nowhere. I decided that I would wake up early and get to it at The Iron Yard. I get to TIY and start looking over the docs to see if I missed anything…one of my classmates comes in and we exchange hellos and see how our weekends were. I tell her my problem and she says in the Getting Started with Rails Guide…the beginning guide and <strong>I MISSED IT!!! </strong>So, I have some time to complete it and turn it in. A quick read and a few questions I solve the problem and I’m done with Epic Mode. My problem was two missing lines of code…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*qOSj3aJGQSjSYOFUB-xS-w.png" /></figure><p>Rails seems like a great framework and extremely powerful tool, but if you don’t read the docs and follow their guides…You’re going to have a bad time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0c29aa2f1f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What a strange trip it’s been…]]></title>
            <link>https://medium.com/@brunz36/what-a-strange-trip-its-been-4bef6501e0c1?source=rss-d95b2ffc6b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bef6501e0c1</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Bruno Ribeiro]]></dc:creator>
            <pubDate>Tue, 04 Apr 2017 01:42:26 GMT</pubDate>
            <atom:updated>2017-04-04T01:42:26.516Z</atom:updated>
            <content:encoded><![CDATA[<p>The Iron Yard, a month into my journey and this already feels like the most rewarding professional experience of my career. I decided before the start of the cohort that I would completely immerse myself into the program, but I never thought it would be like this.</p><h3><strong>The Lead Up</strong></h3><p>My love for computers and anything related started with my first exposure to it, the Macintosh LC II. I remember being so excited to go to school where</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*8SMbCdfR9VwHy4xJWV617A.jpeg" /><figcaption>Compaq Presario 425</figcaption></figure><p>our new middle school had 8 computers per classroom. While I was interested in playing video games like Oregon Trail and Civilization than any type of coding but the seed was planted. By 7th grade my parents bought my first personal computer, the Compaq Presario 425. This was the computer that I grew up with, this was my first love. I had an AOL account and the digital world was my oyster. One of my fondest childhood memories was when I decided I needed to add more RAM to my computer. I used to mow several lawns around the neighborhood, and within a month or two I had enough to double my RAM. I was so excited to go to the CompUSA, I literally didn’t sleep the night before. My mom drove me to the CompUSA on Hillsborough Ave. at the intersection of Dale Mabry Hwy and I plunked down $135 for 4MB of RAM(hahaha). I felt so proud of myself being able to install my own RAM, it made me feel like Wozniak when he built his first circuit board. In High School, I take my first programming class Pascal. This was a very basic course but I felt empowered by creating something from nothing. Fast forward a year and now I’m graduating High School and going off to study Computer Science at the University of North Florida. My parents tell me that for me High School graduating present that they will buy me a computer…I say no. I want to build my own computer. I do my research and decide that I was going to buy the AMD Athlon CPU with a mid-tower setup. I don’t remember the rest of the details but I went to a local computer store this time and purchased all the necessary parts, picked the store owners brain for what seemed like two minutes but by the look on my parents face it must have been at least an hour. I spent the next six hours putting together the computer and installing Windows 98. My college years were mainly spent on the water surfing and immaturity reigned supreme. My focus waned from computers to the life lived by a bartender. Then came the realization that working in restaurants wasn’t the life that I wanted to live. So, I went back to the family business which is jewelry manufacturing. I got back to my love of creating something from nothing, meanwhile I spend a lot of my time reading and watching various technology related publications. A few more years pass and I start reading about the world of CAD/CAM and how it could be applied to the Jewelry Manufacturing process. I completely immerse myself in these programs and continue learning new techniques and programs. I spend about a decade perfecting my craft and becoming quite proficient in jewelry manufacturing. But there was always this feeling that this wasn’t what I really wanted from my experience with computers. So, with my father approaching retirement age, I decided to change careers. I decide to go the local college and enroll in the Cyber Security against a few of my friends’ recommendations who are web developers. They said I would be better served in the programming field due to my background in CAD. A year later I came to the realization that they were right. The security field while interesting was becoming rather boring and tedious. I already took a Python course and was really excited about it, so much so that I read the textbook after the course ended to further my Python learning. Then at a Christmas party I start talking with a family friend who works at Malwarebytes and tell him that I’m probably switching to programming degree at the local college. I tell him while I’m not exactly thrilled with the curriculum they offer, what were my options. He proceeds to tell me about a school that while extremely difficult, very rewarding. He himself has gone to what they Demo Days and hired a few graduates of The Iron Yard. A few more months pass and I find myself waking up at 6:30 in the morning and drive 50 minutes to St. Pete and looking forward to being pushed to my limit every day.</p><h3><strong>Pay the Iron Price</strong></h3><p>When I signed up for The Iron Yard I decided that I would shut myself from the world and completely immerse myself in the program. While I’ve been an entrepreneur for over a decade and have had to wear many hats in my business, I don’t ever remember feeling like this. I’m excited about all the new things I’m learning, and learning to forget. This is because TIY is teaching us the basics and the hard way to program in Ruby and HTML before we get the frameworks. It was comical to watch the instructor take our code that we spent all weekend writing with at least 200 lines of code and whittle it down to about 50 lines in about 5 minutes. I’m glad for this teaching method because it truly explains how to solve a problem before we get to the more automated processes. One of the many aspects of this course that I love is the way the instructors push us to find the answers on our own. They show us where the documentation is and push us to seek those answers where other teaching methods may have given us a snippet of code but gained nothing from the teaching exercise. While we have worked on many different parts of Ruby and HTML this has been the best part so far, because this will be used for the rest of professional life. New versions, frameworks, languages will come out and be used but these techniques will always be there. In the three weeks at TIY it feels like I’ve learned more about coding and myself than the last two years at the local college.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bef6501e0c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>