aaaaaa

re: builder pattern - At least in js I find it very difficult to write unit tests against. For instance in order to verify 'run()' is called, you need a mock which exposes the underlying builder and to make sure each method returns the instance of itself. You then need access to the instance such that if multiple instances exist that each can be asserted separately from each other. I've recently ran into this problem in knex - and prefer apis that allow you to configure them e.g. const myTrainedModel = buildMyModel({ train: true, withWeights: 'random', withOptimizer: 'SGD', run: true }),

I like how simple and pragmatic this solution is.

"[man spreading] can show swagger, confidence, and suggest dominance" - I normally come to SO to learn interesting tidbits. This brings me back to my worthless days of college, particularly a feminism course which decided stores shouldn't be allowed to sell pink clothing to baby girls and blue clothing to boys.

@DonThermidor_LobsterMobster - pretty obvious it's not a job where timely attendance affects the employee's output. The industry is irrelevant - the problem is the culture that being timely has an incorrectly perceived inherent value.

Some day parenting will be data-driven and the discussions here will be all moot. Until then, all these opinions and discussions would be good ones to have a drink over.

@Tim - I've found a great place for comments are next to regexes. The abstract of that is "next to any code which by design is hard to read".