264 karma · joined September 15, 2011
workdir/ ├── README.md ├── CLAUDE.md # Claude Code instructions ├── BACKUP.md # Backup documentation ├── .gitignore ├── traefik/ │ ├── docker-compose.yml │ └── config/ │ └── traefik.yml ├── authentik/ │ ├── docker-compose.yml │ └── .env.example ├── umami/ │ ├── docker-compose.yml │ └── .env.example ├── n8n/ │ ├── docker-compose.yml │ └── .env.example └── backup/ ├── backup.sh # Automated backup script ├── restore.sh # Restore from backup ├── verify.sh # Verify backup integrity ├── list-backups.sh # List available backups └── .env.example
I follow him on twitter and he has a number informative videos on the net regarding startups and more. He also maintains a blog on his website.
If you started your law career helping startups then an opportunity to transition to the startup side might present itself. It is a simple matter of creating opportunities for yourself by positioning yourself strategically.
Hard space to penetrated but with a lot of federally funded initiatives the past few years. New regulations around EHR is driving the space.
Very cool and I can relate as we all have an old computer case in closet somewhere.
I was talking with a prospective client that had spent the past three years rushing a SaaS solution to market. They even referenced the technical debt as an area they need help with overcoming as they move forward.
Second order change is difficult for any organization or established project, but remaining consistent with your message can drive the process in that direction. Sounds like a challenge for the two of you, but try to bring solutions / recommendations instead of minor resistance that might get misinterpreted. Not easy I know.