Skip to main content

How can I keep my code in mind?


Many newcomers ask this query. Do programmers memorize everything? Do they memorize the entire documentation and programming language? Do I have to remember every detail to qualify as a professional developer? There is a resounding NO to each of these. The goal will never be achieved by memorization of the code.

Today, almost every piece of information can be looked up directly from a computer or smartphone. The most crucial ideas will survive in your head because you apply them repeatedly, while the more enigmatic ideas will be permanently preserved online. Every time you need them, just a fast Google search.

A developer's most frequently utilized resource is.... google.com

Good programmers don't waste time trying to learn everything by heart. They do a good job of understanding the topics, reading the documentation, and correctly using Google to fill in the blanks.

There will never be a time in programming where you can say, "I have learnt and mastered everything" in a given programming language. But there will come a time when you'll be at ease. You won't feel anxious anymore. You will feel confident searching it up and figuring it out if something new appears. All you need to do is keep learning and working on your skills.

You will recall some code because you are a developer. But it's not because you make a conscious effort to learn the code that you can recall it. It has happened thanks to continuous practice. We have repeatedly practiced writing the same code. Because of this, we are able to write various portions of our code without even thinking about them.

You should concentrate more on constructing projects rather than trying to learn more things by heart. Instead of memorizing codes, use project-based learning. You need to be exposed to something repeatedly if you want to learn it. When you build anything from nothing, you are referred to as a programmer. only with the aid of docs, Stack Overflow, and Google.

“I don't need to know everything, I just need to know where to find it”
-Albert Einstein




Comments

Popular posts from this blog

States, Initial state, Successor function, Action, Goal test, and Path cost to formulate 8-Queens problem.

asked by MU in Nov-2019 examination The 8-Queens problem can be defined as follows :   Place 8 queens on a (8 by 8) chess board such that none of the queen attack any of other. States: Any arrangement of 0 to 8 queens on the board. Initial State: No queen on the board. Successor Function: Add a queen to an empty field on the board. Action: Placing a queen on the board. Goal Test: 8 queens on the board such that no queen attack another. Path Cost: 0 (We are only interested in solution). Theory: This problem can be solved by searching for a solution. This formulation as a search problem can be improved when we realize that, in any solution, there must be exactly one queen in each of the column. Thus, the possible action can be restricted to placing a queen in the next column that does not yet contain a queen. This reduces the branching factor from (initially) 64 to 8. Furthermost, we need to consider only those rows in the next column that are not already attacked by a queen that was pre

Utility-Based Agent

asked by MU in Nov-2019 & Apr-2019 examination     The agents which are developed having their end users as building blocks are called utility-based agents . When there are multiple possible alternatives, then to decide which one is best, utility-based agents are used. They choose actions based on performance (utility) for each state. These agents are similar to goal-based agents but provide an extra component of utility measurement which makes them different by providing a measure of success at a given state. Utility-based agents act based not only on goals but also the best way to achieve the goal. The utility function maps each state to a real number to check how efficiently each action achieves the goal. Agent's happiness should be taken into consideration. Utility describes how "happy" the agent is. 

Quality Assurance (QA) in Software Testing

asked by MU in Nov-2019 examination Quality Assurance (QA) : In Software Testing, Quality Assurance is described as a technique for ensuring the quality of software product's or service's given to client by a company. Any systematic process of verifying whether a product or service fulfills stated requirement's is known as Quality Assurance. Quality Assurance is concerned with making the software development process more efficient and effective in accordance with the quality standards established for software product's. Quality assurance is a proactive procedure that identifies strategies to avoid bugs in the software development process. A Quality Assurance System is designed to boost consumers trust and credibility while also enhancing work procedure's and efficiency allowing a company to compete more effectively. The ISO is a driving force behind Quality Assurance Methods and the mapping of the Quality Assurance Processes. Quality Assurance is frequently used in