Very well said. I think there is enormous complexity in many layers because we don't have that building block easily available.
634 karma · joined November 21, 2012
Very well said. I think there is enormous complexity in many layers because we don't have that building block easily available.
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?
It's not that the colors are indistinguishable per se, always. They are hard to distinguish under certain conditions such as:
a) size of the elements of the same color. If half my screen is in one color and the other in different color, it's very easy to distinguish them and say which one is what. If on the other hand you have just a few pixels, it's much harder to say what color they are.
Recommendation for app devs: don't use only 1px red border to show validation errors in forms. It's almost impossible for me to say that the border is red and not black.
b) closeness to each other in terms of distance. Similar colors far away from each other are easier to recognize vs when they are right next to each other (like in the map).
c) Similarity between colors. If the colors are not used for scale, use very distinctive colors. I always take my colors from: https://colorbrewer2.org/ based on the use-case. This has already been researched and it works.
d) movement. It does not help in recognizing colors.
These conditions don't occur that often in "real life" when walking, shopping, etc. They are mostly annoying on screen and paper.
Regarding compensation techniques:
If it is not work related, I just don't bother and don't put any effort. There is a cool map on reddit, and I can't read it because of the colors? My loss, not gonna spend time on it.
My biggest pet peeve: sport team outfits. Sometimes certain teams play vs each other and I cannot distinguish who is who. That is maddening. Why would you play black vs red when white vs red would be 100x more distinguishable. There should rules about minimal necessary contrast between the jerseys. I can't watch some matches so I don't watch them. I like teams with blue, yellow, white colors. Maybe that's why GSW is appealing to me :)
When I play FIFA with friends, I need to tell them which jersey variant to choose so I can comfortably play and have some chances. You cannot do it online games :( I wish I could select what I see on my machine. I wish there was a setting to use artificial jerseys of high contrast. Or make my opponent jerseys always black or always white and let me pick the clothing for my side. There are some colorblind options in FIFA but I don't find them good enough. They don't solve the problem fully.
If it is work related and I cannot decipher it, I will politely complain that someone used colors only to encode some information and I cannot process it. I will recommend to use something additional (words, borders, tooltips, patterns, anything that makes sense).
I also notice that kind of issues when our engineers work on dynamic maps or charts, and I try to bring it to people's attention. It's a lost battle in the grand scheme of things, but I keep fighting.
I believe it's easier in big companies because the probability of having a colorblind stakeholder is higher. In small teams (<= 7) you might not have a single colorblind person who could share their perspective and point out the problem.
I guess it works that way with everything: race, gender, translation and localization, and other disabilities, but I can mostly comment on that one thing.
Did we though? Can you point out some books, or PHDs or whatever slightly more scientific and substantial than blog-post anecdotes?
I honestly believe as an industry we completely don't know how to scale development and I would love to read something that helps understanding this challenge.
Recently Google got much better in understanding full sentences and there are tons of SEO optimized pages for certain phrases. Nevertheless, using keywords is what I imagine advanced users do.
What does it mean exactly? I feel you are trying to share a nice idea but I can't comprehend it. What are those small parts? Classes? Modules? Services? What does it mean to treat them as a separate full product within an organization?