If there is a formal arbitration step, check what it costs and who pays before you agree to it, and if the money ever moves off platform get an actual professional to look at your contract. Platform arbitration and a real contract dispute are different animals and people conflate them constantly.
Nadia Brill
@nadia_brill
Grant administrator at a research university. I know exactly why your indirect cost rate ate a third of your award.
118 credit Trusted
- From answers
- 0
- From questions
- 120
- Lifetime
- 120
Disagreeing with the framing rather than the answers. The market question is unknowable and everyone in this thread including me is describing one draw from a distribution. What is knowable is whether you will still want this house and this city in five years, and if the answer is yes then the timing question shrinks a lot.
The honest counterweight: Prisma is nicer for two people who do not want to think about SQL. Nested writes, the migrate workflow, Studio for poking at data - that is a real productivity story and drizzle does not have an equivalent for all of it.
Drizzle asks you to know SQL. Not as a slogan, you will write sql template fragments for anything beyond CRUD, and if neither of you enjoys that, you will be slower. In that case pick Prisma and run it somewhere that is not an edge runtime.
Worth adding a guard so the total is not misleading where it genuinely cannot be answered: wrap it in IF(HASONEVALUE(Customer[CustomerKey]), ..., BLANK()) and show a dash instead of a number someone will screenshot.
Rental pricing has a convention worth knowing: many houses charge roughly a three-day rate for a full week, so a two-day job and a five-day job can cost surprisingly similar amounts. That changes the calculation if you can pick the kit up on Friday and prep over the weekend. My rule for buying is that it has to appear on more than a third of my jobs, otherwise the money is better spent on the thing I use every single time.
New to this and reassured by the whole thread. I assumed everyone else was running the full ritual and I was the only one quietly failing at it.
Went with this. Six months later the prefixes have saved me more debugging time than the choice of id type could ever have cost me.
Found it, a helper query that appends the year to the SharePoint site URL so it picks the right archive folder. Rewrote it with RelativePath and the phantom source disappeared.