+ 69

[Good Programming Habits]

Care to share on the habits that make you a good programmer?... I'd like to know what initiatives do you take to ensure your coding skills are top notch, and how do you go about on your coding habits on a daily basis.😊 I wanna gain some experience that'll ensure I stay updated with the latest tech. Any help is appriciated upfront, thank you🤓

23rd Oct 2017, 1:42 AM
Given - avatar
85 Answers
+ 32
For me, just looking for easy and simplest coding style from my friends whom I consider him or her as better than me. some friends are very talented in coding and making amazing apps, but if their coding style are beyond my comprehension, I just ignore it. And dont try to undetstand their codes.😜😜😜😜😜you will be growing very old before you could make your first app😰😰😰😰😰😰 but some guys are very talented, clean and neat coding, I just learn from them.👍👍👍👍👍👍 here is my suggested list👉👉👉👉 1. Set your coding style😎😎 shorten your code line as much as possible and readable. 2. Accumulate algorithms as many as possible👷👷👷 for example-hashing,stack,heap, linkedlist,OOP, MVC,and so on💥💥💥💥 2. Make small or light apps make apps which can be useful for you and for the others such as ebooks apps, tutorial apps 3. Make Small games For example- Tic Tac Toe, Puzzle, tetris and snake game. it is very challenging and good for logic problems...👼👼👼👼👼👼
25th Oct 2017, 2:46 PM
Andrew Ting Mai Zau
Andrew Ting Mai Zau - avatar
+ 90
23rd Oct 2017, 1:27 PM
Bhavesh Gupta
Bhavesh Gupta - avatar
+ 73
1. Comment your code as you go, future you (or someone else) will thank you as they will understand why you chose to do something and what scenarios you've thought of. 2. Test by yourself as you go, much easier to debug that way. 3. Have a fellow programmer review and test your code. 4. Have a non-programmer try your code. 5. Use modular code if you have to repeat a task within your code. Makes it easier to read and update. 6. Practice, practice, practice.
23rd Oct 2017, 8:25 PM
Duncan - avatar
+ 51
When I start making a new program I always draw or write down the functionality with pen and paper (usually in pseudo code). So I solve most of the problems before writing a single line of actual code. For me this has been the best way to avoid annoying time consuming mistakes and it has saved me from so much pain. :)
24th Oct 2017, 2:20 AM
Hanna Enqvist
Hanna Enqvist - avatar
+ 30
Read Sololearn programming tips 🤗
25th Oct 2017, 12:37 AM
NimWing Yuan
NimWing Yuan - avatar
+ 26
Don't bother my brother and you follow the coding languages on soloLearn.
23rd Oct 2017, 2:17 AM
Chinthana Kavinda
Chinthana Kavinda - avatar
+ 22
+ Use github! learn git if you haven't yet, and build your programming portfolio there.
24th Oct 2017, 2:25 AM
Hanna Enqvist
Hanna Enqvist - avatar
+ 20
23rd Oct 2017, 11:41 AM
Amjad - avatar
+ 17
Before you just write coding. Make a clear algorithm of what you want to do
26th Oct 2017, 3:43 AM
Gaurav Adhikari
Gaurav Adhikari - avatar
+ 16
One tool I use for many things : SPEAK IT OUT ! When you're building something complex, or analysing a problem, use your voice and tell your thoughts to yourself. Sometimes thoughts can be quick and messy if you let them go wild. Using your voice makes it more concrete and organised. Give it a try ! Well, maybe not too loud, and be careful who is around, they could make it another reason to consider you as a maniac !
24th Oct 2017, 12:43 AM
Cépagrave - avatar
+ 16
Understand the task first. 1. If it is big task divide it in modules (mentally) just for yourself. 2. Start writing pseudo code for module. 3. Test that module. 4. Repeat steps 2 and 3 for all small modules you created. 5. When all modules are done, merge these modules. 6. Test complete application once. 7. Get it tested by other programmer as well. 8. Fix bugs if any. 9. Take care of exceptions that can occur. 10. Comment your code well. 11. Keep it simple. 12. Use any version control if you are working on big task or with team, it saves efforts, confusion and time. 13. Try to use concepts of OOP that makes code reusable and secure. 14. As you get experience, you will know more good habits, Do share those habits with us :)
24th Oct 2017, 11:56 AM
Popat - avatar
+ 14
A good programmer is someone who looks both ways before crossing a one-way street.
26th Oct 2017, 5:57 AM
kenneth mayor
kenneth mayor - avatar
+ 13
Of course there are all the remarks about coding style and putting comments. The most important : you will never spend enough time thinking about the big picture and the algorithm complexity before running into coding.
23rd Oct 2017, 1:55 AM
VcC - avatar
+ 13
Being different and stupidly patient.
24th Oct 2017, 7:17 AM
kenneth mayor
kenneth mayor - avatar
+ 10
Tips: Think of the most stupid user. Make everything very user-friendly. Program first, design second.
23rd Oct 2017, 5:48 PM
ykahveci - avatar
+ 9
Please write down PSEUDO CODE (code simply written in your native language to draw a rough sketch of your code) before writing the code it will save lots of time.. Writing comments in your code helps in debugging the code.. ✌️✌️✌️✌️
26th Oct 2017, 7:06 PM
Vishal Sharma
Vishal Sharma - avatar
+ 9
Make effort
28th Oct 2017, 6:41 AM
Bomi - avatar
+ 8
I usually read articles about programming such as how does the code/module works, what library should I use, the best way to build somethin' (depend to my project), question about some cases that I probably get someday, so on. when I'm stuck, I ask in forums
23rd Oct 2017, 12:13 PM
Nurul Uhkrowi
Nurul Uhkrowi - avatar
+ 8
You gotta experiment!
23rd Oct 2017, 1:31 PM
Glitched - avatar
+ 8
What I have come to realize with larger projects, is that you should definitely plan your moves out and write them down before you do anything. For smaller projects it may seem redundant, but another trait that a lot of programmers posses, is definitely a difficulty to stay on track. There's so many times I have seen great programmers, just get stuck up on the details, and get lost in them. Obviously it is important for you to pay attention to detail, but if you're stuck on something for over 5 minutes, you're probably going to be stuck on it for the next 30 minutes to an hour. That's another great hint for a beginning programmer. Work on your projects dynamically, because it really helps your innovation and prevents getting frustrated over a minor details.
24th Oct 2017, 1:39 PM
eRosz - avatar