News for hackers. Stuff that matters.

A comment on Talks that changed the way I think about programming. Parent comment

Re:Talks that changed the way I think about programming by SanderMak on Thursday December 08, 2016 @07:07AM (#13129828)
Care to elaborate? We're having quite good experiences with it at the moment, but would like to learn from others.
[ Parent | on HN ]
Re:Talks that changed the way I think about programming by JOURNEYSA on Thursday December 08, 2016 @07:27AM (#13129886)
We used this mess of a library, which provides no clear interface and corrupts data https://github.com/johnbywater/eventsourcing
[ Parent | on HN ]
Re:Talks that changed the way I think about programming by maxaf on Thursday December 08, 2016 @07:50AM (#13129957)
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.
[ Parent | on HN ]
Re:Talks that changed the way I think about programming by kbutler on Thursday December 08, 2016 @10:15AM (#13130764)
> 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?

[ Parent | on HN ]
Re:Talks that changed the way I think about programming by strictfp on Thursday December 08, 2016 @09:23AM (#13130405)
Yes, but even so it's a huge undertaking to build your own event sourcing. Many get burnt.
[ Parent | on HN ]
Re:Talks that changed the way I think about programming by jasonm23 on Thursday December 08, 2016 @07:49AM (#13129952)
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.

[ Parent | on HN ]