I mean why is it hosted on a site designed for Version Control when it could easily be hosted on something like Pastebin or as a public document?

I'm confused about the GamerGateOp. Why is this important?

Finish them. It sounds like you have a lot of things to complete.

So like learnprogramming?

Yeah. Where I'm working we have one dev who is adamant about it, but he's come from some really old school code shops and worked in large corporations. it seems like these huge enterprise solutions would require a lot of testing to ensure that things are functioning properly.

I've never heard of writing unit tests in the same file either. I've always seen them done in a separate file. Usually you're working on "person" and have "persontests". Maybe that's my inexperience though.

Already love this. It seems a little young and not incredibly active, but hopefully that changes.

I get the importance of some unit tests. But I don't think that they need to be done for everything. I don't agree with justletmevoat, but I also don't agree that we always need them. I think they are good for specific tasks that require either a lot of validation with a lot of moving parts, but I don't see them being useful for smaller things. Maybe because I haven't really done test-driven development, but the way I've seen them implemented in most cases seems like a waste of time.

It as built on the ASP.Net WebForms framework and didn't have any kind of asynchrony built in. It just got to the point where it was sending huge chunks of data back and forth. All we did was introduce some AJAX requests and that alone improved speed by something like 900% and reduced the amount of data per call by over 300%.

It's just a disaster waiting to happen. Once you logged into a user's account you had access to their CC's, birthday, address, everything. There was no security in place because it was 'too much of a hassle for the older users that want something that's easy to use and easy to understand'.

I guess it's not really 'hardest' but as far as 'craziest thing discovered while fixing bugs' is this:

I was working for some academic testing software trying to find why the system had slowed to a crawl. I had some test accounts for admins and teachers. During this process I discovered that the passwords and all personal information was stored in the database in plain text. Okay that's pretty bad, but it gets worse.

I decide to follow the rabbit hole and here is what I discover: A user can 'change their password' and it will display their previous password in plain text. They can 'change' to a 'new' password, by using the exact same password they had previously used. Additionally, they could choose 'forgot my password' and it would show you a pretty standard security question and answer page. Only the questions and answers were user submitted, and could be left black. So you could choose any random user that you had an email for, click 'forgot my password', and security question would pop up that was likely blank, the answer field was also likely blank, it would display their old password and you could then change to the same password they were always using.

The sad thing is that when we brought this up, "We wanted users to be able to know what they were currently using so that they didn't use the same password when changing it. We also wanted to allow them to choose a custom security question and answer as we feel this is better than the regular security questions other sites used".

Essentially, this is the best "It's not a bug, it's a feature" I've ever seen in real life.