Using the 5S Principle in Coding • Hacker News Board

Re: Using the 5S Principle in Coding

#51

Post by jimbokun » Thu, Jul 11, 2024, 3:10 PM UTC

pphysch wrote: post #14

codelikeawolf wrote: post #8

When I used to work in manufacturing, my company was super 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 "Shove Stupid Shit Someplace Secret". In my experience, that wasn't an entirely inaccurate interpretation. Joking aside, I think this article does a decent job of translating Lean manufacturing principles to co…

> "Shove Stupid Shit Someplace Secret" This sums up the broad concept of Compliance and security in general. The people who pretend to care about compliance (i.e. management) don't have the technical know-how to grok the implementations by those who pretend to implement said compliant systems. There isn't remotely enough QA/red-teaming (expensive to do in a bias-free manner), most of the time all you need to do is sc…

I work on software for the healthcare industry, and recently found out about PHI (private health information) insurance. Basically they pay out if you suffer a breach,

The part I found interesting is that the premiums vary based on their assessment of your practices. This strongly aligns their incentives with actual best practices when evaluating your systems, as they are on the hook financially for any breach.

Re: Using the 5S Principle in Coding

#52

Post by anonymoushn » Thu, Jul 11, 2024, 4:41 PM UTC

vmurthy wrote: post #45

bruce511 wrote: post #41

Earlier quoted context omitted.

Every time I get involved in a project it seems to start with this neatly organised tree where everything is squirreled away. By contrast my own systems are often just one giant folder. Conceptually I'm just not bothered by large directories with 20000 files. And I'm happy to mix files of different types in one folder (OMG .c files and .ico files in the same folder like a barbarian!!!) I find the system is simple, an…

It maybe that this works for you individually, but does it work well as part of a team? I think it's one of those cases where one needs to do what is convenient for most of the team rather than one member?

Are there people for whom it works better to have nearly as many folders as files?

Re: Using the 5S Principle in Coding

#53

Post by 01HNNWZ0MV43FF » Thu, Jul 11, 2024, 11:31 PM UTC

ajaymenon0 wrote: post #47

01HNNWZ0MV43FF wrote: post #44

`/organisms/` What?

https://atomicdesign.bradfrost.com/images/content/atomic-des...

Hm. Hard to add middle layers to that unless you have e.g. tissues, organs.

I propose going back to line numbers. Start with 1000, 2000, 3000. Sub-divide as needed.

Re: Using the 5S Principle in Coding

#54

Post by ajaymenon0 » Fri, Jul 12, 2024, 8:57 AM UTC

cglace wrote: post #49

01HNNWZ0MV43FF wrote: post #44

`/organisms/` What?

Yeah, I've encountered people who insisted on using this structure. I was not too fond of it.

Honestly it's just a nomenclature or convention to define hierarchies. I've had certain projects where it was useful to get teams aligned on how to view a particular project. That being said, sometimes it's also heralded as something super life changing, which it isn't.

Re: Using the 5S Principle in Coding

#55

Post by hgyjnbdet » Fri, Jul 12, 2024, 8:59 AM UTC

buttercraft wrote: post #46

BurningFrog wrote: post #20

Earlier quoted context omitted.

In general, problems are much easier to solve when you have them, than when you try to guess what they will be.

This is a good generalization but I worry that it's too broad. I.e. if your lifeboat is sinking, it's too late to find a better lifeboat.

But at that point your problem isn't needing a better lifeboat, the problem is why it's sinking. At this point solving the problem of why it's sinking is the problem you've got, solving it before you had that problem seems silly.