FlarnieEvery year I choose some items to read daily, because it allows me to learn and focus on a few ideas as a theme for that year.
My list last year had 13 items, and this year I've cut it down to 6: 🧵
1/n When problem solving, always think of 3 solutions and compare them instead of choosing the first solution you think of.
Picking from 3 solutions is better because it avoids narrow scoping.
I often find the 3rd solution is the best out of the 3, and I would have missed it if I'd picked the first solution.
Picking from 3 solutions is better because it avoids narrow scoping.
I often find the 3rd solution is the best out of the 3, and I would have missed it if I'd picked the first solution.
2/n When architecting software, list the use cases for the developer, *and also* list the impact for your company/end user. Run your assumptions past someone on the business side - does your architecture fit with the business priorities? Are we building the right things?
3/n When someone seems “off” or upset, get curious. It may be about something bigger that they are experiencing. “What brought this up for you?” Or “How are things going, in general?”
4/n Use the Feedback formula; Observation; Impact; Request.
From https://larahogan.me/blog/feedback-equation/
From https://larahogan.me/blog/feedback-equation/
5/n Hiring and keeping the SWAN people is one of the most important things we can do. Smart, hard Working, Ambitious, and Nice.
6/n The last item on my list is something I crossed off my list from last year.
I had written "Having one person on the team who tries to do things the wrong way is good - forces us to bolt everything down to weather the storm of their bad coding intuitions."
This was my way of looking on the bright side when working with someone who kept insisting on doing things the wrong way.
I learned that there is actually nothing good about working with someone like that, and it's better to not.
