Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
1 - You can't study all the languages at once.
2 - practice is the best way to learn any programming language. -
htlr51307yBe a programmer. Try to reach out to as many tech as you can but master a few and be a god in one.
And never ever start with am a python developer or am a node.js developer unless it is necessary for domain specific reasons the other way its like saying u mastered chisel and u are a chisel carpenter. You need to be a carpenter morty, no a fucking jerk who know only how to use a chisel. -
heres mine. imcurrently 14 and ive built several things that are far advanced.
(compilers, NNs, Chess engines)
dont learn while doing, do while learning (might seem equal, but its not)
example:
instead of reading a tutorial on how to Output hello world in cpp,
try assembling the pieces together.
ask google:whats the cpp file architecture, whats Cpps print command, whats cpps main function?
once you know that, and didnt get any positive results, ask google "how to printhello world"
this way, yau are submerged in the stuff -
tkdmatze4407ytop 10 ? thats hard
0 as a developer you will never stop to learn something new
1 most problems are already solved
2 there is a good reason for design patterns
3 naming matters
4 if the method does not fit on the screen, it does not fit in the brain
5 knowing your ide saves you a lot of time
6 there is always more then 1 truth/solution
7 you will spent more time reading code then writing, so make you code readable
8 write enough code to solve you current problem/task, do not try to solve all problems at once
9 just because a framework is hip right now, it does not mean it helps you
10 arrays start a 0 ... obvious -
Ok. ive had a thought on this. not what tips i have, but what tech you NEED to know.
i think, you should know it until next year. (// if a tech is optional only)
//C++ (because back to the roots)
Linux (Much more flexible than windows)
HTML (how else are you gonna create that awesome website? jimdo.com???xD)
Js (has many interesting functional paradigms)
//Java (not a good language, but its nice checking out the crazeOOP side of stuff)
Unit testing (I should learn it too, but im too lazy to)
And most important tech of all: pencil and paper. im not joking. Learn to sketch out problems before doing them...
Sketch out your dependency diagrams, your Class structure, your variable dependency.
It wont help you, but it will. (this sentence will make sentence once it saved your ass) -
0. Learn programming as much as you can by practice
1. Understand the requirement and ask questions. (e.g. I thought OP wanted 10(in binary) advice, and hence I gave. But what if (s)he was talking in other base?
Related Rants
What would be the top 10 things you’d tell a junior developer still in his first year? Hit me
question
csharp