Slippery slope fallacy...You are incredibly oversimplifying what he is saying. Sure, he is generalizing but he isn't citing a single coding interview to judge the entire process.
Having said that, I actually agree with him because I've learned that it's not always simple as who can't write code. I would much rather assess a candidates' ability to learn (sharpness) than the current skill-set.
Being angry is fine but lashing out and saying "..you claim to be better than PHP dev when you don't care about.." serves no purpose other than reacting to your emotions...ESPECIALLY as a leader. If you said that publicly in front of others, that's even worst and you should seriously think about getting mentored by someone you trust. (regardless of how ridiculously clueless he is)
Being assertive is important but being an asshole just adds distance between you and your team. You gain respect on the former and loose respect on the latter. I agree with partisan:
1. Take a deep breath and run it by your "boss" to gain perspective
2. Apologize to your developer for the poor choice of words and tone and tell him that you regret, and it would never happen again.
3. Once that's done, ask: "But do help me understand what you did here and why."
If he repeats his mistakes, take the "I don't think we are a fit" or "this arrangement is probably not a match for us" or whatever. After that's done, you can go to your boss and vent some more. :)
My take on it is HIPAA is meant to protect your privacy which is great BUT we have to make sure it doesn't impede progress in mental health. I am no expert but there has to be incredible amount of information based on studying the data. This is especially true in mental health.
Personally, I am not a fan of a general statement like "don't collect any data". As a patient, I am totally ok if a system collects data ON me BUT never ABOUT me. In another words, the data should in no way be identifiable. That way, we continue to make progress while maintaining privacy.
I recently made a decision to shutdown the startup I co-founded 3 years ago. Brutal. Now, I am catching my breath to figure out what I want to do next. You?
For me, it's a great read. Yes, I cringed when I saw the word "Rules" when we are talking about beautiful UI. However, after reading the article, he is just using it as a framework to convey the message. And it works for him (and me) who are not "designers" but still aspire to create great designs.
I say read it lightly. To me, an engineer realizing the importance of great design is a huge thumbs up for me. I would hire him in a heartbeat.
Absolutely, usable UI is a must but why not make it gorgeous. It doesn't have to be one or the other.
> ..then it doesn't matter how nice it looks.
In a way, making it usable (done elegantly) is part of "gorgeous" UI. I wouldn't underestimate the power of beautiful visual design. It evokes user's emotions in such a way that makes it memorable. It makes it a great UX all around. I try not to look at it in a separate way as the whole thing (usable and nice visually) is what makes it beautiful.
But in its crude form, I do agree the usability is the most important but I just think visual design is not too far from it.
Yup, this sounds way too familiar. Happened to me. I agree wholeheartedly with sm88. Cut your losses and move on.. And here is why.
1. I have feeling you already know deep inside what you have to do and you're looking for reassurance which is totally understandable. I, myself, didn't realize that until waay after. So, go with your instincts. So, before posting, ask yourself. "Am I unsure about what I should do -or- do I already know what I must do but being hesitant or need reassurance, etc."
2. If you had said "we both believe in MVP but he wants feature A and I want B in MVP..and we are arguing.". I would tell you to work it out, work through it. Those arguments are actually great as long as you both are always willing go get drinks in the evening. Seriously, for me, it came down to that: "end of the day, can I still go grab drinks with my co-founder many nights of the week if I had to?" test. But you said "our difference in values cannot be reconciled and I worry that his vision.." Little too deep in my opinion. Huge red flag.
3. I hate making judgement without knowing the details, but come on, aggressively pursue a patent before MVP?...Maybe there are scenarios that warrant this but I think it is very very rare. So, another huge red flag.
4. Don't underestimate your opportunity cost. As long as you are working with this guy, you are not working with the co-founder you'll love (and hate at times). :)
Wow, you sound like me 20 years ago. And I am quiet surprised at "that's life, shape up" responses.
Knowing what I know now, I wish someone would've told me:
- Try to get into top schools like Stanford, Harvard, etc.
- If you don't have the financial means or the grades or whatever, don't get discouraged one bit!
- Since you enjoy "programming or researching", stop stressing over colleges. In my humble opinion, most colleges are overrated. They are designed for drones and will suck the passion out of what you are majoring in. (note: may not be true for all)
- In my opinion, typical educational institutions in our country is broken.
- Instead, start interning. Do small projects that you can showcase on your passion. Join programming groups, meet ups that are related, etc.
- In short, make a living in doing what you love (programming). When you find a job and love what you do, you are no longer "working".
Hmm. Interesting. I have always contemplated this problem. First, I want to simplify the problem a bit and hope it'll apply to traffic jams. I think the problem is human reaction time. I must be missing something but hardly people talk about this. (although my solution might not be feasible). Let me explain.
So, lets say you are stopped behind 30 cars and the first car is waiting for the red to turn green. Now, as soon as it turns green, it takes a second (or two) for the first car to start moving. After that second, second car adds another second before starting to move. Based on this, you won't move your car until 30 seconds have passed. Isn't this one of the big issue? If all of 50 cars instantly start driving once it hits green, wouldn't it reduce traffic jam greatly. Now, I do realize this is not feasible but if computers were controlling the car, 50th car can move instantly after green.
On a side note, I realize the bottleneck situation can't be solved easily BUT again, I think human reaction (response) time is a huge part of it in most of these scenarios. If computers were driving, I wonder if we can have 10 times the car we have today without traffic jams.