<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Sushant Kulkarni</title>
    <description>The latest articles on Forem by Sushant Kulkarni (@sushantkulkarni).</description>
    <link>https://forem.com/sushantkulkarni</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F432802%2F03d42cf8-06d7-4b0e-bde4-70964a6219c7.jpeg</url>
      <title>Forem: Sushant Kulkarni</title>
      <link>https://forem.com/sushantkulkarni</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/sushantkulkarni"/>
    <language>en</language>
    <item>
      <title>Tmux - less windows, more ⚒</title>
      <dc:creator>Sushant Kulkarni</dc:creator>
      <pubDate>Wed, 07 Jan 2026 05:49:33 +0000</pubDate>
      <link>https://forem.com/sushantkulkarni/tmux-less-windows-more-5bhf</link>
      <guid>https://forem.com/sushantkulkarni/tmux-less-windows-more-5bhf</guid>
      <description>&lt;p&gt;I love terminal, being a windows user I use #wsl for more than 3 years now. I tried lots of terminal emulators to name few cmder, fluid but world is not perfect after all.&lt;/p&gt;

&lt;p&gt;I have a really perfect setup using zsh and ohmyzsh! with some useful plugins, customised theme and harnessed aliases over the time. &lt;/p&gt;

&lt;p&gt;Now, coming back to topic, with a tabless #wsl terminal I was always in clutter to manage lots of windows. I was looking for a minimal solution which would blend in my existing setup. Tmux, it's no brainer pane management. All I have to do is remember less than 10 shortcuts and it helped me reduce the terminal window count from 10 to 3&lt;/p&gt;

</description>
      <category>cli</category>
      <category>linux</category>
      <category>productivity</category>
      <category>tooling</category>
    </item>
    <item>
      <title>Warp Rust Clean Architecture Boilerplate</title>
      <dc:creator>Sushant Kulkarni</dc:creator>
      <pubDate>Mon, 05 Jan 2026 20:10:43 +0000</pubDate>
      <link>https://forem.com/sushantkulkarni/warp-rust-clean-architecture-boilerplate-jl</link>
      <guid>https://forem.com/sushantkulkarni/warp-rust-clean-architecture-boilerplate-jl</guid>
      <description>&lt;p&gt;A modular, production-ready Rust monorepo implementing Clean Architecture with a fully structured workspace. Modular Rust backend suitable for microservices&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/sushant-at-nitor/warp-microservice" rel="noopener noreferrer"&gt;https://github.com/sushant-at-nitor/warp-microservice&lt;/a&gt;&lt;/p&gt;

</description>
      <category>rust</category>
      <category>cleancode</category>
      <category>cqrs</category>
      <category>backend</category>
    </item>
    <item>
      <title>#microfrontends - top down or bottom ups</title>
      <dc:creator>Sushant Kulkarni</dc:creator>
      <pubDate>Fri, 22 Jul 2022 18:05:31 +0000</pubDate>
      <link>https://forem.com/sushantkulkarni/microfrontends-top-down-or-bottom-ups-47do</link>
      <guid>https://forem.com/sushantkulkarni/microfrontends-top-down-or-bottom-ups-47do</guid>
      <description>&lt;p&gt;Maybe, I would like to open this up with a Question. &lt;/p&gt;

&lt;p&gt;If you have to implement #microfrontend how would you do it? Top-down or bottom ups? Confused? The very well known and proud #Webpack module federation is more focused on the bottoms-up approach, you are forced(?) to create some set of components and then plug those into a root application, which sounds very obvious. In my honest opinion, this approach is there in any frontend framework and library nowadays, nothing new! Even in the bit.dev it is advised to create your application as a composition of loosely coupled components. But, if I am intended to serve this as a fully functional web application I need a sophisticated way to present these components as a functional and complete application&lt;/p&gt;

&lt;p&gt;I would rather prefer an approach that you can loosely correlate with imperative and functional programming. I would prefer to keep my use-cases at the Center (Centre, long live the Queen) to methodologically implement my frontend. The framework should support easy plumbing of my components and needlessly to say deal with the complexity of moving my frontend between the unavoidable transitions of the browser. I may sound like I have made up my mind on a specific framework/library, indeed yes, but I have my own reasons for that and I would like to cover those in subsequent posts. Let's keep it slow and steady to help you digest and create some momentum for this series&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>frontend</category>
      <category>microfrontend</category>
    </item>
    <item>
      <title>Micro frontend - update</title>
      <dc:creator>Sushant Kulkarni</dc:creator>
      <pubDate>Fri, 22 Jul 2022 15:39:42 +0000</pubDate>
      <link>https://forem.com/sushantkulkarni/micro-frontend-update-1l6o</link>
      <guid>https://forem.com/sushantkulkarni/micro-frontend-update-1l6o</guid>
      <description>&lt;p&gt;Hello, there&lt;/p&gt;

&lt;p&gt;Again, I missed on my promise.. Sorry for that. We have exciting things coming, trust me on this. I am deep into implementation and feaguring out how I could take this to you guys. We are making amazing progress on #microfrontends;and could not wait to take it to you. I am promising article dropping this Monday, please watch out. Thank you for the patience &lt;/p&gt;

</description>
    </item>
    <item>
      <title>Microfrontends - Primer</title>
      <dc:creator>Sushant Kulkarni</dc:creator>
      <pubDate>Mon, 20 Jun 2022 02:04:55 +0000</pubDate>
      <link>https://forem.com/sushantkulkarni/microfrontends-primer-4n3h</link>
      <guid>https://forem.com/sushantkulkarni/microfrontends-primer-4n3h</guid>
      <description>&lt;p&gt;We all know what microservices did to the backend. We must admit, even though we do not fully implement the #microservices in its purest form, we are habitual to it; the buzz word, may be started thinking in the direction of writing more modular backends, clean code, separation of domains and more importantly the individual deployment and scaling of domain specific services.&lt;/p&gt;

&lt;p&gt;I agree the change and the adoption is gradual, it will allow everyone to learn, adopt and implement keeping the lights on 💡&lt;/p&gt;

&lt;p&gt;The same concept is picking up very rapidly for the frontend. I wanted to use this primer to set the stage for #microfrontends. I have been evaluating, assessing and implementing few methodologies, frameworks and libraries to do clean and not too much of #opinionated implementation of micro frontend&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>microservices</category>
      <category>react</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
