superbaconman

I think you're underestimating just how "standard" many of the shortcuts are when mapped against a standard shell.

With zero energy cost it will run until it stops working or runs out of fuel, which I'm guessing is between 5-7 years.

I'm considering buying enough batteries for my day usage, then recharging off the grid during off-peak hours. I can add solar later on.

Within the context of building AI systems: What's the distinction between hallucinating, imagining, and inferring?

I've worked with a large number of vendors and I prefer juniper. They're very easy to write software against.

Publishing the documentation seems like a lot of work. I guess everything is just manually synced between users via git?

"ctrl+f" looks at github "home" looks at youtube

Right but is the particulate matter from burning natural gas any more harmful then the particulate matter from searing protein?

> What does that user need to hear? Not which file or subsystem was changed. But the reason there is a change in the first place.

Doesn't that belong in the code itself? Do we really want the intention of a change to sit under multiple levels of blame?

I've been building network controllers my entire career and the "hard part" has never been interacting with devices. Like who cares if you're using Ansible? The hard part is configuring these things; Every vendor has a different way of configuring the same 5 solutions to the same problem, and even with a single vendor network you may have to tailor your configs based on the device type that you're configuring.

IMO there needs to be some higher level abstractions emerge. Half the time I just need a layer 2 network (please don't ask me to configure it one way for a point-to-point vs greater than two endpoints. if there's an optimization to be made do it for me). The other half the time I need a layer 3 network that can peer with BGP (don't ask me what underlay or overlay protocols to use, I only care about the VLANs I'm terminating on).

Slightly related: Cloud providers expose APIs for networks to setup peerings between the cloud provider's network and the network's end customers. These APIs aren't standardized at all, and are a complete PITA for networks that try to integrate their SDN solution with multiple cloud providers. This is one area of complexity that the big guys could cleanup without a lot of work.