"better to burn than talk about it when theres 100 things to burn". Glad you're back

appreciate your rawness.

I think you've done an exceptional job leading the team and delivering an incredible product in PAT. You've got a very strong sense about the product, what makes a good product, including not just the tech implementation, but also things like what good engagement with the customer base looks like. You've owned it top to bottom, and that's really cool. You've also done a really good job with motivating the team, establishing a culture of innovation and entrepreneurship, cutting thru, making quick loops, etc, which I think is key in the FDE space, and I think is a key reason PAT has been such a success. Culturally, and as a leader, I have seen you repeatedly seek open and honest feedback, and reach out to me multiple times to make sure I am doing well, that my morale is good, etc etc. In terms of areas for growth: 1. I think as a tech lead, you can level up your effectiveness by being plugged in more with what's happening in the broader organization, and who you can go to for help with various things. An example that comes to mind is around the CI/CD pipelines, where it felt like we were kind of stuck, until we finally talked with ████████. 2. You have a very strong sense of how things should be, which is a key strength, and I don't want that to be lost. But I worry that sometimes you're holding on to the principled view of what you think good looks like a little too strongly, at the expense of practical considerations. An example of this was working thru the performance and delorean branching strategy work, where I think it took a lot to convince you to go ahead with the change. I think you had really good concerns, that led us to a net better place, but I think the process was bumpier than it needed to be.

PAT. Enough said. But to say a little more — you excelled this period in a few key areas. (1) getting it done — you picked your bets, fought your battles, and (mostly) avoided getting bogged down in bureaucracy. I'd take that bet 10/10 times, especially in the FDE space, but should note that it came at the cost of your own time/sleep, cross-team dependency bumpiness, and some management friction — all areas you can improve. (2) Your focus on keeping folks motivated and unblocked, especially newcomers like ██████ — don't lose that, although for your own sake consider how much of a shield you need to be for your team. It was a genuine joy to build PAT with you. (3) Cultural engagement — you are relentlessly open to feedback and self improvement and provide excellent feedback to others up-and-down. You stretched across many different dimensions this period. Which excite you the most? What focus is sustainable for you in the long term?

self grade: above PAT went very well and we delivered a tough product that people love. all in all, im very happy with how things went. lots learned and excited to do better next time.

PAT would not be where it is today without you leading it. No two ways about it. You had laser focus on delivery and looping. You didn't tolerate slow iterations or blockers and came up with creative workaround everytime to ensure the flow is never disturbed. On the technical side as well, you effortlessly stood a complex product like PAT in no time with agentic workflows, evals, custom delivery mechanism, integrating with external teams (e.g. Delorean search), etc. Sheer hours you put in to achieve this is admirable. Constructively though, there was some noise around xteam dependencies (delorean search, pixi/uv, gitlab, getting more resources, etc.), target state architecture (service based or local, delorean storage, etc.). Seemed like you were trying to fight all those battles by yourself vs leveraging others or escalating to get more help.

Absolutely excellent PAT demo at the LangChain Interrupt conference. It's a rare demo that captures an audience from the beginning, and doesn't let go throughout — but you guys managed!

Really great presentation at LangChain — came across as very compelling / impressive!

LangChain PAT presentation — nice job! Clear & compelling across multiple levels; packed a lot of good detail into a pretty short talk.

LangChain talk on Pocket Analyst — great work!

Thank you both for your time (it was quite an investment) this week on on boarding the team. We will likely continue to lean on you for a while, but you are always willing and available. Doesn't go unnoticed.

yesterday — appreciate that you were game from the start and made it happen

Good demo in the prod eng meeting, generating code for the whole graph in parallel with defined interfaces was a very interesting detail and a potential design pattern to learn from

The last few days. Always saying and doing the hard things

very belated dot, but pushing for open beta vs GA, and getting in sync on expectations post first release

checking in on morale, recognizing the hard work, encouraging me to take time off if needed

