310 reputation
18
bio website awmckinley.net
location Lakeland, FL
age 28
visits member for 3 years, 7 months
seen Apr 14 '13 at 20:25

May
29
comment What are the worst things that inexperienced developers forget to think about?
@Aaronaught: I apologize then - not wanting to waste anyone's time. I really thought I had a specific question in mind, but I guess I'm not quite sure how to articulate it yet. I guess I'll just have to wait until I'm more experienced to be able to ask an appropriate inexperienced question. ;-) I definitely appreciate all the good advice though.
May
29
comment What are the worst things that inexperienced developers forget to think about?
@Billy ONeal: Just edited my question. Does this make more sense?
May
29
comment What are the worst things that inexperienced developers forget to think about?
I'm sorry, Billy. Maybe I wasn't clear in the way I asked my quesiton: I'm not looking so much for development practices (like source control). I think that was pretty well covered in What would you add in this Software Development Project Checklist?. The "taxes" section is definitely helpful though.
May
29
comment What are the worst things that inexperienced developers forget to think about?
Maybe "checklist" implies the wrong thing. I'm not looking for a list of things to think about at the end of development; I'm curious what things should be considered as you're developing an application. Do you have a suggestion for how I could restate my question?
May
11
comment Which language was used to create Visual Studio 2010?
That's true. But I think I did hear or read that they used C# (if my memory serves correctly).
Jan
7
comment How do you structure your shared code so that it is “re-findable” for new developers?
Yeah, definitely. I'll have to talk to the guys about the Wiki idea. Maybe dividing a Wiki into a Silverlight section, an ASP.NET MVC section, etc would be helpful.
Jan
7
comment How do you structure your shared code so that it is “re-findable” for new developers?
Wow! That looks very interesting! We'll have to look into that... thanks!
Jan
7
comment How do you structure your shared code so that it is “re-findable” for new developers?
I definitely agree about the need for communication (esp. letting the other developers know what you're working on). Are there any ways to one capture that information in such a way that it can be helpful to new developers after older developers leave or have split off into separate teams?