vrek

Personally I would prefer ham or bacon but I can deal with chicken...

Well if that's what you want it's in the wrong hole

That's actually really cool...

Ahh, ok yeah makes sense

I don't recognize the name, what dud facepunch make?

Yeah, my previous employer had shutdowns on the week of July 4th and Christmas so the production operators on contract(aka not paid for holidays) could volunteer to help in the counts.

I was curious if libraries have a similar system...

One time I was sick. I was stuck in the bathroom rotating between sitting and kneeling. I texted my team lead and said I couldn't come in and I was taking a sick day.

He responded by claiming I was lying and was not really sick. I responded with a picture of the toilet bowl after several rounds(unflushed).

He responded with "get well soon"

Out of curiosity do you have a routine to periodically (annually, quarterly, I don't know) to re-arrange books put back in the wrong place?

I know they do it in warehouses to verify like "system says we have 500 of x but we have 495. System says we have 1100 of y but we have 1132" and they correct all the counts annually.

Only reason I can think to do that is to "verify" the data in the pointer is not null/empty and is a valid int???

There are much better ways to do that but I can't think of any other intent the programmer had.

I saw a talk recently, I can find the video if you like but pretty sure it was the most recent ND conference, where they made the point that a lot of lack of efficiency in modern code is because of large companies. Basically in alot of cases it's more important to get a product out ASAP then to care if it was well done. Ok, a poorly written program may cost an extra $10,000 a month to run but if it earns them a million a month and saves 6 months of development time it pays for itself and they can eat the cost.

This seems like the case with renting vdis instead of fixing the program.

I believe so but I don't remember the exact encryption algorithm and don't have access to the code anymore.

This was the same place that had a 500 line file named glob_vars.cs which you can guess the content of because "passing around variables cause memory leak issues".