devmor
Joined 6 years ago
Joined 6 years ago
"Microstate" is a term generally reserved for tiny geographical locations that can't even support their own defense.
Most importantly, it’s bad at catching things that are not normally part of documented processes or openly reasoned about. I think that this specific weakness is extremely important and exactly how you end up letting something go by that would be trivial to catch for a human reviewer.
If you don’t rigorously verify everything by hand before then, you are telling the world that they must do what you should have done for you. Or more likely, you are telling the world that that you expect free intellectual labor and will be ignored and chastised- and cause more scrutiny to fall upon others who did the work properly.
I chose my wording very intentionally. My criticism is exactly what I said.
It’s like comparing a bicycle to a light duty farm truck.
While people do often use pis to do things you could do with an esp32, an ESP32 cannot do the majority of things a Pi can do.
Of course there are problems where knowing the code deeply is essential to solve the problem, but those really aren't the majority, if even less than 1% of business problems.
When it comes to what the average developer needs to understand, having a strong grasp on one functional and one procedural language can enable you to solve almost every problem in any language ecosystem, provided the correct resources. If you can do this, you can utilize an LLM for programming assistance well. If you can't, you probably should not heavily rely on one at all yet.
You should own and be the expert on the architecture and design of what you're building regardless of whether yourself, an LLM or another person is writing the code.
The LLM isn't "smarter" than you, it's more resourceful. It can (to varying degrees of success) translate your design into code. If you aren't still taking ownership and driving the design of that logic, the LLM isn't going to bring you success with anything other than single-use or hobby applications.
The vast majority of tech support scams come through apps on the Play Store. Not only that, but malicious apps get approved on the Play Store constantly.
There is no reason to take any claim that this change is meant to mitigate scams seriously, because there's no evidence to support that it makes a noticeable dent in such activity.
What this change does noticeably and impactfully do, is prevent, via chilling effects, users from being able to use their phones in ways that could lose Google and its partner vendors post-sales revenue.
As you said, serving people should be the end in itself, and this change doesn't do that - it hurts people.
Reading through the whole post, this sounds like an thoughtfully and intentionally designed product. One with strong opinions and the developer’s real lessons behind it. In the current era of slopware- especially around AI tooling - this is giving me damn near an emotional reaction. I am happy to see this.