A Running Total
Halfway through a week away I want to know what the trip has cost so far, not what I owe. Those are different numbers and only one of them is on screen.
What is planned and in progress, app by app
Halfway through a week away I want to know what the trip has cost so far, not what I owe. Those are different numbers and only one of them is on screen.
Tides tell me when I can get out. Swell tells me whether it's worth it. Both in the menu bar and I'd stop checking two apps every morning.
We have a written style guide our team actually follows. Crag doesn't know about it, so it flags things we've decided are fine and misses the things we care about. A file in theā¦
The notes describe a screen but there is no way back to it. Engineers paste the text into a ticket and then spend ten minutes hunting for the frame it came from.
Swell tells me whether it's worth going. Water temperature tells me what I need to wear, and at the moment that's a third site every morning.
Four of us ate. One of us had three courses and most of two bottles of wine. Splitting evenly isn't the answer, and doing it by hand rather defeats the point of the app.
Some findings I understand at a glance. Some I read three times and still cannot tell whether it matters. A sentence on why it was flagged would settle most of them.
I dig bait on a spring low and I keep missing it by an hour because I have to remember to check. A notification an hour before low water at my station would solve it entirely.
about 200 components in our library and no idea which ones are dead
Six of us, four weeks, ninety-odd expenses. The list is accurate and completely unreadable. I want one line per person and nothing else.
On an old file it reviews the whole thing and I get forty findings about code I didn't touch. I want to know about the twelve lines I changed.