refactor(content): keep single placeholder episodes for podcast sections
This commit is contained in:
@@ -1,16 +1,9 @@
|
||||
---
|
||||
title: "Stable Frontend Systems"
|
||||
---
|
||||
title: "Poyraz ile yazılım'a dair yakında başlıyor."
|
||||
date: "2026-02-23"
|
||||
youtubeUrl: "https://www.youtube.com/watch?v=XWUeVzf0t6Y&t=2s"
|
||||
spotifyUrl: "https://open.spotify.com/show/placeholder-yazilim"
|
||||
podcast: "yazilim"
|
||||
---
|
||||
|
||||
## Episode Notes
|
||||
|
||||
This one is about component contracts, UI consistency, and reducing regressions in fast-moving projects.
|
||||
|
||||
## Sources
|
||||
|
||||
- Design token architecture references
|
||||
- Next.js App Router docs
|
||||
## Poyraz ile yazılım'a dair yakında başlıyor.
|
||||
|
||||
@@ -1,16 +0,0 @@
|
||||
---
|
||||
title: "Writing Cleaner Service Layers"
|
||||
date: "2026-03-02"
|
||||
youtubeUrl: "https://www.youtube.com/watch?v=H8sP8HejI7A"
|
||||
spotifyUrl: "https://open.spotify.com/show/placeholder-yazilim"
|
||||
podcast: "yazilim"
|
||||
---
|
||||
|
||||
## Episode Notes
|
||||
|
||||
We discuss service-layer boundaries, validation ownership, and error mapping strategy.
|
||||
|
||||
## Sources
|
||||
|
||||
- Practical clean architecture examples
|
||||
- Team code review checklist
|
||||
@@ -1,17 +0,0 @@
|
||||
---
|
||||
title: "Foundations Over Tools"
|
||||
date: "2026-03-09"
|
||||
youtubeUrl: "https://www.youtube.com/watch?v=9JEOGCX5aSQ&t=22s"
|
||||
spotifyUrl: "https://open.spotify.com/show/placeholder-yazilim"
|
||||
podcast: "yazilim"
|
||||
---
|
||||
|
||||
## Episode Notes
|
||||
|
||||
This episode focuses on software fundamentals and why architecture basics matter more than tool hype.
|
||||
|
||||
## Sources
|
||||
|
||||
- Domain modeling notes
|
||||
- Node.js internals docs
|
||||
- System design interview references
|
||||
Reference in New Issue
Block a user