The typical "30% on income" advice is based on gross, not net. Which is about 93,000 a year for the median mortgage payment right now.

All milk has lactose, which is sugar.

It doesn't destroy their brain (though screens for newborns can mess up eyesight development), but it also doesn't provide any benefit at an extremely crucial time in their development. It definitely shouldn't be something they're doing frequently for long periods of time since that comes with a very real opportunity cost.

That's quite the claim. Do you have an example of NPR espousing the same points that Fox News is?

Definitely agree with that. I always thought that people that do that have hang ups that they just need to get over. My wife and I are a team. My success is hers and her success is mine. We share all debts, including those from before we were together.

I've been using vim as my daily driver for development for the last 8 years.

There are a million things I could talk about regarding vim's editing language, consistent interface, scriptability, performance (seriously, I've opened 1GB+ files and vim barely breaks a sweat), etc., but one thing I'll highlight that most people don't talk about is vim's ability to interface with other tools. It's what takes vim from a great editor into a full-fledged development environment. You can:

• Read the stdout of any shell program into a vim buffer (:help read !)
• Use the contents of a buffer as stdin to any shell program (:help write !)
• Filter a portion of the buffer through any shell program, replacing the contents with that program's stdout (:help !)
• Parse the output of a program or the contents of a file into a set of entries for quick navigation (:help quickfix, :help make)
• Insert the output of a shell program into the current buffer (:help <C-R>=, specifically when used with the :help system() function)
• Control arbitrary jobs with vimscript and communicate back and forth with code

And much more. I use all of these every day: the output of git commands give me filepaths I can jump to with gf; a range in vim selected with the v command gives me line numbers to pass to git log -L to see the history of a section of code; the current filepath of the vim buffer is pass to many different shell commands to do processing with that file; the symbol under the cursor is passed as an argument to the open command on macos to lookup external (company-specific) documentation in a Web browser. And many, many other things. Unix is my IDE, and vim is at the heart of it.

It's definitely not great here at all, though I'd say it's a bit different for professional software developers (who probably make up the bulk of contributors), since that kind of job tends to give you better benefits. In my experience, it's typical to either have unlimited PTO (that you may or may not be able to take, admittedly, though I've never had an issue with that), or at least a couple weeks of vacation a year. I've never worked anywhere as a software engineer where I had to really even account for sick time at all. I just tell my team I'm sick and that's about it.

Zalando explicitly forbids it in their RESTful API Guidelines, and I would say their argument is a very good one.

Basically, if you want to provide more fine-grained semantics, use dedicated types for that purpose, rather than hoping every API consumer is going to faithfully adhere to the subtle distinctions you've created.

That doesn't sound right. Is everyone in Sweden drinking untreated water? That sounds incredibly unsanitary.

1 Is pretty standard in the industry for people with experience. I haven't actually applied to any jobs myself in a while. Job hunting for me is sifting through the recruiter messages that hit my inbox.

I don't want squashed commits. It makes git tools worse (git bisect, git cherry-pick, etc.) and I work very hard to craft a meaningful set of commits for my work and I don't want to throw all of that away.

But yeah, I don't actually give a shit what they are doing on their branches. I regularly rebase onto master anyway.

Agreed. It's annoying for sure, but OP is insane. Even if it's stupid, there's absolutely nothing about it that indicates negligence of anywhere near the degree needed to justify forcibly removing a child from their parents.