<story><title>Using the 5S Principle in Coding</title><url>https://santhoshsundar.medium.com/using-the-5s-principle-in-coding-6237a1614a02</url></story><parent_chain></parent_chain><comment><author>codelikeawolf</author><text>When I used to work in manufacturing, my company was &lt;i&gt;super&lt;/i&gt; into Lean. I even ended up getting an ASQ Six Sigma Green Belt certification. My favorite thing to say to people when they asked what 5S stood for was &amp;quot;Shove Stupid Shit Someplace Secret&amp;quot;. In my experience, that wasn&amp;#x27;t an entirely inaccurate interpretation.&lt;p&gt;Joking aside, I think this article does a decent job of translating Lean manufacturing principles to coding, but the &amp;quot;Set in Order&amp;quot; section grinds my gears a little bit. I have worked on many projects of various sizes, and I think my fellow web devs tend to lean too hard into an overly nested directory structure. In manufacturing terms, imagine if you needed to open a cabinet that contains a toolbox with a plastic organizer in one of the drawers that contains a box that you had to open to get access to some rivets. It doesn&amp;#x27;t take much for that level of organization to kneecap efficiency. I would much rather have a single directory with 20 files than try to chase down a component file that&amp;#x27;s eight directories deep. Give me a big list of long descriptive file names, not short names that rely on the directory name to give context.</text></comment>
<story><title>Using the 5S Principle in Coding</title><url>https://santhoshsundar.medium.com/using-the-5s-principle-in-coding-6237a1614a02</url></story><parent_chain></parent_chain><comment><author>smithbits</author><text>It&amp;#x27;s worth keeping in mind that lean manufacturing and all the interesting things that Toyota did that get written up are about building cars.  In software the equivalent process is compiling and deploying code.  Writing software is equivalent to designing, prototyping and testing a car.  So while there are many interesting lessons to learn they are about the deployment and running of code, not about writing it.  In the mass manufactured automobile industry you spend more time and effort building the product than designing it.  In software you spend much more time designing (specs, coding, testing, all that stuff) the product than deploying it.  The lessons of lean manufacturing may not apply to design.</text></comment>