> To me, that signals there is at least something fishy about the technology.

> I'm not saying Node is bad, but...

You're giving off slightly mixed messages there.

Charging per exception also adds a nice synergy to bugfixing.

Sergei,

I think it was a mistake to put this post on a blog with no other content. I think it leaves the reader with the impression that this is the only thing you want to contribute to the community... and as other commenters have pointed out that contribution could be perceived negatively.

Something to think about next time.

Every blog has a first post. What's so bad about that?

"In our opinion, the NoSQL decision to give up on ACID is the lazy solution to these scalability and replication issues."

They had me up until they called NoSQL "lazy" and claimed NoSQL solutions "give up on ACID". They aren't lazy and a lot of them support ACID, or most of it.

From that point on this veers away from logic and moves towards a self-justified argument. Tools are just tools. If you need immediate consistency then go for an immediately consistent solution, if you don't then you should feel free to take advantage of the performance gain of eventual consistency.

The thing is that implementing ACID is, well, atomic - you either support it or you don't. Anything else is one of a series of different types of compromise. All currently available NoSQL systems I'm aware of compromise it very heavily, resulting in greatly increased programmer complexity for the types of applications that really require something that looks like ACID. I'd be interested to know which ones you think support ACID - as far as I'm aware none of them claim to support anything like it (with the possible exception of VoltDB, which has its own set of problems).

Scalaris has supported ACID transactions for years, but it never caught on because at scale you care more about availability than about having transactions: http://twitter.com/Werner/status/1008722501

If you're counting important things (money, inventory, etc), being up with the wrong answer can be worse than not being up.

I'd add UX Bookclub, and the UX Freelancers group on LinkedIn.

I'd also look at Product Management groups as UX is a specialism within that, so ProductCamp and ProductTank for starters.

My tuppence would be to attend events and meet people in person... as once you've established a credible relationship it's easier to convince a potential employer to give you a shot.

From their perspective it's about risk. Commercial experience de-risks you as a potential hire, but so does a relationship, even a new one.

If you make it to London get in touch with me and if I can help I will. My email is richard dot marr at empora dot com

Edit: another route would be to take part in open source projects with a strong contingent in London.

Thank you for your help and for your contact information. I will get in touch when I move to London. I understand what you suggest, however it is hard to attend events/meeting in London still having a job here. If I cannot find anything first, I am considering taking the risk of moving without a job and try to find one onsite. But that is something I really need to give a thought. On the other hand, joining another open source project with folks from London would imply perhaps another year before I could move... To be honest, I am not sure I could maintain my professionalism for such a long time and continue doing my job.

Exactly. If you can find someone that great (and that important to your business) who's genuinely happy with salary & options rather than full equity... then hire him because he's a rare beast.

Empora are hiring in London. I'm not going to list technologies because I expect awesome technologists who can work with anything and everything. We're working on interesting search and product problems related to the world of aesthetic retail. Take a look at our site and send a CV to richard dot marr at empora dot com if you fancy a chat.