If you’re random Joe Schmoe who happens to need a database, I don’t expect you to contribute. But when you’re of the largest tech firms in the world…

Is kill -11 even allowed?

On the other hand, the OOM killer is worst of all: “kill process or sacrifice child.”

For the benefit of anyone reading this later, the function to check end-of-file should be feof, not foef.

It actually makes some sort of weird sense if you can get past the inconsistent labeling. Since it’s a daycare, each option is probably an enrollment period, and they are arranged in reverse chronological order. Still weird, but perhaps not as outrageous as it initially appears.

I know this will come as a shock to a lot of people, but a lot of software doesn’t do CI/CD. Especially CD. Basically only webapps can do CD, although Dropbox is close with weekly releases. A lot of enterprise and industry software still does quarterly or even semiannual releases. Hospitals, banks, and government agencies in particular have stringent vetting procedures that mean they can spend months verifying and approving a new major version before upgrading, so there’s no point throwing one at them every couple weeks.

Just what we’ve been waiting for!

Nonsense. The compiler can handle type-checking far more quickly and acurately than any code reviewer. When I review code, I want to look at code structure, algorithms, data structures, interface design, contracts, logic, and style.

I don’t want to go through your code line by line cross-referencing every function call to make sure you put the arguments in the right order and checking every member access for typos. That’s a waste of my time, and by extension, the company’s money.

That’s a great point. In any sort of enterprise system, you should be unit-testing your front end when you commit, and you should be UI-testing your front end before you deploy. If you’re in a CI/CD pipeline, that normally happens right after the build step. If you need to have the pipeline running anyways, you might as well build.

I’m on Hover. They’ll host and email inbox for you, but not a website.

Not quite sure what you’re looking for, but I think Dreamhost can just hand you an Ubuntu box you can SSH or SFTP to to manage your site.

NEMA has called them “plugs” and “receptacles” for decades.

You forgot “don’t say ‘thank you for pointing out that we were sending social security numbers to everyone who visits our website that anybody could stumble across,’ but rather ‘you will be prosecuted to the fullest extent of the law, hacker!’” Courtesy of the Missouri Department of Education.

I got news for you. If you’re not a citizen of the country you’re located in and you don’t have a work visa for that country, you’re probably working illegally, whether or not your employer realizes. (Some exceptions for EU citizens, Canada, etc.)

Re: too lazy for Let’s Encrypt, a) last I used LE (for my personal site), your site had to be publicly available on the Internet so that you could prove you controlled the site. Most test servers are not public. and b) many (most?) companies would throw a fit if you started generating your own certificates for their domains.

But there are always solutions. I was able to talk my company into getting properly signed certs for our test servers.

I’m not sure I want my banking apps to store anything on my phone in the first place. But maybe that’s just me. I don’t even use banking apps.

Rather than messing with the EventListener, wouldn’t it be easier to just throttle the function that it calls? You can find a bunch of articles online that will explain how to implement a throttle (and also a debouncer, which is similar, but not quite what you’re looking for; a throttle allows a function to be called immediately unless it’s already been called too recently, while a debouncer waits every time before calling the function and restarts the wait timer every time someone tried to call the function).

This 100%. Part of my job is writing test cases, which can be extremely repetitive. With multiple cursors, I can frame out a dozen or more cases simultaneously and then go through and fill in the details. It significantly reduces typing time.

Also, if you work with any sort of XML or HTML, learn Emmett abbreviations and learn them properly. It will take you an hour to learn them properly, but they save so much time over typing tedious tags longhand. Being able to type html>(head>meta[charset=utf-8]/+title{My page})+body saves so much time over

<html>
    <head>
        <meta charset="utf-8"/>
        <title>My page</title>
    </head>
    <body>

    </body>
</html>

That’s a harder proposition than you might think. On the one hand, UUIDs are mathematically guaranteed to be universally unique, which is great. On the other hand, there has to be some way to go from a UUID to a particular post, which suggests a lookup table, but the federated nature of Lemmy basically makes that impossible, since there’s no assurance that any instance is aware of any other instance.

The Danish word for 99 is nioghalvfems, which literally means “nine and half five.” Which you could be forgiven for assuming meant 11½. The trick is that a) “half five” actually means 4½, as in half less than five, and b) it’s implied that you’re supposed to multiply the second part by 20. So the proper math is 9 + (-½ + 5) * 20 = 99.