|
Laiju k wrote: guys give me some tips which can be done by less effort as i am having enough work to do.
Sorry, no. It doesn't matter if you've enough work to do.
If you want to do what you're asking for, you've to put in a lot of efforts. Read, read, read, write code, repeat. Invest in a lot of books, and find the time to read them several times. Alongside, practise what you learn. If you're OK with reading on a Kindle or PC, you'll, be able to find books a lot cheaper (safari books library, pluralsiight, ebooks for kindle, etc).
There's no short cut to improving your knowledge.
"Real men drive manual transmission" - Rajesh.
|
|
|
|
|
Thanks for your reply.
Rajesh R Subramanian wrote: There's no short cut to improving your knowledge.
yeah.But we should try if there is one.As we repeat the codes make it short by refine it.Change bad codes etc.If we do a long thing short then it can be said as shortcut.
|
|
|
|
|
Laiju k wrote: But we should try if there is one.
I don't think there is. At least not while the matrix knowledge injection is not invented.
Laiju k wrote: If we do a long thing short then it can be said as shortcut.
Shortcuts can hold traps and are not necessarily better paths. Like our friend already said, read books, study experienced people codes (open source projects are a good way to do that) and code, repeat.
You can't improve a piece of code if you don't know it can be improved.
One way that I learned a lot was while I was contributing in forums and helping people find answers. I helped others while learning as I did not know the answer for all the questions.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson
----
Our heads are round so our thoughts can change direction - Francis Picabia
|
|
|
|
|
Thanks for the reply
Fabio Franco wrote: One way that I learned a lot was while I was contributing in forums and helping people find answers. I helped others while learning as I did not know the answer for all the questions.
I am doing the same now.
|
|
|
|
|
Regardless of what others might imply, I don't think there's any substitute for working with a mature, experienced team. I spent my first 5 years as a programmer reading forums and volunteering on open source products and even writing CodeProject articles! I thought I was hot stuff, until I joined a new organization and got paired up with some highly experienced engineers. They spent hours sharing their desktops and explaining in great detail why they wanted certain patterns and how to write enterprise grade code.
In summary, I learned more from this group of experts in a few months time than I had learned in total, on my own, over the previous five years. The moral of the story, get yourself on an experienced development team or find a great mentor. Going it alone with nothing but Google and StackOverflow.com on your side can only result in a poor outcome.
|
|
|
|
|
I agree with you...
I think there are two kind of people here...
- The ones that can better learn just doing stand alone research.
- The ones that can better learn when pairing with experienced ones, going to war...
I'm more of the 2nd type, I read, I research, yes, but if I'm not in a project that requires what I just read, I will go to a very dark place into my brain... unless I find a way to use it (have a project) I will then never try it.. ok I will have it in my memory, so in a future project I could recall it, use it then real learn it... there is where I love to work in good teams, when you are working together with experienced people you will learn crazy and useful secrets that you will just not notice in a book. (normally you could learn everything in a project or work in around 2-3 years, if the project is not good enough or too simple you will notice you get bored... time to something new)
My best recommendation is: try to join an external project, just for education, that will help you, you will have a better reason to research and learn that just reading (normally I forgot what I read 2 pages ago...) plus contacting other people in the project will help (open source project, with good forums are good)
|
|
|
|
|
Thanks.Member 4673202 wrote: The ones that can better learn when pairing with experienced ones, going to war...
I like that,if we don't go with experience we will be getting killed early else we can survive a little more experience more things.
Member 4673202 wrote: if the project is not good enough or too simple you will notice you get bored... time to something new
It also happens a lot.Sometimes we will be using outdated technologies in our project just simply maintaining the old one.
Member 4673202 wrote: My best recommendation is: try to join an external project, just for education, that will help you, you will have a better reason to research and learn that just reading (normally I forgot what I read 2 pages ago...) plus contacting other people in the project will help (open source project, with good forums are good)
That was a good tip.I will surely try.I also forget what i read after a day or two.If we don't use a tip,trick that is even a line of code.we don't remember it.by regular usage only it will set in our mind so we can reuse it after a long time also.
|
|
|
|
|
Thanks.I think like you have told.I know by working with a experience team is a great aid to our carrer.we can study a lot from them in months than we gain by ourselves in years.As we all years of experience what enhance our carrer.If our experience is only in years but no actual experience compared to years we work we have to struggle a lot.
|
|
|
|
|
Laiju k wrote: I have to research a lot for keeping new things in my code
There's your mistake!
Keep abreast of emerging trends and topics, but don't research things for the sake of getting new things into your code. If you know a way of doing it and that way works without problem, and you're not immediately aware of a better (more efficient, easier to maintain) way of doing it, then benefit from your own experience, and do it the way you know how.
That way your code base will be consistent.
Then, when you come across a problem you don't know how to solve - or believe there may be a better way of solving, spend some time investigating that and decide if the advantages are worth the time spent learning the new technique.
In short
new != better
PooperPig - Coming Soon
|
|
|
|
|
Laiju k wrote: Can you guys give me some tips which can be done by less effort as i am having enough work to do
Well, it won't work this way. But you are asking this on CodeProject - the home of thousands of great articles and tips by the legends. Simply search what you want to learn and you have it right here! 
Your time will come, if you let it be right.
|
|
|
|
|
Thanks.I am regularly reading tips and tricks,articles.I am preferring general ways of programming which will make it more effective.
|
|
|
|
|
Some people are lucky to work with really experienced and good programmers, early on in their career. However, I feel this is not the case in more than half of the cases.
1. Continuously learn; do not stop learning. Some years ago, I came across this site Stanford Engineering Everywhere[^], where there are three courses - Methodology, Abstractions and Paradigms. Go in the order stated there. While you listen to the lectures there, visit cs106a[^] and cs106b[^] for the latest software updates / downloads. These do not teach you the programming languages you mention, but they do teach you how to solve problems using computers.
2. Remember that there is no "instant success". You'll need at least ten years[^].
Addendum:
Got reminded of a quote I had seen back in 1993 in Bengaluru, India.
"Good judgement comes from experience.
Experience comes from bad judgement".
modified 4-Nov-14 7:41am.
|
|
|
|
|
Thanks.
Amarnath S wrote: Some people are lucky to work with really experienced and good programmers, early on in their career. However, I feel this is not the case in more than half of the cases.
We can learn new methods,tips,tricks like that from experienced colleagues else we had to struggle a lot to even reach a certain level,real and continuous hardwork is needed for that.
|
|
|
|
|
Experience is a relative term so then dont get put off if the guy is 2 year experience. It depends what he mastered in this duration.
And IMHO, trying new things in code just to look cool is very bad idea. When I am working a real customer project, I stick to what is required and how robust is my code. I work mostly on labview and I have been sticking to a simple but boring architecture when I work on live project cos I know it well and I am very efficent.
But I use "new" things on my Pet project to learn the craft. Few months back my daughter wanted to chat with one of her friend online. So I decided to implement a one-2-one chat application for them. So I used this to experiment with latest and greatest. Unfortuantely this was a disaster and I think I lost some respect from my kid
cheers,
Super
------------------------------------------
Too much of good is bad,mix some evil in it
|
|
|
|
|
Back in April this year (but, not on April 1), I said (on another Lounge thread):
"By the way, in my book, an "experienced developer" is one who has learned the necessity of constant re-training in order to be able to implement the wisdom, principles, heuristics, etc., learned from formal education, self-education, and long experience, in technology that is constantly changing, using tools that are constantly changing." In my opinion the source of knowledge, information, wisdom, and, ultimately, skill is not located in "other people" ... although, of course, other people can challenge us, inspire us, make use aware of what we don't know, motivate us by example, etc. ... but in ... yourself.
Learning "how to learn" is a lifetime work, but how wonderful it is when that becomes a habit, and, even, a passion !
In my opinion, programming is, like playing a musical instrument, both skill, craft, and art.
Of course, few violinists have the number of strings, the shape of the bow and body of the violin, change every year so much they have to learn to play again
« I am putting myself to the fullest possible use which is all, I think, that any conscious entity can ever hope to do » HAL (Heuristically programmed ALgorithmic computer) in "2001, A Space Odyssey"
|
|
|
|
|
Nice message.
Quote from Swami Vivekananda - "Be free; hope for nothing from anyone. I am sure, if you look back upon your lives, you will find that you were always trying to get help from others, which never came. All the help that has come was from within yourselves."
Inspired me during my Ph.D. days.
|
|
|
|
|
Hoping help will come is not good if we know there is no one to help.But if we get help it is nice.
|
|
|
|
|
Laiju k wrote: Hoping help will come
You should never hope help will come or else life will run you over. You should take matters in your own hands and if help comes along, awesome, but you should never depend on it. Learn to reach out.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson
----
Our heads are round so our thoughts can change direction - Francis Picabia
|
|
|
|
|
Fabio Franco wrote: You should never hope help will come or else life will run you over.
Sure.I will never hope for that.
|
|
|
|
|
nice but the analogy at the end isn't really accurate.
contemporary music (brand new stuff by living composers) very often asks musicians to learn brand new techniques ('extended techniques', or ways of physically playing their instruments) as well as new notation that composers dream up as a way of expressing the new techniques they want you to use.
programmers learn new languages and techniques but still use computers and peripherals; musicians learn new musical notation (languages) but still use the same instruments (sometimes in new ways).
|
|
|
|
|
I was in the same situation with a very similar technology stack (I use AngularJS instead of JQuery but everything else is the same). I ended up hiring a guy by the hour to teach me design patterns and do code reviews with me outside of my company. I hated to pay but it was the BEST money i have ever spent. I learned more in those sessions then i ever did at my university programming courses.
Finding a "good" software engineer is hard but you can do it. A good test is if they can explain a couple design patterns in a way you can understand. If they can explain a factory pattern and when it is used and why in a way you can understand then they are most likely worth paying to do your code reviews and teach.
Also, watching code reviews on youtube is helpful though they will often put you to sleep.
Good Luck.
~ Eric
Eric
|
|
|
|
|
Thanks Eric,
I don't even think about that.I think I will fetch a person good enough.I don't know I can get somebody like that.Eric Whitmore wrote: Also, watching code reviews on youtube is helpful though they will often put you to sleep.
I will also try this.
|
|
|
|
|
You make a very good point, Eric: at certain times engaging in a relationship with a "mentor" can be something that catalyzes the learning process ... if you are lucky enough to find a mentor who both has a depth of knowledge, and practical skill, and is able to teach.
« I am putting myself to the fullest possible use which is all, I think, that any conscious entity can ever hope to do » HAL (Heuristically programmed ALgorithmic computer) in "2001, A Space Odyssey"
|
|
|
|
|
Watch Pluralsight videos and read code project articles.
|
|
|
|
|
Joshua Hightower wrote: Watch Pluralsight videos and read code project articles.
Thanks
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
