13,985 karma · joined August 16, 2012
My opinions are my own and do not necessarily reflect those of my employer.
* X: [@tracker1](https://x.com/tracker1) * Email: tracker1 at gmail * Website: [tracker1.dev](https://tracker1.dev/) * Keto Blog: [Keto Playhouse](https://medium.com/keto-playhouse)
-----
``` [ my public key: https://keybase.io/tracker1; my proof: https://keybase.io/tracker1/sigs/DAQeHW19H-HCUr1ZBXVK7v0QEKqyv4J40IU227AiCVg ] ```
For that matter, there's always a risk of downloading/installing anything from anywhere. There have been successful compromises of many application supply chains at this point in official release paths. You will accept some risk regardless of your approach.
Just that simple practice has kept me reasonably safe, even from an AI scam once.
As I mentioned earlier, this is part of why my own plans for international travel are to only go with a notebook/sheet with contact numbers and buy throwaway devices on the other side. I don't think I'd travel internationally with a phone or laptop at this point, and that's kind of been my thoughts for a while. Especially given the direction that many countries, not just the US have taken. For that matter, I don't think I'd ever even risk travelling to the UK or China at this point. Not that I like the surveillance state here in the US, at least I still have some rights preserved.
TBF, similar mindset if I ever attend defcon, etc. as well.
There was absolutely zero advantage in how the data was structured in that case (auto classifieds website).
That's not to say that database normalization and modest level of joins is always bad... it's just something that can go too far, and holds things back even more in certain environments. FWIW, I started bundling child data in XML before JSON was a thing in highly controlled environments where any schema change was very difficult and required approvals through several groups in a large banking org.
That JSON is fairly well supported today only makes this an easier and better option IMO. Again, sometimes, but enough times to make note of.
I made me smile.
I can even understand the cheaper novel prints... but there should be decent hard back/cover copies that are much higher quality than what we see today. There's really zero excuse for it. Other than general enshitification we see everywhere.
I think if a work is out of publication/availability for over a decade, then copyright should maybe be forfeit altogether. Especially, if that would include digital copies, that has pretty much zero production cost.
Again, I don't know any of IPv6 enough to use it really right or wrong.
If they'd have done that, much like MS, they'd have a piece of every PC sale, not just their own hardware.
That said, I don't think IBM culture could ever have that level of foresight or for that matter hold back the greed to try to own the whole pie. Just watching what became of OS/2. By the time NT4 came out, it was pretty much over... NT4 was leaps and bounds nicer to work with than OS/2 had been, and the software much more plentiful.
Not that MS was much better in terms of monopolistic tendencies, they managed to leverage their position both better, and in many ways have better overall offerings. Then again, MS today is a poor shadow itself of what it could have been had they not tried to start leveraging their own desktop customers for pennies on the dollar. Linux will erode their market share over time, and frankly, I'm surprised that MS doesn't have an AppImage/Flatpak version of MS Office for Linux that they license. They still have relatively nice tools, and though their online versions mostly work, it's not nearly as good and a lot of the integrations are still clunky.
like 1.1.1.1/192.168.45.4 ... for a router that understands IPv6, that's the direct route to the sub-network, otherwise it will have to use IPv4, and the subnet route is treated as NAT and otherwise isolated.
To me, that would make more sense... then internal IPv6 might be practically limited to 10. and 102.168. in the nearer term, but adoption would be MUCH simpler in practice, and distribution would mostly already be established, however unfairly, but can then be broken into single addresses and vNext adoption could be that much quicker as a result of piggybacking.
I know you can just block inbound non-established connections, but it feels like an extra step and complexity. Not to mention, that I really don't understand how IPs are supposed to be provisioned to devices on IPv6. Is there like a 50-100 page book you can recommend "for dummies" on IPv6, that hopefully contains at least a tiny amount of how to configure a common router and/or linux host.
Not to mention, at home, most of the ads I do see (PiHole) are IPv6 addresses.
Google's DNS worked fine, but Cloudflare's didn't. No idea if they ever fixed it... I'm using it as a backup for my main connection, eventually I'll setup autofailover on my router (OpnSense). For now, I just swap the cables.
On the shotgun, or adjacent, I do tend to prefer ammo classes for my nets... 10.22.x.y, where x may be 1, 38, 45, etc. Allows for site to site vpn with friends/family a bit easier to remember.
Maybe limiting npc's to only a certain number of moves that aren't a response to other users per day...
It could be a lot of fun.
What's as or more weird is how much hardware is backordered, and how much live hardware is allocated, but waiting on facilities for operation. And how many facilities are years behind at this point already... all on various credit and dept swaps between all the involved companies... it's not just a balloon, it's a house of cards balanced on a balloon.
But using your own example, how many people with bachelor's degrees are asking if "you want fries with that?" Not every, or any path is guaranteed success... I've worked with plenty of degreed programmers who aren't able to function at all.
I mean, sure start with a unified schema file until you have a production release... deploy, populate with placeholder data, etc... but once released, having a file for each set of changes isn't a bad thing.
Also, the management tools you can have single files for each view/sproc, etc... it's just schema migrations you need to take care of.
Just being able to do basic drywall and paint along with simple wiring for electronics (hanging/wiring a wall mounted TV, for example). Can do pretty well, ex: $100+/hr .. though you're not going to be 100% productive.
One bit not mentioned, and particularly useful in more modern RDBMS with JSON binary expressions in the database are to leverage JSON columns and avoid joins altogether for a lot of use cases. There are a lot of times where you have variance of sub-information, or other data where table normalization and joins work against you. Even with indexes, joins are costly, especially under load at scale with millions of simultaneous users. You can avoid a lot of this by simply having that sub-table information inside a JSON field with the row in question.
For example, logs and notes related to a specific field. Variable transaction data (paypal vs amazon vs google payments), where the logs/details from the API aren't something that really needs to be in a separate table but related to the transaction.
Another would be something like a classifieds site where many fields are repeated, but sub-fields can vary dramatically by the type of item or category.
Knowing how/when to leverage denormalization and JSON can be one of the most impactful things you can do in terms of performance in practice, short of falling back to a search database (Elastic, Quickwit, etc), which can also be practical depending on your needs, but adds complexity.
Similarly, knowing how your datagase uses certain types of data/serialization... for example UUIDv7 if you don't mind storing creation time (utc) of a record, or COMB if using say MS-SQL in particular... the serialization of said field in practice helps in terms of understanding how indexes update and impact performance.
I do wish the guide was expanded a bit with lots of specific examples and details... a lot of it is hand-wavy blurbs.
The tools, libraries and languages you are using can also dramatically affect results. Even on state of the art models, I find, for example, the output of SQL for complex interactions, or C# for that matter to be sub-par, where I find Rust results to be pretty great, with JS/TS falling in between.
At the best, it can feel amazing and productive, at worst, time consuming and annoying that you could have done it faster yourself. YMMV in real world use.
Note: I'm a proponent of human in the loop gatekeeper/reviewer usage of AI, and I'm not able to even consider Chinese models for my own use, and not able to use anything at my day job.