Think Again#
Feelings and Thoughts#
My blog has two tags: "Feelings" and "Thoughts". One day, I saw them myself and was a bit stunned. What's the difference between these two? It seems quite similar.
Think again
There is still a difference. "Feelings" tend to be the initial reaction of the mind and body when seeing or perceiving something for the first time, while "Thoughts" may occur after a certain period of time when thinking about the matter.
This explanation is just my own speculation and may not be accurate, but it is useful because it turned what I thought was a bug in the blog tags into a feature.
Shell-wrapped Domestic Products#
One day, I came across a post where a programmer was complaining about having learned MySQL, Tomcat, and other knowledge, but the client required the use of domestic tools, which the programmer felt were just wrapped in a layer of skin and charged extra fees.
My initial feeling was that it was shameful, and it immediately reminded me of a certain text editor.
Think again
From a legal perspective, depending on the licenses of the open-source tools used, this shell-wrapping behavior may be legal or illegal. However, if they dare to charge for it, I believe they must have studied the relevant laws and regulations. This is not my area of expertise, so I don't know much about it.
From the perspective of the buyer and seller: The client has a demand for domestic tools for various reasons, and the supplier is adapting to this demand. There's not much more to say about it.
From a value perspective, if the shell-wrapping is accompanied by a certain period of after-sales service, it can be understood as selling a service, which is also understandable.
From the perspective of the open-source community, I have always been just a user and have not contributed much code or deeply participated. I can't say much about things I don't understand.
But for me, I still find it shameful. Because when I use someone else's code, I will delete unnecessary things in the final product, but I will declare that my project has referenced and used someone else's code. I think this is a basic form of respect.
Smart Sensing Payment#
One day, I saw a video of someone holding a barcode scanner against a certain phone, and the smart sensing payment advertised by this phone worked. There were concerns about privacy in the comments, saying that having the front camera always on is terrifying.
My initial feeling was that it seemed to be true.
Think again
The statement that the phone's camera is always on doesn't seem to hold up. I guess: First, this should consume a considerable amount of battery power, and users should be able to notice it. Second, there are better ways to implement it, such as adding a distance sensor, so that it only detects when there is a certain distance.
But then again, regardless of the implementation, it will definitely increase the usage of the front camera to some extent. As for privacy concerns, I think as an optional feature, if users choose to enable it, it means they accept the corresponding possible risks and are willing to sacrifice certain things for relative convenience.
Think again
If possible, would I use this feature? I think I probably wouldn't, at least not in the short term. My current thinking is that payments shouldn't be too convenient, as excessive convenience can make me unknowingly spend more money. Some inconvenience can give me more time to dispel unnecessary thoughts of consumption.
Think again
Speaking of the convenience of payments, I think scan-to-pay is a tradeoff for popularity, and for places where scan-to-pay machines can be used, I think using NFC, which allows payment with just a touch, is quite good.
Heart Rate Measurement with Fitness Bands#
One day, I saw a video where someone took different brands of fitness bands and tied them to sausages or water bottles to measure heart rate, comparing the quality of the brands.
At first glance, I thought it was silly. The better way to compare superiority and inferiority should be to compare accuracy, battery life, and other parameters in actual use, rather than doing something like this to please the crowd.
Think again
I still don't like this approach, but I think this video still has its significance if we don't compare superiority and inferiority based on it.
- For example, developers who see it may think that they need to add a detection function to ensure that it only detects when worn on the wrist.
- For example, as an ordinary consumer, I would think: Hey, this shows that these fitness bands use different detection mechanisms. The same function can be implemented in different ways, which is quite interesting.
Pre-packaged Meals#
There was a lot of discussion about pre-packaged meals for a period of time, and at first, I was quite repulsed by the term, thinking that it represented something unhealthy, unhygienic, and not tasty.
Think again
Are they really unhealthy? Maybe. After a dish is processed, packaged, and needs to be stored for a considerable period of time, some form of preservation technique is likely needed. I'm just an ordinary consumer, and based on my own life experience, I have some concerns about this. And these concerns may be reasonable or unreasonable.
Are they really not tasty? I'm not sure. I haven't conducted a double-blind experiment comparing pre-packaged meals and non-pre-packaged meals, and my taste buds are not particularly sensitive.
Are they really unhygienic? It depends. I can't even guarantee the hygiene of cooking at home, let alone those fly-infested restaurants or small take-out shops. If pre-packaged meals are produced by manufacturers of a certain scale, following the appropriate standards, I think hygiene should be assured.
So my opinion is that we shouldn't demonize pre-packaged meals excessively. They can be a choice.