Skip to content

Commit 6c2c918

Browse files
vault backup: 2025-12-14 12:40:42
1 parent 5a71edd commit 6c2c918

3 files changed

Lines changed: 68 additions & 0 deletions

File tree

src/content/index.md

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,62 @@ tags:
159159
</tr>
160160
</thead>
161161
<tbody>
162+
<tr>
163+
<td>
164+
<img src="1404-09-26-It-Works-on-My-Machine/poster.png" alt="1404-09-26-It-Works-on-My-Machine">
165+
</td>
166+
<td>
167+
<div class="title">
168+
<a href="1404-09-26-It-Works-on-My-Machine/notes.md" >#006: It Works on My Machine !</a>
169+
<span> | Docker: From a Tool to a Cultural Shift</span>
170+
</div>
171+
<a href="">
172+
Saba Soltani Firooz
173+
</a>
174+
<div class="tags">
175+
<span class="tag">Nov 19, 2025</span>
176+
<span class="tag">docker</span>
177+
<span class="tag">containers</span>
178+
<span class="tag">software-deployment</span>
179+
<span class="tag">devops</span>
180+
<span class="tag">reproducibility</span>
181+
<span class="tag">portability</span>
182+
<span class="tag">developer-experience</span>
183+
<span class="tag">team-workflows</span>
184+
<span class="tag">collaboration</span>
185+
<span class="tag">software-culture</span>
186+
</div>
187+
<div class="description">
188+
<p>
189+
Before Docker, deploying software often meant uncertainty, manual setup, and the infamous
190+
<em>"it works on my machine"</em> problem.
191+
Docker didn’t just introduce containers — it introduced reproducibility, portability,
192+
and a new way of thinking about software.
193+
</p>
194+
<p>In this talk, we’ll explore:</p>
195+
<ul>
196+
<li>
197+
<strong>How Docker was born</strong> and why the industry needed it
198+
</li>
199+
<li>
200+
The core <strong>technical ideas behind containers</strong>
201+
<span style="opacity: 0.8;">(without the boring parts)</span>
202+
</li>
203+
<li>
204+
<strong>How Docker reshaped team workflows</strong>, DevOps culture, and the developer mindset
205+
</li>
206+
<li>
207+
Why Docker is <strong>less about technology</strong>, and more about
208+
<strong>how we collaborate</strong>
209+
</li>
210+
</ul>
211+
</div>
212+
<div class="resources">
213+
Resources:
214+
<a href="">Slides (Will be uploaded soon)</a>
215+
</div>
216+
</td>
217+
</tr>
162218
<tr>
163219
<td>
164220
<img src="talks/1404-09-19-When-Models-Become-Actors/poster.png" alt="Intro to Game Theory Poster">
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
2+
>[!info] Presenter: Saba Soltani Firooz
3+
4+
> **Overview:** Before Docker, deploying software meant uncertainty, manual setup, and the infamous “it works on my machine” problem. Docker didn’t just introduce containers; it introduced reproducibility, portability, and a new way of thinking about software. In this talk, we’ll explore:
5+
> - How Docker was born and why the industry needed it
6+
> - The technical ideas behind containers (without the boring parts)
7+
> - How Docker reshaped team workflows, DevOps culture, and developer mindset
8+
> - And why Docker is less about technology, and more about how we collaborate
9+
10+
---
11+
### Lecture Notes
12+
Will be added soon :)
2.28 MB
Loading

0 commit comments

Comments
 (0)