Tips for people new to programming

1. Start counting from zero
2. Trees are upside down, root's probably at the top
3. Warnings are usual, go rogue!

What more? 😂

  • 71
    4. Turn on show hidden files.
  • 53
    5. Clouds are other's computers
  • 46
    6. Don't be afraid to use the terminal/console: now you have a new friend.
  • 54
    7. Learn git
  • 69
    8. Dark theme everything
  • 83
    Good job contradicting yourself in the first fucking tip
  • 11
    Forget to mark as a joke/meme
  • 20
    12. Use vim AND an IDE
  • 3
    Where's "Hello World!"??🤔
  • 20
    13. Fix your warnings, they are there for your benefit...
  • 22
    14. console.log. All. The. Time.
  • 49
    15. If it works on first try then IT'S A TRAP!
  • 21
    16. Always document your work
  • 12
    Different error messages are friend not foe.
  • 17
    17. Triple-check everything.
  • 1
    @N3vR send links to learn using debugger....
    I know only basic usage of debugger and no more....
    Been searching since 2 months but failed to learn more
  • 12
    20: Don't be afraid to dive into lower level languages like C or any Assembly. That knowledge will prove very useful later on!
  • 17
    Learning what to google is 75% of the battle
  • 18
    21. Name your Variables meaningful.
  • 17
    22. Language before Frameworks!
  • 13
    23. If you don't find solution, it's not the end of the world, use StackOverFlow, and make it work!

    24. Code hard, don't hardcode!

    @akashvartak, @kkdev do you want add anything?
  • 12
    @htlr @kkdev @kalex
    25. Unable to solve an issue or bug and getting frustrated? Be patient, take a break for the code, relax and then back to your issue, more often than not you'll now find a good solution to your issue. Basically start with a fresh mind.

    26. Get a fresh perspective on things. If possible, talk to team mates and get suggestions and different ideas.

    27. Dont code for hours a stretch, you are unknowingly draining your brain to the limit. This is unhealthy in the long run.

    28. Every 30-40 minutes, get up and walk around, stretch a bit. Sitting for a while can harm your shoulder muscles and lower back. Learnt it the hard way. 😞
  • 15
    29. Write automated tests for unit and integration testing, at least after the fact.

    30. Try to apply best practises like design prinsiples. DRY (don't repeat yourself), IoC (inversion of control, with dependency injection the big one), at least some SOLID (look it up 😉).

    31. Program against interfaces or contracts, even in JavaScript. Makes your code a hell of a lot easier to change later (i.e. changing from MySQL to DynamoDB or AirTable only affects that specific module, not the rest of the app)

    32. Give back to the community. Help people on StackOverflow (and be nice about it 😉). Found a bug in some documentation or plugin you use? Raise an issue, fork, fix and PR if you are able. The world runs on open source these days.

    33. SSL all the things. Certificates are free, use Let's encrypt if you don't have money.

    34. Hash the damn passwords with a salt.
  • 8
    35. Get a ruber duck or a gipsy slave to share your problems
  • 5
    36. Do proper estimations: Take the ideal estimation, sum that value up with the worst scenario estimation and triple the resulting value for getting a proper estimation (which in fact has a 50% chance to be correct 😉)
  • 0
  • 3
    And unless you're learning python never forget " ; "
  • 3
    37. close the pc sometimes
  • 3
    38. Actually read error messages
  • 2
    39. OTY after work most of the time
  • 5
    40. if your problem seems too complex and hard, get yourself a pen and a sheet o' paper and start laying down your ideias. it actually helps a lot. I find it better to do with lots of drawings and not lots of writing.
  • 3
    41. Serverless isn't Serverless
  • 0
    @Hakash link?
  • 0
  • 1
    @Hakash @bezorp for let's encrypt? just Google it, it was first link for me
Add Comment