good job letting ████ make the case for his vision and trusting him

Dotting from weekly retro — you've been on top of user feedback and issues both in slack and all over the office; great hands-on interaction to both solve problems and build connection with people. Definitely don't stop doing this, but we can compound this and prevent both burnout and key-person risk by doing a little more runbooking

PAT Support this week.

Great team event last week, thanks for organizing

Pushing for what you believe on for DGame access in workspaces. And with broader vision for why you're doing the thing you're doing.

Slack thread today about D-Game changes. It was kind of a mess of a message. Didn't do a good job of communicating what you were looking for. In the specifics it was hard to engage on what you sent. Think you were pushing forward on writing code without thinking about how that fits into a broader picture and what it means to land a change of this sort well. Missing basic things like a design which would help you on both fronts as minimally an artifact to get people in sync with on your goals, approach, etc.

Awe in AE — thanks for organizing!

Awe in AE event was excellent — thank you

PAT to GA

Belated but PAT is / is going to be transformational for hwdw. Well done!

Re todays PAT-Security Go-NoGo: I think that session was really WGLL — Ive attended many meetings like this, and this one felt significantly smoother. The level of ownership and thoughtfulness came across clearly in the room. To call out a few specifics — your writeup was detailed and literally had answers to anything that popped in that meeting. The effort you put in to prep for the meeting and generate that page proves that you arent treating security signoff as an annoyance, but rather an issue you care about and want to serve as a real thought-partner. Lastly, I think good job communicating clearly and always ending with "so I am hearing a Yes on this one, correct?" Dont think anyone left the room unsure about the decision. Good work

Great job in security meeting. Clear you did lots of prep and thought you communicated very clearly

██████ and I basically did an entire IC writeup's worth of analysis almost entirely in PAT this week. the new version is really a game changer and massive step up vs before. amazing stuff, great work

Proud of you two for showcasing your work today. Really well done.

Pretty incredible work getting us to where we are today with PAT. Blown away by how far this has come from where we started thanks to all of you...

Seeing a hugely renewed version of you this week. So on your game, guiding the PAT team well. And as always, excellent reflections in our conversations.

Great stuff this week. Really on top of everything (code reviews, logistics w external teams, CI, product stuff, etc). Huge spike up on the intensity and proactiveness over the past week or two. Love to see it, and it's what we'll need to maximize PAT's potential

setting up speakeasy magick team event — thanks for organizing

"I'm not personally entertaining it" is not an acceptable answer to anyone who is trying to help you. Try "That seems like a horrible suggestion, why do you think it's reasonable?" or something similar. Dismissing and not engaging is not going to work.

tight collaboration on storage interface. easy to rapidly engage with you and get the context i need separate story on how looping on that design is going but that's not entirely relevant to you

PAT newsletter

Good advice in the FDE All hands around nuking the code, I haven't been doing that enough and keep running into reshaping slowly as much as possible with painfully slow rate of success. Maybe I should try the 're-write + delete method' part by part instead.

Your PAT GA document and kickoff meeting were excellent. The doc was comprehensive and your participation in the meeting was motivating and unifying.

Your engagement on PAT resourcing needs over the past two weeks was below the bar on several fronts. I need you to synthesize your team's needs clearly and consistently, manage communications in coordination with others (██████/██████), and proactively pull me in when you need help. We spoke about these issues and I think you're making clear changes on some of these.

There's a buzz in the air and a vibrancy to the team, that feels exciting and like a breath of fresh air, and it seems to start with the two of you

Actively seeking and encouraging feedback. It feels empowering

In the future I would appreciate it if you gave me the opportunity to talk to my resources about any changes in their responsibilities before making announcements about it in public channels

Quick call / check in today

Appreciate your thinking on retro items and reflections on recent frustration — it's helpful to hear when I'm not in every conversation

