@jnunemaker Been using them for endpoints on a static site for a few years. Pretty easy to use, loved how easy it was to get setup. Also did some POCs using them for AI LLM use. Documentation is top-tier.
For kicks tried to see how much of C I remember. Forgot just how simple it was to get an idea out. Neural network up in no time and piped the epoch data to Claude on the command line to provide feedback on the rate of learning and the network generally. Pretty cool ๐
@endingwithali I had to write out a backup and retention SQL procedure in an impromptu job interview exam. Got the job and and about 3 months later recognised the code in the midst of my first monthly backup activity with the team ๐
@dorkitude I used it to try to fix Bluetooth on my Ubuntu Mac book Air. Gave it free reign of the system, I paid attention to make sure it wasn't nuking anything, and I did sudo where necessary. Was plenty impressed with what it tried, went as far as importing kernel modules.
Hey Junior Devs, just know that even with decades of experience, a 60 minute dev trip caused by "user_prod" instead of "user-prod" is enough to trigger an identity crisis ๐
@sysxplore Agreed. Hopped all about the ecosystem for a while, Mandrake, Cent OS, Fedora plus others but Ubuntu is the go to. Now I veer outside only for experiment.
@jeffdafo@gwenshap Each implementation or vendor will identify their niche and optimise for a different set of needs. Same reason we have so many car brands, same reason you can self host or use a VPS. To conclude the discussion ... 12 joins is nothing to be making architectural decisions about.
@jeffdafo@gwenshap The DB can do significantly more than we give it credit for, joins are the least. If you can't get good response on the joins the first thing is to pick apart the explain plan to see that your SQL code is optimal. Table partitioning etc, a whole load is possible before app layer
@jeffdafo@gwenshap If your dataset has grown enough that you can actively consider the investment of replicas and sharding them you are already in the position to manage replication. You're not taking this step on a whim, this is a solved problem.
@jeffdafo@gwenshap That's optimising for a different problem, one that may never come. Changing entire data layer implementations do happen but not as frequent as one would think, that gets debated a lot. In the meantime you would have resigned yourself to the performance penalty of passing...