A project or more commonly the projects is a slang term in American English referring to government owned housing for low income residents. It's short for Public Housing Project. Projects built en masse during the mid 20th century were (in)famous for being large scale, bland looking, brick, apartment towers, often built on the same plot of land, offset from the street. This is what a stereotypical project looks like in New York City (where I'm from). Modern public housing tends to be much more well integrated into the neighborhood and is often hard to distinguish from other housing. Also, nowadays it's much more common, at least in New York, for certain residences to be reserved for low income residents in an otherwise regular apartment building, rather than building purpose built towers. More on reddit.com

More on old.reddit.com

The FAQ has a list of lists of project ideas , some of which are quite complex. Think of stuff like making a custom web server, a programming language, a game, and so on. More on reddit.com

I was working with QA in a telecom at the time. Our customer service representatives claimed to experience some occasional lagspikes in the CRM application they used to manage customers and products, which they said often froze for 1 minute and a couple of seconds. The IT department were never able to reproduce it manually, and as such that matter was in a limbo for a long while since IT didn't allocate resources to a problem they didn't believe existed, and customer service lost faith in IT for not fixing a problem they experienced. At the time we (IT) didn't have that many resources to allocate to investigating possible server/VM issues, but they had me. I was just a QA junior, and I was in between test-projects - meaning I hads lots of time. So I planned to THOROUGHLY test this by running through a "customer service representative usage scenario" non-stop for 72 hours, without break. Of course, no human can do this. So I started by learning Java and Selenium, and wrote a script that would mimic a user, then write down a lot of statistics about how the user experience was. Then it'd shutdown and do it all over again. Then I aggregated all of this data and made a manager-friendly report. After this we realized the timing, length and intervals of the freezes coincided with cache dumps on several of our VMs. So those poor sods who had the freezes were connected to VMs who happened to dump the cache at that time. So we were able to fix all of this due to my investigation. Couple of months later I was promoted to junior backend developer from a QA position without any dev background. More on reddit.com