Good (unprompted) reflectiveness this morning. You do this better than many; I think it's why you're looping / evolving so fast.

As discussed live after PAT GA plan meeting with tech, I think you had a slight miss in setting the goal and making sure key folks had the right context/frame of mind before jumping into specifics. Still achieved the meeting goal and live discussion was great, so this is mostly on the margins.

#2025Reviews Above expectations for the year. Strong first half in the platform space with the logic model being a key win. Switch to the AI team was another fruitful change — Code Assist really demonstrated solid delivery but more importantly excellent engagement with users. Lots of little but meaningful wins (testing framework as an example) throughout the course of the summer. With PAT, showed great entrepreneurial skills — leading and engaged in all aspects of the project. Over the next year, plenty of room (and potential) to grow. How to actually take PAT from a prototype to an actual product will be challenging and the associated complexities will be new. Can also be more effective by managing emotions, especially frustrations, better. Excellent at taking feedback, internalizing and looping but in the moment it shows and at times erodes collaborative nature.

Pre holidays team win slack message

PAT UAT war room: Good job (as with last time) setting it up and achieving the goal of us all getting deep into the next version of PAT. However, surprised that the ad-hoc session later that was framed in Slack as a "technical React handoff" was actually a feature/bug prioritization session — if ████████ hadn't messaged me to join I would have missed that. Reminder that such convos should be in a team setting and not in a sub group silo.

Productive PAT React war room — good problem perceptions and user-empathetic feedback

Escalating for what you need is excellent.

Problem perception and raising it well.

Good feedback on recent large MR. Not per se complimenting the feedback (although it was good), but more so want to call it out that it shows you are really engaging with the changes and not letting things slip through the cracks. Good balance of knowing when to get in the weeds and when not to (and I think it's a good habit you have of asking what does / doesn't require deep review from you)

great feedback this am. incredibly helpful for my development and appreciate you both forcing the more "uncomfortable" conversations + putting me on spot

In general, you're encouraging discourse and debate on the team in a really good way. Good mental maps re: getting the team in sync on a nubby issue this morning; spending more time to get in sync is always the right call.

Good push in today's team session to recognize the wins and progress from the recent period

demo & technical walk through yesterday!

