On: Talks that changed the way I think about programmi...

[stock_toaster]

The following talk about event sourcing (not listed in the article)•, really made an impact on me:

Event Sourcing - Greg Young

https://www.youtube.com/watch?v=JHGkaShoyNs

•: Not that I really expected it to be I guess.

[JOURNEYSA → stock_toaster]

Overly complicated pointless eventsourcing wasted 1mil+ at my previous employer. Now they have to spend 6 months removing it all.

[SanderMak → JOURNEYSA]

Care to elaborate? We're having quite good experiences with it at the moment, but would like to learn from others.

[JOURNEYSA → SanderMak]

We used this mess of a library, which provides no clear interface and corrupts data https://github.com/johnbywater/eventsourcing

[maxaf → JOURNEYSA]

A faulty implementation doesn't necessarily invalidate the idea. I also strongly suggest looking into statically typed languages. Python is very poorly suited to working with data.

[kbutler → maxaf]

> Python is very poorly suited to working with data.

This does not seem to be true, based on widespread industry and scientific use of Python generating, managing, and analyzing data.

Perhaps you meant in some specific way, like "Python does not enforce objects' data schema" or some such?

[strictfp → maxaf]

Yes, but even so it's a huge undertaking to build your own event sourcing. Many get burnt.

[jasonm23 → JOURNEYSA]

I'll go out on a limb here and say it wasn't Event Sourcing that caused the problems.

Anything can be ^H^H^H^Hmessed up.