aboutsummaryrefslogtreecommitdiff
path: root/content/posts/software_engineering.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/posts/software_engineering.md')
-rw-r--r--content/posts/software_engineering.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/posts/software_engineering.md b/content/posts/software_engineering.md
index aa5e8e9..91d596b 100644
--- a/content/posts/software_engineering.md
+++ b/content/posts/software_engineering.md
@@ -1,6 +1,6 @@
+++
title = "Notes on Software Engineering"
-date = 2025-02-04
+date = 2026-02-04
+++
I worked at a large software company, [SAP](https://www.sap.com) for three years. But I didn't get to learn much about software engineering. SAP has its own tools and process that have already dictated how things work. But over the years, I have realized how important software engineering can be. Here I outline some of the lessons I have learnt (some with a lot of pain) about this. If you are reading this and don't know where you or ytour team stands on software engineering, take the [Joel Test](https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/). This is a living list and will be kept up to date based on my experiences.