I use tmux (or screen) as a bag for holding context. I set an environment variable before spawning it, and then key a lot of things in my .bashrc off that environment variable so I get context-specific functions/aliases/vars/etc, and keep them when I open a new window in an existing tmux. The single best part of this is separate histories for my development vs system administration vs whatever, although the rest is still quite useful.
> some people favor one parent, and some the other
A number of the responses here say things like this, and I'm picking this one somewhat arbitrarily to call out that "people" isn't the only dividing line - some people very much favor different sides of it at different times, in different moods, in different contexts, to varying degrees.
Perhaps Devil's advocate, but my rebuttal would be that we're not necessarily comparing similar gains to correctness as to optimisation, and that perhaps the correctness gains can be better attained another way where the optimisation gains cannot.
(Personally I find a type checker tremendously valuable for communicating with myself - and my team, I suppose - about assumptions being made in other parts of the program, which can probably be accounted "correctness".)
No, the crime isn't staying in. The crime (if it is one) is choosing to stay in. If he reports on messages from 6mo ago with an auto-delete of 1wk, he was aware of it roughly 6mo ago (and taking it seriously enough to preserve things).
> Can you do the first two years of education and credits at a community college, and transfer to a state school for the last 2 years?
That's what I did (albeit at a very different time in my life) and it worked well. Community colleges are usually quite supportive of students taking a light load for longer - it's a common need among their (actual and potential) students for a variety of reasons.
Actually, I contend that it can increase supply of "housing sufficiently near sufficient income" by improving some marginal (existing or potential) housing.