[-] alr@programming.dev 20 points 6 months ago

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

[-] alr@programming.dev 8 points 10 months ago

Is kill -11 even allowed?

[-] alr@programming.dev 29 points 10 months ago

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

[-] alr@programming.dev 3 points 10 months ago

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

[-] alr@programming.dev 2 points 1 year ago

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.

[-] alr@programming.dev 5 points 1 year ago

Just what we've been waiting for!

[-] alr@programming.dev 1 points 1 year ago

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.

[-] alr@programming.dev 1 points 1 year ago

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.

[-] alr@programming.dev 28 points 1 year ago

NEMA has called them "plugs" and "receptacles" for decades.

[-] alr@programming.dev 56 points 1 year ago

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.

[-] alr@programming.dev 3 points 1 year ago

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

[-] alr@programming.dev 1 points 1 year ago

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.

view more: next ›

alr

joined 1 year ago