I was under the impression mislav was maintaining it at the moment. At least I've seen some commits from him in the last 2 months, including some a few hours ago, although that might have been prompted by this thread.
My Coderwall App (https://github.com/OiNutter/Coderwall-iOS) is open source and I'd be happy to have you to take a look and maybe make some suggestions. However it's my first ever app so I doubt it would do much to help you with your goal of becoming an engineer. Even so, if you want to take a look and get involved then feel free.
I learnt a lot from the Stanford online courses on ITunes U. Granted they are video lessons, but you can also grab all the lecture notes and sample code from this link:
Other than that I just googled the hell out of things, Stack Overflow was, as always, a valuable resource. Chances are that whatever you're trying to do, particularly when learning, somebody else has already done.
Hmm, like the layout, presents a lot of info well, but really not a fan of the font they've used for that top section. It's just on the edge of being hard to read, not quite, but not clear. And the main headers with the gradient effect just look a bit blurry to me.
Used to use SmartGit at my last job and that generally worked pretty well. New places uses svn :( so have got familiar with TortoiseSVN, which works pretty well, so would imagine TortoiseGit would also be a good choice.
What, no mention of ASP? Particularly Classic ASP? I had to use that at my first job and it was just painful! No proper array support makes me a sad boy!
Hmm, while I agree that it can be hard to keep on top of you emails in that kind of volume, if you're a boss, and you're bothered enough about being kept up to date on a project, perhaps some email rules that filter emails about that project into a seperate folder so you can see, quite easily that there are emails about that project, might be a good idea?
I occasionally get similair situations to this at work, which is why I request read receipts. Makes it even more satisfying when an account manager is having a go at you for not emailing them something and you point out they sent you a read receipt for it, they just obviously didn't actually read it. My account managers hate my read receipts :)
What you don't get here (and he didn't really spell it out because I guess it seems obvious once you're in that position) is you don't have time to (nor should you even want to) follow every email thread about every project that you (should, theoretically) already have complete faith that your employee is successfully executing. If you need an update, you just want an update (hey I noticed Bill's getting a little antsy, here's the status of project 127: "status") not to find and trace back through a discussion of x y and z aspects of implementation or marketing or whatever.
Bingo - you have to trust that the people working for you know what they are doing. This means going to meetings and being belligerent with other managers at times as they try to claim your people are screwing everything up, without even checking with your people. You always defend first, never call anyone out by name and never let any other manager talk derogatorily about your employees. Part of your job is to protect the people who aren't there to defend themselves.
This also means that if your developers drop the ball, you're screwed. You can't possibly know if someone is sticking bugs in the code as they race for a deadline, but when the system misses deadline because of it, guess who's responsible?
Doesn't help when you stick up for a dev for weeks or months and then they burn you by introducing shoddy code or not testing thoroughly, and their response is 'well I sent you a bunch of read receipt emails, so those browser bugs I introduced aren't my fault - you should be paying attention'.
This experience is why I work so hard to back up my boss or lead when I'm just a developer on a project.
Reminds me of the stock update system for one of our major clients at my first job. The predecessor of myself and my colleague had thought it a brilliant idea to build a clothing ecommerce site, with a complete list of all stock going back to the year dot with ASP and Access (that's Classic ASP, not .NET). Towards the end the stock update would take pretty much an entire afternoon to run.
Eventually we got the approval to change to MySQL for the database. When they ran the first stock update with the new version they rang us up to check it had worked because it was near instantaneous.
But yeah, that was an attempt to be funny that just fell way short.