Being fat is a disease now? Seriously?

Apparently, now obesity is being classed as a “disease.”

Pardon me but, what the actual fuck?

Why is this a disease? Yes, I know, for a small set of obese people, it’s an honest medical condition, but the other 29.5% of Americans that are obese? That’s not a disease, at least, not a physical disease.  A social disease, sure.

If it was a real disease, I’d expect to see the same obesity rate in other countries, and you know what? You don’t. Not even close.

So, with my advanced degree in fat-ology, here’s the *real* cause of this obesity epidemic.

I’M SO HUNGRY

That’s how you do a recall

To be clear, the Model S does not need to be brought to our service center by the owner. Tesla will pick up the car at a location of the owner’s convenience, provide a Model S loaner if needed, perform the work and bring the car back to the owner a few hours later.

via

Talk about an interview red flag

So, I just read this article from Venturocket (what a stupid ass name), titled “The one job interview question you need to ask to find your A players

The the “A player” question they came up with?

Are you willing to work nights and weekends to get an assignment done on time?

What the actual fuck?

That’s not a “A player” question. Obviously nobody looking for a job is going to say “no” to that, duh.  Before you, theoretical hiring manager, ask that question, think more about what it says about your own culture.

It says to me, potential hire-ee, “Expect a lot of hours as a normal thing, with little to no appreciation, because we think ‘A player’ means ‘has a shitty work/life balance'”.

A real, actual, honestly good place to work that gets tech workers would ask something more like

Do you have a hard time just stopping when something’s half done?

Or

Does the code keep you up at night, sometimes? And not because it’s shitty.

I’d never work for a place that would ask me a question phrased like that.

Writing documentation is the worst thing ever

I hate writing documentation. It’s one of those things that’s awful to do, and it’s awful when you don’t have it.

Being a developer, it’s double icky (technical term).  In the first part, I hate writing it. It’s time consuming, it’s a pain to keep up to date, it’s hard to write good documentation, etc, etc.  On the other hand, as a developer, I use a lot of other people’s code.  When I do that, I want to be able to use it as fast as I can, and get on with my life. So I really hate it when the documentation is trash.  It makes my job harder, and things take longer.

I’m in the midst of this cycle now.  At work I’m creating an API that I won’t be directly using, so the documentation is aimed at our other developers.  It has to be accurate, and let them move rapidly.  It’s a giant pain.

I’ve been researching ways to make it easier for me, and better for them.  Take a moment to appreciate the irony (or whatever it is). I’m looking for a library to help me make documentation easier, so it also has to have good documentation.  DOCUMENTATION-CEPTION *bwwwaaarrrrr*.

I’ve mostly settled on apipie. It’s does a decent job of getting out of my way, as the code for the documentation (it’s a documentation generator, essentially) lives right next to the code it pertains to.  It also can serve the documentation up to consumers along side your application, which is nice, although we won’t use it like that.

For all that, I still hate it.  I wish that computers were smart enough, or that somebody had made them smart enough to just look at my code, and make some documentation. I don’t care if it did everything but write nice descriptions about parameters and junk.  If it just put it in a framework that I could add the nice english into, and kept it up to date, I’d be so happy.

I might even pay for it.