The Linux whatever’s, PC whatever’s and Mac whatever’s, and even Communications of ACM and the equivalents just aren’t the same thing.
1,243 karma · joined May 25, 2016
The Linux whatever’s, PC whatever’s and Mac whatever’s, and even Communications of ACM and the equivalents just aren’t the same thing.
I think we made Slashdot. We ran this off of one of the first batch of cable modems available in San Diego at the time and well, as I recall it, all of a sudden the car just starts moving all over the place freakishly and then we lost all connectivity.
Fun times!
The format isn’t inherently flawed, though much like other less than perfect standards (I’m looking at you SMTP), the implementations frequently are.
And also, much like the author, I’ve been “professionally” dealing with data in all (most?) its forms for the length of my career (~25 years).
I let it expire.
I kinda like that if you want to reach me you at least have to Google my handle. Just about the right amount of indirection I think.
While we're reminiscing, the thing I remember the most from the late 90's is that it seemed no one knew what they were doing (or perhaps it was just me). The Internet opened up such a frontier in computing, for effectively hobbyists, as I guess we'll never see again. Perhaps that's why I don't recall thinking about what computing would look like in the 21st century--there was too much to be done right in front of my face!
EDIT: There's a mention or two of thin clients. I think only Sun thought that would work :).
Oh ok, I can think of one that actually worked out: Linux on commodity hardware in data centers. It became clear by 98 or so that the combination of Apache (httpd) on a bunch of cheap Linux boxen behind an expensive LB would tear down the Sun/IBM scale up model fairly easily due to both cost reduction and an improved resiliency. Of course there were MySQL bottlenecks to work through, but then memcache landed and pushed that off a cycle. Then there were the 64-bit AMD chips and a large bump in RAM density that pushed it back another. And then I guess true distributed computing landed.
On a lark ordered one. It's not the most _accurate_ clock, but rather the most _reliable_. Either way, seems like a fun weekend project!
Thanks for the push to lookup heathkit again (though this appears to be a reboot).
In a different lifetime I had a few bikes including a TL1000R that was just plain intoxicating to ride with aftermarket pipes.
There is no way in hell I could do that to my neighbors at this stage of my life, however, and I often cringe at the actions of my younger self. Nowadays, I refuse to even use gas powered garden tools for noise (and environmental) reasons.
Still, that was circa 1997 so, um, I forgot pretty much all the detail :).
ref: https://www.padi.com/courses/open-water-diver
PADI does emphasize that with an open water cert you must absolutely always remain above 60ft.
That’s what’s shocking to me the most about the article and some of the conversation here—many folks are talking about diving to crazy depths as if that’s normal.
I don’t know why that is, but I will agree with your general point as a result. Folks need to understand this is a dangerous sport and one that can easily kill you (though not by barracuda).
You're right that it was rare to get full 56Kbps especially on the early modems and especially on the dreaded winmodems (https://en.wikipedia.org/wiki/Softmodem).
All that said, I also seem to recall that at least in major cities 56Kbps never really went anywhere as cable modems started becoming widely available.
I dug this post up showing a service performing an internal auction of up to 530M advertising campaigns/sec on 88K CPUs in Mesos: https://medium.com/criteo-engineering/migrating-arbitrage-to...
We also ran HiveServer2 and the Hive Metastore in Mesos, though that wasn't super CPU intensive (that was a pain, but mostly due to our Kerberos deployment).
The general use case of Mesos/Marathon always worked for us just fine (self-executable JVM apps), though there was plenty of Mesos hate at Criteo (and eventually Kubernetes spun up, though I left about a year ago and don't know its footprint).
PS, Hi Greg S! Hi Maxime B! <-- if you're reading :).
This seems a fairly common refrain in the comments. Am I the only one who forgets things? I have to reread things to keep the ideas crisp in my head.
Oh well!
Ok, so wow! No! Definitely not the message I was trying to convey. I love books, have many of them, don't read as much as I'd like, but would _certainly_ love to have more of them memorized! I'm always jealous of those folks who can recite poems from memory and the like.
> "I write by hand. Using a typewriter will take me away further away from the essence of 'writing'" etc...
Off (my) topic, but because you brought it up, writing by hand does increase memory retention! (https://www.scientificamerican.com/article/a-learning-secret...)
> "Why would I email? Fax works fine for me and I get a hard copy" etc...
Well... I do have a very nice laser printer and tend to print whitepapers even though I have a really nice iPad to read them on.
So I guess all of the above could add up to me being a bit of a luddite, which I accept, but really I guess I was just expressing my way of retaining and improving my own knowledge of programming languages that I like. Hard copy reading, hand writing (which I don't actually do much of) and navigating scaladocs instead of tab-completion helps me do that.
As I also said, if my job depending on my coding output, I would absolutely use a full featured IDE of one sort or another.
Instead of auto-imports and auto-complete I was forced to have java/scala docs open for whatever library I was using. Beyond giving me better muscle memory for the core language libraries, this had the interesting side effect of only using well documented libraries.
The lack of jump-to-definition also made me think more about dependencies in the code I was writing since they would require a cognitive leap and reasonably heavy context switch. Since cross-file refactoring requires bash-fu and is also a heavy process, this furthered my desire to minimize coupling.
I can't say I'm more productive and if I were coding day in and day out for my day job I would probably still use IntelliJ (especially for large Java code bases that were crafted by advanced IDE usage), but I find coding to be a more holistic endeavor now.
Hmm... not sure I agree with this. A few points come to mind:
- Some portions of a project become hotspots at different times and have a natural code concurrency limit (it may not be 1, but certainly 10 people can't make changes to the same class or other critical code path concurrently)
- Onboarding is a real thing. It requires current staff to train newcomers, at the very least. At worst, they have to account for the newcomer's coding/architectural misses
- Communication and consensus building with more folks takes exponentially more time (or is it combinatorial, I can't keep that straight).
I also like to recommend Coders at Work by Peter Seibel (https://www.goodreads.com/book/show/6713575-coders-at-work). It's incredibly useful to read about just how different 16 ultra high performing software engineers are/were. Nothing prepares you for technical leadership better than understanding that.
EDIT: just saw that Mythical Man Month was added 1 minute prior to my comment.
> They even take about the same amount of syntax. ("__proto__" vs "blessed", "prototype" vs "bless").
omg, I totally forgot that (I left day-to-day JS use a good decade ago, sorry!).
It is flexible and fun and I do miss it.
True story: years of passing functions to other functions and map/greps made the switch to FP Scala (another language I fear will die) a lot easier!
Sure, but that doesn’t preclude that Chinese restaurant from having their own delivery function. Each Domino’s restaurant needs to be self sufficient as well. Googling “Chinese food near me” seems to provide the look up.
> Customers are no longer paying for the delivery.
Have you seen the charges from an Uber eats delivery? We stopped using food delivery services entirely and just pick up now to save the ~$20 overhead on dinner.
I was, a long time ago, a delivery driver for Little Caesar’s and it seemed to work out for everyone without any technology to speak of.
EDIT: I am aware of the three party optimization problem for food delivery services. In housing seems to simplify that problem immensely given there is no /fourth/ party trying to optimize it from the outside and take a cut in the process.
Google. Circa 2030.
I work for large adtech company in France and out here oncall is paid (even if you’re not called) and we never intrude on personal time unless there is a major disaster, and even then there are almost always enough folks being paid to handle the oncall event to take care of things.
We do have R&D offices in the US and I don’t know the specifics of HR policy wrt oncall there, but everyone rolls up to the French HQ so I know it remains human-first.
My advice is to ask questions and read up. You can ask trusted advisors/friends what to read up on before asking questions to the scary folks (who are usually not that scary anyway).
From where I sit I find that the Cambrian explosion of frameworks, systems and methodologies is causing us to regress in terms of productivity.
I think this is a reasonable generalization, though organizations can fight this tendency. I tend to think we do, though we have very specific initiatives to tackle this very problem.
> You clearly thrive in a big company environment, I definitely don't.
So “thrive” is a bit of a strong characterization, but I can say I’ve pretty well adapted to my current environment.
Please also don’t let me lead anyone to believe that everything is perfect in Big Corp land (here or anywhere I suppose). As you hint at, it’s all about the trade offs you’re willing to make at any given point in your career.
I guess that’s what I was mostly trying to point out in my original comment.