14,007 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 ] ```
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.
For example, I'm currently working for a local government office on elections management software... It's a no-go from the get-go for me... AI, in general is not allowed, though a couple groups in the city do have copilot access.
Even if it's running on US hardware, without Chinese comms, that doesn't mean it's completely safe... there are complex attack paths that have and do happen. StuxNet was a long time ago, and it's only gotten worse and escalated from there. Not every job/position/application needs this level of paranoia, but don't completely discount it because you don't have to worry about it.
I'm largely with Mike Rowe on this one... it's been a shame the level that people have not been directed into more vocational fields and the level of skilled labor shortages as a result. Higher education has largely been self-serving, not community serving.
On the plus side, men do have an advantage regarding size/strength in terms of being able to help disabled people move. I think this is probably part of why a lot of men become EMTs (similar field/training).
Assuming such work was happening.
You're just an idiot who assumes everyone that doesn't agree with you is the same. I'm surprised you're able to reply with Xi's penis in your mouth... even if it is kind of spacious in there for his limited size. How is the poo bear these days? Does he like it when you gargle his testicles in your mouth?
Paramount is more of an also ran as far as streaming media IMO... HBO/Max under Warner is far more established in terms of forward looking/facing and the Paramount catalog and broadcast systems can only enhance this. I think they should be required to divest in the actual cable and broadcast stations though.
What we really need are more fair licensing requirements for older content under copyright, but nobody is really pushing for that.
If you let a model spin too much, you get worse results... that's a fact, even for the best models. Nothing you've stated since actually refutes that and acting like a paid bot doesn't mean anything.
I mean, if you want to felate Xi Jinping, have at it... that's all on you bro. I don't have a horse in this race.
As to the why, it's because I switched jobs and got my regular labs done and apparently was between coverage that week... they tried to charge me a large multiple of what they charged insurance for the same labs, so I refused to pay.
I also had several bills that were never paid from a week long hospital stay in my mid 30's... Most of them got paid if they'd agree to reasonable payments or settle for lower amounts when I had the money (tax return time, bonus, side work). After 7 years, they were all off my credit and I stopped bothering...
A model will often come up with worse results given more cycles of compute, only because it will tailspin from second guesses, rethinking and literal flip-flopping on concepts.
--- edit: to those following the thread below... if you look at the comments from the account replying, it's pretty obviously a pro-China account and all replies are antagonistic against anything other than a total submission to the Chinese state. My responses are intentionally antagonistic as every point I've brought up is completely ignored in favor of insults, so yeah, I've been insulting back.
I can't even consider Chinese AI tools for my own use on my own time on my own hardware without potentially risking firing or worse. Yeah, it's cool on a technical level.. but the "open" part of this and K3, etc. is of limited use depending on how/where you can actually use it yourself. Trust is another issue entirely.