ismarc

16 year old me had no clue, no help from parents or other adults and teachers that disallowed all calculators that weren't the required ones. I learned about they books of tables from an old man who helped me withmy homework I was doing at the public library, it's likely the only way he knew how. Not to mention, my main source of food during this time was the free school lunches and I was working 3rd shift to help pay rent and utilities, $5 was a lot of money (to us at least, this would have been mid 90s).

I was in the required but too poor group. I had to borrow others or do the work by hand. I eventually was able to get gifted one from one of those "help families in poverty with school supplies" donation drives. I had those books with tables of logarithms and one other one constantly checked out from the public library just so I could do my homework.

I can confirm it's drilled into Army soldiers as well, so I'd bet on the air force and navy being the same way.

I sometimes lose words. Like chair disappears from my mind, I can describe one, I know what one is, but the label for it is gone and even if you say it I may or may not recognize it. I don't have dyslexia, but a mental health issue that causes it. The funny part is names do the same thing, they're labels for specific people.

You are grossly misrepresenting the situation and what your own link says. If wages + tips don't equal the normal minimum wage of $7.25, the employer is required to make up the difference.

They get, at worst, normal minimum wage.

My 2011 only has the gas gauge, without any gallon markers on it and numerous 2016/2017 cars I've been test driving haven't had it. It's certain classes of cars that have had it for quite a while, nowhere close to all.

You're showing your ignorance of what it's like to be poor. It takes time and money to get to those locations, two things the poor don't have. The bus trip, or train, or gas in a car that's used has to cost less than what the app would gain them and that money/time needs to not be slotted for anything else (such as making it to and from jobs until payday).

Someone elsewhere in the thread said that the poor aren't good with managing money. From my experience, it's the opposite. Imagine you're behind on every bill, with less money coming in than it costs to have electricity, get to and from work, eat and pay rent. You literally rotate which bills get paid based on what will be shut off next. If someone gives you $100, you could pay more of the bills, or put it in savings, or spend it on entertainment/something fun. In 3 months, no matter what happens, you'll be back in the same state you are now. Spending it on entertainment to feel like a person isn't a bad decision at that point. It's just not one that those who live privileged lives would make

Our use-case is different (not cassandra or db hosted on ephemeral drives), but what we've found using AWS for about 2 years now is that when an availability zone goes out, it's either linked to or affects EBS. Our setup now is to have base-load data and PG WAL files stored/written to S3, all servers use ephemeral drives, difference in data is loaded at machine creation time, AMI that servers are loaded from is recreated every night. We always deploy to 3 AZs (2 if that's all a region has) with Route 53 latency based DNS lookups that points to an ELB that sits in front of our servers for the region (previously had 1 ELB per AZ as they used DNS lookups to determine where to route someone amongst AZs and some of our sites are the origin for a CDN, so it didn't balance appropriately...this has since been changed) that is in the public+private section of a VPC with all the rest of our infrastructure in the private section of a VPC (VPC across all 3 AZs). We use ELBs internal to the AZ for services that communicate with each other. The entire system is designed to where you can shoot a single server, a single AZ or a single region in the face and the worst you have is degraded performance (say, going to the west coast from the east coast, etc.).

Using this type of setup, we had 100% availability for our customers over a period of 2 years (up until a couple of weeks ago where the flash 12 upgrade caused a small amount of our customers to be impacted). This includes the large outage in US East 1 from the electrical storm, as well as several other EBS related outages. Overall costs are cheaper than setting up our own geo-diverse set of datacenters (or racks in datacenters) thanks to heavy use of reserved instances. We keep looking at the costs and as soon as it makes sense, we'll switch over, but will still use several of the features of AWS (peak load growth, RDS, Route 53).

The short answer is to design your entire system so that any component can randomly be shot in the face, from a single server to the eastern seaboard falling into the ocean to the United States immediately going the way of Mad Max. Design failure into the system and you get to sleep at night a lot more.

You've obviously never had any real interaction with someone in the grip of a mental health emergency. She was put on suicide watch and evaluation, not because it's just fun. She cut the shit out of her leg, to where it bleed through, had repeated, documented thoughts of suicide and then tried to just pretend everything was OK. The first night was emergency care, i.e., make sure she didn't die. The next days were mental health evaluation while making sure she didn't die. You cannot be forcibly admitted in the U.S. she admitted herself. She did not have to stay after the first night, but they will make you think you do because they want you alive and to help you get better. It's not some giant conspiracy to do harm to people.

Does mental health services suck pretty much everywhere? Yes. But nothing she went through was inhumane (I've been through similar scenarios in less pleasant medical facilities) and all of it is geared to try and help.

I was on a medication that did something similar (I believe it may have been depakote or gabapentin). Thing is, I have absurdly good relative pitch, and combined with an 'internalized' sound of 60Hz (I've worked around a large number of generators and high voltage equipment over the years), I have the same net effect as perfect pitch (60Hz is roughly a quarter step above B-flat, a quarter step below B).

What bugged me was the intervals were off. It's hard to describe, but, for those not familiar with how the notes are laid out, 60Hz is quarter step below B, 120 is quarter step below B, 240 is quarter step below B, and so on. However, as you get higher, the frequency difference gets larger (B is actually 61.75ish Hz and B flat is 58.25ish Hz, next higher is 123.5ish Hz and 116.5ish Hz, and so on). Things were translated ~1/4 octave higher, which completely threw everything off because the 60Hz sound no longer fell evenly between two notes or even directly on a note, it was an 1/8th step away. This meant that as the notes got further away from 60Hz (higher or lower), the distance to the note got larger. So while everything was still evenly in tune, my guidepost began to really suck.

Long story short: I have no idea why it did what it did, but it was freaky. However, it was probably the most amenable side-effect I had from the medication.

When I first used oop, or any object orientation, it was in the early days of the public internet. There wasn't nearly the resources available now, especially for a hobbyist. So when I learned the syntax (I believe it was early c++), I had nothing else to go on. I naturally leapt to using objects to describe and build new data types. It made me think about what data I needed, then how the data needed to be operated on. It wasn't until I started taking courses that I heard the noun approach... And it just seems completely backwards. It isn't about modeling your data, it's about the conceptual items you're working on. I still think oop is a good approach if you ignore all of the 'best practices' and instead use it to build custom data types that simplify your algorithms. It's part of what I really like about Erlang records (even though they're a bit annoying to use) and Scala in general. You can build custom data types without having to just compose lists and maps but you get a lot of the benefits from functional programming.

I really don't understand why so much of the programming classes, tutorials, guides and common wisdom aren't 'data first' style design.