u/aral10

I have a 3 ton split system that's about 8 years old. Never had a problem until this summer. Tech came out and said it was low on refrigerant, added 2 pounds and it cooled great for a couple months. Now it's struggling again and I'm pretty sure it's low once more. They didn't mention finding a leak last time. Is it normal for a system to just start leaking after years of no issues? Should I pay for a leak search or just keep adding refrigerant every few months until I save up for a new system? I don't want to waste money if the whole thing is dying anyway.

I swear every single time I do a bubble or flutterflow build for a local service company it goes exactly the same way

Scope docs: "we just need a simple dashboard that emails us when a lead fills the form"

two weeks before launch: "hey so we realized our guys don't check email on the road. can we make it text them instead? oh and can we do mass broadcasts to old clients from the same number?"

usually I just use the twilio api and call it a day, but this client is super non-technical and I knew if I gave them twilio access they'd break something or get confused by the billing console. ended up chaining it through make.com into the drop cowboy platform just so they could have a dummy-proof separate dashboard for the voice and text stuff.

getting the webhooks to play nice for the SMS marketing side of it was a massive headache though, the json arrays kept coming out flat and Bubble was throwing absolute fits. took me like four hours to realize I just needed to parse it differently in the make.com intermediary step.

im just so tired of the "oh one quick thing" requests. next time someone says simple CRM my base price is tripling tbh

I am running a campaign that has a decent mix of roleplay, exploration, and combat. My players are generally smart and creative. They often try to talk their way out of fights or use stealth to bypass encounters entirely. I love that about them most of the time. But every now and then, the narrative really needs a combat encounter to land properly. A villain reveal, a set piece battle, or a moment where talking should not work. The problem is, when I put them in a situation where I think combat is inevitable, they still try to avoid it. I do not want to railroad them or take away their agency. But I also do not want every major confrontation to end with a persuasion check. How do you signal to players that this is a fight they cannot talk their way out of without just saying no to their ideas? Do you just let them skip every fight and adjust the story accordingly? Looking for a balance between player freedom and narrative stakes.