456 karma · joined July 21, 2022
Might have been in the c++ Users Journal or Dr Dobbs in the late 90s.
Personally I appreciated the flexibility to work and leave early.
To be fair, it did seem like the artists did get some benefit, but it was definitely a net negative for most of the developers.
I’ve been in private offices, and cubes, and open office, and honestly the most productive environment was when I was in a set of cubicles that had sliding doors, around a bullpen with multiple tables. When you needed to go head-down to get some code down you could, but otherwise you hung out at the tables in the middle.
The first time I looked at it, I saw that the make file set the warning level to 0 and redirected the output to NUL. Removing that, I ran nmake and prayed. About 45 minutes later it finished building, evidently successfully. It turned out that having the warnings actually print added 10 minutes to the build.
It was averaging more than one error per line of code at /w3. And it was around 40k lines of code. Not large by the standards of today but huge back then for MSDOS. Peeking, it used K&R c and included no header files. So step 1 for me was to hook up some scaffolding using various tools from mks to make sure as I edited things that the error count didn’t increase.
The biggest thing I learned from this project was to not combine other coding with the warning removal or other cleanup. Makes it much easier to spot when you introduce bugs.
cat “filename.txt”
Up | grep “thing”
Up | grep -v “not thing”
Up | grep -v “other thing”
Etc. it’s just easier to build this way even if the initial cat is unnecessary.
We didn’t get the cameras for security, we got them to watch the feral cats in the area to help catch them for TNR, but security is a nice extra, so we are considering replacing the Rings with something wired.
The problem is twofold - one issue is there is a lot of the real estate tied up being used only during the cold weather months from snowbirds. The population goes up by roughly a third then. The other issue is folks moving here from other states, primarily California. The influx has greatly exceeded the rate of new construction.
I like to say that I have 5 years experience in everything, over the last 35 years, but two of my last three jobs have involved modernizing old codebases, mostly in perl, moving them to modern languages and the cloud, with a short stint in SRE in the middle. I'd love to find another job doing that, or possibly someone who isn't very far along in their DevOps journey, where I can add a lot of value quickly.
By the mid 90’s they were all gone, smoking moved outside.
Then we got acquired by Zynga and that business got sold off.
I do tend to eat more candy tho than I did on other diets - several times a week I will get the feelings of low blood sugar, and a few bites usually fixes that without affecting weight loss.
There’s one reason - from experience, it’s a lot easier to find a job if you are currently employed. So if you think you will likely be a target in round 2 or 3, the rational thing to do is to try to stay employed as long as possible and switch jobs quickly. Also, the severance tends to get worse with each round. I saw one job where round one got 3 months severance plus a week per year, with insurance, round 2 got a month, and round 3 got 2 weeks. I found new employment between rounds 2 and 3.
It seems like there are quite a few people here who have never experienced a tight labor market.
The very nice 911 operator told me it happened all the time. After the second time it happened I tracked down the setting to disable it.
You can actually set up a situation where one player is guaranteed a win, which is why the systems will require at least two players.
I spent a couple of years in the mid-2000s working in the edges here, so I have a bit of knowledge. Note: I've been out of this industry for at least 15 years, so some of my knowledge might have aged, but I'm fairly certain that it's still true in the general sense.
First, under federal regulations, there are three classes of gambling. First, class I, which is basically, "I make a wager with you over the outcome of a sporting event". So if I'm playing golf with you and I bet you $10 a hole on outcome, that's class I. It's not regulated at federal level, and not generally regulated at state level.
The next class is Class II. This covers things like raffles, and mid-week church bingo. There are some limits, but it's not regulated by the states generally, and not by the feds at all.
Class III is what we think of as traditional gambling. Table games, traditional slot machines, etc. This is absolutely regulated by the states, and only allowed if the states allow it. This is what your Vegas and Atlantic City casinos operate under.
But there are Indian casinos outside of this in these markets operating. How do they operate, you ask? The simple answer is, if the games are operating as Class I or (more likely) class II games, the states have no say in them. And it's very easy to make a lotto drawing, or a bingo card, appear as a slot machine play. All random wins are basically equivalent to each other. If you go to an Indian casino, and you want to play a slot machine, but it's requiring you to wait on another player, you're dealing with a class II machine.
What about class III? Well, states are allowed to negotiate compacts with the various Native American tribes where they allow them to conduct class III games. A number of states have done this. This allows them to run, say, blackjack and poker, as well as slot machines that don't fall under class II. Interestingly, in a lot of jurisdictions, you're still basically following the ideas of class II, but just not requiring competition. So if you go to a casino in Oklahoma, you'll see that you are (most often) playing a game of instant bingo on each spin, or possibly a game of instant lotto on each spin. Because that's what the compact between the state of Oklahoma and the tribes there allows.
But there are still loopholes that allow you, in some jurisdictions, to run slot machines outside of these provisions. Let's say, you're allowed to run raffles that allow up to a $1000 prize on a $1 entry. These are just numbers to use to illustrate the concept, and they vary state to state. So I set up a slot machine that you pay $1 a spin, which is an entry in a lotto that pays maximum $1000, and after the total number of tickets allocated is depleted, will pay the house 10%. Perfectly legal, though local law enforcement in the bible belt in the south may disagree. I've coded a number of systems that implemented exactly this.
Other jurisdictions may allow you to have prizes up to, say, 25x the entry on machines, to allow the legality of the claw machines. This can also be (ab)used to make slot machines.
It turned out that the lawyer next door would come in, turn on his PC, printer and coffee pot simultaneously because they were all on the same power strip, and the drain was causing an undervoltage on the circuit the server was on during startup. We had it on a UPS, but it turns out that at the time consumer grade UPS systems only handled outages.
I measured drops as low as to 85 volts, in practice anything under 95 or sou would reboot.
Times sure were different then.