I was just making a comment. I've been coding in .NET since beta and learned
as I coded or buying book after book after book or by using Google to find
what i was trying to do and to 'put the pieces together for my apps.
Is 'hello world' an application? yes. I was just saying I have several Java
books that starts out with 'hello world' as well, but then gets into,
creating a GUI, accessing a database, showing data, updating, data,
compiling the app, deploying the app, security, etc. and by reading that
book it gave me a better understanding of what I need to do when creating an
application within Java from what to look for when compiling, creating a
install package, etc.
yeah now a days there are tons of sites out there that have starter kits
from winform apps, web apps and even some hand held device applications,
which makes development easier for developers these days.
But what I'm seeing (and I'm not saying all developers just a few I've
talked to or worked with) with all of these 'starter kits' and drag and drop
code, and the controls that .NET has now and all of the third party tools
out there, developers aren't really understanding of whats going on. For
example, I have a BA that created this incredible application for his area
and doesn't know much about programming. He used everything that .NET
provides which made it a snap for him to create this app. But when he got
some requests in for some customizations he was clueless because he didn't
know how to write a line of code. He used a starter kit and just pointed his
grid, drop downs, etc to his database,
So is 'hello world' an app? Yes
does every app need to talk to a db? NO
but do developers need to understand how an application works from front to
back without the use of widgets, starter kits, etc,? In my opinon yes.
I agree with eveything you said and the web sites are great learning tools
as well.
its like, there never is a wrong way to code something (unless it doesn't
work) because there are a 1000 different ways to get to that same result.
this is kind of the same thing
Most any introductory book will start off with a "hello world" sample
applicaiton. That's your "complete application from beginning to end." It
may not be a "complete application" because it is so incredibly small. But
it is still a "complete application." Beyond "hello world" it's so totally
open-ended as to [what a "complete application" even is]; that it is up to
you to define. Do you consider an application to be incomplete because it
does not talk to a database? That would be a totally valid opinion. The
opposite would be equally valid.
What might be helpful is for you dive into one or more [reference
applications]. These are completely functional applications that come with
all source code and necessary resources, and typically thorough
documentation (terse as it may be in the code) including an eBook in many
cases. The idea is that you install a reference application on your
development box, run it, and then dive into the code to see how it works.
This is an incredibly useful learning tool.
Here are some links to a few reference applications. I'm sure you can find
more.
Windows Forms
http://devcenter.infragistics.com/RefApps/Tracker/Tracker.aspx
- Show quoted text -