Legitimately listening to this book for the first time after a coworker recommended it. It's rapidly becoming one of my favorite books that balances the truly alien with the familiar just right.
Not so ironically, it came up when we were discussing "software archeology".
It has been a while, but I remember a project of mine trying to port a FTP client to a 'secure compiler' (this was long before Rust and probably a distant ancestor of Checked C). In theory, if I could successfully port it, it would be much more resilient to particular kinds of issues (and maybe even attacks). This was in the era where formal proof coding was trying to take off as well in the industry.
After wading through an impressive number of compiler errors (again, it was technically compatible) and attempts to fix them, I eventually surrendered and acknowledged that at the very least, this was beyond my abilities.
I probably would had gotten much further just rewriting it from scratch.
The age old tactic of vilification. It's easy to overlook all the nuances on all sides; it's a whole spectrum with plenty of overlap.
My hope in the US is that folks at least take the time to evaluate their options and/or candidates; voting a straight ticket just because someone calls themselves something can lead to undesirable outcomes.
Admirable, but short of a local credit union I used to use (which I am no longer with as they f'd up a rather critical transaction), I can scarcely imagine a business that fits such a model these days. The amount of transparency needed to vet this would be interesting to find though, and its mere presence probably a green flag.
Ugh, yes. Normally, you can theoretically pair someone up with a stronger engineer and watch as they learn and grow through their mistakes, while the stronger engineer keeps them on the proverbial straight and narrow with what they produce, through code reviews, documents, etc.
But now, I can't trust any of the models to be that reliable. I can't delegate that responsibility. And since context and prompting is such a fickle thing, I can't really trust any of them to learn from their mistakes, either.
In what ways? Apple, IMHO, has been jumping on every proverbial band wagon. And some of its 'better intended' changes like ATT seem only to have been to stifle competition while they set up their own solution.
Well, the alternatives is Android and... not really much else, for a full-featured smartphone. Say what you will about Apple, they're not perfect, but they have a better track record w.r.t privacy than Google in every way.
I'm not saying I like what Apple is doing here, but I trust Google a lot less with my data.
This! Sure you might need a Google account for your android but you don't HAVE to use all their services.
First just don't use Gmail, docs, search, chrome and co. But even better get a Pixel with Graphene and Google's invasive tactics are even more limited.
However it is sad that a company like Apple that used to produce superior hardware with superior UX is falling apart on all fronts - hardware (especially pricing), UX (hello glass design), software (macos just getting worse every release without adding ANYTHING of value)
And now introducing more and more ads while keep selling you "pro" laptops with 512GB SSD :-/
Real-time multi-directional communications over massive geographic areas with tens of thousands of physical cell sites connected to ~140M devices vs... public text messages with media.
I realize your point, but its fair to say maintaining a nationwide physical wireless infrastructure may not be the same as hosting tweets, particularly when outages strike.
Not so ironically, it came up when we were discussing "software archeology".
reply