+ 6
With programming, do we really need to do some conception work ? Like UML or RUP? Or do just need to master coding ?
if i'm learning coding with sololearn and others courses , do i need to learn conception or for example design patterns ?
8 Answers
+ 4
It's really good to plan ahead and map things out before you do it, for various reasons.
First off, it'll help you go ahead and formulate a design for how you want to create the program, so you can discover and think about things first so you don't have to redo things later. Nothing worse than getting really far and realizing your structure isn't going to support other stuff you need. Whether you're doing it solo or with a team, you need to know what your specifications are for the program before you begin.
Aside from helping you, your flowcharts/pseudocode is going to really help the people on your team or your clients understand what's going on. It's a lot easier to show people that stuff and them understand than try to explain your code to them line by line.
It takes some time, but it's good to always plan ahead, and it's good habit to have if you end up working for a company. Same with making sure your code goes by some form of common standards. It's worth mentioning that commenting/documentation is equally as important as your code, so get in a habit of always doing that too. Helps you out too when you revisit something you haven't touched in awhile.
For myself, I get bored when I'm always doing just one thing, so I learn various things at the same time, kinda like if you were in school. It helps me not get burnt out on one thing, and most things seem to compliment one another in some way or another.
Anyways, best of luck to ya. In my opinion, learn any and everything you can, it only makes you better.
+ 8
Thanks very Much @Netkos
+ 7
I'm just beginning coding and i would like to learn best practicices .
+ 6
Of course m'y objectif is large Project. but for now i'm going slowly
+ 6
Thank you very Much @Schindlabua
+ 3
like i said, for larger projects yes, for small ones nobody bothers.
Stick with learning a language first tho.
+ 2
for larger project it helps, except if you want to code everything 10 times
+ 2
Never needed UML for personal stuff, but I hear architect people will use it in big projects so us coding monkeys need to at least be able to read it.
Design patterns are mostly a Java thing but theres some you will come across everywhere.
I'm sure you'll pick either of those two things up as you learn more and as you need it.