vault backup: 2024-12-15 23:22:57

p-society · Dec 15, 2024 · 023fd9b · 023fd9b
1 parent 1e3d70d
commit 023fd9b
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 2 deletions.
diff --git a/content/General/Best Practices.md b/content/General/Best Practices.md
@@ -1,8 +1,10 @@
+----
+
 Unlike [guidelines](Guidelines), these are not enforcements. They are suggestions and advice for writing performant, maintainable and scalable code. You should follow these to have a great degree of control over the code you write, avoid unnecessary abstraction and [technical debt](Glossary/Non-technical/Technical-Debt) in the code base.
 
 ### 1. Write Atomic Code
 
-It is easy to keep bundling functionality into a single block of logic in our code. We must avoid this and write code that is decoupled, atomic and reusable.
+It is easy to keep bundling functionality into a single block of logic in our code. We must avoid this and write code that is decoupled, isolated and reusable.
 
 Say, we have to implement a function `renderPDFAndUploadToS3` that has to:
 -  render some template HTML into a PDF

diff --git a/content/General/Workflows.md b/content/General/Workflows.md
@@ -1 +1,7 @@
-Picking up a feature, understanding requirements, reaching out for doubts (technical and requirement), maintaining documents
+#WIP
+### Picking up a feature
+### Understanding requirements
+
+### Reaching out for doubts (technical and requirement)
+
+### Maintaining documents