prodigal_erik

Surely the greater good would be dubbing in Mandarin, rather than English subtitles.

An unfunded mandate is entirely punitive. If we as a society valued it, we'd be paying for it.

This company isn't offering voting rights nor planning dividends. What's the benefit of owning shares, other than trying to choose the right moment to sell them to other speculators?

It's a kind of tragedy of the commons. If two languages are basically equivalent yet incompatible, neither of the authors did something wrong, but it's a shame about the missed opportunities and problems that didn't need to happen.

Reading and writing CPP macros is awful, but it's still not as bad as reading and writing the mind-numbing boilerplate that they replace.

If you can't build and deploy your own system without a piece of code, you should not be relying on the goodwill of any third party to keep it available for you with no SLA. A good build system is a deterministic function of its input (a commit from your repo) and can run offline.

Why do that? If your screening test says they're both qualified, interview them both. Hire them both if you possibly can.

What happens when your production system blows up at 3 AM? Does your team have a list of who can and can't be expected to assist?

Lots of good vendors offer free trials or guarantees without it harming their reputation. In fact most customers object to shouldering all the risk.

I wouldn't hire a frontend-only guy instead of a qualified developer, for the same reason I wouldn't hire a guy who can only mount wall outlets instead of a qualified electrician. Everything he didn't care enough to learn is a risk.

> if you already have open sourced a bunch of code

How do I know you wrote it and didn't merely paste your name over some project I've never heard of?

> It hardly seems worth even having a bug system if the frequency of from-scratch rewrites always outstrips the pace of bug fixing. Why not be honest and resign yourself to the fact that version 0.8 is followed by version 0.8, which is then followed by version 0.8?

Java was adopted very rapidly (as soon as it ran acceptably on commodity hardware) because the industry desperately needed a safe subset of C++. The pain point addressed by Go is mostly deployment and packaging, which is why mostly devops (who have rejected OS packaging for some reason) are excited about it.

The only way to get team cohesion is positive-sum priorities. If I spend more time helping you improve long-term and less time delivering on my own responsibilities, that needs to improve my next evaluation, otherwise I'm pretty much compelled to stop doing it.

I distinctly remember "Homicide", which is actually a specialty intended for attorneys working in criminal law.