A surprisingly generalizable strategy for creating value
- Find something which everyone assumes that someone must own (in the sense of “having responsibility for”)
- Act like you own it.
If you’re not about end goals, you’re screwed.
If you’re an entrepreneur, you should damn well make sure you know what type of person you are–if you’re not about end goals, you’re screwed. Also, if you’re an entrepreneur, make sure you hire and manage people so that they’re focusing on end goals and not motion or, once again, you’re screwed.
Reflections on 10,000 hours of programming
- Browsing the source is almost always faster than finding an answer on StackOverflow.
- Build your tools for repeated workflows. There is nothing faster than using a tool you made yourself.
- A rough rule of thumb: never directly depend on a small library that you could easily rewrite or a large library that should have been small.
- Organizing your code into modules, packages, and functions is important. Knowing where API boundaries will materialize is an art.
- Name variables correctly. Again, an art.
- Good APIs are easy to use and hard to misuse.
- Delete as much code as you can.
- The Quick Skim
- read the code
- check for tests
- ask questions
- suggest improvements
- get out
- The thorough review
- read the code
- ask questions
- suggest improvements
- review tests carefully
- consider implications
- suggest missing test cases
- The exhaustive/critical review
- read the code
- download the code
- run unit tests
- boot up the application and manual test
- ask questions, and point out missing functionality.
What makes a good error message
- “Generic errors are the result of bad development and product. … We must all care about it together.”
- Say what happened and why: Make it clear what did or didn’t happen. This can be done with a combination of visuals and text. Explain why the user got this error, even if the only explanation is that there was a technical issue. At Wix, we decided to say “an issue on our end” if we have the space to reiterate that it’s not the user’s fault.
- Provide reassurance: Let them know what was not affected by the error. For example, were their changes saved as a draft, even though their email wasn’t sent?
- Be empathetic: While we don’t want to be overly apologetic, we decided that we still want to use “please” if the situation warrants it. Maybe it’s a dire situation, or it’s something we can’t help the user solve. In that case, we might use “please” to empathize even more.
- Help them fix it: Tell them exactly what to do if there’s a way to possibly fix it. Short on space? Send them to a knowledge base article with a descriptive link like, “Learn how to resolve this” or “How do I fix this?”
- Always give way out: If they can’t fix the problem, or if it’s possible the issue could keep happening, provide them with a way to contact Customer Care.
Few ways to find more awe in life
- Regular doses of awe may be vital to our well-being and make us nicer people.
- Get into nature and notice
- Seek new music
- Observe people with unique abilities
- Move with others (exercise)
- Try understanding a new concept
- Ask others what makes them feel awe
- Document day-to-day beauty