HNHacker News
TopNewBestAskShowJobs

jqcoffey

1,243 karma · joined May 25, 2016

submissionscomments
jqcoffey··on Vintage Byte Magazine Library
I know we’re a small community overall, but I’m really (probably naively) surprised that a publication like Byte is no longer viable.

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.

jqcoffey··on The first webcam was invented to keep an eye on a coffee pot
Ah fond memories of my roommate and I (circa 1997) hacking together a webcam of an RC car in our backyard. It involved me writing some sort of perl script to pipe the low-res jpegs dumped from god knows what camera to I honestly can't remember what sort of web resource (maybe I transcoded the jpegs into an endless streaming GIF?) and my roommate doing the dirty work of bit-banging some kind of rs-232 connected servos to wire the remote up to the server (which I then hooked up via some perl scripts to our webpage).

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!

jqcoffey··on Time to retire the CSV?
I’m going to cite “worse is better” in disagreeing completely with the author. CSV has won because it’s easy to generate, easy to read as a human, easy to parse with standard tools (when generated correctly), and really the last point is the salient one.

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).

jqcoffey··on Strange domain names that developers bought
Years ago, in my younger, I thought I was extremely funny days, I bought yomamashouse.com simply so I could own the email address of im@yomamashouse.com.

I let it expire.

jqcoffey··on Build your own SPARC workstation
Ironically, I got into the sysadmin (and later programming) business because a wise coworker of mine told me to stop mucking around in Windows 95 and grab the Sparc LX in the corner of the shop and install RedHat on it.
jqcoffey··on Tell HN: Consider listing your contact details
My handle pretty much unmasks me. I was pinged at work as the result of a post or two (thankfully in a good way).

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.

jqcoffey··on Ask HN: 90s programmers, what did you expect the future of tech to look like?
Lot's of good stuff here, but I'll admit I can't remember a single "prediction" of my own. I just thought everything would keep going in the same direction, faster CPUs, faster network, cheaper disk and RAM, more e-commerce and more information exchange were the expectations I can recall.

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.

jqcoffey··on The Heathkit Legacy (2013)
Of note: https://shop.heathkit.com/shop/product/most-reliable-clocktm...

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).

jqcoffey··on Yamaha MOTOROiD
Or, more generously, just young and immature and not completely cognizant of the impact of your actions on others.

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.

jqcoffey··on The Blue Hole in the Red Sea is the deadliest dive site in the world
Yeah, that's crazy too. Maybe I have rose colored lenses because I did my advanced open water through my university and we did tons of dives to the same spot with I guess more academically focused exams and whatnot.

Still, that was circa 1997 so, um, I forgot pretty much all the detail :).

jqcoffey··on The Blue Hole in the Red Sea is the deadliest dive site in the world
> As a PADI Open Water Diver, you'll be trained to a maximum depth of 18 metres/60 feet, and are qualified to dive in conditions as good as, or better than, those in which you trained

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).

jqcoffey··on Dr. Quinn official website from 1998, still online
If memory serves 56K was pretty widespread in _availability_ by 1998. I worked at a small local ISP in San Diego from 95ish to 97ish and they were available at the tail end of my time there.

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.

jqcoffey··on Apache Mesos to be moved to Attic
There must be some folks from Criteo lurking here. I'm an ex-Criteo'er and if memory serves we had something on the order of 10K nodes running mesos/marathon. We did all kinds of silly things to it, like running very CPU intensive .NET/Core apps.

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 :).

jqcoffey··on Some Were Meant For C (2017) [pdf]
Isn't OpenBSD written in C? w.r.t. "unsafe", just sayin'.
jqcoffey··on Achieving 11M IOPS and 66 GB/S IO on a Single ThreadRipper Workstation
Also, purpose built data center chassis are designed for high airflow and are thus really quite loud.
jqcoffey··on Steve McConnell
> Reading these books after 20 years of programming I found that I really struggled to find anything useful to take away from them.

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!

jqcoffey··on Switching from Vim to Intellij
> That sounds awfully close to "books will ruin the world. If people stop memorizing their scriptures they'll stop believing" and complaints against progress.

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.

jqcoffey··on Switching from Vim to Intellij
Once coding no longer was on the critical path of my employment (as a middle manager in a large tech company) I went back to vim from IntelliJ with nothing more than syntax highlight and autoindent. The reason? I wanted to know my programming languages better.

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.

jqcoffey··on Classic books for tech leads or those aspiring to be
> Brook's law is also outdated. It's mostly only relevant for when you deliver your software with a forklift.

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).

jqcoffey··on Ask HN: What makes a good technical leader – any recommended books?
Ah, that's good to know. Thanks!
jqcoffey··on Ask HN: What makes a good technical leader – any recommended books?
Crazy that no one mentioned the Mythical Man Month by Fred J. Brooks (https://www.goodreads.com/book/show/13629.The_Mythical_Man_M...). I thought it was the definitive classic.

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.

jqcoffey··on Perl 7 is going to be Perl 5.32, mostly
> Did you know JavaScript classes are blessed hashes?

> 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!).

jqcoffey··on Perl 7 is going to be Perl 5.32, mostly
Ok, so I wrote tons of Perl and am to this day a fan, but I don’t think one can call a blessed hash (or scalar for the fancy folks) an object _system_.

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!

jqcoffey··on Our restaurants are failing. Why should food delivery apps thrive?
> Location. Dominos has been within 10 minutes of everywhere I have ever lived or vacationed. My last order of Chinese food came from the other side of the city.

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.

jqcoffey··on Our restaurants are failing. Why should food delivery apps thrive?
The question I keep asking myself is, if Domino’s can be their own delivery system and now most restaurants are 100% delivery why can’t they do the same thing?

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.

jqcoffey··on I Miss Microsoft Encarta
> Makes you wonder, will there ever be a replacement for the Internet?

Google. Circa 2030.

jqcoffey··on Yelp Fired Manager After He Didn't Take Calls, Check Email 24/7, Lawsuit Claims
I am the manager of a decent sized R&D org in a company on the order of Yelp’s size and not only do I find this inexcusable on Yelp’s part, but where I work we would put the firing manager into a training/coaching program to sensitize him to the work life balance needs of his team. If he refused he would probably be removed as a manager and perhaps shown the door.

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.

jqcoffey··on Ask HN: How do you get over the initial fear of learning something hard or new?
We have this problem all the time where I work. It usually manifests itself as a “slow engineer.” When you dig a bit that usually means the engineer in question is afraid to ask questions, generally out of fear of looking silly.

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).

jqcoffey··on Ask HN: What big programming productivity gains you see happening in 5-10 yrs?
A quick scan through the comments and I was surprised that no one referenced the No Silver Bullet essay[0].

From where I sit I find that the Cambrian explosion of frameworks, systems and methodologies is causing us to regress in terms of productivity.

[0] http://worrydream.com/refs/Brooks-NoSilverBullet.pdf

jqcoffey··on You Weren't Meant to Have a Boss (2008)
> You will learn a lot about a very narrow area. Working in a small company gives you a much broader experience, both of the technology and business.

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.

← PreviousPage 2 of 3Next →