Init
This commit is contained in:
13
Career/Projects/AI/AI.md
Normal file
13
Career/Projects/AI/AI.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
created: 2025-07-09 10:20
|
||||
updated: 2025-07-09 10:20
|
||||
---
|
||||
Starting point:
|
||||
<https://github.com/snwfdhmp/awesome-gpt-prompt-engineering>
|
||||
|
||||
<https://m.youtube.com/watch?v=8omTe58MNQE>
|
||||
<https://docs.text-gen.com/>
|
||||
|
||||
[[The Proof Reader]]
|
||||
|
||||
MOdels /s
|
||||
11
Career/Projects/Model cache/Model cache.md
Normal file
11
Career/Projects/Model cache/Model cache.md
Normal file
@@ -0,0 +1,11 @@
|
||||
A cache tied to the model, is automatically clear when saving. This allows for caching without much thinking about cache invalidation.
|
||||
## Usage
|
||||
Call the model cache method on the model to access it
|
||||
## Todo
|
||||
- [x] Create a class which implements the cache methods and tags all caches. ✅ 2023-10-28
|
||||
- [x] Create a trait which allows for access to this cache and clears is on saved. ✅ 2023-10-28
|
||||
- [x] Add readme about usage. ✅ 2023-11-05
|
||||
- [ ] Allow for the adding of other tags, so the cache can store values dependent on multiple models.
|
||||
- [ ] Make the cache macroable so complex callbacks and tag configurations can defined just once. Add a cache()->toArray() example.
|
||||
- [ ] Add a class factory as a place to store these macros.
|
||||
|
||||
9
Career/Projects/Overbuild Laravel/Overbuild Laravel.md
Normal file
9
Career/Projects/Overbuild Laravel/Overbuild Laravel.md
Normal file
@@ -0,0 +1,9 @@
|
||||
A attempt to split Laravel into domains and modules to support large projects without creating a ball of mud.
|
||||
## Structure
|
||||
The app folder has been removed and instead of that there are multiple folders in to root. Each resembling the app folder.
|
||||
|
||||
These folders are different domains. Pieces of the overal system that are or could be loosly coupled. Information exchange between these domains must use events or by specifically designated services.
|
||||
|
||||
Events are used to lat subscribers from any domain know something happened and it's up to that domain to die with that information what is want.
|
||||
|
||||
Service are used to query and command other domains.
|
||||
Reference in New Issue
Block a user