inChargeOfIT

thanks for this!

It's free for now, just like registries were "free" and docker desktop was free.. until they weren't. I am not against Docker capitalizing and charging for their services (as they should); however, the pattern of offering a service for free and then reneging after it's widely adopted, makes me hesitant to adopt any of their offerings.

A month or two after a visit to Iceland (my favorite country by far by the way), I received a ticket in the mail for speeding. It included a picture of the car I rented and a closeup of the driver's face- a face that did not belong to me (presumably another renter).

Luckily, a quick phone call and a copy of my drivers license cleared things up, but systems like these inevitably lead to "guilty until proven innocent" scenarios instead of "innocent until proven guilty".

works for me

From the abstract, it sure sounds like any electronic checkers or chess game would fall under this patent. If so, I'm sure there is plenty of prior art to invalidate their claim.

I'm not even sure it saves a ton of time to be honest. It sure _feels_ like I spend more time writing up tasks and researching/debugging hallucinations than just doing the thing myself.

So that would include everything? - cloud/hosting expenses - system administrators/devops engineers and their laptops, workstations - project management software, office software, support, etc - project managers, designers, technical writers, qa engineers - software licenses, domain names, certificates, etc - internet bandwidth, data-centers, HVAC, backups

Proxmox uses qemu for vm’s.

little known fact: you can write shorthand for any ip address. It simply omits 0. Ie 127.0.0.1 (or 127.000.000.001). Try pinging it. `ping 127.1`

10.0.0.3 -> ping 10.3

It sounds like the same requirements as a 70b+ model, but if someone manages to get inference running locally on a single rtx4090 (AMD 7950x3D w/ 64GB ddr5) reasonably well, please let me know.

I totally agree. And some long/complex files are simply unavoidable (shell/build scripts, config files, etc).

This is not always possible and a little short-sighted, especially when you are on a large, complex, established project with many contributors, where "just refactor 1.5 million lines of code, spanning 1500 files that have evolved over a 10 year period" is just something not open for debate.

In those cases, and in the cases where a single large file just makes more sense or is unavoidable (IaC/build scripts, shell/sql/migration scripts, config files, etc.), the author's methods are absolutely valuable.

I find if you subscribe to the "Write libraries not software" mantra where your libraries/packages/classes are focused and adhere to the single responsibility principal, code organization kinda sorts itself out. But I agree with the author that organizing and commenting long files like this makes it easier to grok what's going on.

But if you are clicking around a project and scrolling with your mouse, instead of taking advantage of your IDE's ability to use keystrokes to find and open files, jump to references/definitions, find and replace text, etc., you are handicapping yourself. It's worth the investment to learn.