#beginners
17 posts

Hard truths for new software developers

You don’t need to reinvent the wheel to make a difference. In the early years of your career, aim to learn about others’ thought processes and why things are being done the way they are.
Read more

Hard truths for new software developers

  • Accept that you don’t know everything, that tech knowledge is competitive and that you have to keep working and learning to stay relevant throughout your career.
  • Acknowledge that social and soft skills matter as much as tech knowledge. You will need to hold mature human conversations that solve human problems to grow through your career.
  • You don’t need to reinvent the wheel to make a difference. In the early years of your career, aim to learn about others’ thought processes and why things are being done the way they are.
  • You will not always get the help you need, so seek out a mentor you can trust, who is also invested in your success and with a 5-10 years’ experience gap.
  • Your goal in the workforce is not just your success but that of the product. So assume that in interviews you are being evaluated not for accuracy but for brainstorming human factors that can affect the product’s success and learn to test for them.

Full post here, 9 mins read

Ways to stay motivated while learning to code

Aim for small incremental improvements. Look at the bigger picture of what you're enabling.
Read more

Ways to stay motivated while learning to code

  • You are going to spend a lot of time finding & fixing bugs. When you solve a problem completely, treat yourself.
  • Don’t learn to code - code to learn. Aim for small incremental improvements.
  • Amplify the positive, not negative. Don’t give in to the impostor syndrome. Learn to keep moving in spite of it.
  • Always look at the bigger picture of what you're enabling. Find and frame the reasons why you love your job.
  • Develop a hobby that gets your blood flowing, literally. Physical exercise helps a lot in staying motivated and focused!

Full post here, 14 mins read

These four ‘clean code’ tips will dramatically improve your engineering team’s productivity

‘If it isn’t tested, it’s broken’, so write lots of tests, especially unit tests. Code not covered by a test gets invisibly broken until customers spot the bug.
Read more

These four ‘clean code’ tips will dramatically improve your engineering team’s productivity

Top strategies based on Robert Martin’s Clean Code:

  • ‘If it isn’t tested, it’s broken’, so write lots of tests, especially unit tests. Code not covered by a test gets invisibly broken until customers spot the bug.
  • Choose meaningful, short, precise names for variables, classes and functions and make it easy to find files by name. In case of conflict, choose precision over brevity.
  • Keep classes and functions small - four lines per function and 100 lines per class at most - and make them obey the single responsibility principle. This will help with documenting code better as you will have lots of well-named sub-functions.
  • Ensure functions have no side effects (such as modifying an input argument), and specify this explicitly in the function contracts if possible (such as passing in native types or objects that have no setters).

Full post here, 7 mins read

Stop writing crap code

Stop using else statements as your defaults. Make your code more descriptive. Use built-in functionality.
Read more

Stop writing crap code

  • Stop using else statements as your defaults. As code grows, logic gets complicated and these else statements come to bite you back while debugging code 6-12 months later.
  • Take the time to find & use built-in functionality of the language you are using. It will save your code from bloating.
  • Each function should have just one job to be done. Don’t hide your logic inside functions.
  • Make your code more descriptive by naming things properly, by adding code comments, etc.

Full post here, 4 mins read

How to be a rock star developer

Write utility code that can be used by all. Focus on your work integrity, adaptability and the desire to do excellent work.
Read more

How to be a rock star developer

  • Write utility code that can be used by all and collaborate with other developers on projects beyond your scope of work.
  • Don’t give in to FOMO. Spend time doing the essential work that gets you real results.
  • At crunch times, rise to the occasion with a leadership mindset to rally, organize and collaborate.
  • Try to be essential but not indispensable. Indispensability eventually leads to burnout.
  • Focus on your work integrity, adaptability and the desire to do excellent work.

Full post here, 5 mins read