calineczka
Joined 14 years ago
Joined 14 years ago
Our current stack is Ruby, Rails, PostgreSQL, ElasticSearch, GraphQL, Kafka, K8s. Mostly working on majestic monolith, occasionally on one of the smaller services. We are building a lot of integrations with external providers, recently integrated Google Drive, elastic and LLMs for AI search.
Apply at: https://www.toptal.com/careers/senior-back-end-engineer-plat...
In every project that I've seen using it, it was a tremendous unnecessary waste of time in comparison to writing feature/acceptance tests just in Ruby. Gherkin is just such a poor language in terms of expressiveness compared to Ruby. Not to mention things like poor REPL experience when writing the scenarios.
I am backend engineer with a non-JS background and to me that's a a very useful thing. I really don't want to install specific node version, yarn version, etc to run some node/JS application. If I can just docker-compose up that's much easier to me and I know it does not affect anything globally. So removing it after playing around is easy and non-risky.
It says "This mode protects a table against concurrent data changes" but it does not elaborate how. Is it similar in consequences to what MariaDB describes?
Very well said. I think there is enormous complexity in many layers because we don't have that building block easily available.