<?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 Yassir Acaf on Medium]]></title>
        <description><![CDATA[Stories by Yassir Acaf on Medium]]></description>
        <link>https://medium.com/@yassir.acaf?source=rss-9e738d664ed7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hcAgiXtDWEgJSyXLL_9pqQ.jpeg</url>
            <title>Stories by Yassir Acaf on Medium</title>
            <link>https://medium.com/@yassir.acaf?source=rss-9e738d664ed7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:00:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yassir.acaf/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[Decorating Objects in Java: From Wrapper Classes to Lambdas]]></title>
            <link>https://medium.com/@yassir.acaf/decorating-objects-in-java-from-wrapper-classes-to-lambdas-e71506ef84ea?source=rss-9e738d664ed7------2</link>
            <guid isPermaLink="false">https://medium.com/p/e71506ef84ea</guid>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[java]]></category>
            <dc:creator><![CDATA[Yassir Acaf]]></dc:creator>
            <pubDate>Tue, 20 Oct 2026 08:07:28 GMT</pubDate>
            <atom:updated>2026-10-20T08:07:28.273Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Hello everyone, new day new things to share with you guys 😎.</blockquote><p>Today, I want to revisit one of the oldest design patterns out there: the <strong>Decorator</strong>. Rather than repeating the textbook definition, I’d like to show how Java 8 lambdas completely change the way we write it.</p><p>For that purpose we are going to build a small <strong>camera with pluggable filters</strong>.</p><p>The Decorator pattern lets you add behavior to an object at runtime by wrapping it, following three simple rules:</p><ul><li>The wrapper exposes the same interface as the object it wraps.</li><li>It delegates to the wrapped object, then adds its own behavior.</li><li>Wrappers can be stacked as many times as you want.</li></ul><p>If you are wondering what its real usage would be, you already use it every day: new BufferedReader(new InputStreamReader(new FileInputStream(file))) is a stack of decorators from java.io. Think also of a photo app where the user stacks filters (brighter, darker, sepia…) on a picture: each filter decorates the previous one.</p><p>Okay now that we know what we are going to build, let’s move to implementation.</p><h3>The classic way : wrapper classes</h3><p>Before touching lambdas, let’s see how the Gang of Four book (1994) would write our camera filters:</p><pre>public interface Filter {<br>    Color apply(Color color);<br>}</pre><pre>public class NoFilter implements Filter {<br>    @Override<br>    public Color apply(Color color) {<br>        return color;<br>    }<br>}<br>public abstract class FilterDecorator implements Filter {<br>    protected final Filter wrapped;<br>    protected FilterDecorator(Filter wrapped) {<br>        this.wrapped = wrapped;<br>    }<br>}<br>public class BrighterFilter extends FilterDecorator {<br>    public BrighterFilter(Filter wrapped) {<br>        super(wrapped);<br>    }<br>    @Override<br>    public Color apply(Color color) {<br>        return wrapped.apply(color).brighter();<br>    }<br>}<br>public class DarkerFilter extends FilterDecorator {<br>    public DarkerFilter(Filter wrapped) {<br>        super(wrapped);<br>    }<br>    @Override<br>    public Color apply(Color color) {<br>        return wrapped.apply(color).darker();<br>    }<br>}</pre><p>And the usage:</p><pre>Filter filter = new DarkerFilter(new BrighterFilter(new NoFilter()));<br>Color result = filter.apply(new Color(200, 100, 200));</pre><p>The Filter interface is the contract shared by everyone. NoFilter is the base object that returns the color untouched. FilterDecorator is an abstract class whose only job is to hold a reference to the wrapped filter, and each concrete decorator calls the wrapped filter first, then adds its own step.</p><p>It works, but look at what we wrote: five types to chain two filters. Every new filter means a new class, and the usage line has to be read inside-out to understand the execution order.</p><p>Now look closely at the Filter interface: one method, takes a Color, returns a Color. Does that ring a bell? 🤔</p><h3>A bit of theory : functions are decorators</h3><p>Before diving into the lambda version, let’s understand three tools Java 8 gives us.</p><p><strong>Functional interfaces.</strong> Any interface with a single abstract method can be implemented by a lambda. The JDK already ships a bunch of them in java.util.function, and the one we need is Function&lt;T, R&gt;: takes a T, returns an R. Our whole Filter interface is just Function&lt;Color, Color&gt;.</p><p><strong>Method references.</strong> Color::brighter is a shortcut for color -&gt; color.brighter(). Since brighter() is an instance method that takes no argument and returns a Color, the compiler can turn it into a Function&lt;Color, Color&gt; for us. Same for Color::darker. No more BrighterFilter and DarkerFilter classes.</p><p><strong>Composition.</strong> Function comes with default methods that do exactly what our decorator classes were doing:</p><ul><li>f.andThen(g) returns a new function that applies f, then feeds the result to g.</li><li>f.compose(g) does the opposite: g first, then f.</li><li>Function.identity() returns its input untouched. That&#39;s our NoFilter.</li></ul><p>So andThen is the wrapping mechanism. Every call returns a new function wrapping the previous one, exactly like new DarkerFilter(new BrighterFilter(...)), but read left to right:</p><pre>Function&lt;Color, Color&gt; filter = Function.&lt;Color&gt;identity()<br>        .andThen(Color::brighter)<br>        .andThen(Color::darker);</pre><p>I hope these concepts are clear now, let’s move to the implementation of our camera.</p><h3>Using lambdas :</h3><pre>public class Camera {<br>    private Function&lt;Color, Color&gt; filter = Function.identity();</pre><pre>public Color capture(final Color inputColor) {<br>        return filter.apply(inputColor);<br>    }<br>    public void appendFilters(final Function&lt;Color, Color&gt;... filters) {<br>        filter =<br>                Stream.of(filters)<br>                        .reduce((filter, next) -&gt; filter.andThen(next))<br>                        .orElseGet(Function::identity);<br>    }<br>}</pre><p>The implementation is fairly short. The whole decorator chain lives in a single field, filter, initialized with Function.identity() so that a camera without any filter captures the true color.</p><p>The capture() method simply applies the current chain to the input color. It doesn&#39;t know, and doesn&#39;t care, how many filters are stacked behind that one function.</p><p>The appendFilters() method is where the magic happens. It takes any number of filters and folds them into one function with reduce: given [f1, f2, f3], it builds f1.andThen(f2).andThen(f3), each step wrapping the previous one. Since reduce without an initial value returns an Optional (empty when no filter is passed), we fall back to identity with orElseGet.</p><p>I created a simple demo to test this:</p><pre>public static void main(String[] args) {<br>    final Camera camera = new Camera();</pre><pre>final Consumer&lt;String&gt; printCaptured = filterInfo -&gt;<br>            System.out.println(String.format(&quot;with %s: %s&quot;,<br>                    filterInfo, camera.capture(new Color(200, 100, 200))));<br>    printCaptured.accept(&quot;no filter&quot;);<br>    camera.appendFilters(Color::brighter);<br>    printCaptured.accept(&quot;brighter filter&quot;);<br>    camera.appendFilters(Color::brighter, Color::darker);<br>    printCaptured.accept(&quot;brighter &amp; darker filter&quot;);<br>}</pre><p>Output :</p><pre>with no filter: java.awt.Color[r=200,g=100,b=200]<br>with brighter filter: java.awt.Color[r=255,g=142,b=255]<br>with brighter &amp; darker filter: java.awt.Color[r=178,g=99,b=178]</pre><p>Yoo hooo, it’s working. We changed the camera’s behavior at runtime without writing a single new class.</p><p>But wait a minute… look at that last line again. If brighter and darker cancel each other out, why don’t we get (200, 100, 200) back? 👀</p><h3>The traps hiding in twelve lines :</h3><p>The code compiles and runs, yet there are four things worth knowing before you copy-paste it into production.</p><h3>1. appendFilters doesn’t append</h3><p>Each call rebuilds filter from scratch, so the previous chain is simply thrown away. That&#39;s why our third capture ran <em>brighter → darker</em> on the original color, and not <em>brighter → brighter → darker</em>. A method name that lies is the most expensive bug in an API, so either rename it setFilters, or really chain onto the existing function (we&#39;ll fix that in a minute).</p><h3>2. Decorators are not always reversible</h3><p>Here is the answer to our mystery. brighter() divides each channel by 0.7 and darker() multiplies it by 0.7, but both truncate to int, and brighter caps every channel at 255. Let&#39;s follow the red channel:</p><ul><li>200 / 0.7 = 285, capped to <strong>255</strong></li><li>255 × 0.7 = 178.5, truncated to <strong>178</strong></li></ul><p>The information lost by the cap never comes back. In real life the same happens with rounding, compression or sanitizing: the order of your decorators matters, and lossy steps don’t undo each other.</p><h3>3. andThen vs compose flips the order</h3><p>With andThen, filters run in the order you pass them. Swap it for compose and the last filter runs first. Pick one and document it, because callers will naturally assume left to right.</p><h3>4. Generic varargs trigger a warning</h3><p>Function&lt;Color, Color&gt;... is a generic array under the hood, so the compiler warns you about <em>possible heap pollution</em>. Our method only reads the array, so it&#39;s safe, but the warning can only be silenced with @SafeVarargs, and that annotation is allowed only on static, final or private methods.</p><p>Small bonus: the lambda parameter filter shadows the field filter. It&#39;s legal Java, but naming it acc removes any doubt about which one you are reading.</p><h3>Fixing our Camera :</h3><pre>public class Camera {<br>    private Function&lt;Color, Color&gt; filter = Function.identity();<br></pre><pre>public Color capture(final Color inputColor) {<br>        return filter.apply(inputColor);<br>    }<br>    /** Replaces the whole chain. Filters run left to right. */<br>    @SafeVarargs<br>    public final void setFilters(final Function&lt;Color, Color&gt;... filters) {<br>        filter = Stream.of(filters).reduce(Function.identity(), Function::andThen);<br>    }<br>    /** Adds filters after the existing chain. */<br>    @SafeVarargs<br>    public final void appendFilters(final Function&lt;Color, Color&gt;... filters) {<br>        filter = Stream.of(filters).reduce(filter, Function::andThen);<br>    }<br>    public void clearFilters() {<br>        filter = Function.identity();<br>    }<br>}</pre><p>The trick is to give reduce an initial value. In setFilters() the seed is Function.identity(), the neutral element of composition (just like 0 for addition), so reduce never returns an empty result and the whole Optional / orElseGet dance disappears.</p><p>In appendFilters() the seed is the current filter itself, so new filters are chained after the existing ones instead of replacing them. Now the method finally does what its name says.</p><p>The accumulator Function::andThen is a method reference replacing our hand-written lambda, and the shadowing problem goes away with it. Finally, both varargs methods are final and annotated with @SafeVarargs, so the compiler warning is gone and no subclass can break that guarantee.</p><p>Running the same demo with appendFilters now prints java.awt.Color[r=178,g=141,b=178] on the last line: brighter, brighter, then darker, as expected.</p><p>If you prefer immutability, go one step further: make filter final and have a withFilters(...) method return a brand new Camera. Each camera then becomes a thread-safe value, which is a nice bonus if you read my article on concurrency 😉.</p><h3>Comparing both approaches :</h3><pre>+------------------------------+-----------------+-----------------------------------+<br>|                              | Wrapper classes | Lambdas                           |<br>+------------------------------+-----------------+-----------------------------------+<br>| Types to write for 2 filters | 5               | 0 (just Function&lt;Color, Color&gt;)   |<br>| Adding a new filter          | A new class     | A lambda or a method reference    |<br>| Reading the chain            | Inside-out      | Left to right                     |<br>| Decorating several methods   | Yes             | No, one method only               |<br>| Inspecting the chain later   | Possible        | No, a composed function is opaque |<br>+------------------------------+-----------------+-----------------------------------+</pre><h3>Decorating more than colors</h3><p>Any function can be decorated, not only filters of the same type. Here is a small logged decorator that adds logging around any Function, exactly like a GoF decorator class would:</p><pre>static &lt;T, R&gt; Function&lt;T, R&gt; logged(Function&lt;T, R&gt; fn) {<br>    return z -&gt; {<br>        R result = fn.apply(input);<br>        System.out.printf(&quot;%s -&gt; %s%n&quot;, input, result);<br>        return result;<br>    };<br>}</pre><pre>Function&lt;Integer, Integer&gt; square = logged(x -&gt; x * x);<br>square.apply(4); // prints: 4 -&gt; 16</pre><p>Retry, caching and timing wrappers follow the same shape, and libraries like Resilience4j expose their decorators this way (Decorators.ofSupplier(...)).</p><h3>When classes still win</h3><p>Lambdas are not a silver bullet. Stick to classes when the decorated type has <strong>several methods</strong> (InputStream has read, skip, close…), when the decorator carries <strong>state or configuration</strong> that deserves its own name and tests, or when you need to <strong>inspect the chain</strong> later, like listing or removing an active filter. For the last case, keep a List&lt;Function&lt;Color, Color&gt;&gt; and compose it on demand.</p><h3>Wrapping Up</h3><p>And that’s a wrap for today. We went from the classic Gang of Four decorator, with its interface, abstract class and one class per behavior, to a version where the whole pattern fits in Function.identity(), andThen and a reduce.</p><p>The takeaway? Lambdas remove the boilerplate, but not the responsibilities. Name your methods for what they really do, document the execution order, and remember that composing lossy steps is not reversible. Get those right, and a five-class pattern becomes a five-line method.</p><p>That’s all for this episode. Until the next one, happy coding! 👋</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e71506ef84ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why BigDecimal in java is the solution for handling precise decimal arithmetic]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@yassir.acaf/why-bigdecimal-in-java-is-the-solution-for-handling-precise-decimal-arithmetic-466aa07c3edb?source=rss-9e738d664ed7------2"><img src="https://cdn-images-1.medium.com/max/2323/1*QlbKfAaGU97ftqjINY5bEg.png" width="2323"></a></p><p class="medium-feed-snippet">Hello everyone, new day new things to share with you guys &#x1F60E;.</p><p class="medium-feed-link"><a href="https://medium.com/@yassir.acaf/why-bigdecimal-in-java-is-the-solution-for-handling-precise-decimal-arithmetic-466aa07c3edb?source=rss-9e738d664ed7------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@yassir.acaf/why-bigdecimal-in-java-is-the-solution-for-handling-precise-decimal-arithmetic-466aa07c3edb?source=rss-9e738d664ed7------2</link>
            <guid isPermaLink="false">https://medium.com/p/466aa07c3edb</guid>
            <category><![CDATA[basics-of-programming]]></category>
            <category><![CDATA[java]]></category>
            <dc:creator><![CDATA[Yassir Acaf]]></dc:creator>
            <pubDate>Mon, 05 Oct 2026 10:59:42 GMT</pubDate>
            <atom:updated>2026-10-05T10:59:42.153Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Building a One-Shot Latch in Java: From wait/notify to AbstractQueuedSynchronizer]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@yassir.acaf/building-a-one-shot-latch-in-java-from-wait-notify-to-abstractqueuedsynchronizer-814099fafa9e?source=rss-9e738d664ed7------2"><img src="https://cdn-images-1.medium.com/max/608/1*m7Zb8uGUK4A_Oy70so7rig.png" width="608"></a></p><p class="medium-feed-snippet">Hello everyone, new day new things to share with you guys &#x1F60E;.</p><p class="medium-feed-link"><a href="https://medium.com/@yassir.acaf/building-a-one-shot-latch-in-java-from-wait-notify-to-abstractqueuedsynchronizer-814099fafa9e?source=rss-9e738d664ed7------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@yassir.acaf/building-a-one-shot-latch-in-java-from-wait-notify-to-abstractqueuedsynchronizer-814099fafa9e?source=rss-9e738d664ed7------2</link>
            <guid isPermaLink="false">https://medium.com/p/814099fafa9e</guid>
            <category><![CDATA[concurrency]]></category>
            <category><![CDATA[java]]></category>
            <dc:creator><![CDATA[Yassir Acaf]]></dc:creator>
            <pubDate>Sun, 09 Aug 2026 18:22:11 GMT</pubDate>
            <atom:updated>2026-08-09T18:22:11.655Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[A different approach to load your data in you spring boot app using Hibernate Filters]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@yassir.acaf/a-different-approach-to-load-your-data-in-you-spring-boot-app-using-hibernate-filters-da0ac6e09df2?source=rss-9e738d664ed7------2"><img src="https://cdn-images-1.medium.com/max/1920/1*IgvOKcW0SUJSEX9infOdFw.jpeg" width="1920"></a></p><p class="medium-feed-snippet">Hello everyone, new day new things to share with you guys &#x1F60E;.</p><p class="medium-feed-link"><a href="https://medium.com/@yassir.acaf/a-different-approach-to-load-your-data-in-you-spring-boot-app-using-hibernate-filters-da0ac6e09df2?source=rss-9e738d664ed7------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@yassir.acaf/a-different-approach-to-load-your-data-in-you-spring-boot-app-using-hibernate-filters-da0ac6e09df2?source=rss-9e738d664ed7------2</link>
            <guid isPermaLink="false">https://medium.com/p/da0ac6e09df2</guid>
            <category><![CDATA[java]]></category>
            <category><![CDATA[spring-boot]]></category>
            <category><![CDATA[hibernate]]></category>
            <category><![CDATA[jpa]]></category>
            <dc:creator><![CDATA[Yassir Acaf]]></dc:creator>
            <pubDate>Sat, 18 Jan 2025 17:27:04 GMT</pubDate>
            <atom:updated>2025-01-18T17:27:04.966Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Mastering the Java Date API: Date, Calendar, GregorianCalendar, LocalDateTime, and much more… (…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@yassir.acaf/mastering-the-java-date-api-date-calendar-gregoriancalendar-localdatetime-and-much-more-a50ba8bcf9e7?source=rss-9e738d664ed7------2"><img src="https://cdn-images-1.medium.com/max/1920/1*3h5dGP-SPuP_FnppwqS7yg.png" width="1920"></a></p><p class="medium-feed-snippet">Hello everyone, new day new things to share with you guys &#x1F60E;.</p><p class="medium-feed-link"><a href="https://medium.com/@yassir.acaf/mastering-the-java-date-api-date-calendar-gregoriancalendar-localdatetime-and-much-more-a50ba8bcf9e7?source=rss-9e738d664ed7------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@yassir.acaf/mastering-the-java-date-api-date-calendar-gregoriancalendar-localdatetime-and-much-more-a50ba8bcf9e7?source=rss-9e738d664ed7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a50ba8bcf9e7</guid>
            <category><![CDATA[java8]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[java-training]]></category>
            <category><![CDATA[java-time]]></category>
            <dc:creator><![CDATA[Yassir Acaf]]></dc:creator>
            <pubDate>Sat, 11 Jan 2025 17:06:29 GMT</pubDate>
            <atom:updated>2025-01-11T17:06:29.112Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[A Deep Dive into TUF Framework and Notary]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://systemweakness.com/a-deep-dive-into-tuf-framework-and-notary-e848a325bc16?source=rss-9e738d664ed7------2"><img src="https://cdn-images-1.medium.com/max/1332/1*VDMWuMh6fmiM3R1NZmJOiA.png" width="1332"></a></p><p class="medium-feed-snippet">Hello everyone, new day new things to share with you guys &#x1F60E;.</p><p class="medium-feed-link"><a href="https://systemweakness.com/a-deep-dive-into-tuf-framework-and-notary-e848a325bc16?source=rss-9e738d664ed7------2">Continue reading on System Weakness »</a></p></div>]]></description>
            <link>https://systemweakness.com/a-deep-dive-into-tuf-framework-and-notary-e848a325bc16?source=rss-9e738d664ed7------2</link>
            <guid isPermaLink="false">https://medium.com/p/e848a325bc16</guid>
            <category><![CDATA[docker-security]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[notary]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Yassir Acaf]]></dc:creator>
            <pubDate>Wed, 20 Nov 2024 20:36:15 GMT</pubDate>
            <atom:updated>2024-11-26T13:17:06.304Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How does Spring Security enhance the Chain of Responsibility pattern through its filters ?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://systemweakness.com/how-does-spring-security-enhance-the-chain-of-responsibility-pattern-through-its-filters-9ec8885c2fa3?source=rss-9e738d664ed7------2"><img src="https://cdn-images-1.medium.com/max/1920/1*uM2J5jZ4uFnLEWWQ0DItSg.jpeg" width="1920"></a></p><p class="medium-feed-snippet">Hello everyone, new day new things to share with you guys &#x1F60E;.</p><p class="medium-feed-link"><a href="https://systemweakness.com/how-does-spring-security-enhance-the-chain-of-responsibility-pattern-through-its-filters-9ec8885c2fa3?source=rss-9e738d664ed7------2">Continue reading on System Weakness »</a></p></div>]]></description>
            <link>https://systemweakness.com/how-does-spring-security-enhance-the-chain-of-responsibility-pattern-through-its-filters-9ec8885c2fa3?source=rss-9e738d664ed7------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ec8885c2fa3</guid>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[spring]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[chain-of-responsibility]]></category>
            <category><![CDATA[spring-security]]></category>
            <dc:creator><![CDATA[Yassir Acaf]]></dc:creator>
            <pubDate>Mon, 11 Nov 2024 19:22:24 GMT</pubDate>
            <atom:updated>2024-11-26T13:17:15.097Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Deep dive in password management in Spring Security]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@yassir.acaf/deep-dive-in-password-management-in-spring-security-f7b8658d09d2?source=rss-9e738d664ed7------2"><img src="https://cdn-images-1.medium.com/max/1920/1*Iv-ZPNYCtSAwsbbi5IvokA.png" width="1920"></a></p><p class="medium-feed-snippet">Hello everyone, new day new things to share with you guys &#x1F60E;.</p><p class="medium-feed-link"><a href="https://medium.com/@yassir.acaf/deep-dive-in-password-management-in-spring-security-f7b8658d09d2?source=rss-9e738d664ed7------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@yassir.acaf/deep-dive-in-password-management-in-spring-security-f7b8658d09d2?source=rss-9e738d664ed7------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7b8658d09d2</guid>
            <category><![CDATA[spring-training]]></category>
            <category><![CDATA[spring-framework]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[spring]]></category>
            <category><![CDATA[spring-security]]></category>
            <dc:creator><![CDATA[Yassir Acaf]]></dc:creator>
            <pubDate>Sat, 09 Nov 2024 11:39:35 GMT</pubDate>
            <atom:updated>2024-11-09T11:39:35.492Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Reverse engineer docker image : From Docker image to Dockerfile]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://systemweakness.com/reverse-engineer-docker-image-from-docker-image-to-dockerfile-fda08d32dcfb?source=rss-9e738d664ed7------2"><img src="https://cdn-images-1.medium.com/max/1920/1*YnPKPlfL1OqHLw3cnrLkHg.jpeg" width="1920"></a></p><p class="medium-feed-snippet">Hello everyone, new day new things to share with you guys &#x1F60E;.</p><p class="medium-feed-link"><a href="https://systemweakness.com/reverse-engineer-docker-image-from-docker-image-to-dockerfile-fda08d32dcfb?source=rss-9e738d664ed7------2">Continue reading on System Weakness »</a></p></div>]]></description>
            <link>https://systemweakness.com/reverse-engineer-docker-image-from-docker-image-to-dockerfile-fda08d32dcfb?source=rss-9e738d664ed7------2</link>
            <guid isPermaLink="false">https://medium.com/p/fda08d32dcfb</guid>
            <category><![CDATA[docker-compose]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[dockerfiles]]></category>
            <category><![CDATA[docker-image]]></category>
            <dc:creator><![CDATA[Yassir Acaf]]></dc:creator>
            <pubDate>Tue, 05 Nov 2024 14:17:10 GMT</pubDate>
            <atom:updated>2024-11-26T13:17:17.382Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Ultimate Guide to understanding networking in docker swarm]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@yassir.acaf/the-ultimate-guide-to-understanding-networking-in-docker-swarm-83d7bc3fecb5?source=rss-9e738d664ed7------2"><img src="https://cdn-images-1.medium.com/max/1920/1*6hwQbvAu81WVsSZ0at8VnQ.png" width="1920"></a></p><p class="medium-feed-snippet">Hello everyone, new day new things to share with you guys &#x1F60E;.</p><p class="medium-feed-link"><a href="https://medium.com/@yassir.acaf/the-ultimate-guide-to-understanding-networking-in-docker-swarm-83d7bc3fecb5?source=rss-9e738d664ed7------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@yassir.acaf/the-ultimate-guide-to-understanding-networking-in-docker-swarm-83d7bc3fecb5?source=rss-9e738d664ed7------2</link>
            <guid isPermaLink="false">https://medium.com/p/83d7bc3fecb5</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[docker-swarm]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Yassir Acaf]]></dc:creator>
            <pubDate>Sat, 05 Oct 2024 19:32:34 GMT</pubDate>
            <atom:updated>2024-10-05T19:32:34.100Z</atom:updated>
        </item>
    </channel>
</rss>