Some code is hard. Most business logic (in the sense of pushing data around databases) isn't. The value is in analysis and action, which the system enablrs, not the machine itself.
Creating a high performance general purpose database is hard, but once it exists and is properly configured, the SQL queries are much easier. They'd better be or we wasted a lot of time building that database.
It would close the loop better if you could also use policy to switch off innerHTML in a given page, but definitely a step in the right direction for plain-JavaScript applications.
Reviewing docs is a lower bar than reviewing code because it's a lower bar than reviewing code.
I have never even heard of a software company that acts otherwise (except IBM, and much of the world of Silicon Valley software engineering is reactionary to IBM's glacial pace).
I'm not saying docs == code for importance is a bad way to be, just that if you can name firms that treat them that way other than IBM (or aerospace), I'd be interested to learn more.
I'm not sure we're talking about the same thing, maybe my use of "lower bar" was ambiguous, and I realize now it has a dual meaning.
What I'm saying is, you have to review code to get it out the door with a certain degree of quality. That's your core product. That's the minimum standard you have to pass, the lowest bar.
In contrast, reviewing documentation is usually less core. You do that after the code gets reviewed. If there's time. If it doesn't get done, that's not necessarily saying anything about code quality.
Even if it's easier to review documentation, that doesn't mean it's getting prioritized. So it's not a lower bar in the sense that lower bars get climbed first.
Pilots in a plane on autopilot are never out of the control authority of the plane (by which I mean: "ready to take over at a moment's notice"). Driverless AVs do drive without perpetual eyes-on oversight. The FAA would never allow that for commercial planes.
Interestingly, the round-trip latency from the West Coast to continental Asia isn't nearly as long as I'd assumed (60ms to 250ms, depending on who's measuring).
Not nearly fast enough for real-time highway remote operation IMHO, but surprisingly fast. That's what I get for underestimating how fast light and electric fields can go.
After reading this blog post, going to grapheneos's site, and browsing a half-dozen or so pages that I thought might show me what it looked like... I cannot find a single image of it.
GrapheneOS team, I'm begging you... Hire or recruit one person with advertising or copy-for-public-consumption experience. Just one.
The datacenters are thirsty for energy, and the sun is free. In this gold rush, renewables are selling shovels.
reply