prsimp

> when someone comes up with excuses for not making something open source

This is a wild take even coming from HN. Nobody needs an excuse to not make something open source.

This sort of entitlement does, and has done, far more damage to the OSS movement than anyone's "excuses" for not open sourcing their code. Full stop.

You can absolutely prefer open source software and choose not to trust closed-source apps. That’s all fair. But treating closed source itself as evidence of deception or impending betrayal is exactly the kind of ideological purity test that makes these conversations exhausting.

In my experience, there is a thin line between "blameless" cultures and "responsibility-less" cultures. Blameless cultures accept that we are all human, make mistakes, have off periods, etc. "Responsibility-less" cultures are as you describe -- they eschew honest conversations about the actual forces that affect projects. Instead they tend to repeat the same process discussions ad nauseum, typically discussing symptoms rather than the actual causes.

Since we as humans often prefer to avoid conflict (sometimes at all costs), it's not uncommon to see companies tilt towards the latter. This is exacerbated in "scale up" environments when rapid personnel changes make it difficult to build the kind of trust necessary for direct, honest communication.

> One sort of answer would be how people are convinced that their data is not important.

When I'm wandering through my yard watering plants, I like to imagine a world where our personal data, or more precisely access to it, is treated more like mineral rights today.

Companies would be required to pay a small micro-payment royalty anytime your data was used to make them money, and you would be able to transfer/split the rights just as you could mineral rights today. This micro-payment world would supplant the current "your data is the price of admission" world we live in.

In all fairness, it makes it pretty tough to take your comment seriously when you consistently refer to Rails when you mean Ruby.

Also, I have to disagree. Like the author of the post, I found Olsen's book to be a delightful read. It is certainly not a great "first book" on Ruby, however. I think you ought to read it once you've gained a little better understanding - its wonderful for smoothing out edges and cementing some of the more advanced concepts.

Snide comments aside, I think you're missing a lot of value in slides 26 through 34, the section on communication. Reducing the 'spin-up' time for new employees and documenting even the one-off conversations seems like a great way to increase productivity.

I sleep ~4 hours a night during the week. I find that if I sleep more (~6-8), I am not tired again by the time the remaining hours have passed and it is time for me to sleep again. For instance, when I sleep 6 hours, I am not ready to sleep again 18 hours later. This becomes a real problem after two nights or so, at which point I have a lot of trouble falling asleep.

I do tend to sleep more on the weekends, but I often end up essentially forcing myself to sleep come Sunday night.

I read this more as being about creating jobs than making money for one's self.