Explore >> Select a destination
|
You are here 
|
ma.tt | ||
| | | | |
blog.martinig.ch
|
|
| | | | | Informations and opinions about software architecture, developers on call, holacracy, Scrum, continuous testing, product management, saying thank you, tech leadership, customer journey maps, code reviews, code sharing, good bugs, android testing and open source project management. | |
| | | | |
automattic.com
|
|
| | | | | I will never stop learning. I won't just work on things that are assigned to me. I know there's no such thing as a status quo. I will build our business sustainably through passionate and loyal customers. I will never pass up an opportunity to help out a colleague, and I'll remember the days before... | |
| | | | |
gibrown.wordpress.com
|
|
| | | | | I'm reading Bill Walsh's book The Score Takes Care of Itselfon his methodology for getting the San Francisco 49ers to perform at a high level in the 1980s (and win 3 Super Bowls in the process), and I found it interesting how closely his Standard of Performance matches up against the Automattic Creed.I thought I... | |
| | | | |
www.eliza-ng.me
|
|
| | | The practice of interviewing potential employees has long been a part of the hiring process. In recent years, however, there has been an influx of "this is how you hire" posts that focus on Leetcode-style interviews, popularized by companies such as Google. But are these posts really worth their weight? Can the interview process really lead to high performance hires? To answer this question, it's important to first define what "high performance" means. Is it making economically valuable contributions? Or getting good performance reviews? Or simply being good at writing software? Unfortunately, all three metrics have underlying issues that make them unreliable for judging engineering talent. | ||
