Warsaw Meeting Tuesday 4th

Live
Executive Summary4–6 bullets · decisions, cost impact, schedule impact, top risks
1

1.1

1.1.1
How does product adjust?
1.1.2
how does arch adjust?
1.1.3
Eng needs to have more of a product mindset and product needs to be building more
1.2

1.2.1
Full AI developed, but starting from scratch with less legacy dependencies
1.2.2
Better auth than we currently have, stripe integration for self service montetization with plug ins
1.3

1.3.1
Use AI iterations to reduce product rework by front loading discovery and find the best solution
1.3.2
Wants it to be in Vue and Postgres so hand over is easiest for ENG
1.3.3
Eng skeptical that the hand over will be efficient 
1.3.4
1.4

1.4.1
25% of time on code, is the optimization the actual issue
1.4.2
PRoduct going through vercel iterations allows for easier dog fooding to make requirements more clear and accurate because there are miles on ai
1.4.3
3/4 of work is before the coding
1.4.4
Ben "fix product first" 
1.4.5
Both sides need to solve for their inefficiencies (pre dev and dev)
1.4.6
interally test to see if it creates value with layer it on 
1.4.7
1.5

1.5.1
Split teams into smaller domains and smaller head count to reduce communication overhead. Have them focus on bugs and TD 
1.5.2
Bigger companies like atlassian are spending 25-40% on TD
1.5.3
Small teams like 3-4 with 1 person dedicated to TD, bugs and public channles
1.5.4
2-3 others just focused on new features
1.5.5
Nick has bots that monitor logs that go and fix errors. Why aren't we doing it in Sentry
1.5.6
Certain features are legacy and holding us back
1.5.7
With the knowledge known now how quickly could W2 reimplement tasks in? 
1.5.8
Do we have configured skills to make sure ai agent are consistent and effective across teams
1.6

1.6.1
Using ai to go from functional requirements then iterate on technical decisions to then develop technical specs to make development of production code with ai in one massive prompt
1.6.2
Going through the feedback loop internally with prototypes rather than with production release
1.6.3
Nick wants hand off through skills to make the code 80% there with engineering polish makes translating to prod easy
1.6.4
Meeting minutes prototype better than bidding because Eli is closer to the source of feedback
1.6.5
PM's become more engineers and engineers get more producty
1.6.6
Everyone needs to be in the mindset of iterations and automation to get better features
1.6.7
Eli vibe codes and merges 20k lines of code
1.6.8
Need a plan to bridge the gap from prototype to production code
1.6.9
why does engineering need to reverse engineer rather than integrate the code
1.7

1.7.1
Pre-development from Nick's perspective is solved for. Prototype and kick the tires until were happy
1.7.2
Unified skills to make the code and tech stack as aligned and effective as possible
1.7.3
Short term that does not matter but long term that gap will close so should be working towards the prototype can eventually be used with minimal hand off 
1.7.4
Get the design system into the prototypes and other changes to make it more effective and efficient
1.7.5

1.8

No notes yet — type your own, or generate from the transcript.
1.9

1.9.1
The team discussed the rapid development and deployment of standalone AI-driven applications within the industry, noting the implementation of an isolated app prototype for change orders. No formal decisions or action items were established.
Title
Warsaw Meeting Tuesday 4th
Starts
Aug 5 · 5:20 PM
Ends
—
Timezone
Not set — shown in your local time
Frequency
One-off
Location
Location / project
Web Conference URL
Zoom / Google Meet / Teams link
Description
Add a description…