greydius

    while (alive) {
        hussle()
    }

    getCuteCat img = do
        cropped <- findCat img
        withTie <- addBowTie cropped
        withSparkles <- makeEyesSparkle withTie
        return (addRainbow (makeSmaller withSparkles))

It wasnt an option. I think, especially in larger organizations, that IT departments dont want to support yet another OS. My previous employer didnt even offer macs.

1) test suite - this shouldn't require explanation

2) documentation - both top level docs with examples and well-commented code. keep track of units

3) one-step build - I should be able to download the project, type 'make' (or something equivalent), and start using it

I could keep complaining, but I don't want to give people the impression that I don't like what I do. It beats the hell out of writing CRUD apps.

[1] https://ocw.mit.edu/courses/electrical-engineering-and-compu...

[2] https://ocw.mit.edu/courses/electrical-engineering-and-compu...

This is exactly how banks operate.

Classes that hold data have no methods (beyond getters/setters). Classes that implement behavior have no mutable state; they exist as namespaces for the functionality that they provide.

I've been quite successful with this approach. It leads to code that is easier to understand than a big ball of stateful objects.

That's a common western viewpoint. I wonder how the 'warring barbarian bands' felt about the 'cultural standardization'.