Selfhosted Information flow
https://mermaid.js.org/syntax/entityRelationshipDiagram.html
TL;DR
You better write daily/weekly notes and work with them
Intro
- Why Im writting this post: bc I want to standardize the way i capture information across my forcely scattered daily flow and create meta-frameworks with it to apply cross-domain
- What Ive learnt with it: When principles/ideas are clear, just apply them harder
Why you need this
I dont care if you are a director, an IC that moonlights has independent consilting work, or a solo-preneur:
QnA to the team to avoid accountability laundring 🚀
Use when someone asks for a quick call without enough written context:
…and weaponized incompetence 🚀
I cannot jump on a call right now, but we can probably handle it async.
Can you send:
- the exact error or behavior
- what you already tried
- the doc/wiki section you followed
- what result you expected vs what happened
Once I have that, I can point you to the right fix or doc update.
You better ask questions on time
QnA for Product teams 🚀
Yep, make sure meetings are clear and actionable :)
EOD Accountability Review:
- What did I move forward today?
- What did I make clearer for other people?
- What ambiguity did I convert into owner/action/trigger?
- What is still exposed?
- What should be visible in the weekly summary?
When you are a solo-founder, you dont have time for bs.
You can avoid noise, non-sense promises, wishes with such form: https://app.formbricks.com/s/cmtljp6ee1j5d01xdkqdqpdyp
QnA for ppl that need help with their ideas 🚀
The Setup
Earlier this year I got my read books notes distilled with very interesting feedback
Tools
https://github.com/hedgedoc/hedgedoc
The Indie Way
For some cases, you can consider to just write into your Forgejo instance, in case that github is non accesible.
Ill assume that you are fine with .md files
YT Summaries
That’s exactly what ive done around this Hormozi video one more time
Audio Recaps
I was using fireflies, but then I created a setup around google recorder
Gold Info for SoloPreneurs
Ideas Checklist 🚀
For this I dedicated a full post few weeks ago.
The general idea checklist is as follows:
Prospects/Clients Checklist 🚀
Info to Video
You are already aware, PoC, make a hyperframe video about it, or about yourself
Conclusions
If it was not clear, now has to be.
No more bs hello, accountability laundring, weaponized incompetence, underf…
…Pardon my French, I meant:
- “weaponized incompetence” -> “repeat low-context dependency requests”
- “cover my ass” -> “maintain an evidence trail”
- “under-filtering manager” -> “unfiltered upstream directive”
- “take off the mask” -> “raise process issues explicitly”
Yep, i apply and got my information and workflows in place: goes pretty handy together with skills C:/Users/.../.codex/skills/weekly-work-summarizer/references/templates.md
flowchart TD
Start([Ambiguous work situation]) --> Diagnose{What kind of pattern is this?}
Diagnose -->|Unclear owner, vague handoff, meeting drift| Accountability[accountability-framework.md]
Diagnose -->|Busy updates, low verified output| LoudLabor[loud-laboring-framework.md]
Diagnose -->|Need stakeholder movement| Communication[communication.md]
Accountability --> Pattern[Name the pattern]
LoudLabor --> Pattern
Pattern --> NextState{What next state is needed?}
Communication --> NextState
NextState -->|Facts / root cause| DFIR[DFIR / TRACE]
NextState -->|Ownership transfer| PASS[PASS]
NextState -->|Owners, status, triggers| COAST[COAST]
NextState -->|Decision between options| ADAPT[ADAPT]
NextState -->|Fast response / unblock| DRIVE[DRIVE]
DFIR --> Script[accountability-response-playbook.md]
PASS --> Script
COAST --> Script
ADAPT --> Script
DRIVE --> Script
Script --> Send[Send work-safe message]
Send --> Evidence[accountability-daily-template.md]
Evidence --> Weekly[Weekly proof: delivered, unblocked, decisions, risks, ownership]HomeLab Updates 0926
I was trying lately technitium for custom DNS at Omarchy
Architect or Principal
Just in case you are preparing for an internal promo / outside CV or how to frame what you do for prospects.
Currently i observe a huge gap between expectations: people billing 1k/person/day for adding one line to a csv
Versus: the cost per task being literally smashed with every new model released (to cents of a $)
How long will that gap / arbitrage possibility last?
Looking for a way to elevate yourself from the how, upstream to the what’s and why’s?
If you are an IC, you might consider:
The Architect spends a lot of time in cross-functional stakeholder meetings, drawing system diagrams, analyzing vendor tech, and ensuring the business goals match the technology stack. In many companies, architects rarely touch production code anymore.
The Principal Engineer is usually the highest-ranking technical hands-on expert in the room. They design systems too, but they are also expected to build the foundational architecture, debug the most ambiguous, critical outages, and optimize engineering processes.
The easiest way to understand the difference is scope of execution vs. scope of design:
+————————————+————————————+ | Software Architect | Principal Engineer | +————————————+————————————+ | Focuses on the “Blueprint.” | Focuses on the “Execution & Truth."| | Works with product and business to | Goes deep into complex systems, | | map out what to build and how | enforces standards, and writes core| | systems interact broadly. | code/infrastructure. | +————————————+————————————+
- You Own the “Infrastructure of Rules”
As a Principal, you are responsible for defining team standards and dev velocity.
This means you have the organizational power to unilaterally destroy accountability laundering and useless meetings.
You can literally write a policy that says: “No sync calls without a written ticket and log,” and because you are the Principal, it becomes law.
- Built-In “Deep Work” Shielding
Principals are expected to tackle complex, ambiguous engineering problems.
Everyone expects you to be offline, heads-down, and writing architecture code or documentation for blocks of 4 to 6 hours at a time.
Nobody questions why your Slack status is “Away” or “Focusing”—they just assume you are solving a high-level problem.
- High Leverage, Low Meeting Density
Architects get pulled into endless discovery calls with product managers and clients to figure out “what is possible.”
Managers get pulled into HR drama. Principals are insulated from most of that.
Your value comes from your output, your technical direction, and the documentation (like your wikis) that you build to make the rest of the team self-sufficient.
So ask honestly: do you want status, control, income, or optionality*?
They are NOT the same game.
What are you optimizing for next?
FAQ
Useful CLI Tools
Coming from here
Ive lately found useful:
herdrSelfhosted Forgejo
I got this ready in my x300 some time ago to tinker with agents:
Having termix ready http://192.168.1.2:8090/ and Forgejo http://192.168.1.2:3034/
docker ps -a --filter "name=forgejo"The syncing setup to github so that each forgejo repo has a gh backup in a branch:
gh statusIn this case, what i want is to do: GH <-> Forgejo for my daily notes
cd ./Home-Lab/forgejo
make migrate-repo REPO_OWNER=JAlcocerT REPO_NAME=my-logseq-notes #makes a mirror of gh
#make sync-repo REPO_OWNER=JAlcocerT REPO_NAME=my-logseq-notesIf you want to expose this:
docker inspect forgejo --format '{{range $name, $_ := .NetworkSettings.Networks}}{{println $name}}{{end}}'
#docker network connect cloudflared_tunnel forgejoCheck that forgejo:3000 ready:
#dig fossengineer.com anySelfhosted Communication
Selfhosted Media
qbit and prowlarr at 6011 and 9696.
sudo docker compose -f ./z-homelab-setup/evolution/2601_docker-compose.yml up -d qbittorrent prowlarryt-distil: http://192.168.1.2:8001
Kodi vs Jellyfin
with kodi adons