Till & Tally

If you have the newer functions, FILTER does not have this problem at all because it does not impose a column type. =FILTER({A:A, D:D}, B:B = "open") gives you both halves. You lose QUERY's sorting and grouping, but for a straight filter it is simpler and more predictable.

The mechanism you are looking for is a qualifying life event, and starting a job is one: but the window it opens is usually short and it opened when you started, not now. Marriage, birth or adoption, losing other coverage, and some moves also count, and each opens a limited window to join or change. Ring your benefits administrator and ask directly which events her plan recognises and how many days you get, then ask the same of her plan, because employer plans do not all define this identically. This is what happened in my case, not advice about yours.

Correct, and if something does happen, act the same week. People lose the option by waiting for paperwork they could have chased later.

They had both asked for that Saturday off six weeks ago and I said no to both. I did not connect those things until now.

I would absolutely have changed it on the live file this afternoon. Copying it first.

The laminated reduced menu is going up this week. I spent that whole Saturday trying to run the normal operation with one person, which was the actual mistake.

It is the semicolon. Colleague set the file up in his own locale and I have been fighting it for a fortnight.

Two things the cents-per-point number hides. First, portal bookings normally behave like paid tickets: you earn miles on them and they count towards status: whereas award tickets usually do not, and that gap is worth real money on a long flight. Second, award tickets can carry taxes and carrier-imposed charges that vary wildly by programme and route, so a redemption that looks brilliant can arrive with a few hundred in cash attached. Compare the total out of pocket, not the headline.

I run four on a slightly smaller plot than yours and it works, with caveats I would want you to know. Robbing is the thing that changes when you go past two. With one hive, a careless moment costs you nothing. With four sitting close together, a dropped frame or an open feeder in a dearth can set off a robbing frenzy that involves every colony you own and puts a cloud of agitated bees over your garden for an afternoon. That is the scenario that generates a neighbour complaint, not the day to day flying. Entrance reducers in autumn and never feeding in the open have kept mine calm.

I got impatient one January and moved two jars next to a radiator to hurry them along. Three days later they were sour, soft and slightly boozy, and the cabbage had that yeasty smell you get when it goes too fast. Slow and cold is a feature, not a delay.

The mental model that fixes this permanently is that 'use client' is not a label on one file, it is a door into the client bundle. Everything that file imports, and everything those files import, gets pulled through the door with it, which is why a helper that reads cookies suddenly finds itself being compiled for the browser and complains. The boundary is therefore not where you wrote the directive, it is the entire subtree below it. Once you see it as a subtree rather than a file, the placement rules stop feeling arbitrary.

Price it against the true cost, not the build. Bespoke work runs about double whatever you estimate, so call it three weeks, and three weeks of a two-day-a-week schedule is most of a quarter.

Then add the part everyone forgets: you now maintain that code forever. Every refactor, every dependency upgrade, every change to your import pipeline has to keep one customer's adapter alive, and you cannot test it because you do not have their system. That is a tax on every future week, and it is why bespoke features feel cheap the month you build them and expensive two years later.

Either charge enough to cover it - 2,000 plus a maintenance fee, or 2,000 with a clear support boundary - or put an end date in the agreement. I use a sunset clause: supported for twenty four months, after that we revisit.

Also worth trying a slightly higher finishing angle on a softer German knife. Around 17-18 degrees per side instead of 15 gives up a bit of initial keenness for a noticeable jump in how long it stays useful. That steel is not hard enough to hold a very acute edge through real prep work.

Small thing that helped me: pour off the accumulated fat and juice about two thirds of the way through. It is free, takes ten seconds, and there is noticeably less steam in the last stretch.

Run both levers through a payment calculator before you decide which one you are waiting for, because they do not move the same way. A meaningful rate drop changes your monthly payment a lot and often pulls buyers back into the market, which pushes prices the other way. Waiting for both to improve at once is waiting for a thing that rarely happens.

Never let them search. Give the exact flight numbers and dates you already found and it becomes a two minute call instead of a twenty minute one.

Very known thing, and it has two separate causes that look identical from the outside. Either the programme's website genuinely cannot display that partner online - plenty of partnerships are phone-only bookings even in 2026, or the seats you can see are being released in a booking class your programme does not have access to. The first is fixable by ringing them with flight numbers and dates in hand; the second is not fixable at all. Ask the agent to look up the specific flight and they will usually tell you which of the two it is within a minute.

Fields your invoice needs to survive an AP system, from being bounced repeatedly: your full legal entity name exactly as registered, your address, your tax identifier, a unique sequential invoice number, the invoice date and the due date spelled out, their PO number in its own labelled field, the service period, the currency stated explicitly, and full bank details including the intermediary details if it is an international transfer.

Also put your contact email on it. A surprising number of AP queries die because the only address on the invoice is a no-reply.

Time it honestly, because the first one is always the expensive one. Mine was about five hours: portal registration, the tax form, chasing the right contact twice, and the questionnaire. On 588 that is a terrible hourly rate for year one.

But most of those five hours were answering questions that never change. Keep a single folder with your entity details, tax forms, bank details, the security answers, a data processing description, your uptime story and a short list of subprocessors. The second customer like this cost me about forty minutes.

My line is roughly 1,000 a year for a first-time enterprise process, less if I can see three more customers behind them. Below that I offer card only.

Plan for it in the accounts rather than emotionally. I now treat December's surplus as January and February's float and do not touch it, which turns a frightening month into a boring one. The first year I did not do that and spent December's takings in December.

This is the one to check before anything else. The premium is fixed, the benefit is conditional.

That split is a healthy sign. The version that worries me is flat footfall with falling spend, because that usually means people are trading down for a reason.

Do not sign a DPA with unbounded liability, and do not agree to a breach notification window you cannot physically meet while holding down another job. Those two clauses are where the actual risk lives, not in the encryption questions everyone focuses on.

It was meant to be a per-row threshold, so E2:E was the fix. Works down the whole column now. I would never have spotted that on my own.

The habit that has saved me the most is shopping every renewal rather than every few years, and getting quotes from an independent broker as well as direct. Loyalty pricing works against you at most carriers, and the quotes on identical cover have varied by a lot more than twelve percent between companies for me. Take your current declarations page to whoever quotes so they are pricing the same limits, otherwise you are comparing a cheaper policy rather than a cheaper price.