marktani

> In the long run the non-release repository states don't matter that much either

That's not true. Many a times I needed to comb through old commits for debugging purposes.

Also, with multi-branch development, you often have many non-release branches that are relevant at a specific point in time.

How many HN readers read about OR before? Haven't read the blog post yet but it seems like a nice way to refresh my knowledge from some obscure lecture I attended about it ~5 years ago ;)

For me, Wikipedia, Twitter, Facebook all are down or show abnormally long loading times.

What goals are more desirable to you than happiness?

Did you mean to say in his native tongue? There are way more English-speakers than native English-speakers.

You don't have to leave to influence, being on the inside often gives you better access, knowledge and opportunity to influence change.

Having a company culture where _everyone_ feels safe enough to speak up and being heard (instead of getting kicked out) is not democracy. It is smart and crucial, in my opinion.

I am surprised that critizing something at a company equals being a trouble maker to you.

What is the meaning of being anti-intellectual and who are these anti-intellectuals you talk about?

What do you mean by that?

That's a very interesting approach. Do you have more data/anectodes etc. on your point:

> By the way, for reasons I won't speculate on, this method (assume failure, which would you pick) turns out to be a pretty good way of picking the option more likely to succeed, actually.

I'm going to try to keep this one in mind for big decisions.

Hopefully this provides a good intro to LLCs to you https://medium.com/@parissathena/what-the-hell-c-is-an-llc-l...

Pariss is also talking about LLC on Twitter you might want to follow her

From the article:

[T]he jury focuses solely on games released in Germany within the past twelve months. From my understanding, a game needs to be available in a German edition prior to the end of March to be considered.

payment processing fee = pay the payment provider (Stripe, PayPal, etc.)

a cut from the payment in order to pay for their services = additional fee on top on payment processing fee to cover operational expenses, employee salaries etc.

How do you distinguish

(A) two random developers that met each other at several conferences over the years, have contributed to a few same projects and really like the efforts the other one is putting into their OSS project

(B) two random developers that met each other at several conferences over the years, have contributed to a few same projects and want to fraud GitHub for the donation match

I think this could be a real practical problem for GitHub. And lawyering up against developers supporting the campaign potentially counteracts the marketing benefit of it.

Perhaps you don't mind it, but it would be interesting to know more about GitHub's and Microsoft's thoughts/thought process on this topic.

You're right I didn't read that passage at first glance. In a year, both donation matching and 0 fees may very well be gone.

I support one project on Open Collective [1] on a monthly basis. They do take a cut from the money I donate to cover the credit card fees and their operational costs. GitHub Support does not take any fees and even matches donations... wow!

While this news sounds amazing on the surface, I am also concerned it might have negative effects on the OSS ecosystem overall. Let's see how this pans out!

[1] https://opencollective.com/

Have all your team members work 30h and the "not pulling their weight" argument is gone.

Or if that is not sustainable/beneficial for other types of jobs than developer, only apply the 30h to your developer team. But do it consistent per team.

Another thought, I haven't seen this dynamic with part-time employees, so I don't think it applies to 30h employees either. Have you seen this with part-time employees?

Balancing out a missing team member 12 times a year for one day vs. once a year for up to 16 days (12 days + 2 weekends with 2 days each) is much more justifiable for the employer.

I think it's because 30 supposedly sounds/looks better than 32. 32 is 4x8 after all, so I imagine many "30h jobs" would turn out to be 32h.

Example: https://wildbit.com/blog/2017/10/19/4-day-work-week-update (also found a job offer by this company on the board).

time to ask for a promotion!

I agree with your last sentence, but the natural way to get to write great posts is to hone your skills writing dozens of ok posts first.

I recommend this talk to see what both technologies can still "learn" from each other - https://youtu.be/LUF7plExdv8. I don't think SPARQL or GraphQL completely replace one another.

Even though subscriptions are very much in progress from a specification point of view, the community came up with different approaches that are already employed in practice.

Here are some additional resources:

- RFC for GraphQL subscriptions: https://github.com/facebook/graphql/pull/267

- How to use Subscriptions in GraphiQL: https://dev-blog.apollodata.com/how-to-use-subscriptions-in-...

- Using GraphQL Subscriptions with Apollo: https://www.youtube.com/watch?v=wo9XFmW0W2c

If you want to use GraphQL subscriptions right now, I encourage you to try out our demo over at https://demo.graph.cool/worldchat/. I work at Graphcool :)