@nabeelazeez@dropkickcopy Same in AV. The integrators I trust most run the gear in their own office and know exactly where it breaks. Hard to sell a fix you've never had to live with
@vineerpasam Overnight runs with no done-check just go in circles. Give it a list file it ticks off, one issue per session, and a test that proves each fix before it moves on. I also get a second model to review before anything is marked closed
@abhishekanita1 Yep. Apprentices learned by getting it wrong with someone senior standing right there. If AI takes the grunt work, we have to build that bit back in on purpose
@Mr_AshishM@X Switchback: a Mac app that adds Windows Explorer features inside the real Finder. A path bar you can type into, a folder tree in the sidebar, copies you can pause.
The design rule I keep coming back to: it should look like Apple built it, not like Windows got bolted on.
@MikeOdeke Build one small thing you actually need, and don't keep a line you can't explain. Use AI, but when it writes something you don't get, that's the bit to go deep on. Docs and tutorials are for when you're stuck, not instead of building
@idavidjain Running a consultancy plus four apps, my rule is one gets the week's focus and the rest only get fixes. If a new idea can't beat the weakest current one, it goes in a notes file, not a new repo
@SandrineZambou True, that's the bit I'd watch. If people won't invite their team because of the price, the product never spreads inside the company. Free viewers or a cheap extra seat tier usually fixes it
@git_cat8d@Hiteshdotcom Take the QA role if SDE-1 calls aren't coming. Paid experience beats a gap. Automate tests in code from week one, ship small tools for the team, and after 6-12 months apply for internal SDE moves. QA-to-dev is a common, workable path.
@itshshekhar Don't spend the βΉ50k first. Pick a skill you already have, offer it to 5 people you know this week, and only buy tools once someone pays. Keep βΉ40k as runway. Service first, product later is the cheapest way to learn what sells.
@realZahedSaifi Best one I've heard: we own the messy workflow and the data the customer can't easily move. Everyone has the same models. Not everyone has done the boring bit
@KramerArundel When the main job works end to end, even if it's ugly. Hand it to 5 people, watch them use it live, and tell them up front what's rough. Broken edges are fine, a broken main path isn't
@malpani Same in service businesses. Handshake deals feel fine until the first bad month. A one-page note on who does what, and what happens if someone leaves, costs an afternoon and saves the friendship
Best sales filter I've found in 20+ years of AV jobs: give a ballpark on the first call.
The ones who go quiet were never buying. The ones who say "ok, what's next" usually are. Saves everyone a site visit.
Do you give a number early or hold it back?
@DenLennie Writing the limit down is half of it. The other half: when round three lands, send a short written variation with the extra cost before touching it. Once the client says yes to that, it's a line item, not a favour, and the next request gets priced the same way.
@codingXdynasty Plain Docker Compose. Boring is the point. Every app is one file you can back up and rebuild from. Only reach for Kubernetes when you actually have the problem it solves
@CodyAlt In my experience good people don't stay for the vision. They stay because they got trusted with real work early and someone backed them when it went wrong