Insights Blog
-- Browse All Articles --
Physics Articles
Physics Tutorials
Physics Guides
Physics FAQ
Math Articles
Math Tutorials
Math Guides
Math FAQ
Education Articles
Education Guides
Bio/Chem Articles
Technology Guides
Computer Science Tutorials
Forums
Science and Math Textbooks
STEM Educators and Teaching
STEM Academic Advising
STEM Career Guidance
Trending
Featured Threads
Log in
Register
What's new
Search
Search
Search titles only
By:
Science and Math Textbooks
STEM Educators and Teaching
STEM Academic Advising
STEM Career Guidance
Menu
Log in
Register
Navigation
More options
Contact us
Close Menu
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Science Education and Careers
STEM Academic Advising
What are some pieces of advice for a struggling programming learner?
Reply to thread
Message
[QUOTE="Kat-hi, post: 6848132, member: 692966"] Since you mentioned "presentable websites", often in many larger companies I had worked, there were programmers who wrote the guts of the presentation but not the presentation screen itself - since that also seemed to take some artistic ability and actually good practice. You may fit into the former category. Even that category may be split between programmers who write the database interfaces alone and the logic rules - and at times instead of actually writing pure code for logic, they might even use logic "engines" purchased from larger companies. Breaking the entire site construction by functionality also facilitates the ability to create modules that are more easily modifiable and avoids spaghetti code. Also it's important to do a technical design ahead of writing any code. Most beginning programmers don't do designs except on maybe a smaller scale - until they actually get more expertise in what is good and what is not. Often your choice of database, language and OS makes a huge difference in how you implement things. For instance with a relational database, you might write a query that is in a book you read that works, but it could be extremely slow for your particular database, your OS and the database "file" design. That kind of knowledge is important when constructing a design - and even how to design you "files." That takes often a lot of sweat and work - although there are often guidelines by companies that developed your OS and database type product - yet that is not usually specific enough for your own needs. Most programmers strive toward excellence in this aspect of coding - because their technical design proves itself as good over time, and exhibits speed and flexibility. THEN the technical design, in my opinion, should only be done after a person knowledgeable in the needs of the users writes a thorough analysis of the desired product. It helps to have programming take part in this process - even to work with the user themselves during the development - if the system is small enough to allow them to do that. As far as replicating what is in books - I think those were just meant as examples anyway for specific instances. When I started, I also taught myself after buying tons of books while working (there was no internet back then) and also had some good "friends" who were more mentors willing to help. You probably may do better either experimenting with the ins and outs of what you are trying to pick up (and only use the books as the first step in a more complex process). Also try to find a mentor of sorts who will work with you - not always one on one, but in a more relaxed fashion where they can tell you things after reviewing where you are at on a project. The mentor should be a friend, not an adept criticizer. Avoid people who offer no help and only consistently find issues with your work. If someone can't offer valid help or truly constructive criticism then they probably are lousy programmers themselves. Even if its a teacher - same goes there - many teachers have never worked in the field which is sad. Yes, many people program, but a good proportion of people are really not good at it. They just sound like it. Don't be fooled by people who talk big and produce small. Many create websites with virtually little of anything beyond basic HTML 1.0 - even with no CSS - and many often use pre-built offerings that do a good part of the "coding" for them under the covers - things you are trying to learn yourself to build without that. Don't give up. The more you do, the better you get. [/QUOTE]
Insert quotes…
Post reply
Forums
Science Education and Careers
STEM Academic Advising
What are some pieces of advice for a struggling programming learner?
Back
Top