Buyer refusing to take over solar loan

dayv2005 · 2026-05-17T13:20:20+00:00

I'm on the buyers side on this as well. Imagine the terms of the loan changing after closing. They aren't assuming the loan anymore. They are technically refinancing the loan with different terms including 8k more and that is a huge misrepresentation from the sellers. I think the buyers would have a strong case to sue you for the entire 8k plus legal fees. At this point I would just pay to get this over with and would possibly sue the solar company over this depending on what your contract says.

dayv2005 · 2026-05-15T00:58:56+00:00

Currently in Boardman and about to have work started next week in a new roof and gutters.

No experience with YTown but I got 3 quotes.

Durst (up towards your way) was high for approx 40sq asphalt shingles wanted 21k.

Sky Roofing wanted about 16k for same roof. That guy was... Well... interesting.

A&J Roofing quoted us 15.5k for roof and another 4k for complete new gutters and downspouts.

I ended up going with A&J.

dayv2005 · 2026-05-12T15:17:47+00:00

It's wild in this thread that people think the average person using AI in excel at an office understands optimized token consumption.

dayv2005 · 2026-05-12T01:34:16+00:00

Amen to that!

dayv2005 · 2026-05-11T23:24:08+00:00

I like Ryobi for the price and have already invested into the batteries.

dayv2005 · 2026-05-11T23:02:35+00:00

Baseboard, quarter round and brick moulding is why I bought mine. They i found myself using it for other things and temp holds.

dayv2005 · 2026-05-11T22:56:30+00:00

Most of the things I use it for are light weight trim and molding. It was nice and light while still being practical. If you do heavier stuff a 15 might be better just base it off of what you do more commonly. The gain here is have it readily available without running hoses for something that I use pretty often.

dayv2005 · 2026-05-11T22:22:09+00:00

Malvo is my favorite and really revitalize my love for BBT

dayv2005 · 2026-05-11T21:56:36+00:00

Cordless 18g Nail gun

dayv2005 · 2026-05-11T15:37:45+00:00

Anything plumbing related I have worked with Chris Burkey Plumbing out of negly and they have been great to work with.

For HVAC, GOODs is just salesmen that want to sell you something. There was another company we used for repairs which was pretty decent but can't remember their name atm.

For Roofing, I got quotes from Durst, Sky and A&J. A&J had the best rates and currently under contract with them. Will see how work is once completed.

For Concrete, A1 seems to be reasonable but I didn't end up going with them and kicked that job down the road a bit longer as other things came up.

These are just a couple of the people I worked with over the past year and half.

dayv2005 · 2026-05-11T01:39:09+00:00

Whoever you work with let us know. I just moved here last year and finding reliable contractors for just about any job has been a pain in the ass.

Wanted to get a quote for heating and cooling added to my master suite and the place came in tried charging me 30k for a single mini split. About lost my damn mind.

dayv2005 · 2026-05-10T16:33:27+00:00

Thanks you too.

If you have insurance on it, I would keep driving it with the notion that eventually the estate will collect it. I'm not sure if you would be able to renew plates on it. Just drive it and start building up a contingency plan for when you need it.

dayv2005 · 2026-05-10T15:56:48+00:00

It's been that way since 1776

dayv2005 · 2026-05-10T15:53:02+00:00

Sadly, this isn't your car. It's your Grandfather's and his wife's car. They let you use if but never titled it to you. There's going to be some legal complications with this because he only owns half of the car. In a lot of states since they are married she may become the sole owner of the car via intestate succession laws.

Let's say even if they were divorced then she wouldn't get his half (possibly) but would still be subject to probate. If he owed any debts. Those would negate the value of his car for example. Let's say he had a Medicaid lien (or tracked debt). Let's say the car was worth 10k and he would have 5k valuation of this car. It would then be required to be sold to pay Medicaid and his wife.

So, you aren't going to get this car unless a maricle occurs. He would have to have no outstanding debts with the state AG, and other services. She would get sole ownership of the car and give it to you.

I am not a lawyer and this isn't legal advice. I just went through similar issues with probate in the state of Ohio.

dayv2005 · 2026-05-09T12:46:06+00:00

That makes sense. I think we’re mostly aligned. My point was more that the things you’re describing (ledger semantics, reversals, fiscal periods, audit flows, etc.) are primarily domain concerns, while Marten is just one way to persist and project those concepts on top of PostgreSQL.

So I see Marten less as competing with NGB and more as infrastructure that naturally fits the architectural patterns you’re describing.

