Right now the admin team is 2 people and mostly myself. The labor side is growing as work flows in. The whole reason I took this job is the stake in the company. Its been around for nearly 3 decades very well established and deep roots in the community. The key players are still in the business and industry tied. They have assets and a good crew. But no real internal structure and infrastructure.
Comment on Ideal Business Stack?
zbyte64@awful.systems 2 weeks ago
I think a concern for the business is whether other people can help maintain the system. As such don’t go too custom and roll your own. Take things like nextcloud and see if you can fit the requirements by bolting on a few docker services.
OhVenus_Baby@lemmy.ml 2 weeks ago
catloaf@lemm.ee 2 weeks ago
The whole reason I took this job is the stake in the company
Man I was suppressing the red flags up until now; this is the straw that breaks the camel’s back. You are going to get shafted at this job. It might be because someone is embezzling, they’re committing fraud in their manufacturing processes, or one of the owners is going to cut and run and leave the rest of you holding the bag. Maybe one day you’ll just show up and the doors are all locked.
You need to do absolutely everything by the book, document, document, document, CYA, and in a way that when shit goes south you’ll still have that documentation. And always have an exit plan.
OhVenus_Baby@lemmy.ml 2 weeks ago
Everything is by the book. It’s a family business. I have documentation of every single move that’s happened since my arrival, I’m in the financials and business customer and vendor relations. None of what your saying holds any water at all. You simply have misjudged the situation. Likely due to my poor explanation.
Gradually_Adjusting@lemmy.world 2 weeks ago
I see people who are showing concern borne of experience, and with marked consensus. If you’re confident they’re wrong about your situation, it still may be worth reflecting on what they’ve learned and to limit your ambitions - or at least, consider building things on a more conservative timeline than you were imagining. Have big dreams, but start with biting off an amount you can certainly chew.
zbyte64@awful.systems 1 week ago
Regardless of the team size, I say simplify as much as you can so you can dedicate your resources customizing what makes their business special. You mentioned a PBX system and no infrastructure, this makes me think you talking about Customer Management. It sounds like you’re documenting as you go, fantastic. Maybe loop in a noob time to time to review the documentation or have a Q&A that reifies the docs. Best of luck!
Colloidal@programming.dev 1 week ago
Yup. I’ve worked in big multinational companies where a local department would roll their own solution (a database and a web page, usually), and then the people that built it moved on or retired and now no one will maintain the thing.
The closer the stuff is to off the shelf, the better. Reliability and maintainability are paramount and should trump feature set when deciding.