tyurok
Joined 11 years ago
Joined 11 years ago
After some years working, it's clear it's useful in some capacity but it's easy to overdo it (like require every detail of the system to be in those formats) or misuse it (sequence diagram improperly documenting async flows).
Inheritance x composition is orthogonal to OO.
Don't get too attached to market/industry defined roles.
Another way to raise rates is to take risks (like deadlines, promises) but every person had their own risk profile.
It covers a little bit of the MindGeek story but primarily how pornhub rebuilt the industry.
[0]: http://www.jonronson.com/butterfly.html
[1]: https://www.amazon.com/The-Last-Days-of-August-audiobook/dp/...
I can't tolerate OOP stuff that `obj1.calls(obj2)` and changes `obj2` anymore. I didn't care before, now it makes me want to refactor everything or not write it at all.
Using Elixir kind of made me not want to use anything else.
The further you steer dev environments from production, the more you'll have these kinds of issues.
Would you mind expanding on their explanation? The way you described doesn't sound like an argument at all.