I'm quitting my job due to vibe coders and poor leadership

Paging /u/flippedturtle - did you quit or stay?

Buddy, you are missing a major opportunity that is \*right in front of you\* and it's a bloody shame. You could turn this situation from chicken poop into chicken soup. I really do feel the poor leadership and vibe coding overwhelmed feelings. It's a major stressor for folks in our roles to take this wonderfuly nebulous and dangly initiative and turn around with a half-baked idea and make it your problem. The bad leadership aspect here has really culminated in a free-for-all and your calendar is unfortunately on the menu. I would argue that you need to triage & prioritize & be prepared for some stuff to fall on the floor. I have no idea what your day-to-day looks like. If I had to solve this problem with my boss, here's what I'd do: 1) Monday morning meeting, like 10 AM. Half an hour. "The company clearly wants to put a major focus on the AI initiatives. We cannot chase them all so we need to prioritize. I need to know how much of my day / week you want me to put into making the AI initiative successful. I suggest four afternoons a week." \*\*Outcome:\*\* If your boss says "You can't put any time into this." then that's that. Problem is solved. If you do get a time allocation, then you can work on these things. 2) Next meeting is to sort out the work items in your life. Everything gets tagged - either follow the MoSCoW model or the Pauch method or whatever works for you. This is where choices are made to fit the work that you \*must\* do to keep the lights on in the non-AI spent time. You have a hard limit of number of hours: 40/wk - AI time = this is your KTLO budget. Make a list, put hours to those list items, make a mock weekly calendar to help keep organized. Send it to your boss for approval. Boom- you have an agreement. 3) Immediately the next thing is to set up an intake for all "AI-related project requests". Time to get these chickens into boxes! I'm not sure what ticketing system you use, but this is the time to set up a new project category or incident category; all questions/problems/projects/requests go in here. Anything not in here? Doesn't exist. 4) Ruthlessly triage the incoming requests. This is the beautiful part! This is where you employ your own agent of an AI/LLM if your choice. The agent needs to: distill the request into actions or questions and apply a time guesstimate; look broadly at the body of requests and de-duplicate- put teams in touch with one another whose requests / needs / ideas overlap- and then report to you (and your boss) a list of actionable requests. Rinse. Repeat. So long as there are requests in queue, the agent analyzes them. No, it's not going to be perfect. It's a garbage in / garbage out system. Eventually, a requestor will complain that they were 'misunderstood' or that they didn't get what they thought they wanted. That's going to be part of the exercise- skill with AI comes down to being so crazy specific with your questions / prompt / needs that an 8 year old can understand it AND not screw it up. 5) Sort what you can in your AI-initiative time budget. Leverage the LLM to find the most productive things / lowest hanging fruit. Eventually, with enough iterations, you'll get a feel for what's important vs what's not. Spend your whole budget minus two hours here. 6) One of those hours is spent polishing the tool in step 4. The other is spent on a "Friday burndown" with your boss. Report your successes and get feedback on what's important & what's not. Ask your boss to invite other bosses for input. Also important to report out on what \*isn't being done\*- "I need more people to do more better. The AI efficiency objective creates distractions when there's 50 mouths to feed. Someone needs to step up and drive a cohesive strategy, or we need more people to chase more threads. Pick." 7) Improvise. Adapt. Overcome. This is the new normal until the AI initiative is dead. It \*will die\*, but it's unlikely that we will ever be the same. Or you can quit; that's the chicken-shit option.