mohanmca

Why do we need to search source-code?

  1. Quickly learn the domain and context of the application
  2. After adding a feature, we should aware if we broke anything (assume you work with code that doesn't have test-case), it helps even to search testcases
  3. Find similar code and ensure you are improving quality of the overall similar code (not just fixing current bug)
  4. Understand how application behaves when there are production issues.

Most often I deal with large inherited code-base in my career, often we need to search similar code or usage of certain variable or a function/class/module. When it is statically typed language to certain extent IDE/compiler helps. But we have to deal with different languages and sometime developers copy/paste for various reason. Searching/grepping code and its usage seems to be very useful for various reasons.

You as a developer, what are all the ways you search source-code before working/fixing feature or bug? Do you use any CLI tools other than grep. I have used OpenGrok, But few times it is not maintained by me or other developers.

Below is my steps.

  1. Read the relevant code, and know certain domain keyword, variable names (inclusive class/method/function)
  2. Use the bitbucket/GitHub/git search
  3. Use the grep
  4. Use the git-grep

Still few times, I end up missing.

Seems like this is (Especially CLI based search) very valuable skill to have. Do you have any tips/tools for other developers?

Need suggestion from polyglot programmers, How do you quickly switch to a programming language that you won't code often?

I sometimes need to switch to few programming languages that I feel not proficient, But at times should do something with that like execute as a script, evaluate interview, manage/refer others code, find the treasure hidden in large code-base. For example, groovy, python, pl/sql, c# or typescript.

Do you have any tested technique to quickly recollect the entire language? hope few others would be in my situation!

Do you have any technique to come up to speed?

I am in need of help to find list of mistakes to avoid and if possible few guidelines to follow while joining a new team as a senior developer.

Below is my draft list

* Be patient and listen, listen and listen without any judgment. There is no better friend than active listening. * No one likes a know-it-all - Be honest, confident and humble * You will still do something embarrassing. And you will survive. You can't improve if you are worried about your mistakes. Don't worry about it! * Observe what everyone is doing. Ask questions. * Be comfortable asking others for help or referencing documentation, Try not-to-figure-out-yourself unless that is expected * Follow Before You Lead, * Be tolerant of practices that are foreign to your established approach. * Mastering established team practices and rituals builds trust. * Automating an existing process is likely to be better received than making an independent decision to replace an existing tool. * Spend some of your personal time masterings and enhancing tools the team uses. * Ensure your output is reviewed by an existing employee before it is rolled out.