From 1a0eaf184b429e4563341c8df045a6652fade125 Mon Sep 17 00:00:00 2001
From: Sven <6847381+svengeance@users.noreply.github.com>
Date: Sun, 16 Oct 2022 02:14:22 -0500
Subject: [PATCH] Create code-organization.md

---
 code-organization.md | 5 +++++
 1 file changed, 5 insertions(+)
 create mode 100644 code-organization.md

diff --git a/code-organization.md b/code-organization.md
new file mode 100644
index 0000000..d18845b
--- /dev/null
+++ b/code-organization.md
@@ -0,0 +1,5 @@
+### Putting Code Where it Belongs:
+
+Code organization is an opinonated endeavor that's easily overlooked - it's easy to focus purely on _what_ to write instead of _where_ it'll be written.
+Proper, consistent code placement enables you to enjoy refactoring by minimizing the chances of inadvertently accessing wrong code; and there's more to it than a rigid file structure. Using some of the newest language features, we can work on separating our data, logic, persistency, and display elements so that we our code can be concise, focused, and readable. 
+This talk will go over some of my own approaches and guidelines to code separation mimicking real-world examples that can be broadly applied to many projects, though with a focus on a typical ASP.NET Core setup.