As I approach the end of a significant chapter of my life, I’d like to share some nods and advice in hopes of supporting my prior (and future) peers. In the style of a snackable top-ten list, please enjoy these brief words-of-wisdom and a bit of humility.
10. This AI fad isn’t going away. Create waves by making it work for you.
ROLES
Job roles, content, and processes (even in current tech giants) may increasingly be automated away, which is ideal for any advancing society.
ETHICS
Embed ethics in guiding and assistive technology; would you would trust with your own family?
9. Don’t make something unless you need to.
OPEN SOURCE
Embrace open efforts where appropriate, especially if you’ve spent the last decade building something that’s replacable.
EFFORT WHERE NEEDED
Learning and growth come from a try and fail scenario far more frequently than a grueling DIY epic.
8. Most rules and policies only have power if you support them.
VOICE YOUR ISSUES
Always challenge a rule that keeps getting in the way. It’s very likely you aren’t the only one having a hard time.
KNOW YOUR DOMAIN
In other spheres, this belief and support can be detremental or constructive is like stress, meditation, or faith.
GRASSROOTS
The most impactful push for change may come from the hands on the line (or keyboard).
PROCESS
Process can block or inspire creative solutions. Try to artfully dodge or dismiss the former.
7. Call on peers often for help and sharing.
COMMUNITIES
Communities and camaraderie are built via bi-directional information and talent flows.
EDUCATION
Lead by example and do what’s right - tutorials, code shares, a talk, a workshop, whatever!
6. As a technical contributor, if source code and databases are your core value, consider a career change!
INNOVATION
While IP may be great for plaques and licensing, individual and organizational longevity usually comes from ability and intuition.
INTUITION
The how and why of a solution may be more important for reusability and robustness than one example of created content or its code.
5. If you're skilled at data or ML or DS or AI, excel there first - don't jump to making products.
SWIMLANES
Even if a technologist job role expects you to know all things, it doesn’t mean you have to do them all.
EXPERIENCE
Rock the job and skills you have first, and the confidence and prowess elsewhere may follow.
TEAM SKILLS
Said plainly, unless you’ve got a crack team of ops, support, and designers by your side, you’re not ready to make products for other people.
4. Learn when to say no and commit!
SELF CAPACITY
Declining anything is hard the first time, but others will respect your ability and commitment if you don’t overtax yourself or accept responsibility beyond your capacity.
3. Build a career by giving first.
GIVE KNOWLEDGE
Whether it’s expertise, occasional help, or great code, setting a precedent of exploration and communicating wins or losses will pay off for years.
2. Getting lost in innovation is a healthy endeavor.
IMAGINE
A “what-if”, fan fiction, shower thought, or disposable demo are seeds for something more.
SURPRISE
Some of our most salient and lasting experiences are from the surprise (uniqueness of events) in these new thoughts.
1. Make your time impactful! When you are building something, know what and for whom you’re working.
IMPACT
Know your intent and where to stop to get the MVP and time to reflect.
AUDIENCE
Learning from my marketing peers, know your customer for adoption, TAM, and KPIs.
LET'S DO THAT AGAIN
Thanks to my peers and colleagues who supported our ideas, work, and learnings. Thanks to those giving chances, whether exploited or squandered. Thanks to those who laugh. At my jokes. Thanks to those who continue to make work about gains in knowledge and growth in individuals – you make up the brand, the resources, and the location that matters.