808 karma · joined June 3, 2016
I get so many robocalls, I stopped answering my phone. But when I get a FaceTime call or an iMessage, I'm on it.
Robocalls dilute the trust consumers have in the phone system. The telcos are rapidly ceding this trust to other forms of communication -- those provided Apple, Google, Amazon, Facebook etc. As robocalls proliferate, tech companies win and telcos lose. Unless they fix this, eventually the phone system might go away entirely. Consumers -- especially young people -- won't want or need it.
If you already have enough sample code, there may not be a need to provide more.
You may be hiring for guitarist and require at least 3 years experience playing the guitar. J.S. Bach applies, but has never played the guitar. As an industry, we typically wouldn't hire him due to lack of experience. Instead we might hire some mediocre kid with the 3+ years experience and a history of guitar lessons, even though after a 100 days on the job, J.S. Bach would have been a mind blowing, mesmerizing guitar player, even if he was still a little clumsy. And after a few years, he'd be more amazing still. Yet as an industry, we focus the ability to be productive on day 10 instead of day 100 or 1000. For long term positions. Why?
How would the software industry conduct an interview for a musician? We'd ask you about all of the songs and instruments you've ever played and have you talk about those experiences. We might ask a hypothetical question about what if you had to play a certain piece, how would you handle it. Maybe we'd have you answer some trick questions: "What are the frequencies of the first five harmonic multiples of B right below middle C?"
I find this to be utter madness.
I think the best way to find a good (or potentially good) developer is to have them do what we do in our jobs, which is, given some vague requirements and some undefined period of time -- a few days or so -- write code to solve a simple problem.
And I loved the part in the article about mediocrity. I've found the best developers to be humble enough to constantly work on improving their craft. So, don't reject a candidate because they appear to "lack confidence".
Get a load of those prices. :-)
Also, I love how the minimalism even extends to the domain name.
I can't help but draw a parallel to how Tesla is considered by the old guard to be a laughingstock today. See https://news.ycombinator.com/item?id=16305520
I've been in organizations where you have the Language/Platform X people over here and the Language/Platform Y people over there, and they duplicate work, don't collaborate, and their libraries don't interoperate. They have different hiring needs, and developers can't easily move between them. Ultimately, everybody with their pet languages moves on, and new people come into a very fractured environment and ask themselves WTF is this? Over the years, developers (especially new ones) are only a fraction as effective as they would be if the company had just paid the relatively small up-front price of nudging everyone into the same ecosystem.
And BTW, I have yet to encounter a problem that is hard to solve in my preferred language, but is way easier to solve in another. I think the key to that is to choose carefully what you're going to commit to.
Why do organizations allow this? I realize that some platforms require their own languages (iOS, Android), but outside of that, just pick one or two and hold the line.
I heard an analyst say that you have to carry a lot of fuel to carry a lot of fuel. The optimal size from an efficiency perspective is the much smaller 737 -- the more you deviate from that, the larger the efficiency penalty.
I think that a large part of the problem is just the name, "antidepressant". If they were called Serotonin Stabilizers or something, maybe there wouldn't as much of a stigma.
http://www.3m.com/3M/en_US/company-us/all-3m-products/~/3M-P...
I understand that this is different because the radiation bounces around an enclosed chamber and so momentum wouldn't be conserved, but if the issue is to create propellant-free propulsion, doesn't that already exist (even though it's not practical)?
After a very dark period of taking jobs that required less typing (Kafkaesque jobs at mega-corps involving mostly fixing other people's bugs), I'm better now because of:
1) Using an Apple keyboard, which even though it doesn't look ergonomic, the reduced key travel has helped immensely. 2) Using JetBrains' IDEs instead of vim. If you are a bash/vim/tmux (or equivalent) user like I was, try coding in your favorite language in a JetBrains IDE. Automated refactoring and code completion are your friends. 3) Try drinking red wine. The resveratrol in red wine is a natural anti-inflammatory.
Here's a reminder re: Toyota's coding practices: https://news.ycombinator.com/item?id=9440094
Not one of them will be able to touch where Tesla will be in a few years from a software perspective, and that's where all the differentiating value will be in the coming wave of new automotive technology.
I find SpaceX's predicament to be deeply troubling, maybe because if this is sabotage, it casts a pall on the humanity's ability to make progress.