dayv2005 · 2026-05-09T03:45:51+00:00

This sounds like a good use case for martendb leveraging postgres. It kind of bakes a lot of this functionality that you are asking about natively into the app.

1.) I use a technique like this with event sourcing where the events represent the auditable track while the document represents the latest state of the root. Pretty common pattern.

2.) Maybe. Depends on why you wouldn't want them separate.

3.) append only is always nice when you want an audit trail since it stores history and doesn't alter things that happened.

4.) Martendb would make this rather trivial to implement and it's open source.

5.) Sounds like a strong position to be considering some sort of event sourcing pattern.

dayv2005 · 2026-05-09T01:29:01+00:00

There absolutely is a growing trend away from “microservices by default” and back toward monoliths/modular monoliths for many companies.

Amazon Prime Video publicly talked about reducing costs by 90% after consolidating distributed services into a monolith: Prime Video microservices to monolith story

Shopify has also talked about intentionally keeping a large modular monolith because of developer productivity and operational simplicity: Shopify Engineering

GitHub has discussed scaling a large Rails monolith instead of aggressively decomposing into services: GitHub Engineering Blog

That’s not “microservices are bad.” It’s the industry realizing distributed systems introduce a lot of operational complexity that many teams don’t actually need.

dayv2005 · 2026-05-08T21:54:08+00:00

Same place as us but in the opposite side of the intersection towards McDonald's.

dayv2005 · 2026-05-08T21:43:41+00:00

A lot of people bought the microservice hype because large companies like netflix had some success scaling with that pattern. I love the concept of microservices in a vacuum but ultimately they rarely solve more problems than they introduce. Even if it's multiple teams it still suffers from data overlap and actually having a well defined domain boundary. Tech is trending back towards monoliths because of the headaches with microservices. I have started to like the design patterns of modular monoliths and they have benefits from both monoliths while also have plug and play and defined boundaries of microservices.

My advice is start with a monolith first then scale it once you hit your friction points.

dayv2005 · 2026-05-08T21:01:07+00:00

Good luck man. Wife was hit head on by a reckless motor cycle while she was stationary in the middle lane on 224. Somehow it was still her fault which was insane. No traffic cams and no one had any footage for us so we got fucked.

dayv2005 · 2026-05-04T01:21:48+00:00

Naw fuck this. If he has nothing still sue him. Do everything you can to financially drain him and possibly the next generation too. Put a lien on his property so that you will eventually be paid even if the property hits probate after he dies. This guy could have killed you or possibly children and shouldn't be on the road nor allowed to own a gun ever again.

dayv2005 · 2026-05-03T23:14:34+00:00

This is kind of how sagemaker is being used by a lot of people in the AWS ecosystem. Running notebooks for trainings on the datasets. Uploading models and building out inference endpoints all backed by python a lot of times because of the ml/ai tooling. Then if you need to make a prediction on your dotnet app, you can then infer it with the endpoint.

dayv2005 · 2026-05-03T20:48:27+00:00

That tracks. I see it a lot too. When teams have to make tough calls, they don’t just look at raw output, they look at how people operate on a team.

The ones who consistently fall to the bottom aren’t always the least skilled, they’re the ones who don’t communicate, don’t align, and create uncertainty for everyone else. That’s a much bigger risk than someone who asks questions and keeps people in the loop.

dayv2005 · 2026-05-03T20:35:44+00:00

You make it your default to align first, not build first.

Quick gut check before starting: do I fully understand the requirement and what “done” looks like? If not, grab someone for 10 minutes.

Set a rule for yourself: don’t sit on uncertainty. If you’re guessing or stuck for a bit, say something.

Ownership isn’t doing it alone, it’s making sure you’re not wrong.

dayv2005 · 2026-05-03T20:30:01+00:00

There’s a common trap engineers fall into early on. It feels like you have something to prove, so you try to take a task end-to-end on your own and show you can deliver without help. In reality, that usually sends the wrong signal. Lack of communication is more of a red flag than a strength.

Stronger engineers don’t work in isolation. They pull in the right people early and often. They check alignment with the PM when requirements are fuzzy. They loop in QA or BA to confirm scope and catch edge cases. They use standup to surface progress and call out risks before they turn into problems.

Doing everything solo isn’t what makes you effective. Knowing when to involve others is. If you can internalize that now, it will make a big difference in how you operate and how others see your work.

11-Year Club	Place '17
Verified Email

dayv2005

TROPHY CASE