diff --git a/chan.dev/src/content/dailies/2024-03-28.md b/chan.dev/src/content/dailies/2024-03-28.md
new file mode 100644
index 00000000..549730ec
--- /dev/null
+++ b/chan.dev/src/content/dailies/2024-03-28.md
@@ -0,0 +1,17 @@
+## Three goals
+
+## Tasks
+
+# Interview cut-up process
+- Export two-up in Riverside (normalize audio)
+- Download assets
+	- Host
+	- Guest
+	- Exported two-up
+- Resolve
+	- Add to media pool
+	- In Edit page,
+		- `Create New Multicame Clip from Selected Clips`
+			- Sync angle by soundwave
+		- `Open Clip in Timeline`
+		- Sync audio manually (if needed)
\ No newline at end of file
diff --git a/chan.dev/src/content/dailies/2024-03-29.md b/chan.dev/src/content/dailies/2024-03-29.md
new file mode 100644
index 00000000..e08e8679
--- /dev/null
+++ b/chan.dev/src/content/dailies/2024-03-29.md
@@ -0,0 +1,14 @@
+## Three goals
+
+## Tasks
+
+IT GETS HARDER
+
+🆕 interview with @aarondfrancis and @chantastic for #LayoffLog 🆕
+
+There's a huge amount of humanity in this interview. I was tempted not to share it, because it felt so personal. But in my new favorite phrase by Aaaron:
+
+POST ALL OF IT!
+
+
+sadly, riverside.fm did us a little dirty this time and video quality is significantly degraded.
\ No newline at end of file
diff --git a/chan.dev/src/content/projects/2024-epic-web-conf.md b/chan.dev/src/content/projects/2024-epic-web-conf.md
index fe2d4ef1..939c5f73 100644
--- a/chan.dev/src/content/projects/2024-epic-web-conf.md
+++ b/chan.dev/src/content/projects/2024-epic-web-conf.md
@@ -7,10 +7,10 @@ effects:
 
 ## Tasks
 
-- [ ] Book travel
+- [x] Book travel ✅ 2024-04-08
   - [x] Await budget. $450, include travel insurance ✅ 2024-02-20
   - [x] Book outgoing flight $138.98, 4/9 ✅ 2024-02-27
-  - [ ] Book return (or 2nd leg) flight
+  - [x] Book return (or 2nd leg) flight ✅ 2024-04-08
 - [ ] Write talk
   - [ ] Create checkpoint pieces of work
     - [ ] Write outline
@@ -59,3 +59,108 @@ Possible checkpoints:
 
 **Visual Testing UI with Storybook**
 
+## 04-08-2024
+
+- Hired: Storybook to Web Devs (UI Dev)
+	- Funnelling vs Why
+	- Talks
+	- SB: very interesting testing solution
+		- CSF3 is genius
+			- https://storybook.js.org/docs/api/csf
+			- https://github.com/ComponentDriven/csf
+			- Object syntax
+			- https://www.youtube.com/watch?v=Waht9qq7AoA&t=34s
+			- Killer features
+				- composition
+		- Ideas in the space
+			- Playwright
+			- SB
+			- Cypress
+			- etc.
+			- JSDOM
+				- (the old way)
+		- Difference
+			- "2nd environment problem"
+				- only a problem for DEVs
+				- Design systems (Figma, Storybook)
+				- Component Libaryr (Storybook, Ladel)
+- Examples
+	- Tic-tac-toe is good
+	- Epic Web workshop
+		- tic-tac-toe
+- Termonology
+	- Story
+	- CSF
+	- "Stories without Storybook"
+	- interactive UI test
+	- visual test
+- Anecdotes
+	- My job at Storybook
+	- What Astro taught about what I wanted from Storybook
+		- chan.dev
+		- wanted to use storybook for interactive components
+			- Pick a framework for Storybook
+			- No .astro
+		- CSF directly
+			- .stories
+			- my/page/path/stories
+				- in `dev`
+	- Maybe Storybook "tries to hard"?
+		- The right layer of integration is CSF
+			- Why?
+				- "2nd env problem"
+				- mirror
+					- this can't happen without a ton effort
+					- why do i want to recreate Next.js?
+						- Next.js webpack => turbopack?
+						- How to support new unknown (Astro)
+					- exponential problem as ecosystem develops
+	- **CONSCIOUS UNCOUPLING**
+		- https://goop.com/wellness/relationships/conscious-uncoupling-2/
+		- solar system metaphor
+			- https://giphy.com/gifs/solar-system-Sugs8e7Qm44a4
+			- independent movement toward same goal
+		- Storybook *seems* like an uncoupling
+			- And duplicated config even seems to attest to how uncoupled it is
+			- Two things that have to remain synced to be work effectively are coupled
+- Concerns
+	- Having to choose a framework seems like weird constraint when selecting a UI- documenting tool
+		- No reusability?
+			- CSF using testing-library, should be able to re-use even if i swap out the library of the component under test
+	- Sub-rant
+		- I'm not a code contributor
+			- acceptance: can't *own* it despite my *wanting* it
+				- bad maintenance is worse than non-creation
+					- caring => doing => owning
+						- what does owning looking in a project that's already overrun with requstes
+						- OSS maintenance, direction, hard to prioritize (exponential)
+- Why is this talk happening?
+	- WE NEED MORE "Storybooks" not Storybook integrations
+		- Lean 100% on framework's rendering strategy
+			- opts us out of client v server v ssg v ssr
+			- opts us out of config dulpicating
+			- we can focus on authering ergonomics
+			- focus on in-framework developer experience
+				- 2rd envinorment problem"
+		- Increases reusablity of tests W/O having to go full e2e
+- different types of testing strategies
+	- UNIT
+		- TS (dev-time)
+		- remainder: run specifics
+			- But in most cases, better via integrations
+			- joining first name last name
+	- Integration
+		- JSDoc / Jest
+			- Cypress but wanted to test styles
+				- grab dom styles and test specific style values
+				- reality: i just want to know it dsnoet look different
+				- harness-aware, brittle tests
+				- **'does it actually LOOK different'**
+	- E2E
+		- user-modeling problem
+		- beautiful things about componnets
+			- function of props
+			- go as hard as you want in building test cases without some
+				- no <AuthenticatedUserProvider /> context needed
+			- isolated from your broader system. this isolation is a valuable aspect of components
+				- correct / sound decisions at the edges of appliation design