cballard

OK Cupid also has questions covering:

- Evolution.

- Whether or not dinosaurs were a thing.

- If the Moon landing happened.

- The relative size of the Earth and the Sun.

- If Astrology is scientifically accurate.

... among others, all of which I had marked, with the correct answer set as "mandatory". If someone answered enough of these with the wrong answer, you won't even see them (if you do, you'll have a high "enemy" percentage), so you won't waste your time talking to them.

Maybe this is not really an issue for homosexual couples, but I would never have considered Tinder because unlike OK Cupid, there's no way to filter out Republican-hates-the-gays-hates-abortions types. The question/answer filtering and profile text was the most important part of online dating to me.

C# and Java optionals aren't very useful, since they would be reference types themselves, and thus could be null!

I would submit Rust and Swift as "decent" type systems, if Haskell is the standard for "good". They do nullability correctly, but lack HKTs.

"Decent" is being very kind to any language that has a type system where every reference type is implicitly a Maybe (okay, Scala exists).

GitX is my favorite, despite being quite buggy, because the others I've seen are all way too complicated.

I really just want visual log and visual add -p and GitX nails that.

The author of NSHipster works for Apple now and typically, Apple employees don't blog about work - possibly a policy?

If you call 311, TLC will slap a $300 fine on them, so taking out your phone and doing that will instantly fix the machine.

It's really not an issue in New York. 311/TLC doesn't mess around with this.

There are so many cabs that I don't really see the need for this, and most cabs take Apple Pay now, so I've never really seen the point of this and the other one (is there another one? I think there is?).

If I was somewhere where there aren't a lot of cabs I'd probably just use Uber, it's cheaper and cleaner anyways.

In New York, taxis are required to have functioning credit card machines.

http://www.nyc.gov/html/tlc/html/passenger/passenger_creditc...

Small PRs are an issue because PRs are dependent on other users and can't be dependent on a prior PR.

Let's say we're adding an interface/typeclass/protocol and a concrete implementation. I'd say these should be two separate commits, as they're adding two different things. An interface doesn't require a provided implementation to work. But, if we were to create those as two separate pull requests, it would be more work for the project maintainers, and the initiator wouldn't be able to create the PR for the concrete implementation until the interface PR was merged - the concrete PR can't be added as a dependent PR of the interface one, or something to that effect.

Since you can "compare" almost anything on Github, small commits aren't really an issue, just view a larger-scope comparison to get an idea of the whole PR.

Another way to put this might be that commits are for individual code changes that build up to a pull request, which is a conceptual change?

This is a bad idea masquerading as a good idea. Before making a pull request (or doing any sort of merge), you should rebase against upstream master (or whatever you're going to push to). However, keeping distinct atomic commits that change one and only one small thing, when possible, is much preferable if bisect or blame is used. If you have broken or poorly written commits, use fixup, reword, squash, etc. in rebase -i.

Using fast-forward (and possibly only allowing fast-forward) is a good idea. Squashing entire pull requests that may change multiple things into a single commit is a very bad idea.

I'd shorten that to:

> Contrary to what this VC believes, it is NOT okay to expect someone to "work 60 hours a week at Facebook"

Let's get one of these already https://en.wikipedia.org/wiki/Working_Time_Directive

To be clear - this is a bike lane on a road with onramps? Uh, what? There aren't even bollards (in the part without an onramp, obviously) or any semblance of protection.

Non-"blatant spam" email advertising really isn't better. Purchasing a product from almost any non-Amazon company will instantly sign you up for an almost daily torrent of email.

Even worse is when you're automatically signed for dead trees being sent to your house, because those don't have unsubscribe links.

It's crazy. I already bought the thing! I don't need more things, or else I would have bought them when I bought the original thing. Yet, companies are treating their customers - people who have actually already bought things - in this terrible manner. Maybe we need legislation mandating opt-in?

Using a language in which 1 + "1" == "11" instead of one of the best type and null-safe languages to be developed in the past few years is not exactly my idea of a delightful experience, but interface as a pure function of state is a good idea.

In this case, though, as I understand it (I live in NYC and am thus not the target market for these types of products besides maybe lightbulbs), Apple's solution, HomeKit, does allow interaction between disparate products, and it's even the banner feature!

https://www.apple.com/ios/homekit/

You can also use .json (for almost every Reddit URL, actually!)

Both you and the OP are incorrect. The file is not included in the app (only referred to), but is only downloaded by iOS itself - or anyone who points a web client directly at it, of course.

> "HubSpot and John have decided to go separate ways"

That's not much better. It's very rarely mutual. Either John has been fired, or John has found another job - perhaps at a company where no one lights cleaning equipment on fire - and is quitting.

I have dogs in my office. They run around and bark all the time. Their presence shows to me that serious engineering work is not important, but the image of being a "startup" is. The idea of a musical instrument being played while I am trying to focus on engineering is horrifying.

There's also a whole world of potential designs besides "drab cubicle farm" and "kindergarten mashed-up with ComicCon". For example, the 37signals[1] office.

If they want to show effort and interest in the workplace environment, they should try providing private offices with doors that close.

[1] https://37signals.com/office

> play table tennis daily

Do you still leave 8 hours after you arrived, or do you add the table-tennis time? If so, do people that do not play table-tennis leave 8 hours after they arrived, and, if so, are they viewed negatively by those that do not (even if the people viewing them negatively spent two hours playing table-tennis)?

How much does your company spend on beer? Would you not rather have that as salary, which you could spend on intoxicating liquids if you wanted, but also spend on travel or things for your apartment if you wanted to do that instead?

Wearing headphones every day will permanently damage your hearing. If you really want noise, put on headphones. Respectful quiet should be the default.

An eight and only eight character password? Less security than a social network, all aboard the American banking system!

> Why work for peanuts of a salary when you can make way more in tips?

This is why they won't pay servers minimum wage (i.e. Danny Meyer doesn't).

Europe doesn't have tipping and service is perfectly fine -actually, better in many cases, in my experience they bother you much less, and there's no aggressive pre-bussing because unless it gets to the point where the business fails, table turnover doesn't matter nearly as much to the employees.

This is illegal, in New York at least. The employer cannot take the worker's tips.

I think that bad group chat behavior (which is encouraged by the UI of group chat applications that I've used) and dress codes both fall under the same category. They make me less productive, which generally translates into longer hours and more stress.

I like strict workplace policies iff they actually improve my productivity. Otherwise, they are harmful.

I wonder if there's an overlap with people that like strict static compilers that scream if anything is even remotely incorrect.

Does NPM offer a way to check in your resolved dependencies? While it would brick updates to dependencies, new clones and builds would work fine.

That is the "limited multitasking". You're limited to two, your ability to view information is arbitrarily limited by the application displaying that information.

Want to view two emails side-by-side? Use two emails apps, I guess.

I'd argue that an open office, in the absence of strict library rules, is analogous to an all-day meeting, e.g. "quick question!".

Meekan looks interesting, and they have the idea right (since as a third-party they are limited), but it's a plugin, and it's a bot[1]. Scheduling would be a core concept of my theoretical group-chat app - something you were incredibly encouraged to do by the interface, instead of bothering an arbitrary number of people that are probably trying to focus.

[1] the problem with bots is that it pushes stuff that ought to be "interface" into public view, with all of the notification and visual noise baggage that is implied by that.

Date/time localization should just work, here Amy needs to manually ask for it, and everyone else is notified that she did! And that doesn't even cover language localization! If I'm having a meeting with a colleague whose English is weak and prefers Chinese, will it just drop even more noise into the chat when she requests a translation?