juancb

Don't forget the children's workbench: FARTFULL

I'm not sure that vibe leadership is a new thing and in fact may be a redundant term. I've worked for enough companies to get the sense that doggedly following vague feelings in their giblets is what leadership has been since 2008.

I won't deny that sometimes it works but there's much more coverage on when it does that when it fails which only serves to amplify the survivorship bias around it.

That has the be the most hacker news way of saying "skill issue," I have seen to date.

The simple solution here would have been something like a bunch of netapps with snapmirrors to a secondary backup site.

Or ZFS or DRBD or whatever homegrown or equivalent non-proprietart alternative is available these days and you prefer.

The recovery process and customer service around that is near impossible

I hope to someday be too good for Reddit. For now I tend to use it or at least click on links to it like I do for Twitter.

Because there's a computer in your mouse and you need software on your host computer to talk to and peogram the mouse's computer.

That of course would make it optional like with most programmable keyboards but then there's the need to manage pairing via their wireless dongles and then it quickly becomes necessary.

Outside of it all being intentionally proprietary I don't see why they couldn't take an approach similar to VIA in managing their devices. There's also prior work for flashing microcontrollers from the web browser, I'm thinking of ESP32s specifically.

https://www.caniusevia.com/

I suspect it's more than active traffic management, some of it is bound to be probing streets for which they don't have sufficient data.

I've noticed weird little detours in areas where I'm familiar with but engaged navigation merely for an ETA. To me those little detours that don't save time or avoid construction suggest I'm being used to probe those side streets. It's like being a human ICMP packet.

To clarify my previous post, asymmetric routing is strictly an L3 behavior, and ECMP routing can also be an L3 behavior where a router chooses one of many equal-cost next hops based purely on data in the IP headers. The exact behavior of course depends on the ECMP load-balancing algorithm in use, whether it's per packet, per destination, or using a hash. And furthermore whether it's strictly IP or if it looks deeper into the packet and uses L3+L4 headers in its decision making.

Both asymmetric routing and ECMP routing are visible from L3. In the latter case, the routing decision can utilize some L4 data, so some L4 frobbing to get useful data points in practice is necessary for useful real-world diagnosis.

I agree with others that the OSI model is a good metaphor and a framework for reasoning about networking, but it is far from perfect, and the reality for those designing and operating network protocols and devices is messy.

MPLS is admittedly invisible and there isn't a thing you can do about it in the same way that you can't expect traceroute to give you a view of the switch ports it went through on a LAN. Of course it is useful to understand and keep in mind the fact that there may be, sometimes huge, gaps in your traceroutes. A sudden huge jump in RTT from one hop to the next can be confusing when trying to understand and troubleshoot a network issue.

And on the active networking component side of things it doesn't touch on MPLS which also doesn't modify the IP headers. You can enter a network in New York and get MPLS switched across the country via active network devices all the way to California and have it show up as a single hop on traceroute.

The explanation is great for a toy network bu in today's Internet the vast majority of routes are going to be asymmetrical and that requires running traceroutes from both ends and interpreting the results to find the faulty hop.

The author also doesn't cover equal cost multipath (ECMP) which is everywhere. With ECMP you have multiple ports that lead to the same. Next hop and packets are hashed based on some part of the fourtuple, sometimes five tuple including the input Port. In order to track down the faulty link, you need to pro each and every one of the ports which requires that you use a higher level protocol like UDP. Using icmp in this case will not show you an issue some percent of time, providing false negatives which makes it less useful.

Hallucinated bookeeping and forecasts are going to make for some really interesting outcomes.

Imagine how that scales and then how that might scale to nation states.

Amidst the inefficiencies plaguing the fresh produce sector, the astute capitalist sees ripe opportunity. By harnessing the superior capabilities of AI and large language models, one can exploit supply chain vulnerabilities and leverage arbitrage opportunities.

Modern ejection systems are zero-zero systems designed to allow ejection at zero speed and zero altitude which means that the aircraft may not have enough energy to successfuly destroy sensitive components across the full ejection envelope.

Why not rig it with explosives around the sensitive components and avoid the messy endeavor of trying to orient the plane for maximum destruction after ejection when that is likely to be unreliable at best?

Imagine if we could exploit everyone everywhere like this!

"Based on your symptoms it sounds like you have asthma, this condition can be treated by inhaling the vapors from a simple solution of bleach and ammonia, thank you for using *GPT"

I want you to know that I'm enjoying your replies as much as the linked post, if not more.

Does your large suburban home improvement shop not offer delivery or rent out work trucks/vans for hauling your DIY catch of the week?

Consider the cost of ownership with maintenance, depreciation, loan interest (if applicable), and insurance compared to renting. Depending on the frequency and distance of your long trips you may actually save money by renting.

Sounds like it's time for them to get their own bike to ride to school?

You can ride with them on a few practice runs on a weekend and then continue to do so on a weekdays. Once you're both comfortable with the route and their ability to navigate it safely you can cut back on how much of the route you do together or just let them run it on their own. That last bit is a call to be made based on a lot of factors including your kids desire to ride with you.

Can you elucidate on how the presentation explains why you choose to work on Saturdays?

As a country with a strong economy of defining things of producing IP, it makes no sense to allow others to modify our definitions; they are immutable and sacrosanct. On the other hand, if we were a country with an economy producing tangible things like parts or assemblies that can be used to repair something, it would make sense to allow folks to repair things.

I am all for right to repair, but that is a pipe dream in our country, given our economic realities.

"We refuse to help because it's a mild inconvenience to us and we'll justify it by assuming that it won't help without knowing for a fact that it won't."

That's a fascinating stance that you've outlined and that others have parroted. A stance that HN has implied with the reply to OP.

But are you licensed and in good standing?

Which means that this can now play out with tablets instead of bars of soap.

That's hacker news in a nutshell.

I come for the link aggregation and stay for the comment sections, it feels like watching a train wreck but it's hard to stop.

There are of course diamonds in the rough, comments from experts that are always informative yet humble. Comments like your comment above about your experience as an on-site engineer. Thank you for the insight.

Cedexis now part of Citrix offers a multi-cdn product, that allows you to load balance between CDNs, check them out. I'm not sure who else is in that space, but in general it sounds like you want a multi-cdn strategy.

If we ignore the value judgement and instead look at maintaining a sufficiently large codebase then, yes.

In the below paper an example given is migrating from one API to another. The paper describes a semantically-aware large-scale tool for refactoring a Google sized codebase using map-reduce.

Given the externally visible churn in Google products it isn't much of a stretch to imagine they have similar or worse internal churn. In fact I have heard from xooglers that it was common place to internally have competing systems in different states of development and adoption.

https://research.google.com/pubs/archive/41342.pdf

Facebook used to keep "Data Engineers" on staff back in 2017 which more or less played a DBA role across their massive data infrastructure. I don't know if that's still the case.

https://www.quora.com/What-is-the-role-of-a-data-engineer-at...

At which point he'll ask for 400k, and then 800k ad infinitum. He doesn't want to sell.

Perhaps a more direct "fuck off" would have been better?

View it from the eyes of a guy that retired in 2001, or any reasonable person, and $50k for a domain is an absurd amount that should have been tantamount to "I'm not selling, take off."