Panorama retweeted
if you haven't seen this, @JaclynLunger shared our thoughts on token-maxxing and the way our team works with the @speedrun community.
Should You Be Token-Maxxing? open.substack.com/pub/speedr…
Panorama retweeted
at @withpanorama, we know humans see sparkles, moment to moment. In the seemingly mundane, we create.
Panorama retweeted
Just set up our booth for @speedrun demo day tomorrow, hope to see you there! Come play in my account and see what hidden structures Panorama has learned about me… before I get too embarrassed and switch to a sandbox 😅
Panorama retweeted
We ended our launch day yesterday at #2 on Product Hunt! Thanks to everyone who showed up and supported us, it means a lot :)
We’re live on Product Hunt today, would love your feedback/support! tinyurl.com/575btdrn
Panorama retweeted
We’re live on Product Hunt today, would love your feedback/support! tinyurl.com/575btdrn
Our app has started chastising me… today it told me I only review code when feeling extra guilty.
As a scientist and first employee at Lila Sciences I noticed that as we went from 1 employee to 100 I was spending more of my time preparing for meetings and filling in forms, and less of my time on the fun parts.
At Twitter, Lyft, CashApp and Google, my co-founder Jingwei saw the same thing.
That's why we're working on Panorama, a continuous discovery engine for hidden structures and workflows.
Here’s me being amused while chastised.
Panorama retweeted
Just watched my cofounder @haojingwei meditate on stage at a16z speedrun progress day!
Panorama retweeted
It was honestly such joy working with @haojingwei on their @withpanorama new website. After first generic AI-style iteration, she told me to go "as bold as you can" and those words re-ignited my passion for unique sites with a character. I missed this feeling of a "flow"
Panorama retweeted
One question I get frequently when I talk about @withpanorama is:
What metrics are important for a team's day to day operation?
Before I wondered outside of my own neighborhood of engineering, the first thing came to my mind was "how many thank you or more accurately, signs of help provided, a team or person received per day, week or quarter":
- I used to work on infra teams for years, IMO one important aspect of an infra eng's work is to unblock others (provide help & gather feedback from interactions). Infra is also a place where engineers get to build fancy stuff, and it's *really* fun to build fancy stuff, but that's a different story.
- I've been talking to people: big tech, startups at different stages, engineers, head of eng, CTO, HR, design, research, exceptional recruiting lead, many founders at various stages of their journey. What I learned is the practical knowledge of something I intellectually know from reading psychology books: every team/group is at its own stage (dynamics), and for each set of dynamics, there are a set of metrics that'd make sense for that particular stage and for that group of people: I talked with a first time founder without prior management experience and just started off in engineering, the team is full remote, and from a different culture, the metrics for the team to focus in order to get to the next level of operations, will be very different from a team of senior engineers who worked together for 2 years or 3 companies together. And the moment the team gets to the next level of operation, the metrics for the team to focus on will need to be reset/re-evaluated.
Panorama retweeted
what a day in the life of a designer founder looks like.
want a summary like this for your team? check out view.withpanorama.com/
