I go to the store – the ATM is not working. The seller says – just a sec, we’ll fix everything. Opened it, loaded money, I withdraw. The store gets two bucks from each transaction. The embassy does not accept cards, only cash.

I go to the store – the ATM is not working. The seller says – just a sec, we’ll fix everything. Opened it, loaded money, I withdraw. The store gets two bucks from each transaction. The embassy does not accept cards, only cash.

When I start the car, the phone automatically connects via Bluetooth and begins playing something through the car’s speakers. Since in 99% of cases my car is set to radio mode, I didn’t even notice it, and Bluetooth audio consumes a significant amount of battery. Auto-play can be disabled neither on the car nor on the phone. It turns out there is special software on the Android Market that even works properly for turning it off. Link at the end of the attached post. Who dropped the ball, Google or Toyota?
http://blog.smirne.com/2015/02/how-to-stop-bluetooth-auto-play-feature.html?m=1
Evening New York.
Kharchio, pelmeni, and compote!
Shopify are really progressive folks. I spotted their idea of using a messenger as a channel to communicate with customers. Now I see they’ve made an iOS keyboard with products https://www.shopify.com/blog/put-your-store-at-your-fingertips-with-the-shopkey-ios-keyboard
They could have written that LinkedIn is blocked in Russia for being glitchy and that everything there is done ass-backwards. And no one would say a word!
I have a new blog post about Hybris. It discusses three components that, in my opinion, are necessary for 100% of Hybris projects. You can literally include these topics in the requirements for any of them without considering what kind of project it is. The depth of development depends on the scale, but the basics must be there.
I’m somewhat surprised that I can’t come up with a fourth topic to add to the three described. It either isn’t universal enough (i.e., it doesn’t fit some specific Hybris projects), or it pertains to infrastructure or the development process rather than to functional scope.
https://hybrismart.com/2016/11/16/three-things-that-every-hybris-project-must-have-in-scope/
Yesterday, I binge-watched five episodes of Stranger Things. I barely managed to convince myself not to watch the sixth. Addictive!
Dim, I’m working on an article “5 Things That Must Be in Absolutely Any hybris Project.” In fact, not just hybris projects, but my blog is about hybris, so there you go… So far, I’ve come up with the following (order is arbitrary):
1. Feature toggles – enabling/disabling/switching features, including A/B testing
2. Feature usage monitoring and alerts – this includes Google Analytics for storefronts and various system resource charts. This also includes systems that analyze unusual behavior (for example, if the number of orders in an online store has halved compared to the usual at this time)
3. Automated tests – I want to write that even for the simplest and very fast projects, tests are still necessary, even if they are just the most essential ones.
I need to come up with two more. I’m conducting a survey – write your ideas)
For example, there is no CI/CD and Code Quality Gates – because that’s about infrastructure and development process. I’m collecting about development itself. That is, what needs to be included in the code that’s helpful in 100% of cases. Any ideas?