zaine/org_roam
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updates on some notes

Browse Source
This commit is contained in:
Zaine Arch
2026-01-25 15:06:43 +00:00
parent 0b042238b2
commit 56feb90d9a
4 changed files with 17 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
20250724230557-books_org_agenda.org
View File

@@ -7,7 +7,7 @@
#+filetags: :books:org:index:
#+DATE: 2025-05-19
#+STARTUP: content
#+PROPERTY: GENERATED_AT 2026-01-24T00:00:01.736252
#+PROPERTY: GENERATED_AT 2026-01-25T00:00:01.130521
* Career
** Clean Code_ A Handbook of Agile Software Craftsmanship - Robert C. Martin :Read:

2
20260101010049-concepts.org
View File

@@ -18,7 +18,7 @@ Part of being a software engineer is having a good grasp of mathematical concept
- [[id:275988a8-59d8-40c8-a8b4-47118d6eb834][Big O Notation, Time and Space Complexity]]
- [[id:631b2086-4b8f-4fe3-829d-be1dc014e293][Design patterns]]
- [[id:631b2086-4b8f-4fe3-829d-be1dc014e293][Design patterns]] WIP
- [[id:49b195c8-e116-40ca-86e8-62c65dbb5a4f][API Architecture]] WIP

15
20260104155940-server_backend.org
View File

@@ -41,3 +41,18 @@ The project is packaged as a Docker container, making it easy to deploy. You can
docker logs -f org_backend
#+end_src
* Bruno
Bruno is used for testing the backend API endpoints. It is a simple HTTP client that allows you to send requests to the backend and view the responses. I used the OpenAPI specification to generate Bruno tests for each endpoint.
* Future?
** Integration with ~notes.zainezq.com~
As the API is primarily used by ~zainezq.com~, I want to think of ways that ~notes.zainezq.com~ could also use it. This website is used to store all my notes, and they are exported using ~org-publish~ in Emacs. Perhaps I could write an Emacs Lisp package that interacts with the backend API to store and retrieve notes.
Flow of how a note would be written:
1. User writes a note in ~notes.zainezq.com~ as org mode.
2. When the note is saved, a POST request is sent to the backend API with the note content.
3. The backend API stores the note in the database.
4. This will trigger a function that republishes the notes website to include the new note.
**Need to think more about this.**

1
20260121173318-api_architecture.org
View File

@@ -4,4 +4,3 @@
#+title: API Architecture
#+filetags: :notes:concepts:api:
[[./assets/career-notes/api-layers.png]]