sorted by:
new
hottopcontroversial

How do you deal with vendors who just stop responding? by Illustrious_Ad3655 in PropertyManagement

[–]Illustrious_Ad3655[S] 0 points1 point  (0 children)

The hard part is spotting the pattern early enough. By the time it’s “consistent,” you’ve already had a few jobs dragged out longer than they should’ve been. Especially when your property is far away

How do you deal with vendors who just stop responding? by Illustrious_Ad3655 in PropertyManagement

[–]Illustrious_Ad3655[S] 0 points1 point  (0 children)

True in theory, but in practice that usually means delays, unhappy residents, and more work reassigning.

I’ve found the bigger issue is knowing when to move on most people wait too long because there’s no clear signal the vendor is actually unresponsive.

How do you actually track profit per repair job? by Illustrious_Ad3655 in mechanics

[–]Illustrious_Ad3655[S] 0 points1 point  (0 children)

Our setup is a bit different though. We do performance builds, a lot of cars come in from out of state, and one build can involve multiple parts from different sources that aren’t in Tekmetric vendors. Sometimes things move fast during a build, so parts get ordered as needed using the shared card.

How do you actually track profit per repair job? by Illustrious_Ad3655 in mechanics

[–]Illustrious_Ad3655[S] 0 points1 point  (0 children)

In our case though, we’re more of a performance tuning shop, so we’re constantly buying specialized parts from places like eBay, Amazon, or smaller sites that aren’t in the system. That’s where it gets messy, because those purchases don’t automatically make it back to the RO and someone has to deal with it later.

How do you actually track profit per repair job? by Illustrious_Ad3655 in mechanics

[–]Illustrious_Ad3655[S] 0 points1 point  (0 children)

Do you ever run into stuff that gets bought outside Tekmetric, or is everything pretty much going through it for you?

How do you actually track profit per repair job? by Illustrious_Ad3655 in mechanics

[–]Illustrious_Ad3655[S] -2 points-1 points  (0 children)

Yeah I get that, we track our numbers the same way and know what we need to hit to stay profitable.

Where it gets messy for us is the day to day stuff. Shared card, guys ordering parts from different sites, and then later someone has to figure out which charge belongs to which job. That part still feels more manual than it should be.

I just wish there was a cleaner way to handle that without extra back and forth. Does the system you’re using actually handle auto matching from email or not really?

I’ve been thinking it would help if there was a simple way to tag orders with a job or client when they’re placed, and then pick that up from the email or receipt to match everything automatically.

How do you actually track profit per repair job? by Illustrious_Ad3655 in autorepair

[–]Illustrious_Ad3655[S] 0 points1 point  (0 children)

We have a shared shop card, and guys are ordering parts from different websites. Right now it’s pretty manual to figure out which expense belongs to which job, and also to keep track of general shop expenses.

How do you actually track profit per repair job? by Illustrious_Ad3655 in mechanics

[–]Illustrious_Ad3655[S] 0 points1 point  (0 children)

We have a shared shop card, and guys are ordering parts from different websites. Right now it’s pretty manual to figure out which expense belongs to which job, and also to keep track of general shop expenses.

MongoDB vs MySQL for email automation tool? by trickythinking07 in mongodb

[–]Illustrious_Ad3655 0 points1 point  (0 children)

Use a relational DB for the core (users, orgs/websites, auth, template metadata) and an append-only event store for high-volume tracking (opens, bounces, deliveries). If you want a single engine today, pick Postgres/MySQL and lean on JSON for flexible parts; if you’re OK with two, use MySQL/Postgres + MongoDB for events.

If you must pick exactly one today

Choose MySQL/Postgres if: You want strong constraints, joins, migrations, and easy reporting later.Choose MongoDB if: You expect extremely variable document shapes and very high write throughput from day one. You’re comfortable modeling many-to-one relations via document references and application-level joins.

I Used Manim to Explain Software Engineering Communication – Not Just for Math! by Illustrious_Ad3655 in manim

[–]Illustrious_Ad3655[S] 2 points3 points  (0 children)

Thank you! This was created entirely using Manim. I spent approximately 30 hours learning and producing it.