<?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 Joel Lim on Medium]]></title>
        <description><![CDATA[Stories by Joel Lim on Medium]]></description>
        <link>https://medium.com/@aljorhythm?source=rss-de10ddde9ac------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*6fzXqqyUprzekKzw7rjvsg.png</url>
            <title>Stories by Joel Lim on Medium</title>
            <link>https://medium.com/@aljorhythm?source=rss-de10ddde9ac------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:27:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aljorhythm/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[The Frankenstein MonoMicroLith]]></title>
            <link>https://medium.com/aljorhythm/the-frankenstein-monomicrolith-40010e69e379?source=rss-de10ddde9ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/40010e69e379</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[system-design-concepts]]></category>
            <category><![CDATA[monolith]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[Joel Lim]]></dc:creator>
            <pubDate>Sun, 23 Apr 2023 14:33:00 GMT</pubDate>
            <atom:updated>2023-07-27T03:15:04.290Z</atom:updated>
            <content:encoded><![CDATA[<p>Getting Independent Deployment Wrong</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*quegLw41CRp03t0rTZyMsg.png" /></figure><p>The warning of faux-microservices has made rounds in the community in recent years. A cursory reading of authoritative sources (e.g., <a href="https://microservices.io/">https://microservices.io, Building Microservices) </a>will tell you one of the central ideas of a microservice architecture is independently deployable services. Many organizations exhibit some form of the distributed monolith, incurring the costs of operating distributed systems while not benefiting from the objectives of a microservices architecture.</p><p>The boxes in the illustration represent different code bases with their own histories, and the colors represent concerns that could be loosely coupled. A modular monolith or properly designed microservices is desired. Avoid the situation in the third box —run-time decoupling with verification-time (the process of taking a change from a developer’s environment to production) coupling. Requiring any change to go through a process involving everything else fundamentally contradicts independent change implied by decomposing concerns into separate services. Such confusion is an example of <a href="https://wiki.c2.com/?CargoCultProgramming">cargo cult programming</a>. If you don’t have good justifications and don’t understand the costs that come with micro-services, don’t do it.</p><p>Threedots has a good <a href="https://threedots.tech/post/microservices-or-monolith-its-detail/">article</a> on how modular software can be achieved with microservices and monoliths.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40010e69e379" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aljorhythm/the-frankenstein-monomicrolith-40010e69e379">The Frankenstein MonoMicroLith</a> was originally published in <a href="https://medium.com/aljorhythm">aljorhythm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Textbook] Tests]]></title>
            <link>https://aljorhythm.medium.com/textbook-tests-6fd275fb4f41?source=rss-de10ddde9ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fd275fb4f41</guid>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Joel Lim]]></dc:creator>
            <pubDate>Sun, 10 Oct 2021 11:57:17 GMT</pubDate>
            <atom:updated>2021-10-10T12:05:57.743Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://martinfowler.com/articles/2021-test-shapes.html">On the Diverse And Fantastical Shapes of Testing</a></p><blockquote>So, going back to pyramids versus honeycombs, when I read advocates of honeycomb and similar shapes, I usually hear them criticize the excessive use of mocks and talk about the various problems that leads to. From this I infer that their definition of “unit test” is specifically what I would call a solitary unit test. Similarly their notion of integration test sounds very much like what I would call a sociable unit test. This makes the pyramid versus honeycomb discussion moot, since any descriptions I’ve heard of the test pyramid consider unit tests to be sociable and/or solitary.</blockquote><blockquote>This semantic picture is made even muddier by the definition of Integration Test, which makes “unit test” look tightly defined. <strong>The take-away here is when anyone starts talking about various testing categories, dig deeper on what they mean by their words, as they probably don’t use them the same way as the last person you read did.</strong></blockquote><p><a href="https://martinfowler.com/bliki/UnitTest.html">bliki: Unit Test</a></p><blockquote>A more important distinction is whether the unit you’re testing should be sociable or solitary <a href="https://martinfowler.com/bliki/UnitTest.html#footnote-solitary">[2]</a>. Imagine you’re testing an order class’s price method. The price method needs to invoke some functions on the product and customer classes. If you like your unit tests to be solitary, you don’t want to use the real product or customer classes here, because a fault in the customer class would cause the order class’s tests to fail. Instead you use <a href="https://martinfowler.com/bliki/TestDouble.html">TestDoubles</a> for the collaborators.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*X5DG1qJJv9U978fx.png" /></figure><blockquote><strong>But not all unit testers use solitary unit tests. Indeed when xunit testing began in the 90’s we made no attempt to go solitary unless communicating with the collaborators was awkward (such as a remote credit card verification system).</strong> We didn’t find it difficult to track down the actual fault, even if it caused neighboring tests to fail. So we felt allowing our tests to be sociable didn’t lead to problems in practice.</blockquote><p><a href="https://martinfowler.com/bliki/TestPyramid.html">bliki: Test Pyramid</a></p><blockquote>The test pyramid comes up a lot in Agile testing circles and while its core message is sound, there is much more to say about building a well-balanced test portfolio. <strong>A common problem is that teams conflate the concepts of end-to-end tests, UI tests, and customer facing tests. These are all orthogonal characteristics.</strong> For example a rich javascript UI should have most of its UI behavior tested with javascript unit tests using something like Jasmine. A complex set of business rules could have tests captured in a customer-facing form, but run just on the relevant module much as unit tests are.</blockquote><blockquote>I always argue that high-level tests are there as a second line of test defense. If you get a failure in a high level test, not just do you have a bug in your functional code, you also have a missing or incorrect unit test. Thus I advise that before fixing a bug exposed by a high level test, you should replicate the bug with a unit test. Then the unit test ensures the bug stays dead.</blockquote><p><a href="https://martinfowler.com/bliki/SelfTestingCode.html">bliki: SelfTestingCode</a></p><blockquote>You have self-testing code when you can run a series of automated tests against the code base and be confident that, should the tests pass, your code is free of any substantial defects. One way I think of it is that as well as building your software system, you simultaneously build a bug detector that’s able to detect any faults inside the system. Should anyone in the team accidentally introduce a bug, the detector goes off. By running the test suite frequently, at least several times a day, you’re able to detect such bugs soon after they are introduced, so you can just look in the recent changes, which makes it <em>much</em> easier to find them. No programming episode is complete without working code and the tests to keep it working. <strong>Our attitude is to assume that any non-trivial code without tests is broken.</strong></blockquote><blockquote>Self-testing code is a key part of <a href="https://martinfowler.com/articles/continuousIntegration.html">Continuous Integration</a>, indeed I say that you aren’t really doing continuous integration unless you have self-testing code. As a pillar of Continuous Integration, it is also a necessary part of <a href="https://martinfowler.com/delivery.html">Continuous Delivery</a>.</blockquote><p><a href="https://martinfowler.com/bliki/TestCoverage.html">bliki: Test Coverage</a></p><blockquote>If you make a certain level of coverage a target, people will try to attain it. <strong>The trouble is that high coverage numbers are too easy to reach with low quality testing.</strong> At the most absurd level you have <a href="https://martinfowler.com/bliki/AssertionFreeTesting.html">AssertionFreeTesting</a>. But even without that you get lots of tests looking for things that rarely go wrong distracting you from testing the things that really matter.</blockquote><blockquote>Like most aspects of programming, testing requires thoughtfulness. TDD is a very useful, but certainly not sufficient, tool to help you get good tests. If you are testing thoughtfully and well, I would expect a coverage percentage in the upper 80s or 90s. I would be suspicious of anything like 100% — it would smell of someone writing tests to make the coverage numbers happy, but not thinking about what they are doing.</blockquote><blockquote>The reason, of course, why people focus on coverage numbers is because they want to know if they are testing enough. Certainly low coverage numbers, say below half, are a sign of trouble. But high numbers don’t necessarily mean much, and lead to <a href="https://sriramnarayan.blogspot.com/2011/04/dashboards-promote-ignorance.html?m=0">ignorance-promoting dashboards</a>. Sufficiency of testing is much more complicated attribute than coverage can answer. I would say you are doing enough testing if the following is true:</blockquote><blockquote>You rarely get bugs that escape into production, <strong>and</strong></blockquote><blockquote>You are rarely hesitant to change some code for fear it will cause production bugs.</blockquote><blockquote>Can you test too much? Sure you can. You are testing too much if you can remove tests while still having enough. But this is a difficult thing to sense. One sign you are testing too much is if your tests are slowing you down. If it seems like a simple change to code causes excessively long changes to tests, that’s a sign that there’s a problem with the tests. This may not be so much that you are testing too many things, but that you have duplication in your tests.</blockquote><p><a href="https://testing.googleblog.com/2019/12/testing-on-toilet-tests-too-dry-make.html">Testing on the Toilet: Tests Too DRY? Make Them DAMP!</a></p><blockquote>Since tests don’t have tests, it should be easy for humans to manually inspect them for correctness, even at the expense of greater code duplication. This means that the DRY principle often isn’t a good fit for unit tests, even though it is a best practice for production code. In tests we can use the <a href="https://stackoverflow.com/questions/6453235/what-does-damp-not-dry-mean-when-talking-about-unit-tests">DAMP principle</a> (“Descriptive and Meaningful Phrases”), which emphasizes <em>readability over uniqueness</em>. Applying this principle can introduce code redundancy (e.g., by repeating similar code), but it makes tests more obviously correct.</blockquote><blockquote>Note that the DRY principle is still relevant in tests; for example, using a helper function for creating value objects can increase clarity by removing redundant details from the test body. Ideally, test code should be both readable and unique, but sometimes there’s a trade-off. When writing unit tests and faced with a choice between the DRY and DAMP principles, lean more heavily toward DAMP.</blockquote><p><a href="https://testing.googleblog.com/2015/04/just-say-no-to-more-end-to-end-tests.html">Just Say No to More End-to-End Tests</a></p><blockquote>Tests create a feedback loop that informs the developer whether the product is working or not. The ideal feedback loop has several properties:</blockquote><blockquote><strong>It’s fast</strong>. No developer wants to wait hours or days to find out if their change works. Sometimes the change does not work — nobody is perfect — and the feedback loop needs to run multiple times. A faster feedback loop leads to faster fixes. If the loop is fast enough, developers may even run tests before checking in a change.</blockquote><blockquote><strong>It’s reliable</strong>. No developer wants to spend hours debugging a test, only to find out it was a flaky test. Flaky tests reduce the developer’s trust in the test, and as a result flaky tests are often ignored, even when they find real product issues.</blockquote><blockquote><strong>It isolates failures</strong>. To fix a bug, developers need to find the specific lines of code causing the bug. When a product contains millions of lines of codes, and the bug could be anywhere, it’s like trying to find a needle in a haystack.</blockquote><p><a href="https://testing.googleblog.com/2016/05/flaky-tests-at-google-and-how-we.html?m=1">Flaky Tests at Google and How We Mitigate Them</a></p><iframe src="https://drive.google.com/viewerng/viewer?url=https%3A//rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf&amp;embedded=true" width="600" height="780" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd4e0337eb7916c264329958f92fb936/href">https://medium.com/media/dd4e0337eb7916c264329958f92fb936/href</a></iframe><blockquote>If you want to reduce your test mass, the number one thing you should do is look at the tests that have never failed in a year and consider throwing them away. They are producing no information for you — or at least very little information. The value of the information they produce may not be worth the expense of maintaining and running the tests. This is the first set of tests to throw away — whether they are unit tests, integration tests, or system tests. <br> <br>Another client of mine also had too many unit tests. I pointed out to them that this would decrease their velocity, because every change to a function should require a coordinated change to the test. They informed me that they had written their tests in such a way that they didn’t have to change the tests when the <br>functionality changed. <strong>That of course means that the tests weren’t testing the functionality, so whatever they were testing was of little value. </strong><br> <br><strong>Don’t underestimate the intelligence of your people, but don’t underestimate the collective stupidity of many people working together in a complex domain.</strong> You probably think you would never do what the team above did, but I am always finding more and more things like this that almost defy belief. It’s likely that you have some of these skeletons in you closet. Hunt them out, have a good laugh at yourself, fix them, and move on. If you have tests like this, that’s the second set of tests to throw away.</blockquote><blockquote><strong>The third tests to throw away the tautological ones</strong>. I see more of these than you can imagine — particularly in shops following what they call test-driven development. (Testing for this being non-null on entry to a method is, by the way, not a tautological test — and can be very informative. However, as with most unit <br>tests, it’s better to make this an assertion than to pepper your test <br>framework with such checks. More on that below.)</blockquote><p><a href="https://medium.com/swlh/dont-mock-databases-just-run-them-with-docker-1564ae21117f">Don’t mock Databases, just run them with Docker</a></p><blockquote>Running Databases for Unit testing used to suck</blockquote><blockquote>In the past, setting up a database to use with unit testing was a hassle. It meant running a database service on either a physical or virtual server. Once you get a server, the following install process is generally long itself.</blockquote><blockquote>In big companies, this could mean working with many teams, which elongates the process. This alone is a common deterrent for using a real database within unit tests.</blockquote><blockquote>Even after going through the process, it is often cost or time prohibitive to get more than one sever. This makes it even more difficult to use within a CI pipeline.</blockquote><blockquote>Most applications have many developers. Trying to use a single database service for every developer doesn’t work. It’s very difficult to coordinate more than one build at a time.</blockquote><blockquote>With the speed of development these days, running a pipeline one build at a time is a major hinderance. It’s also a waste of time.</blockquote><blockquote>What I’ve seen people do in response is only run the tests on the main branch build. Where pull requests or local unit test runs don&#39;t run these tests. This means less testing is performed on pull requests and more testing is done after merge. This in itself is fundamentally flawed.</blockquote><blockquote>The point of executing builds on pull requests is to ensure that new changes work with existing code. Once merged everything should just work. If pull requests are lacking in tests, then there is a higher likelihood of breaking the main build.</blockquote><blockquote>Which means rolling back changes, this is difficult on high velocity repositories. With many pull requests being submitted and merged in the same day. It can be very difficult finding which change broke the build.</blockquote><p><a href="https://medium.com/@eugenkiss/lean-testing-or-why-unit-tests-are-worse-than-you-think-b6500139a009">Lean Testing or Why Unit Tests are Worse than You Think</a></p><blockquote><em>I think you’re missing the point when you refer to Fowler’s testing pyramid. Martin Fowler sees a unit as a unit of behaviour, not a unit of code. This means what Kent Dodds refers to as an “integration test” is basically the same as what Martin Fowler sees as a “unit test”. Martin Fowler writes unit tests that don’t mock out all collaborating code, and that’s the key to it all. The problem is that so many people consider a unit to be a unit of code, and that’s where you end up with tests that are tightly coupled to implementation details and start down the road of diminishing returns.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fd275fb4f41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Textbook] Recommended Videos]]></title>
            <link>https://medium.com/aljorhythm/textbook-recommended-videos-93767ed0965d?source=rss-de10ddde9ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/93767ed0965d</guid>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Joel Lim]]></dc:creator>
            <pubDate>Fri, 08 Oct 2021 07:22:08 GMT</pubDate>
            <atom:updated>2021-10-08T07:22:08.457Z</atom:updated>
            <content:encoded><![CDATA[<p>Software Engineering, Agile, DevOps, CI/CD</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FAvs70dZ3Vlk%3Fstart%3D691&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DAvs70dZ3Vlk&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FAvs70dZ3Vlk%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/11ada9a7eeefab4336f4080f3804c61e/href">https://medium.com/media/11ada9a7eeefab4336f4080f3804c61e/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FURlnxbaHhTs%3Fstart%3D699%26feature%3Doembed%26start%3D699&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DURlnxbaHhTs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FURlnxbaHhTs%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/20960f0108302a4aedeb78cb56fbe010/href">https://medium.com/media/20960f0108302a4aedeb78cb56fbe010/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FvSnCeJEka_s%3Fstart%3D1242&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DvSnCeJEka_s&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FvSnCeJEka_s%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/024cc5533736edc6f5a1bf4481956001/href">https://medium.com/media/024cc5533736edc6f5a1bf4481956001/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FQVBlnCTu9Ms%3Fstart%3D925%26feature%3Doembed%26start%3D925&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQVBlnCTu9Ms&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FQVBlnCTu9Ms%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/02231c33a94cfbb4fac5fb06405ba38a/href">https://medium.com/media/02231c33a94cfbb4fac5fb06405ba38a/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FF42A3R28WMU%3Fstart%3D2055%26feature%3Doembed%26start%3D2055&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DF42A3R28WMU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FF42A3R28WMU%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/a68cb4af1cd393aa6ca5af9235568c33/href">https://medium.com/media/a68cb4af1cd393aa6ca5af9235568c33/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FUTKIT6STSVM%3Fstart%3D953%26feature%3Doembed%26start%3D953&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DUTKIT6STSVM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FUTKIT6STSVM%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/6c3ef109078f1f9e417d5dce7c4c5ef6/href">https://medium.com/media/6c3ef109078f1f9e417d5dce7c4c5ef6/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F2zYxWEZ0gYg%3Fstart%3D2306%26feature%3Doembed%26start%3D2306&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2zYxWEZ0gYg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F2zYxWEZ0gYg%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/a9091a06b924c24988836f705bff6600/href">https://medium.com/media/a9091a06b924c24988836f705bff6600/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F7anxCh-gUWo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D7anxCh-gUWo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F7anxCh-gUWo%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/4c097f440c59ce18151b1e832167ed02/href">https://medium.com/media/4c097f440c59ce18151b1e832167ed02/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FwjF4X9t3FMk%3Fstart%3D1265&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DwjF4X9t3FMk&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FwjF4X9t3FMk%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/4fe46be9da4f8b126ad7e977cf5d7906/href">https://medium.com/media/4fe46be9da4f8b126ad7e977cf5d7906/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93767ed0965d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aljorhythm/textbook-recommended-videos-93767ed0965d">[Textbook] Recommended Videos</a> was originally published in <a href="https://medium.com/aljorhythm">aljorhythm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Most Software Is Never “Done”]]></title>
            <link>https://medium.com/aljorhythm/most-software-is-never-done-c6a9bcda12a7?source=rss-de10ddde9ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6a9bcda12a7</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[technical-debt]]></category>
            <dc:creator><![CDATA[Joel Lim]]></dc:creator>
            <pubDate>Sun, 15 Aug 2021 14:51:28 GMT</pubDate>
            <atom:updated>2021-10-03T17:48:55.922Z</atom:updated>
            <content:encoded><![CDATA[<h4>On some nature of software development and heuristics for gauging impact of technical debt</h4><h3>Preliminaries</h3><blockquote>Developers often justify attention to quality by justifying through the need for proper professionalism. But this moralistic argument implies that this quality comes at a cost — dooming their argument. <strong>The annoying thing is that the resulting crufty code both makes developers’ lives harder, and costs the customer money</strong>. When thinking about internal quality, I stress that we should only approach it as an economic argument. <strong>High internal quality reduces the cost of future features, meaning that putting the time into writing good code actually reduces cost.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*hTUhl0OUzIK5Vaus.png" /><figcaption>“this points occurs in weeks, not months”</figcaption></figure><p><a href="https://martinfowler.com/articles/is-quality-worth-cost.html">Is High Quality Software Worth the Cost?</a></p><blockquote>Your 6 person team with a consistent autodeploy loop would take 24 people to do the same amount of work, if it took days to deploy their changes. Your 10 person team that ships in weeks would need 80 people.</blockquote><blockquote>At cost to the company of approx 200k per engineer, that’s $3.6 million in the first example and $14 million in the second example. <strong>That’s how much your neglect of internal tools and kneejerk fear of autodeploy might be costing you.</strong></blockquote><p><a href="https://charity.wtf/2021/02/19/how-much-is-your-fear-costing-you/">How much is your fear of continuous deployment costing you?</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ToBiMjLKOt8eY7-qiRz7Q.png" /><figcaption>The best teams deploy 208x more frequently</figcaption></figure><p><a href="https://cloud.google.com/devops">What is DevOps? Research and Solutions | Google Cloud</a></p><blockquote>Even ignoring usability, engineering progress slows to a halt once a project becomes too complex. Each new line of code added to an application has a chance of interacting with every other line. The bigger an application’s codebase, the more bugs are introduced whenever a new feature is built. Eventually, the rate of work created from new bugs cancels out the rate of work done from feature development. This is known as “technical debt” and is the main challenge in professional software development.</blockquote><blockquote>…</blockquote><blockquote>Building good software involves alternating cycles of expanding and reducing complexity. As new features are developed, disorder naturally accumulates in the system. When this messiness starts to cause problems, progress is suspended to spend time cleaning up.</blockquote><p><a href="https://www.csc.gov.sg/articles/how-to-build-good-software">How to Build Good Software</a></p><h3>Software Is Never Done</h3><p>An underappreciated aspect of software development that is not found in most other disciplines is that the product is an ongoing endeavor and any work done on it has effects on subsequent efforts. A writer can write a boring book and a factory can produce a batch of physical products of low quality. They are done, finished. The next story, product design, or batch can be produced independently of previous results. Software is unlike this.</p><p>The delivery of software — putting software into users&#39; hands — is like manufacturing but the development of software is everything but. It is more like constantly changing the structure of a house while people are living in it. We have to be concerned about the change of rate/cost of change on top of completion of the immediate requests and not affecting ongoing lives.</p><p>But where do we stop? It is not practical to consider the infinite number of hypothetical scenarios. This brings us to useful but very demanding metrics like lead time, cycle time, and deployment frequency. These terms have more precise definitions but they are used loosely here. The gist is that if once upon a time it took 30 minutes to <strong>reliably </strong>and <strong>confidently</strong> put the smallest changes into users&#39; hands and now it takes 15 more, it’s an indication that it’s probably wise to address the increase in time and nip it. Efforts for big changes are hard to quantify but they are just a series of smaller changes. This is where <strong>technical excellence, techniques, and practices </strong>come in.</p><p>We might think these are things that end users don’t <em>see</em>. But actually often they do. Users do not just need feature A in the quickest time. Implicit is also the expectation and demand to also to provide features B, C, D, and many more changes in the fastest time. They can compare between competitors. If you have a stake in software, you have to be concerned about its internal qualities.</p><p>It is a challenge to quantify “technical debt” and its impact but we can start with heuristics. Don’t let the cost of change bloat — there’s no absolute figure to go for but everyone should be able to feel the friction and act on it. Developers should be able to say “Compared to last quarter, I seem to be taking twice the amount of time to understand and make changes to this part of the code and the entire pipeline is taking 15 minutes more for a single commit” and then spend time to reduce it. The well-known <a href="https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance"><strong>DORA</strong></a> has research on these metrics and their associations with organization performance.</p><p><em>“</em>Developers<em>”</em> often complain about the quality of code slowing down development but the expectation to <em>go faster </em>is always there. Software development is not repetitive work, how can we know if expectations are unreasonable or mismatched? Lead time and cycle time are measurable, observable, and actionable (though in many places impossible because of waterfall, yada yada…). The very best simply outperform the rest in orders of magnitude. We don’t make code more readable because we like it to be pretty. It’s because we expect many future changes to be related and cheaper to make. Conversely, we don’t “improve” on areas where no savings in time is expected.</p><p>Of course, this is all contextual. We do not need to care about the cost of change for software that is not expected to change but that is usually not the case. The cost of software development can be deceptively low because in comparison to physical products immediate and early changes can be observed very quickly. But this is where the challenge lies — keeping the cost of change low because software is expected to change frequently and indefinitely.</p><p>The same concerns will apply in the context of houses if in this imaginary world, changing building structures and installations are not costly and are expected every other day. Firms that are able to make changes quicker reliably and confidently<strong> </strong>will be more competitive. In present reality, unlike physical products, the lower limit of lead time for software development can be very low. Not taking advantage of this has been shown to cost much more. On top of that is great opportunity cost. Software development is more like a marathon than sprints. Most software is never done. Keep them easily modifiable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6a9bcda12a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aljorhythm/most-software-is-never-done-c6a9bcda12a7">Most Software Is Never “Done”</a> was originally published in <a href="https://medium.com/aljorhythm">aljorhythm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Scaling Agile Doesn’t Work]]></title>
            <link>https://medium.com/transcripts/why-scaling-agile-doesnt-work-1f6f00903c57?source=rss-de10ddde9ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f6f00903c57</guid>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[jez-humble]]></category>
            <dc:creator><![CDATA[Joel Lim]]></dc:creator>
            <pubDate>Tue, 13 Jul 2021 18:29:52 GMT</pubDate>
            <atom:updated>2021-07-13T18:32:31.080Z</atom:updated>
            <content:encoded><![CDATA[<p>Jez Humble</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F2zYxWEZ0gYg%3Fstart%3D22%26feature%3Doembed%26start%3D22&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2zYxWEZ0gYg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F2zYxWEZ0gYg%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/3ec112449bccdcc8a90cb2d7e3a28215/href">https://medium.com/media/3ec112449bccdcc8a90cb2d7e3a28215/href</a></iframe><blockquote>32:00 There is a new activity — creating, maintaining, evolving the suite of automated tests. If you went to your manager right now and said please can we invest 23% of our budget in test automation what would your manager say? That’s a rhetorical question. Yet here we have the business case of doing that. Despite you have 23% of your budget in test automation, that has enabled an 8x improvement in cost spent on innovation. It has massively reduced the amount of non-added value activities we are doing. Lean works by investing in removing waste so that you can increase throughput. … Here is the number to take to your CFO</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f6f00903c57" width="1" height="1" alt=""><hr><p><a href="https://medium.com/transcripts/why-scaling-agile-doesnt-work-1f6f00903c57">Why Scaling Agile Doesn’t Work</a> was originally published in <a href="https://medium.com/transcripts">Transcripts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Textbook] Git]]></title>
            <link>https://medium.com/aljorhythm/my-git-textbook-1717f379e6e6?source=rss-de10ddde9ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/1717f379e6e6</guid>
            <category><![CDATA[college]]></category>
            <category><![CDATA[textbooks]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[beginner]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Joel Lim]]></dc:creator>
            <pubDate>Wed, 07 Jul 2021 13:22:34 GMT</pubDate>
            <atom:updated>2021-08-15T15:03:12.541Z</atom:updated>
            <content:encoded><![CDATA[<p>These content should be enough. Crash courses are not recommended. Git is a technical tool with a bad UI. It requires users to have an accurate mental model of what it is, if not it will be used like Dropbox and people lose sleep.</p><h4>The OG: Pro-git</h4><p>It’s free. Chapters 1–3 give you a history of version control systems and a short intro on how Git works.</p><p><a href="https://git-scm.com/book/en/v2">Git</a></p><h4>Missing Semester — Git</h4><p>Great explanation on git internals and data structure.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F2sjqTHE0zok%3Fstart%3D1%26feature%3Doembed%26start%3D1&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2sjqTHE0zok&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F2sjqTHE0zok%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/96c4cdc1065db5a836b17e51df0fbfba/href">https://medium.com/media/96c4cdc1065db5a836b17e51df0fbfba/href</a></iframe><h4>Absolute needed to get going</h4><pre>git fetch<br>git add<br>git commit<br>git checkout<br>git checkout .<br>git checkout -b<br>git branch<br>git merge<br>git merge --abort<br>git push<br>git pull<br>git stash<br>git stash pop</pre><ul><li>Should learn how to merge conflicts (understand what are they first) manually before using things like -xTheirs</li><li>Am not recommending rebase because fast-forward is possible without a linear history and it causes more problems then it solves.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1717f379e6e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aljorhythm/my-git-textbook-1717f379e6e6">[Textbook] Git</a> was originally published in <a href="https://medium.com/aljorhythm">aljorhythm</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jez Humble — Leading a DevOps Transformation — live @ DevOn Summit 2018]]></title>
            <link>https://medium.com/transcripts/jez-humble-leading-a-devops-transformation-live-devon-summit-2018-19d308dd2079?source=rss-de10ddde9ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/19d308dd2079</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[jez-humble]]></category>
            <dc:creator><![CDATA[Joel Lim]]></dc:creator>
            <pubDate>Sat, 03 Jul 2021 19:04:41 GMT</pubDate>
            <atom:updated>2021-07-03T19:16:50.044Z</atom:updated>
            <content:encoded><![CDATA[<h3>Jez Humble — Leading a DevOps Transformation — live @ DevOn Summit 2018</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F7anxCh-gUWo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D7anxCh-gUWo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F7anxCh-gUWo%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/4c097f440c59ce18151b1e832167ed02/href">https://medium.com/media/4c097f440c59ce18151b1e832167ed02/href</a></iframe><blockquote>25:00 A lot of these architectural refreshes focus on the exciting new technologies but not on the outcomes that we are trying to achieve. Our research is very clear about what you should be aiming for with your architecture. We found that people who had answered yes to these questions were much more likely to be able to succeed at continuous delivery and devops and achieve high levels of performance.</blockquote><blockquote>The important thing about these outcomes is you can do these stuff with mainframe systems. Equally you could buy all the finest new technology and use kubernetes and docker and all these stuff and not achieve these outcomes. If you are going to spend the money make sure you achieve the outcomes … If you don’t achieve the outcomes you are wasting your money.</blockquote><p><a href="https://devonsummit.in/wp-content/uploads/2018/03/jez-humble.pdf">https://devonsummit.in/wp-content/uploads/2018/03/jez-humble.pd</a>f</p><blockquote>make large-scale changes to the design of its system without the permission of somebody outside the team or depending on other teams?</blockquote><blockquote>complete its work without needing fine-grained communication and coordination with people outside the team?</blockquote><blockquote>do most of its testing on demand, without requiring an integrated test environment?</blockquote><blockquote>deploy and release its product or service on demand, independently of other services the product or service depends upon?</blockquote><blockquote>perform deployments during normal business hours with negligible downtime?</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19d308dd2079" width="1" height="1" alt=""><hr><p><a href="https://medium.com/transcripts/jez-humble-leading-a-devops-transformation-live-devon-summit-2018-19d308dd2079">Jez Humble — Leading a DevOps Transformation — live @ DevOn Summit 2018</a> was originally published in <a href="https://medium.com/transcripts">Transcripts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Andrew Clay Shafer — What is DevOps and why should you care?]]></title>
            <link>https://medium.com/transcripts/andrew-clay-shafer-what-is-devops-and-why-should-you-care-d8a403d3b4f5?source=rss-de10ddde9ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8a403d3b4f5</guid>
            <category><![CDATA[organisation]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[andrew-clay-shafer]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Joel Lim]]></dc:creator>
            <pubDate>Sat, 03 Jul 2021 12:59:38 GMT</pubDate>
            <atom:updated>2021-10-14T03:59:22.170Z</atom:updated>
            <content:encoded><![CDATA[<h3>Andrew Clay Shafer — What is DevOps and why should you care?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FSrmLySIUvpQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DSrmLySIUvpQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FSrmLySIUvpQ%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/478deff16556bb9b0ea2a47a044202c6/href">https://medium.com/media/478deff16556bb9b0ea2a47a044202c6/href</a></iframe><p>25:00</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LoGs0HuK2-eOR9_8WguOxQ.png" /></figure><blockquote>We have the wall of confusion at scale between these communities or in the organization. So what we decide in some places is we are going to take the dev and ops divide and the wall of confusion and we are going to solve it with a new silo.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fu-NUCRyYqjpdP_gpqjFQQ.png" /></figure><blockquote>Now you have two walls of confusion. Now we have a devops team, or an SRE team. Doesn’t matter. The words don’t matter. It’s probably not the best for your org.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*MQV16khLyOUyO8fBq4pXUQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8a403d3b4f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/transcripts/andrew-clay-shafer-what-is-devops-and-why-should-you-care-d8a403d3b4f5">Andrew Clay Shafer — What is DevOps and why should you care?</a> was originally published in <a href="https://medium.com/transcripts">Transcripts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Martin Fowler — What does Tech Excellence Look Like?]]></title>
            <link>https://medium.com/transcripts/martin-fowler-what-does-tech-excellence-look-like-8281aa72bf8d?source=rss-de10ddde9ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/8281aa72bf8d</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[martin-fowler]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Joel Lim]]></dc:creator>
            <pubDate>Sat, 03 Jul 2021 12:41:51 GMT</pubDate>
            <atom:updated>2021-07-03T12:41:51.136Z</atom:updated>
            <content:encoded><![CDATA[<h3>Martin Fowler — What does Tech Excellence Look Like?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FAvs70dZ3Vlk%3Fstart%3D1142%26feature%3Doembed%26start%3D1142&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DAvs70dZ3Vlk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FAvs70dZ3Vlk%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/aca14084d2622f227ffb499cc243c740/href">https://medium.com/media/aca14084d2622f227ffb499cc243c740/href</a></iframe><blockquote>11:14 That’s the reason that we want to do fast cycle time. It’s because we want this early information. We want the ability to scratch the first number off and see if we are on the right path or not. It’s actually worth paying more money than we would instinctively think to get that degree of information. That is why we want a highly efficient and technical organization. What a good technical organization looks like from the outside — it’s an organization that can give you rapid cycle time. It allows you to take ideas, quickly put them into production, see whether they are working and then be able to pursue, switch or do the rest of it.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8281aa72bf8d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/transcripts/martin-fowler-what-does-tech-excellence-look-like-8281aa72bf8d">Martin Fowler — What does Tech Excellence Look Like?</a> was originally published in <a href="https://medium.com/transcripts">Transcripts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Martin Fowler — Agile Essence and Fluency]]></title>
            <link>https://medium.com/transcripts/martin-fowler-agile-essence-and-fluency-905c36069bfc?source=rss-de10ddde9ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/905c36069bfc</guid>
            <category><![CDATA[martin-fowler]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Joel Lim]]></dc:creator>
            <pubDate>Sat, 03 Jul 2021 12:34:31 GMT</pubDate>
            <atom:updated>2021-07-03T12:34:31.675Z</atom:updated>
            <content:encoded><![CDATA[<h3>Martin Fowler — Agile Essence and Fluency</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FURlnxbaHhTs%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DURlnxbaHhTs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FURlnxbaHhTs%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/52784ce01c6c82be317686f588efdfb7/href">https://medium.com/media/52784ce01c6c82be317686f588efdfb7/href</a></iframe><blockquote>“A late change in requirements is a competitive advantage”</blockquote><blockquote>- Mary Poppendick</blockquote><blockquote>10:00</blockquote><blockquote>You see more sophisticated agile teams focusing a lot on things like cycle time — we are able to change things very fast. Of course this makes success a lot more complicated to measure. Success is no longer going according to plan because the plan changes every week. How can you base success on that? Instead you have to base success on things like business value and are we actually improving, .. are we more efficient as a whole …. It is the responsibility of everybody involved in the organization. It’s hard to point fingers around … It’s still true, if you measure success based on on time and on budget you’re missing the key point of what agile is about.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=905c36069bfc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/transcripts/martin-fowler-agile-essence-and-fluency-905c36069bfc">Martin Fowler — Agile Essence and Fluency</a> was originally published in <a href="https://medium.com/transcripts">Transcripts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>