So I started using AI to help me hack ancient hardware today. Living in Colorado with swamp coolers means very few or just bad options for programmable, app controlled, adaptable thermostats.
Hello hotwired micro controller and Bluetooth sensors!! Should be a fun learning experience!
@PalmerLuckey I think about this more than I should. So cool to imagine what the team is building. Just ordered a copy of The @anduriltech Thesis too. Excited to read it.
My parents let me buy this when I was 12 off a grocery store shelf https://t.co/zAG1U9qIgL still inspiring today!
I start a new role this week.
I'm so thankful that I've been able to spend the last week working on personal projects and some fun ideas for this year.
Can't wait to share more this week! #stokedsunday
5 years @SourceDay.
It's been a great experience, but the time is right for a change on my end.
The team has an uphill battle they need to win. I'm excited about their opportunities if they make the right moves.
As a shareholder, I'll be rooting for them until the end ๐ช
One of the most underrated business applications for RevOps is @Apple Freeform.
We just mocked up our new partner lifecycle for @salesforce in an hour over Zoom.
It is nothing crazy complicated, but the ability to quickly iterate on diagrams using sticky notes and a virtual whiteboard is clutch!
I've seen this happening increasingly with new hires, and I don't know why it keeps occurring.
If you're new to a company as an admin or analyst (marketing, sales, revops, cs, etc.), your first priority should be digging deep into the system to understand how and why it is set up the way it is. That leads to digging into the processes and asking how and why here as well.
Even if the company you join doesn't have good documentation, do the research. Make the documentation for them, then ask if it's correct.
Don't accept any projects until you're confident you know how the work you do will impact users downstream.
Get comfortable asking why (ask 5 times) to get to the root of a problem or a request.
Be able to explain the impact of any changes you make that will flow downstream.
If you don't have sandboxes, TEST on a small sample if you're not sure what outcome will occur before running entire programs.
Most importantly, never stop asking questions.