- SDE, L6, 5 YOE, 290K TC
- For SDE3 Promotion, Consider working on self-projects based on impact instead of projects defined by leadership. If a customer ends up using it, it looks good from a Think Big perspective. It is powerful to have management trust you with these side excursions.
- Don't Switch Teams. If you are happy with your team, work, and manager, having reputation in your organization compounds. Other managers will know your name and that you are good. This is worth a lot at promotion time.
- Get good at writing narrative prose for each decision you make. Make it visible across the org. If you don't have a document for your feature, it can be misunderstood as unimportant.
- Become social with your team. Laugh. Smile. Show yourself on camera. Tell jokes. Look for every opportunity to publicly call out your coworkers when they do something good. Defend your teammates. They are goin
Brian Liao briantliao
briantliao
/ AmazonAdvice.md
Last active
January 21, 2021 00:48
wojteklu
/ clean_code.md
Last active
April 25, 2025 12:19
Summary of 'Clean code' by Robert C. Martin
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
- Follow standard conventions.
- Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
- Boy scout rule. Leave the campground cleaner than you found it.
- Always find root cause. Always look for the root cause of a problem.
In August 2007 a hacker found a way to expose the PHP source code on facebook.com. He retrieved two files and then emailed them to me, and I wrote about the issue:
http://techcrunch.com/2007/08/11/facebook-source-code-leaked/
It became a big deal:
http://www.techmeme.com/070812/p1#a070812p1
The two files are index.php (the homepage) and search.php (the search page)