alr

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

If you used regular filesystem moves, p4 may have registered them as separate deletes and adds. Depending on workspace configuration, Perforce may not propagate deletes from the depot, so old copies might be left behind. Always move files in a workspace using P4V, your Perforce plugin, or the p4 mv command to ensure file continuity. If done properly, this will appear as add/move and delete/move.

But if things aren’t showing up in new places, it’s likely you referred some things you didn’t mean to or didn’t commit everything. Check to see if you still have anything checked out. Also worth noting that empty directories don’t exist as far as Perforce is concerned.

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.