2 ms·

> Not sure he’s a great writer, but there was a lot to be learned there. Would you broadcast here some of the main points he made? Like what's the roots of the

by snaky 8y ago

> Not sure he’s a great writer, but there was a lot to be learned there. Would you broadcast here some of the main points he made? Like what's the roots of the all that were.

bertil 8y ago
Honestly, nothing original, just the sheer amount of it was impressive: - technical debt “so high you could open a central bank” was my favourite quote: he gave implementation details, but it’s hard enough to grasp a working schema, a broken one is just confusing: no indices, bottlenecks everywhere, no monitoring… It was less the individual set-up than the successive obviously inappropriate solutions. Not “queries to this table are slow, let’s factor it, but without checking the query pattern”-bad, more “like let’s host it on a third party service, with incompatible technology, located on a different continent, and edit it 100 times more often” bad. - every executive decision was going the opposite direction of what anyone could possibly want; so much so that my concerns over usability felt like complaining about the shade of paint after a bomb went off; - lack of maturity of the team came up a lot; also how arrogant and absent the managers were; he mentioned someone in particular that had completely different architectural ideas every time you saw him. That particular rant has serious racist undertones. - the product was split in two, or a company was acquired, and they kept the worst code to impose it on others, or only work on the corporate offering… Honestly, I don’t know. It just felt unredeemable. I asked if I should actively try to work with people who had gone through this because of how much they learned or avoid anyone because they sounded not very self-aware. He clearly advertised for the later. He even said that he edited his own CV to hide that he was ever there. Last time I checked, he’s got a really vague “project at Microsoft as a contractor” there.

by snaky 8y ago

> Not sure he’s a great writer, but there was a lot to be learned there. Would you broadcast here some of the main points he made? Like what's the roots of the all that were.

bertil 8y ago

Honestly, nothing original, just the sheer amount of it was impressive: - technical debt “so high you could open a central bank” was my favourite quote: he gave implementation details, but it’s hard enough to grasp a working schema, a broken one is just confusing: no indices, bottlenecks everywhere, no monitoring… It was less the individual set-up than the successive obviously inappropriate solutions. Not “queries to this table are slow, let’s factor it, but without checking the query pattern”-bad, more “like let’s host it on a third party service, with incompatible technology, located on a different continent, and edit it 100 times more often” bad. - every executive decision was going the opposite direction of what anyone could possibly want; so much so that my concerns over usability felt like complaining about the shade of paint after a bomb went off; - lack of maturity of the team came up a lot; also how arrogant and absent the managers were; he mentioned someone in particular that had completely different architectural ideas every time you saw him. That particular rant has serious racist undertones. - the product was split in two, or a company was acquired, and they kept the worst code to impose it on others, or only work on the corporate offering… Honestly, I don’t know. It just felt unredeemable. I asked if I should actively try to work with people who had gone through this because of how much they learned or avoid anyone because they sounded not very self-aware. He clearly advertised for the later. He even said that he edited his own CV to hide that he was ever there. Last time I checked, he’s got a really vague “project at Microsoft as a contractor” there.