mega_dingus

I've known Rick since 2001 and was around when he & Todd kicked this off. We've both since moved and it's been a pleasure watching this take off (inter)nationally. In parens b/c I can only verify the "national" part, personally. :) I look for them whenever I visit new places

"old-person tiktok" is what my kids call instagram

Oh to remember mid-90s humor

How many Intel engineers does it take to change a light bulb? 0.99999999

Didn't read the whole comment did you?

It's about TCO and time to market. Depending on what you're building, it's all YMMV. This article just quotes some individual costs

As somebody who worked at a mid-tier company trying to run databases, I can attest that RDS was a godsend. Trying to hire both a DBA and an Ops team that knew how to write the chef cookbooks for a proper multi-node cluster postgres was a nightmare. Like, we never succeeded, and something that's ootb with RDS

You must not forget that also, many (most?) companies that run things themselves do not do it right. Like, with proper off-site backups that you're regularly testing and know you have options to easily spin up replicas or restore point-in-time backups

Jeff Atwood's been saying this from the initial SO podcasts from 2008. If you have the right people who are motivated, and provide the right equipment and resources, you've always had the opportunity to have lower TCO doing it yourself

I have since moved on to a small top-tier company and still prefer to "outsource" my DBA work by way of using Aurora. Yes Aurora is more expensive. No, I don't have the mental or monetary budget to hire up a proper ops team. I know my limits

This is not the way you're supposed to be using pyenv

You're supposed to install a specific version of python in a specific place, with a specific name. Say, /usr/local/python-3.10.6

Use pyenv to use that python. Control that by creating a `.python-version` file that says 3.10.6

You now have a project that uses 3.10.6. Unless, of course, somebody installs a different version in that path - at which point you've got bigger issues

Using pyenv to use `/usr/bin/python3` and hoping for the best misses the point

I was talking to somebody who worked HR at a multi-disciplinary shop, and she said you could always identify the emails coming from programmers

It was a complaint, definitely not a compliment. She said programmers listed things out in bullet points and bluntly to-the-point. She complained they were dry, intimidating, and she hated dealing with them

I still write concisely and with bullet points, when writing to other programmers. But I now expand things when talking to everybody else. And I've found I get better responses

Why is this downvoted? I consider it and its replies interesting and relevant

If there's an HN policy violation in this post, I'm legit curious what it is

The linked article explains exactly this

You keep referring to that comic. I do not think it means what you think it means.

Compiler was definitely somewhat to blame. I was on the C/C++ team at the time, and C++ was definitely an afterthought on the existing C frontend, of a big 3-stage compiler

I was on Digital UNIX so I didn't deal with VMS or Windows much. But Digital UNIX couldn't get out of their way with object file formats (COFF vs ELF and whatever else), on top of the compiler inefficiencies

A recipe for disaster when the MS company employee doesn't want to do it in the first place, and you give them an artisan product that's hard to use properly