read_wharf

There should be a Congressional Technology Office, similar to the Congressional Budget Office.

They say that you should never re-write a project, but that's in the context of something deployed and operating. It sounds like you are not deployed.

You've put a lot of time into the project so far, so you've learned a lot about the project and its domain.

When you first started your project you didn't know as much as you do now.

So consider using everything you've learned to date, and start over from scratch. Total re-design, total re-write.

If you have trouble explaining the dependencies of your own project to other developers, that's a sign of ... something. If you can't break the project down into pieces for yourself to work on, that's a sign of ... something.

It's a network study. :)

If dev is outsourced, then they'll be right there in the building when they need to tap a QA shoulder.

I'm no economist ... I think houses were appreciating while people were upwardly mobile in the economy. So not just more people, but more people with the means to buy a house (or borrow money for same).

Now we're stagnant, and people are talking about the disappearing middle class, and housing prices are flat.

I have received mail from SSA addressed to <myname> Unknown, because of confusion over my name.

You need the best and brightest so that you can say you have the best and brightest.

You say that you have the best and brightest so that you can say you have the best and brightest.

This was my immediate (and only) concern.

"Am I the only one ..."

The answer to this is always "no."

Except this time.

"Of course, there’s a catch. You couldn’t offload all those metals on the world market at once, for fear of crashing their prices. But the company would still own that much in equity, which would allow them to borrow against it. They would be that wealthy, to all intents and purposes. That’s just how capitalism works."

You don't have equity to borrow against unless you can liquidate and transfer to the lender.

You can't liquidate and transfer to the lender unless you can bring it all down here (destroying the market and making the equity worth much less), or transfer any on-going and steady operation that is bringing it down little by little (show me the money), or by bring us up there in the form of widespread operations across multiple companies.

If we go up there in a big way, well, precious metals aren't so precious.

The worst thing we've learned is that all we have to say is "we followed standard procedures" and we get a free pass, regardless of how egregious standard procedures or implementations may be.

Yes, exactly. We need tutorials for people who are primarily learning to program and are using a language for that, and tutorials for people who already know how to program and are using a language for GST.

I have just been educated by reading more of this thread. I can see an obvious need for one virtualenv, so that you can separate your service and its needs from the system python and its needs. Beyond that my inclination would be to go more servers rather than more virtualenvs, but circumstances vary and my experience is narrow.

"First DO use packages that come with the OS."

I'd go middle ground, and start here, but consider a self-built package where necessary. It depends in part on the focus of your distro.

virtualenv. What problem does it solve? Different python version/environments? Wouldn't that be better solved with another (virtual) server? I understand if an extra $20/month is an issue, but otherwise ...