1,257 karma · joined May 17, 2017
I'd highly recommend Josh Bloch's writings. Josh is perhaps best known for the book Effective Java and the Java Collections library. Here is a paper he wrote about good API design (https://dl.acm.org/doi/abs/10.1145/1176617.1176622) and a short interview with him about API design (https://www.infoq.com/articles/API-Design-Joshua-Bloch/).
Brad Myers at CMU also has done research on API usability. See here for more details: http://www.cs.cmu.edu/~NatProg/apiusability.html
Lastly, if you're doing anything remotely related to security, I'd also recommend Matthew Smith's research. He's studied a lot about weaknesses of today's API designs and how they have led to security vulnerabilities. https://ieeexplore.ieee.org/abstract/document/7676144
First, as you note, CMU is incredibly competitive. Here are some stats for students admitted to CompSci last year (taken from https://admission.enrollment.cmu.edu/pages/school-of-compute...).
Average Unweighted GPA:3.96
SAT Middle 50% for Evidence-Based Reading & Writing: 750-800
SAT Middle 50% for Math: 790-800
We have applicants with perfect SAT scores that aren't admitted. The problem is that, past a certain level, there are so many qualified applicants, and no university can accept all of them.Second, as an Asian-American myself, I have some mixed feelings about affirmative action, but over the years have leaned more towards it. One reason is that grades are a useful predictor but only one of many of how well people will do in university and in life. Take a look at Terman's Termites, and how his testing of young students missed future Nobel Prize winners, and how many of the termites just ended up being average. Another is equity issues. There really are underrepresented minorities that have overcome a lot given where they started, but don't have as high test scores. There are also cohort issues, where dropout rates of underrepresented minorities is higher if they don't have as many peers or role models. There are also pragmatic issues, with young men (mostly Caucasian and Asian-American) dominating in Silicon Valley, leading to real blindspots in product design (basically, people tend to design things for others like themselves) as well as the gender issues at large tech companies that have been in the news (I'd recommend reading what Teresa Meng had to say about this at a conference keynote, especially since she's a superstar in her field https://www.eetimes.com/an-engineers-guide-to-sexism/). Also, pragmatically, if there is a difference in grades and test scores between men and women admitted to our CS program, I haven't seen it in students' actual performance once they are here, and I've taught 1000+ students over the past 15+ years.
Third, this is just N=1, but I was not accepted to my preferred undergrad colleges (possibly because of some affirmative action issues), and was only accepted to two PhD programs (Georgia Tech and Berkeley). I'm now a top scholar in my area of research, along with having founded a successful startup. And I still get rejections all the time, for research papers, grant proposals, and awards. In fact, talking to a lot of my fellow professors, they all have stories about significant past failures. One even has his letter of rejection from CMU's PhD program posted on his door.
Yeah, your situation bites. Give yourself a few days to process things, then dust yourself off and get back up to figure out what you're going to do next. You're going to get knocked down a lot in life, and (systemic issues aside) a big difference between people who can really make it and those who don't is being able to deal with that failure and keep moving forward. Also, keep in mind that really good scholars will still succeed regardless of where they go for undergrad. Take a look at the undergrad schools of various successful folks in CompSci, you might be surprised. And if PL is what you're really into, grad school will matter far more than undergrad.
And last, I'd also recommend this article (below) from New York Magazine, asking about why success for Asian-Americans tends to end after school. There's a lot of raw anger in the writing, but I think it will resonate with you, and hopefully give you some good food for thought. https://nymag.com/news/features/asian-americans-2011-5/
Good luck!
Vannevar Bush helped organize the American scientific effort during World War 2, and afterward was instrumental in setting up the modern university research system we have today. The main argument was that research was the "Endless Frontier" (hence the name of the book about him). Things like the National Science Foundation and DARPA are part of this compact, that the Federal government would fund research universities to do fundamental and applied research, which in turn would help contribute to American national security.
Regarding this specific article (As We May Think), I would argue that it's core impact is that it made a case for why information technologies were needed, and laid out a vision for what that world might be like. Even though the article was written in 1945, it talks about information overload(!), and the challenges of finding the right information when there is so much of it. It also imagines an early form of hypertext via a device called the Memex, which later inspired Ted Nelson, Doug Engelbart, and others in their work. There's even discussion of a kind of collaboration in the form of "trails" or paths as to how one found a piece of information in the first place. One might share these trails with others, forming a kind of hyperlink that we don't have a modern equivalent for. Intriguingly, Bush also imagines wearable computers (a wearable camera) that can be used to help augment people's memories.
In short, this article heavily influenced a lot of people's thinking about what computing technologies could potentially do in the future, and was a major part in getting us to where we are today.
It's possible to complete a PhD in 2-3 years, but this also typically leaves no room for exploration or any kinds of errors. At CMU, the only examples I know of were people who were on leave from the military and had a hard stop after 3 years to return.
The first is learnability. A big problem with gestures is that there is no clear affordance as to what kinds of gestures you can do, or any clear feedback. For feedback, one could couple Soli's input with a visual display, but at that point, it's not clear if there is a big advantage over a touchscreen, unless the display is really small.
The second is what's known as the Midas touch problem. How can the system differentiate if you are intentionally gesturing as input vs incidentally gesturing? The example I used was the new Mercedes cars that have gesture recognition. While I was doing a test drive, the salesperson started waving his hands as part of his normal speech, and that accidentally raised the volume. Odds are very high Soli will have the same problem. One possibility is to activate Soli via a button, but that would defeat a lot of the purpose of gestures. Another is to use speech to activate, which might work out. Yet another possibility is that you have to do a special gesture "hotword", sort of like how Alexa is activated by saying it's name.
At any rate, these problems are not insurmountable, but it definitely adds to the learning curve, reliability, and overall utility of these gesture based interfaces.
"...derived from veterinary euthanized individuals following motor vehicle collisions in Tasmania, Australia"
- Set aside a large amount for taxes, invested it in US Treasury Bond (get an estimate of your taxes from an accountant)
- Got an accountant
- Read up on QSBS (this can save you a lot of money if you got stock when the company was small enough)
- Got a last will and testament drafted and signed. Also asked our probate lawyer about stupid things people do with money, so as to avoid those mistakes.
- Got a financial planner. Also asked about stupid things people do. (At your scale, probably ok to just do standard ETFs and bonds. Note that don't buy in all at once, diversify not just the investments but also by time, so you're not buying all into the stock market at once. This also gives you time to think and reflect about how you want to use your money and what legacy you want, while also getting some returns on investments)
- Set up a donor advised fund (you can donate stock directly to one and get a big tax break)
- Made a donation and got something cool named after two of my long time mentors
- Read book Silver Spoon Kids on how to talk to one's children about money (our financial advisor gave this to us)
- Read a lot about wealth and power in the United States, in particular sociologist and psychologist William Domhoff's "Who Rules America?" https://whorulesamerica.ucsc.edu/power/wealth.html (I stumbled on this by accident, but found it a fascinating read)
Time is on your side here, so don't rush into anything. I was really lucky to have a brother who already had high net worth, so he was able to give a lot of guidance and discussion of tradeoffs.
Here is one of them, I don't recall the other two. https://dl.acm.org/citation.cfm?id=2162095
http://www.cmuchimps.org/publications/identifying_and_analyz...
The title, app description, screenshots, and icon give a lot of signals as to whether an app is targeting kids or not. In particular, icons and screenshots that use a lot of primary colors was a pretty good signal, though app description was the best feature.
Company was also acquired a few months ago, and I'm using some of the proceeds to put together a man cave, which I've informally called the "Wombat Cave" :)
Two ideas to consider for next steps, if you're interested. One is to crowdsource the data, to build out a map of places and how busy those places are. You would need to add in a lot of privacy mechanisms though, e.g. only sharing data of mostly public places vs homes. You could also build out a map of interesting places based on this (e.g. we used foursquare data in our past research to build out clusters of places, see http://livehoods.org/)
Another is to estimate how busy a place really is based on traffic, in terms of #people, and #seats or #tables available. This could be especially useful for campuses (where is a good place to study?) or cafes. You might need some crowd-based approach to label ground truth, and it's unclear what the incentive would be.
We did consider commercialization back in the day, but never came up with a plausible business model. It's not clear why business owners would want this, and they might even have an incentive to cheat. Though I would definitely say that cities would be interested in this data, e.g. urban planners or depts of public works. They have so little data about what is actually going on in a city. For example, we spoke with people who wanted to know the effects of closing a bridge or closing off a street.
- The designers / developers thinking that they are typical users, and that they know how things work ("You are not the user" is the phrase we repeat a lot here at CMU)
- A lack of education about how to design things (e.g., basics of perception, design patterns, basic interaction principles, conventions)
- Time and money
- A common mentality that "we can fix the UI at the end"
- Legal requirements, marketing, corporate partnerships, etc, that is all of the cruft that doesn't focus on user experience
- For popular products, a very large user base, which means legacy support (people don't like change), and different people using different features (I once heard that people only use ~20% of features in MSWord, but it's a different 20% for different people)
Yes, you're right that it does suggest a certain kind of corporate culture and mindset. A common big challenge with UX is educating the rest of your company about best practices, and most importantly, demonstrating results.
Convincing (say) skeptical engineers of the value of user studies can be hard. A common technique is showing videos of user studies and people failing to use the product. Another common technique is to bring an engineer to a site visit and get first hand experience of the pain points.
Having said that, I know folks with master's degrees and PhD degrees who are great UX and product designers doing cool work on autonomous vehicles, drones, etc, so the path really depends on what you're most interested in as well as how lucky you are in finding a good match.
For best books, it depends on if you want to understand users or do implementation. But generally, I'd highly recommend Don Norman's The Design of Everyday Things to improve how you look at the world, and Steve Krug's Don't Make Me Think for simple and practical design tips.
For tools, the best is paper prototyping, where you have your team just draw it out on paper and simulate the UI. It's simple, fast, and cheap, and from a cognitive perspective, you can explore more of the design space (think breadth-first search instead of depth-first), and you don't get overly attached to your designs.
In my course on UX design, we also use Balsamiq and InVision, though other tools seem fine (e.g. Marvel, Figma, etc). One of our alums created this great chart comparing different prototyping tools: https://www.cooper.com/prototyping-tools
For schools, some to check out would be Georgia Tech, University of Washington's Master's of HCI, Indiana University, University of Michigan iSchool, and (of course) Carnegie Mellon's Master's of HCI.
And lastly, here's a slide deck I put together and used at my startup several years ago. It was intended as a short 1-hour crash course. https://www.slideshare.net/jas0nh0ng/01-1hourcrashcourseuxhc...
Some of our team's work (past and present) that may be of interest to folks here: - We analyzed the privacy of Android apps at <a href="http://privacygrade.org">http://privacygrade.org</a>. The basic idea is that we use crowdsourcing to generate a model of what people are concerned about, and then apply that to all the apps we crawled. We're working on an update of PrivacyGrade using network data too, to map out who knows what about us and why.
- Perhaps one of the biggest findings from our team's research is that over 40% of apps that use sensitive data only do so because of third-party libraries (e.g. advertisers or analytics). We've mentioned this in talks to the FTC, Google, Apple, and others, that these third party libraries are the biggest point of leverage here if we want to solve the problem. See this paper: <a href="http://www.cmuchimps.org/publications/does_this_app_really_n... this App Really Need My Location? Context-Aware Privacy Management for Smartphones</a> (PDF).
- <a href="https://privacyproxy.io/">https://privacyproxy.io/</a> (sorry, self-signed certificate is a bit out of date). This is a VPN that scans outgoing traffic for likely personally-identifiable information
- <a href="http://www.android.protectmyprivacy.org/">http://www.android.... This requires rooted phones, intercepts calls to sensitive data on your phone, and aims to help you make better decisions by surfacing these calls and showing you how what the majority chose to share
- <a href="https://privacystreams.github.io/">https://privacystreams.gi.... This is a new programming model that aims to make developers' lives easier, and improve privacy as a side effect by making accesses to sensitive data easier to analyze. A key observation is that most apps don't need fine-grained data, but currently apps require all-or-nothing access. For example, raw audio vs "just loudness", or exact GPS vs "what city". We offer stream-like processing that makes it easier for devs to get the granularity they want, which also makes the app much easier to analyze. So we can analyze an app and output "this app uses your microphone to get loudness"
- <a href="https://www.slideshare.net/jas0nh0ng/fostering-an-ecosystem-... an Ecosystem of Smartphone Privacy</a>, this is a talk I gave last month that summarizes a lot of our team's work on privacy
Our DARPA PM has asked us to focus a lot more on tech transfer activities for our final year, so if any of you are interested, send me a mail. (This is tech transfer in terms of getting industry to adopt our ideas, not necessarily commercialization or licensing.)
It's a perfectly fine strategy to manage things yourself, as long as you diversify. Be sure to get things that are non-correlated with the market, and diversify over time.
The thing that a lot of people are missing in their "don't get a financial advisor" advice is access. Access to hedge funds, access to some investment vehicles designed to hedge your bets, access to early stage funding of companies. These are things that you would not get easy access to without a good financial advisor.
Again, you can do perfectly fine managing things yourself, so it's basically a judgement call here.
- Get a financial advisor. Make sure that they have fiduciary responsibility, that their job is to help you, rather than just fees. Talk to several different ones and find one that you're comfortable with. Note that you will eventually have to spend a fair amount of time learning about all the different kinds of investments that are out there. One surprise for me: I already knew about diversifying your portfolio, but had previously only heard about doing that based on assets. It's also useful to diversify over time too, that is slowly add more investments over time, rather than doing it all at once (since that's timing the market, and you might get lucky, and you might not).
- Get an accountant. You will absolutely need one to handle the taxes.
- Read up on Qualified Small Business Stock. If your company and length of your stock ownership qualify, it could be a quite large benefit for you regarding taxes.
- Set up a Donor Advised Fund. Ok, it's probably too late if you already got the money in the bank, but this would let you donate the stock in a way that would save you a lot on taxes, and allow you to direct money to charities you and your family care about.
- Get this book: Silver Spoon Kids. Our financial advisor got this for us, and I found it incredibly helpful as to how to talk to kids about money, especially to make sure that they don't end messed up. This can be quite common among financially well-off folks.
- Set up a last will and testament. This should be done after you have kids. It's no longer just about you, you have your kids to think about, and what happens if both parents meet an untimely end. You will want a probate lawyer to go through this process.
- Max out your insurance, ie auto, home, etc. People with money can sometimes be targets for lawsuits, for a variety of reasons. Maxing out insurance will help with a lot of things.
- Also echoing a lot of the previous advice, take things slow. Don't make any rush judgements or investments. Time is on your side, and besides taxes, there's no rush here. The interest you would get from just a money market fund will be ridiculous.
Also, the big surprise for me? Well, as you can see above, managing a windfall is actually a lot of work. But think of it as an upfront investment, to make sure that things go more smoothly later on.
Good luck!
http://www.cmuchimps.org/uploads/publication/paper/192/hey_a...
One thing that really surprised me when we did this work is that people actually own more than one Alexa device. One family we interviewed had 7 devices, though they used it primarily for controlling lights and asking the time.
The number one command from the logs was "Alexa stop". The number two was "Alexa". Number three was "stop".
Like the original posted article, we also saw very little use of shopping.
The funniest story we heard (which didn't make it into the paper) was how one family used Alexa as a timer for their children, for timeouts. A parent might say "Alexa, set timer for 5 minutes". One time, once the parent left, the kid said "Alexa, set time for 1 minute."
I'd like to point out that one of the authors (Moira Burke) was a PhD student in our department at Carnegie Mellon University (the Human Computer Interaction Institute) and she did research of the highest caliber with a high level of rigor and integrity.
She and her doctoral adviser (Robert Kraut) also published a very good peer-reviewed paper in the Communications of the ACM entitled Internet Use and Psychological Well-Being: Effects of Activity and Audience (https://cacm.acm.org/magazines/2015/12/194633-internet-use-a...) which summarizes about 20 years of research in the area, and the post from Facebook echoes a lot of the same themes. The Facebook post also mentions a lot of other very well-executed and highly regarded scientific research in understanding how social media affects us.
So I'd really like to ask folks to please differentiate between the science side of the post (which I'd say is very good) from any of the associated policy or business issues (which is fair game).
http://www.cmu.edu/silicon-valley/academics/software-managem...
Some of the differences are that the Master's of Product Management (MSPM) has a much stronger emphasis on HCI and User Experience Design, and is on a different cycle. That is, the MSPM runs from January to December (1 full year, off cycle), whereas the Master's of Software Management is on the regular cycle. The MSM is also available for part-time students. Lastly, the MSM has a stronger focus on being an engineering manager, though there will be some overlap with being a product manager.
Anyways, that's a digression.
The short answer is that we are keeping standards very high for admissions for this program. Also, having been in academia for many years, I can easily say that there are lots of brilliant people from all over the world.
It also seems like the expected roles for people coming out of your program would be general kinds of managers, consultants, or researchers.
There's also a certain underlying style and set of assumptions in the coursework in your program that, for lack of a better term, is European. Have you noticed that in the US that computer science theory usually means complexity theory, but in Europe, it often means automata theory? Sort of the same thing here. There's a strong emphasis in your program on knowledge networks, methods and processes, and so on. It's not that one is better than the other, it's just very different underlying assumptions and starting points for a curriculum.
What you're telling us is actually very well aligned with what we've heard from our alums and from some companies. Yes, product managers are not CEOs and can't always just tell people what to do. Product managers work with their direct team (typically some engineers, QA, 1-2 UX designers, possibly a data scientist), but also need to know how to interface with marketing, sales, and others. Part of our curriculum looks at how to work with and positively influence others to achieve desired goals. But you're right, that's not easy, though there are some strategies and tactics that work better than others.
Speaking as someone who has co-founded a successful company (Wombat Security Technologies, over a thousand customers for our security training software), I really didn't know what I didn't know. As an undergrad and a PhD student in CS, I learned tons about graphics, distributed systems, hardware, algorithms, and so on. But that didn't prepare me to read balance sheets, understand how to do a good competitive analysis, know how to manage people, know the best methods for rapidly prototyping and validating ideas, how to do sales and marketing and (more importantly) how to measure it, and so on.
Just on this last point, like most techies, I originally had a negative view of sales and marketing. I never realized how hard it was, how good you have to be at it, and that it can actually be measured in useful ways. If you're lucky enough to be part of a good team that can teach you these and other skills, that's really fantastic.
Now, our Master's of Product Management won't teach you all of the skills above, but it covers many of them. It also does it in a safe space where it's ok to try out ideas, take risks, and fail. You can do it without having to worry about making payroll (though of course there is tuition), or having to find space to lease, or figuring out founder's pies, or worrying about lots of other logistics and paperwork.
That is, at a startup, you are focused solely on one thing: survival. You don't have a lot of time for reflection, for deep thinking, for understanding what are best practices backed by lots of empirical evidence. Like I had when doing my startup, you might also have a narrow view of things because you simply don't know what you don't know. You don't know what other options are possible. And making too many mistakes can be fatal for a startup, resulting in bad feelings from your co-founders and funders.
Now obviously no single master's program can address all of that, or even guarantee success. These are just very different paths for learning, with lots of different goals and tradeoffs.
It's also worth pointing out that startups are not for everyone. Some people might be at a large company and want to make a career change, but still want to stay at a large company. Again, different goals and different tradeoffs.