vandal_at_your

4 ms·

1. 1.▲
   by vandal_at_your 6y ago

   Worked for them in the Herndon DC. Forget the name of their lovecraftian ticketing/control interface (which was always breaking) but it was hands down the worst interface I've ever worked with. Their remote SA team was not very go
2. 2.▲
   by vandal_at_your 6y ago

   Nope. https, hybrid crypto and pub->free CA's are the largest backdoor into internet traffic ever (accidentally) devised. The standardization on https for everything (including alt app protocols (dns,etc...)) is very apparently an i
3. 3.▲
   by vandal_at_your 6y ago

   When you demonstrate that your ECNL (equally crappy new language) merits an investment of time guaranteed not to break in perpetuity against programmers in the future and changing standards I'll make an effort to learn it. Mind, it mus
4. 4.▲
   by vandal_at_your 6y ago

   Chrome or firefox. Egregious wastes of my time, 90% inaccessible, untrusted interpreters of untrusted code.
5. 5.▲
   by vandal_at_your 6y ago

   Pushing this language and Go as required, responsible, NG languages is another one of the foibles of the cloud/web and it's owners. For those of us in HPC and scientific compute where is the practical reason to switch from C/
6. 6.▲
   by vandal_at_your 7y ago

   Fuck the idea of the browser as interpreter for untrusted code.
7. 7.▲
   by vandal_at_your 7y ago

   For me automation was learned behavior in lockstep with my ability to solve problems via programming. It eventually became automatic: to the point that my own patience with manual repetition and documentation of manual processes is minimal.
8. 8.▲
   by vandal_at_your 7y ago

   I'm torn on this opinion. From 20 years of experience I can see where kubernetes fails and seems absurd (internally routed and natted networks with terrifying complexity and design, obtuse declarations in yml/json that hide more u
9. 9.▲
   by vandal_at_your 7y ago

   Also surprised to see this at HN. The approach to automating interactive applications based on pty superpose (and I/O direction) coupled to a pattern->action model is an extremely old fashioned approach. 20 years ago expect was an