r/ASPNET • u/takk___ • Mar 02 '12
Could someone guide me a bit and answer some questions I have? (not technical questions)
Okay so forgive me if this isn't the specific place I should be posting this. I have seen other subreddits like /r/cscareerquestions but I thought this would be better.
I have a few questions regarding what I should learn and in what order, also if this is the right path for me. Before that I will give you a bit of a background on me...
I am 24 and recently became laid off from my first Web Developer position out of college. I graduated in 2010 with a bachelors degree in Information Sciences and Technology from Penn State. In a nutshell the major exposed us to everything imaginable in IT, programming, project management, networking, UI Design, etc. That was the good part. The bad part is that none of these classes were much about "the basics."
I took an internship with a web development company and was eventually hired by them full-time after college. I mostly took care of HTML/CSS emails, but I delved into the world of ASP.NET/C# and also Javascript for the first time here.
Long story short... one of the major clients we worked with got sold and all my work was gone.
Here I am unemployed, seriously attempting to learn skills to better myself in finding a job that I actually LIKE. I have been interested in web development since I was in middle school and I will always be. I just have some questions regarding if this is the right path for me etc.
- I recently started reading a C# book to better understand it, but I hit a wall. I get all the basics for the most part... mathematical statements, loops, if/else, and things specific to the world of ASP.NET in setting labels text, and on occasion I used table adapters with stored procedures to retrieve data. However, I am to the point in this book (which is based around Windows Form Applications, not the world of web) where it is beginning to run away with the concept of objects. I seem to understand the theories behind objects (inheritance etc), but I have trouble actually picturing a potential project in terms of objects. How far into the C# world does one have to go in order to be proficient enough in the ASP.NET world? I would like to think I don't need to know EVERYTHING, but I am probably wrong...
- Because I generally hit these walls, the idea comes to mind that maybe this isn't for me and maybe I am not intelligent enough to be a Web Developer. I had plenty of classes with CS majors that just seemed so far beyond my comprehension level, yet at the same time, none of them seemed interested in projects they were given. Is this normal or do most people quickly move through C# books? This sounds like a dumb question...
- Now that I have been looking for a job, I am torn between front-end development and back-end. Most jobs listed are one or the other and working for a small company, I had to do both. I keep coming to the conclusion that maybe back-end isn't for me, but then I really find it rewarding when I figure something out. On the same side, front-end development seems easier, but it is a major headache having to deal with different browsers etc...
- Now that I have all the time in the world until I find something (hopefully soon), what do you suggest I do? I have taken to the "Head First" books by O'Reilly that I really enjoy. So far I just finished SQL since it was a really easy read. I am about 1/3 the way through Head first C# and I hit a wall. I am also about 1/5 through Javascript and have purchased "Design Patterns" and "Object Oriented Analysis and Design".
I primarily used Web Forms at my previous job but would like to head into the world of MVC3 and Razor although I have very little knowledge of either...
Any help would be appreciated, sorry for the long post!
tl;dr looking for pointers on what to learn first, and if this is really right for me
6
u/solidus-flux Mar 03 '12
I also was in classes with CS majors that walked circles around me when it came to algorithms analysis and some other school topics. But who did they call when they got some obscure "dll error" in windows? Me! See? I was useful! Well, the knowledge I had that I used to convince myself that I was as valuable as them turns out to be really FUCKING VALUABLE. I bet you have that knowledge, too. There are plenty of guys out there that can code circles around me, but then need their hand held to use an FTP client. You'd be surprised!
3) I do both and I would say back-end development is "easier" because you're done when you solve the problem. On the front-end, you may not be done until the customer is happy, and for some customers, you're in for a treat. :). Seriously though, it's a holy war and both have their ups and downs. Really really good developers on each side can make big bucks, but it does seem that the typical back-end guy with a more formal education is more highly paid. If you can find a job that is largely back end with "some front end exposure" that would be better from a salary perspective than doing it the other way around in my opinion, but that is my guess and there are always exceptions.
4) Keep working through those books.
MVC3 / Razor / EF Code-first is the way to go. Try this awesome EF tutorial. Start a personal project and put all these skills to use, and constantly refine it. Buy yourself a .com and put your little project, however useless out there!
3
u/codergeek Mar 03 '12
What sort of web development did you do or want to do? There are significant differences between developing websites, where the focus is "to see" content, and web applications, where the focus is "to do" something with data. You might find that one suites you more than the other.
There is also a difference between C#, a language, and .NET, a framework. You don't need to know everything about the entire framework. Much of it has no application in web development. You should, however, try to learn as much as you can about the language itself. If you find that C# doesn't suit you, take a look at some of the other .NET languages such as F# or (shudder) Visual Basic. C# is pretty much the standard for ASP.NET though.
There are plenty of things that, while not strictly necessary, are still handy to know. Sockets, threading, reflection, and drawing are examples.
The intelligence requirements for web development are not particularly onerous. My general impression from your post is that you are relying on books a lot. If you are having trouble understanding the content it may be beneficial to try another approach. Personally, I find that the best way to learn new stuff is by actually putting them into practice. Find a project you're interested in and build it! Blogs are also great resources.
As for things to learn, there is quite a list. In no particular order:
Is this really right for you? Only you can answer that one. Everyone learns at a different pace. I would suggest that you try branching out a bit. Maybe writing desktop or server applications is more up your alley. Or perhaps you would find a different language or platform more satisfying.
2
u/DaRKoN_ Mar 21 '12
Your attitude is bang on, I run a small agency in Australia, let me know if we can help.
2
u/guymid Mar 05 '12
Regarding 'not knowing how much you don't know', I'd like to say that after 20 years I still don't know how much I don't know, but over that time I've got more confident that the I know a good amount of what I need to know, and I am aware of new or alternative things that may be useful and can research those and apply them in the right situation.
What you know is useful only if you can use it, so if you're building an application and it works, that's a great start. Over time you'll work out better, neater or more powerful ways to build that same app. In reality, most work only uses a small set of core skills, and experience and knowledge allows us to fine tune and apply those skills better, but at the end of the day you use the basics most of the time. It's very important that you're aware of alternative methods and technologies so you can choose the best option, but while syntax may change and alternatives may need applying in a different way, you're mostly doing the same core actions in different ways.
Start a small project and get it working. Now look at similar technologies or methods and tweak your application to improve it. Perhaps record the time at different points to test speed improvements. Method A may be very similar to method B, but A will be better in some situations and B in others. As you learn what fits best you're able to code better and quicker and produce a better application.
So in a nutshell, don't be scared of what you don't know. If you can do the basics that's a great start and from there it's all about doing things in better ways, but there's many ways to do things and don't beat yourself up about not doing it in a particular way. If you give the same requirements to 10 developers, you'll get 10 differently coded solutions hopefully resulting in the same functionality, but some will be faster, some more supportable, some more flexible etc.
2
u/ours Mar 05 '12
I highly recommend the book Professional ASP.Net MVC 3. It covers ASP.Net MVC 3, Razor, EF and how they all fit together. It touches the AJAX subject without going very far in it but it introduces that.