470 karma · joined August 23, 2008
[1] I write in Java because I work for a Java shop, but even if I had my choice of languages, I'd probably be using either Swift or a compile-to-JVM language.
(An even better solution is SWIFT's approach to nullable types, but that boat has sailed; intellij etc could however implement a static checker for bare Optional-getting)
That said, I usually hate petty/nitpicky code reviews. I try to focus only on issues that I think affect readability, maintainability or functionality.
Never buying or using anything from those sleazeballs, and you should follow suit.
A product manager in team X who noticed a bug in product Y is not going to know what fields are necessary for that product, and as issues make their way to company-wide mailing-lists (or are linked from internal meme websites -- you know who you are), they may accumulate +1-spam if no voting system is put in place. As such, I believe GitHub's ability to move upmarket and satisfy its larger customers is actually aligned with implementing the features requested in the "Dear Github" letter.
I'm not sure it's inherent. This may be a generational thing -- I grew up on paper books. Still, one data point.
The payments team enables Square to move money. From developing infrastructure to working with external partners, we find the best ways to move money across different networks and countries in a way that is cost-effective, available, scalable, secure, and forward-looking.
As a software engineer on the Payments team, you will be responsible for designing, building, and maintaining the Payments Platform services and infrastructure that move money for Square. You will be deeply involved in the technical details of building highly available and reliable services, while also working with product teams to enable Square to rapidly build new capabilities for our merchants and buyers all over the world.
That's not really how WiFi works. Chances are his router is on the same frequency as the buses and he can fix this by changing to a different frequency. Even more likely (since one SSID shouldn't make too much of a difference) is that his WiFi router crashes at random and there's some amount of false causation there.
I know this isn't the beef of the article, but this sort of magical thinking that insists on forcing every little thing into a framework of a class war between the upper middle class and the lower/lower middle class is.