If any item is not showing "No Email", then there might be something wrong with the script/bookmarklet for you. If all the items show "No Email", then LinkedIn does not provide options to unsubscribe some emails.
553 karma · joined February 21, 2011
If any item is not showing "No Email", then there might be something wrong with the script/bookmarklet for you. If all the items show "No Email", then LinkedIn does not provide options to unsubscribe some emails.
I am not clear on if it is actually better to not use feature branch. The article gave a couple of reasons:
1. You don't have to do merges. 2. Risk is generally spread out more evenly into a large number of very small risks created as each commit lands. 3. You can test interactions between features in development easily. 4. You can A/B test and do controlled rollouts easily.
I do agree with 1, 2 and 3. However, I am not sure how to weigh them. One scenario worries me about everyone developing on development is what if someone break development? Admittedly, we need a large test coverage for it, but feature branch isolates each develop group nicely and minimize the risk of one group being interrupted by the other. For reason #4, I don't see how it is a clear advantage. I think there is a way to do the same with feature branches, as long as the developer keep both version on the branch.
I'd like to hear your opinions on this. More over, it sounds to me that with this branching modeling, a variety of systems (e.g. GateKeeper) needs to be in place. What exactly are those systems?
I think per user token is good since we have captcha on registration. But we also want to something on non-logged-in pages/users. What can we do?
Also, if we connect the data point to a certain token, does that count as non-anonymously tracking user?
They are two steps here, first to get the on-site interview and then to pass the interview. You talked about problems in both of them.
First, how to get the interview. For me, the trick is to get a reference and apply to the right position. You have specific background in some languages and environment. It is hard for the companies to decide where to put you. If possible, start with networking with people in your target companies. Get to them to know you first, they will help you on finding the right position to apply to.
About the Twitter manager who didn't reply. Try again, with other methods. Find a direct reference instead of simply email him. Or you can hang out with some other Twitter engineers first and they may help you out.
Second, for the interview part, there is little description here so I am not sure if you did anything wrong. Generally, solve the problem by working and discussing with the interviewer; showing your passion; and relate yourself to the company. It is hard for the interviewer to see the value of your project and weigh them during the interview, solving the problems they give is more important.
Also, there might be a bias since you have the major bank background. I cannot elaborate or back that up though.
This is probably normal for the traditional development cycles(, which is not what I'm familiar with). However, with the web apps fastening the whole process, they will face serious challenges. A good example is CulturedCode's Things[1], a good GTD software with no support for cloud syncing. They wrote a series of blogs about how they will implement it back at the beginning of the year. After roughly 9 months, they haven't finished it and it is still in internal beta. Even for the beta, it has been 3 months. I can't imagine that for web applications. Things was great, but because of the pain of syncing, I switched to Wunderlist.
Panic makes great things, hopefully they will keep it up.