One of the most talented engineers that I've ever had the pleasure of working with at BW. It was clear that he was very good when I worked with him on Plaid; but it was only this past period when he came to work on the Pocket Analyst (PAT) on the AE Core AI team that it became clear the degree to which he is a superstar. His superpower is a combination of ownership, creativity, and intense focus on delivery that enables him to quickly grasp the goals that we want to go after, ideate and ruthlessly prioritize the potential paths to get there, and then actually get after it — first individually (in an architect and SWE role) and then over the last month as the Technical Lead for the PAT project. On top of this, one of the better culture fits that I've seen come out of Technology (always says what's on his mind, is excellent at giving and receiving critical feedback) that more folks from Tech could model their behavior after. And always creates a consistently positive environment for our team. I can honestly say that we would not have been able to get as far as we have gotten on PAT without you. Thank you. The clear areas of growth over the last few months have been with ability to lead, maintain composure while not losing any of the other attributes that make him great. I reflect on some of the challenges that we had to work through in July, how I've seen him work through similar challenges (at a broader scale) in the last 1-2 months and the difference is huge. Able to handle significantly more pressure, react much more thoughtfully than before. And a lot of this growth I attribute to the fact that he is so open and able to take feedback (and loop on it) as well as he does. The main areas to improve on are: — Communication. There are often times where we'll hit a situation where either (a) misunderstanding a question that's been asked or (b) appearing to be in disagreement in a conversation over a particular set of words (when in reality, there isn't actually a disagreement). Communication is obviously a two-way street, but I think that there's probably more that could be done to just slow down, ask questions, push for clarification, push for "in-syncness" on terminology. — Connection to business, how we do work. I think that there's still a pretty material gap in terms of understanding how we do work that needs to close to have even more impact. There's a lot of context that folks like myself, ████████ have that is needed for informing the direction of certain aspects of these types of projects. If able to develop this "taste" by getting closer to how our research process works, how our systems are architected, I think that it could be hugely unlocking. — Collaboration: Much smaller point. Collaboration is generally amazing. But I perceive there's a bit of a desire to play all of the roles — Lead, Architect, SWE, PdM, and even PjM at times. A lot of this happened earlier on, but I still see it happening in fits and starts at times. That can work that way (and almost has to work that way) when in the rapid experimentation phase early on in a project like ours. But I'm not sure that can really work as the project scales in the way that it has. Could do a better job of offloading, delegating (esp. some of the PdM/PjM types of responsibilities that he would occasionally try to take on when we already had a PdM). The overwhelming takeaway here is that he is phenomenal. We wouldn't have gotten as far as we have on PAT without you. And we're only just getting started.

Lots of support during the PAT testing period and good tracking of themes to improve across meetings rather than just tracking the bugs. No outcomes for me to evaluate, since the tool wasn't very helpful at the stage it was during said period, but I hope the feedback was useful for you as a developer

An absolute force in execution and a true dev force of nature. Ships high-quality code fast and shows deep understanding of both our architecture and AI enablement. In PAT, I have seen him step up as a vocal, thoughtful leader who sets clear goals for himself and the team and follows through. I think its fair to say the success of PAT is really attributed to your vision and work ethic, and the palpable passion you have to make this product a smash hit across every dimension. Partnership on input table prefilters and Code Assist has been excellent, and with the context developer crew has set a high bar for engagement, staying close to the work, responsive, and motivating. I also really value how receptive he is to feedback. Even when I have been direct about things that did not go well, takes it seriously and adjusts quickly, which says a lot about maturity and drive to improve. If there is one area to keep working on, it is communication and framing. Sometimes the way things are worded can come off as a bit dismissive toward product or the broader tech org, even when that is not the intent. The "if I do not do it, no one will" mindset has been a big part of what makes him successful, but softening how that comes across in public channels would go a long way. I would also like to see him delegate and loop others in more. When we have sat down together to hash through PAT roadmaps or priorities, the sessions have been great, and I think they would be even better if he pulled me and others in earlier or more directly on areas we can help drive. Lastly, I would love to see more active instilling of his ethos and way of operating across others. Its not uncommon that I hear users saying "I wish we had more of him" and I can imagine a push on embedding your goodness in others being huge. That small shift would help scale impact even further.

This dot only reflects the last few weeks working on PAT. You're delivering rapidly while owning most of the architecture and planning; so far that has been successful. It's a level of ownership that's above what I saw when we last worked together on Plaid a year ago. You also bring a welcome enthusiasm to the team day in and day out; it's been great to work with you! I don't have much constructive feedback yet, but I'll say that so far, PAT has been a small team with a singular focus and few outside dependencies, so I look forward to seeing how you handle the challenges as that changes — a new stack, broader goals & ambiguity, and plugging in elsewhere in the FDE space.

This was my first time working with him, and man, he crushed it. What he did with PAT (and just as important, the speed at which he did it) was fun to see. Navigated the technical complexity of the ideas we were trying to spike out excellently. In addition to HoK work, stepped into the architect role quite nicely/naturally, and done a good job of ensuring we balance speed w/ quality and knows when its important to push on each of those attributes. Always eager to learn/try things out, and just overall a fun person to work with. The main piece of feedback I would have left had this been 2 months ago was that I think there's work to be done on balancing open-mindedness vs assertiveness (where you were sometimes overly assertive)... but the loops on that dimension have similarly been great. Calling it out partially because I think it's a thing we need to make sure keeps up, but mostly to just say the loops on your end have been noted.

Great delivery over the past couple of weeks. Both from a speed and quality perspective — love it

You've been a delivery machine during this push to PAT demo-complete, in terms of your own code delivery and running a pretty tight ship for planning, execution, and priority among different threads.

Pocket Analyst UX is so incredibly sleek now. So well done

incredible job with the re-design of PAT (both UI and arch). still some small things to iron out, but this is so, so much better

Just reflecting on initial experience with PaT, was impressed with the speed of iteration and voracity for honest feedback.

Excellent collaboration this week on PAT design - fruitful discussion and answering my questions across several levels, with help me get up to speed and fill in gaps

Good engagement today in PAT and FDE demos - great to see you on the field answering questions from broad audience. Also had compelling questions for folks presenting in FDE demos.

Good code review comments on my first context PR - helped me learn how to think about context and do the later ones better

On Pocket Analyst, took ownership in a great way: iterated quickly on architecture, made it easy for the business at appropriate times and clearly, was transparent without letting transparency become too distracting from the work, responsive on needs from others. I'm very happy with him on the team: Pocket Analyst is ambitious and ambiguous and he is navigating that smoothly, great relief for me personally. Areas for improvement: - It's clear when you are engaged in a discussion, but also clear when you are disengaged. Meetings can be a drain on you — you allowed yourself to fully focus on meeting content and find a way (with meeting RPs/others) to *make* the time more should help make it easier to shape our time together — please do so. - Find more ways to bring building blocks back to the community. You are blazing a trail to a hilltop but there are smaller traveled that need more of a nudge from you to lay the path. - Reflect more transparently on your process. We used to have retrospectives but given the nature of forward deployed work I'd love to get a crisp understanding from you of how things are going and how you're diagnosing issues in the process. - Sometimes you have an idea that you want to pursue despite pushback from others. This can be okay and healthy but I've found that digging deeper into these issues with you find us in a game of semantics because it's like we agree and disagree at the same time but we don't know where the distinction comes from. - Get closer to the business content: it's remarkable that you're able to bridge the gap so well but on occasion you'll gloss over a use case. Related to this, sometimes I think you try to answer business questions and it doesn't come as strong and clear — foster that understanding and close that gap.

re: sandbox check-in meeting you really acted like an owner in driving requirements for sandbox work today. it was an extremely high bandwidth conversation. came out of the meeting with a lot of clarity on what we should be building and how that immediately impacts your work also can tell you've built a lot of context in the alpha engine space now and it shows

PAT demo was great. Very exciting to see you all putting this together out of what seem like really important fundamental building blocks that we'll use over and over. In particular, I'm very excited about the 'write everything down in LLM-consumable contexts and learn from it' approach. Also thought you found a good way to address a large volume of on-the-fly questions. Looking forward to seeing this evolve.

Worked with me on code-assist and BOTS. Overall, great to work with - was the one I remember with the opposing view of how we should do code-assist in order to do things vs pure context. Also greatly improved the code-assist tests on BOTS was great to work with - was good at popping issues - one piece of advice would be to dive into the platform more rather than waiting for enablement

redot w/ topic above - 5. Expectations @ L5. 5 is for above the bar delivery and for the large amount of idea generation and clarity i drove across multiple unclear projects with a lack of direction and driving design + clear and aggressive execution. PAT clearest example of this where I've excelled across 4 projects this year, 3 of them being ambiguous projects. Was holding a wide view of Plaid prior to its shut-down and driving the core problems in the compiler while delivering features, priorities and building/delivering books of work (reworking list handling throughout compiler; function dispatch; fixing optimization frameworks; lambdas etc.) Finished the swing on pre-filters. built out the BoW and delivered it while managing UATs etc. w/ ████. Grabbed pre-filters and core issues while taking an uncertain feature into a clear and stable place. Post-Plaid got thrown into an uncertain authoring team: ideated the Logic Model and drove it to completion and proliferation. become the foundation of many spin-off projects and one of the major arch wins in ST over the past few years. Set the ground for new logical analyses (e.g. new linting rules, the inferred outputtables LSIP + POC). Lastly, the Logic Model took a massive bar to develop now because of the substantive refactors i designed and implemented (e.g. migrating to scala case classes, which simplified rollout). Presented the work and knowledge shared, and now the work stands on its own and has been easy to extend. Code Assist: jumped into another uncertain world and took it through completion with ████ + ████. Especially later in the process, getting users motivated to get Code Assist in an excellent state (driving a lot of the Hackathon etc.). threw a ton of energy into new books of work and design. Developed the "toolbox" (your naming may vary) approach and design docs that are now the standard, pushed towards the approach of small incremental design that compounds. Took over testing framework effort that was failing and delivered clarity, delivering 20x speed improvements and vastly simpler stack w/ ████ in ~1 week. The work ████ + I did here spun off the business-co-led code assist developer project, where i was guiding IEs across various contexts for delivery: helped ████ design ST migrations which he pushed to the wider community; plethora of code assist contexts. In general, IEs/IAs and helping them build their solutions. PAT: worked w/ ████████ to define a good goal, and then drove project w/ team through ambiguity on multiple axes: product and tech. Paved the way on new design across a load of axes: high-level tech arch, caching execution of python, LLM code-gen for pandas compilation, agentic frameworks in AE, testing of agents. Product-wise navigated a huge number of ambiguities and made quality calls that have paid off. As of last ~month have also been managing project at the goals and execution level. Project not delivered yet but delivered the CIO Summit, where PAT is becoming part of BW's AI posture. Resulting from the clarity i helped build in PAT, it's now back to Tech (e.g. now one of primary drivers for GitLab, sandboxing, composer vizlets et al).

Good focus, good clarity, and leaving space for thinking.

Impressed at how you react well to feedback and show immediate change in collaboration and communication. Case at hand: last week about how we work together shifted the next day into a meaningfully better way of working together. Thank you.

Lead the team very effectively. And it was pleasure working with you. Learnt a lot from you.

This week was tough. Came off a hard drive to execute for CIO Summit after a long 3 months + got sick, and I faltered. Up until now, I've purposefully kept PAT siloed to keep thought clarity and clean execution. I didn't effectively anticipate what the level of clarity is going to need to be for PAT to land bigly and (2) not being communicated to the people who feel they need it. I've been thinking small. For curious readers: I'm tackling first-class and expect much more clarity over next day or two. Giving myself some grace because this is new for me, but... I was mentally complacent and was riding the ego high of having built something that people like PAT, the time for feeling good about is coming to pass, and it's time to be cut-throat again. One big failing here is that I've been stuck on having full ownership over the tech design. I need to open it up and get help and experience here and make sure I'm not missing things (my lack of rigor+experience here is obvious based on ████'s reco). Now that PAT is changing, I need to be less hands-on with some things and more hand-off with others. The scale of things changing is a combo of an unexpected happy outcome, but also some lack of forward-thinking.

Super helpful to chat with you today. Definitely I am struck by your fierce focus on momentum and objectivity identifying what matters most. I felt very heard when we got to the kernel of what Sandbox is really solving, and likewise it was helpful for me for you to clarify where in PAT those concerns do and do not apply. Great collaboration.

Listening well and probing to understand my feedback for tightening work tracking (tickets, MRs, sharing context more, reducing overhead solution. Constructively (as we discussed a bit live) as TL you would benefit from proactively assessing level of context for folks involved. Make sure handoffs and asks are clear. Evident for external partners, but also for internal folks because we don't / won't be working in the same work areas to the degree we did a few weeks ago.

Noticed a positive upwards trend in your collaboration with others in the recent period. Pulling on others for feedback along the way, and pushing more on providing transparency (e.g. GA thoughts) with senior tech leadership ahead of time and well communicated.

being a little weasily in pat retro re. pixi stuff

really, really excellent work getting PAT to where it is today. I know we haven't launched (just) yet, but you should all be incredibly proud.

always willing to get your thoughts out there and give feedback. such a great partner. thank you

Congrats on the Code Assist GA release. It's really a game changer, one which honestly has significantly exceeded what we knew it could help our investors, but you and the team have turned it into something that's become the poster child of what we can do. You've created so much excitement and goodwill along the way. Thank you.

After just a few meetings on the AI analyst project with you today, overwhelmingly excited to be working on this with you, delivering tons of impact.

I think you guys have done a really good job being understanding of the challenge in setting aside time to help with our work but also making sure the ball keeps rolling. Makes you great to work with.

Excellent Tableness-like Python spike. Both the initiative and the swing. Really great energy here. Also thought you were good at bringing the AI code assist discussion to a higher level in the meeting today.

#ManagerReview Mid-Year - Above Has had a pretty solid first half of the year. Strong contributions on the logic model and a good start in the AI space. Have watched him go from behind the scenes to take a leading role in driving the code assist hackathon, helping colleagues and push ethos of AI assist authoring. The logic model was a proposal thought through fairly independently that is now helping bridge a few different gaps. I think what needs to be worked on is how to process and deal with conflicts, friction and out-of-syncness effectively. Gets frustrated, tends to carry a synthesis in his head at time without testing it out, which can lead to a bit of long-winded conversations and distress. For him to make more impact - especially in this high paced, changing environment - needs to learn how to give his teammates more grace, be more explicit and not get easily flustered / frustrated.

Pretty instrumental to this AI analyst push. Great thoughts on design as well as on execution. Finding your strategic instinct valuable as well.

I find it hard to sync and to stay in sync with you. You often jump to conclusions and then stick to them in a way that I find consuming, I just don't expect this from engineers at your belt on my team. The latest is the belting conversation over...

Good stuff today. Excited to be tackling this problem with you all

Good design for gen, execute, schema for AI analyst

Appreciate your feedback -- keep this coming. Thank you. Hopefully a good clarifying working session for both of us this morning.

introducing me so i could put faces to names

I thought your ribbing at ██████ when you got on the microphone in front of the entire company missed the mark by 20%.

Pretty impressive demo of Pat. Looks like you've accomplished a lot, including a lot of good fast loops/pivots, in a short time (having metrics), the dash UI experiments, the multiple pivots on the agent architecture itself. And it was a tight demo — brought the room through it well, anticipated questions, good timing.

PaT demo for tech. Great walk through not just of product to date, but learnings to get here, paths discarded along the way.

Presentation on Pocket Analyst was very well-organized: telling the story and navigating levels of detail and demonstrating the product.

Good, assertive, off-the cuff thoughts on how product limits should hit users in Hydra, during realtime post-mortem.

Lunch dot - I think you're right that it's not ideal in the long term and would build more community to eat together.

I am wary of my bias to be overly bullish on Pat the pocket analyst (and possibly for you to all to be excited enough to be a bit biased as well) -- but in my view you all are doing a great job. Would get more skeptical voices from AIA to tear at it even before our beta testers do — but the importance of standing up the benchmarking looks good. Strategic thinking good as far as I can tell, particularly on the importance of how important you are. All add up to pushing the distribution of outcomes further to the right by both raising the floor and raising the upside for how this can scale. Feels like I am watching a special effort come together with really high quality data) even if it falls short of our hopes.

You've been crushing things recently -- esp the various bugs we've been running into and the broader architecture thread. Always very much so enjoy the process in which you've been doing all this stuff recently (collaborative, open minded). Always willing to listen, unblocked, and generally just fun to work with

Two things at two levels for PAT. Great collaboration, architecture, delivery, and troubleshooting.

A few good things I saw today in our engagement. Listening well and developing others.

Loved getting to see you demo your work earlier this week. Great courage in presenting and solid code delivery.