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
-
chadd1746317yA whiteboard and a flow chart. Map out the logic in your mind before you ever touch the code. Once you have a logic map, write pseudocode. Then find the syntax of your language, translate, and debug. This gets me unstuck nearly every time.
-
For me I solved it by mimicking apps, so that I never have to stop and say: What to do next?
Then when I got the hang of it I started making my own -
stian67yFind one thing you want to do or create and do that regardless of how difficult and out of reach it may be.
Break it down into chunks and as long as you want to do it and you stay disciplined it's a fantastic way to learn. -
shdw9497yBack in the days one used to start with the backend code and then form the frontend afterwards. This way the frontend always depended on the backend. A more modern approach is to design a functioning mockup first and then use it as a reference for your backend code. You will often be able to understand your architecture much better by knowing exactly what it is used for.
-
Output first then input. As in visualize very clearly what you want to have done then work backwards on how that needs to be accomplished. Break it down into tiny pieces and test each step along the way.
Need advice. I've constantly been the type of person who cannot master any programming language because I struggle with knowing "what to do/type next". If you had this problem and fixed it, how?
undefined