<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Methodology on My AWS Rocks!</title><link>https://www.myaws.rocks/tags/methodology/</link><description>Recent content in Methodology on My AWS Rocks!</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 27 Jul 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://www.myaws.rocks/tags/methodology/index.xml" rel="self" type="application/rss+xml"/><item><title>Don't get trapped by the elephant in the room!</title><link>https://www.myaws.rocks/decision-making-for-technology/</link><pubDate>Sat, 27 Jul 2024 00:00:00 +0000</pubDate><guid>https://www.myaws.rocks/decision-making-for-technology/</guid><description>&lt;p&gt;I was part of a webinar with Jeff Barr where he was discussing creating your own luck. One of the elements he talked about was doing something quickly and more frequently can often be better than waiting to ensure you are doing the right thing. He talked about the OODA model which I discuss later, but it got me thinking about how often in technology we so often get caught up in the detail, or even worse, the wrong detail and we end up not doing anything.&lt;/p&gt;</description></item></channel></rss>