We do, too. But I leave the email for webmail/desktop mail. And conveniently hardly touch my laptop outside work, so it works out the same. Laptop is work machine, phone is home machine.

I don't add work email to my personal phone. I have it possible to access, but I put it out of the way to reduce the likelihood of accidental work during time off. Going to log out of the work Slack during vacation, too.

Yikes. That sounds really bad! Is that just London-area, or all across England?

I probably couldn't afford a house in my current neighborhood now, either. Lucked out 5 years ago.

No, I'm not sure I'm following. Can you share a screenshot demonstrating the issue?

The current assumption is the very simple "load newest, then allow to fetch older from there". But maybe that can leave a gap if you refresh at top?

Oh weird. We have the opposite problem here - people are priced out of housing because everyone builds gigantic luxed-up McMansions that cost a pretty penny and have way more space than most people and even families need.

Pretty much my whole neighborhood of reasonably-sized houses is getting bought out, razed, and rebuilt as ginormous houses-of-doom that will sell for 2-4 times what the original property sold for before the rebuild. Any older, larger lots tend to be bought, split in half, and two megahomes built in what was one lot before.

I don't think I ever looked at their branding. I was very goal- and price-focused. They had very little between me and doing what I wanted. DreamHost's Panel always felt labyrinthine to me.

// @kdfrawg

There's oodles to it all. If you ask more leading questions, I can probably give some useful answers.

//

Yup, forms are totally doable. You're on your way to recapitulating the history of CRUD: flat files, raw DB, CGI forms, Rails with forms and migrations…

//

Those are course 0 or 1.5. ;)

But, yup. You're wandering into database normalization and more general database design.

Normalization tends to mean a bunch of tables each acting as canonical store for some bit of info. Answering questions requires gluing stuff back together with joins. Common reports can be rigged up as views to basically save the query definition and let you further query against it. Data input gets "fun", though.

//

Hunt down Frotz in an app store near you.

//