Edoreal: The Learning Community

What is the output of this program?;

#include <studio.h>

int main()
{
  int a=10, b=20, c=30;
  if (c>b>a)
  {
     printf("TRUE");
   }
   else
   {
     printf("FALSE");
   }
   getchar();
   return 0;
}

a) TRUE   b)FALSE   c)error   d)no output

For 1st year engineering students;

Remember that you are in a war zone. Every year on an average 15 lakh students complete their graduation, but the availability of jobs is very minuscule.
4 years is a huge time. Newton invented calculus in summer holidays, of course copied from Indian mathematicians. The quality of your life will depend on how you utilize these 4 years.
Choose a career that you are interested in, and learn everything about that in these 4 years, so that the moment you complete graduation you should be ready for a job.
Connect with mentors, some senior engineers related to your interest, and some great personalities on social media.
If you love coding, choose any programming language and create real time projects.
Join a group who are having the same interests as you and discuss what you learn with them.
Teach what you learn, so that you can improve your understanding.
Set weekly goals, complete and celebrate.
Don’t follow the crowd. Your college culture & environment may not be that supportive for your growth. You are on your own. Just Focus on your goals.
Learn communication skills, management skills, leadership skills, a new language, personality development, life skills, economics.
Read books, meditate, learn to tame your mind, spend time with yourself.
Exercise, eat healthy and be healthy.
Know about startups and try to start your own startup.
All the development in engineering and science was once started in India by the great vedic rishis. Bring the lost glory by becoming a scientist. Research on each topic you learn.

Engineering is not only a study of 45 subjects but it is moral study of intellectual life.

have you wondered how electric rice cookers know when to stop cooking?;

If you have wondered how electric rice cookers know when to stop cooking, the engineering behind that is some of the most minimalist brilliance I’ve seen, brilliance that keeps the cost of these appliances down to ridiculously cheap levels.

So 2 high school physics concepts to revise before we understand this
1. Latent heat of water - you can raise the temp of water pretty quickly to close to 100C but then it takes extra heat to actually get past 100 because of the energy required to actually turn water into vapour

So you can observe this by bringing some water to a boil and checking its temperature. It will rise to 95-96 at a reasonable pace and then slow down because as long as there is liquid water left in the vessel, the temp can’t go above 100C.

The second concept is the Curie temperature - some magnetic materials lose their magnetism at high temperatures, and electric cookers use an alloy whose curie temp is just above the boiling point of water.

So you combine these ideas and use a magnet made of this alloy connected to a spring and what happens is that the moment all the water has been absorbed by the rice, it’s temperature will start going above 100C (because of concept number 1)

And the moment that happens, our alloy loses magnetism and plops back down disconnecting the heating element from the vessel. Job done. As always, no category of engineers makes me drop my jaw as regularly as electrical engineers.

Advise to first year engineering students;

Brace yourself, this is going to be a biggie.
The next 4 years of your life will change your thinking, perspective, outlook, in short it will frame your personality to a large extent. Though you'd have heard this, i want to say this again Don't waste time.
I will tell you my experience and in the process try to answer yer questions. Being from an Electronics background, i will give you more examples from this.

1. First and Foremost, Love what you do. If you don't like Engineering, look for your passion, find it, go after it. Do not become one in the crowd, and just take it up for the heck of it. Make sure you have a real interest for Engineering.

2. Try to forget about marks. Instead learn the subject. I know this is nigh impossible, especially in a place like India, but try. Instead of cramming up a week before the exams, make an honest effort to LEARN what subject you have taken. Often teachers might be demotivating not encouraging your own answers, and insisting on answers, derivations from the textbook, but i have felt happier doing it my way though i ended up with a few lesser marks.

3. Get Hands on experience. I emphasize on this point as much as i can. Be it a project, or a mini project, or competitions, don't be limited to reading and studying Get yours hands dirty and do something. The learning will be much much more than what any textbook has to offer. I would recommend you to get a few like minded friends and enroll yourselves in Fests. This way you will actually make something, and there are cash prizes, which can be a big motivational factor :-P

4. By the end of your 3rd year, make sure you have a clear long term goal. Be it GRE, GATE or CAT. By then you should have made up yer mind as to what you want to do post Engineering. Don't try to gamble by taking up all of them and going with the best result. Make up yer mind as to what you want and go for it.

5. Enjoy yourself. This i guess should actually be point number 1. Whatever you do, make sure you have fun. I guess you will never be satisfied with what you've done, no matter how much it is. So be it studies, academia or otherwise make sure you have your share of fun.

6. Be an integral part of the College. Involve yourself in all activities throughout your engineering. Don't miss any event unless you really have to. Join as many clubs as you can, and participate actively in all, be it cultural or technical.

I think this would come under general advice. Now to answer your questions

1. Refer point 4. Don't try to go for everything.

Preparing for GRE=/= Preparing for Gate=/=Preparing for CAT

You cannot prepare for 1 and say you'll give the other. You should know what you want and go for it.
Usually people give their GRE exams during the vacations between 3rd and 4th year, or latest by midst of 7th semester. This in order to head out directly after their baccalaureate. Likewise with CAT. Held during October and November, people take it in their 7th semester. Gate is held in the month of February.

2. Most students end with an internship after 3rd year. This is because by then they know sufficient stuff and can apply to places they want to. Some apply even after their 2nd year, to places like DRDO, HAL, ISRO. But getting an internship may not be very easy after second year. If you want an internship at a company, simple you write to them and apply. Or you can find out if you know somebody in the company and they will put you in contact with the right people. If you want to go for a research internship, you will have to go meet the professors personally and speak to them. Your college will have tie ups with companies, which you will have to find out.

3. Presenting a paper is not a big deal. Presenting a paper at the RIGHT place is. There are national conferences and International conferences. Go for the reputed ones if you're into solid research. If you have a paper at an international conference, people at your job may not recognize it's potential. It will definitely look good on yer CV if you have a paper published.

4. Decide if you want to get into a university or a company. It's not the same. If you're looking for a technical program (MS, ME, Mtech), they care more about Research. If you're looking for an MBA or a job they look at a well balanced profile. Once you make this decision, things will become a lot more clear. You can do these to look good on yer CV -
a. Make a lot of projects. Develop CO-CURRICULAR activities, more than extra-curricular activities.
b. Getting an internship at a company will help you get a job in THAT company.
c. Try doing some social work, and social service.
d. Organize workshops, fests, talks etc.

I guess that pretty much wraps it up. Hope I've covered what you were looking for.

Hey Freshers, This is what you should know before starting your college life:;

1. You should focus on building your skills

You are not paying the tuition fee for partying/enjoying/making friends.

Although they are necessary, but don't forget about the endgame.

2. Try something new

Do what you always wanted to do during your school life.

Try Dancing.
Try Singing.
Learn a new instrument.
In short, try to learn a new skill.

It will help you build your personality and gain confidence.

3. Don't let your old hobbies die.

Your hobbies define who you are.
They differentiates you from the others.

4. Focus on personality development.

Trust me, anyone can get the "college education" at home.

The only thing that college is helpful for, is personality development.

Learn social skills, learn Soft-Skills (google it)

5. Know that you are not going to be spoon-fed.

School is not Equal to College.

You are gonna have to do everything on your own.

6. Your friend circle will define who you'll become.

Make friends with people who have the same goals and aspirations as you.

7. Maintain a CGPA >= 8

It will ensure that you can sit in every placement drive.

8. Start coding from your first year itself.

Don't wait for your college.
Don't wait for your friends.

Start Coding, Make Projects, Find Internships.

9. Maintain a balance between College exams, friends and skill building.

10. Build a good relationship with professors.

Don't mess with them to look cool in front of the classmates.

11. Understand that the curriculum is obsolete.

YOU WILL HAVE TO LEARN THE NEW AND NECESSARY STUFF YOURSELF.

12. Start attending workshops/meetups/hackathons from the first year itself.

14. Try to stay away from drugs/alcohol/smoking

People will try to convince you.

It is up to your will power to not come into their influence.

My theory: Say no to first time

Need to prepare for a Software Engineering coding interview? Here's the proven, repeatable system to prepare for a technical interview I've used to get into YC startup as a front-end developer.;

You'll be asked five groups of questions, no matter what position you will be applying for:

• Algorithms
• Data Structures
• Coding problems
• Basic computer science knowledge
• Domain-specific knowledge

1️⃣ Algorithms

Here is the list of algorithms you could be asked:

• Sorting algorithms: both comparison sorting and non-comparison sorting.

?
• Tree traversals: just memorize all of these inorder, preorder, postorder, level order.
• All the prefix-tree searches.

?
• Traversals - Dijkstra's, A*, BFS, DFS: know the difference between DFS and BFS when would you use one over the other and why. Also, make sure that you can code recursively and use your own stack/queue.

Interviewers will probably ask you to find the complexity of each algorithm. So learn what is the Big-O and make sure you can find the complexity of insert/delete/lookup/any other operation for each of these algorithms.

Here’s the great resource to prepare for algorithm questions:

https://t.co/Ycze8EMUWb

2️⃣ Data Structures

Data Structures come up in technical interviews in two ways.

1. Coding questions. For example, “What data structure would you choose to design a graph database?”

2. Comparison question. For example, "Why would you use X over Y in situation Z?"

Here is the list of data structures you could be asked in the interview:

• Heap

• Array

• Linked List

• Hash Table

• Stack/Queue

?

• Linked Hash Map

• Directed/Undirected/Weighted Graphs

• Trees (Tree, Binary Tree, Binary Search Tree, Red-Black Tree, etc. Learn as many as you can)

Here’s how to learn them:

1. Go to Wikipedia and read the whole page of each of these.

2. Write your own data structures with the language you’ll use in an interview.

3️⃣ Coding Problems

When you asked a coding question you should do this:

1. Organize your thoughts

2. Figure out the entire solution

3. Validate your solution with the interviewer

Before you start coding:

1. Make sure you understand the problem. Don’t hesitate to ask questions.

2. Make a high abstract plan of how you gonna solve it before jumping into coding

While you are coding:

1. Explain your thought process to your interviewer as you code

2. Break the problem down and define abstractions, into manageable sub-problems

Once you have a solution:

1. Think about edge cases.

2. Make sure your solution works on all edge cases you can think of.

4️⃣ Computer Science Fundamentals

If you have trouble answering what OOP is, how RAM works, what’s bits and bytes, how the internet works, and any other fundamental questions, you should reveal your computer science knowledge.

These questions are simple if you just know the answers. You don’t need to know deeply how RAM works, just the basics.

To prepare for these questions, google

“computer science fundamentals questions” and learn the answers.

5️⃣ Domain Specific Knowledge

The structure of questions about the knowledge of your field is similar to the questions about computer science.

Questions structure:

Interviewer: “What is X”

You: “X is ...”

To prepare for it, Google: “[YOUR LANGUAGE/FRAMEWORK] interview questions”

Example: “ReactJS interview questions”

Find as much as you can. Paste them into a single file. And try to understand “why the answer to question X is Y”

Complete Guide How To Code Review Best practices from Google, Apple, Facebook, and Amazon;

Let's start with the question:

What’s the end goal of the code review?

The primary purpose of the code review is to make sure that the solution is solving the problem in the best possible way. From the code and product perspective.

But how do you determine if the solution you are reviewing is the best way to solve the problem? In other words, how to code review?

Let’s deep dive into it.

1. No “perfect” code

Before you start reviewing code you need to understand that there is no such thing as “perfect” code, there is only a “balanced” code.

As a reviewer, you should balance out the need to make forward progress compared to the importance of the changes.

Stop seeking perfection.

You don’t just write code for code, you solve a business problem with the code.

If code solves a problem and improves the maintainability, readability, and understandability of the system but it’s not “perfect,” don’t delay it for weeks. Leave a comment on how the author of the changes can improve his code, and give it a green light.

2. Your opinions are not authority

Everyone has their personal opinion on everything: how you should write code, how many hours, why you need to use some text editor and not another, and many others.

We all have different experiences and different backgrounds, but we need to turn them off during the code review.

When you are deciding if the solution you are reviewing is written “good” or “not”, you have to rely on technical facts and standards, not personal preference.

3. Resolving conflicts

I have seen a lot of examples where the reviewer was wrong about how to write code, left a comment about it while code reviewing, and after realizing that he was wrong, still decided to bend his line just not to look stupid that he didn't know something

Code review is not a ring where you need to "win" your opponent. You're one team. You work toward the common goal.

The first thing you should do in the conflict is to come to a consensus.

Better to do it not in the comments on GitHub but in chat/video call, it's much faster.

If both of you can't find a common solution on how to write code, ask your team or technical lead for help.

Don’t sit down on one conflict for days, try to resolve it as quickly as possible.

4. Code quality

On a high level you need to look at two things while code reviewing:

1. Changes solve the problem.
2. Code is well designed.

To do this, create a checklist of what you should pay attention to when reviewing the code and use it on every code review.

Here are my general recommendations on what you should look at:

• Changes do what the developer intended. Everything works as it is needed in the task.

• Changes are not too complex to understand. All members of the team can understand every line of code and can easily maintain this code in the future.

• Author picked good names for everything. Not long and hard to read.

• Author added comments where necessary. Good comments are those that explain why some code exists, and not what code is doing.

• Changes follow the style guide. If you don’t have a style guide in the company you should create one

• Do changes need documentation. If they change the main part of basic or main functionality (build, tests, etc) the author needs to create or update documentation about it

5. Test

Every change must be tested.

Ask the author to add unit, integration, or end-to-end tests as appropriate for the change, if he is not already.

Make sure that tests are not written to test themselves. They must be useful and valid.

6. Comments

First, abstract from your feelings about the person whose code you're reviewing. Always make comments about the code and not a person.

If you see that the author wrote a “bad” code and it triggers your emotions, calm down, and leave your comments on a calm mind.

Also, never ever write comments like “do this”, always explain why the author should make changes and add the source (link to the blog post, documentation) where the person could read more about it.

But don’t write a complete solution to the problem when you explain “why”.

Code review must not take you the whole day. And it’s not your job to fix the changes of another developer. Find a balance between pointing out the problem and providing a direct solution.

7. Be a human

And the last one, be a human.

If you found something nice in the changes, tell the author about it. Code reviews should not be just about mistakes. Give some positive feedback as well. Be a mentor.

GitHub repositories to improve your programming skills.;

1. Free Programming Books

Freely available programming books.

Repo: https://t.co/UoHTMEXBxT

2. Awesome
Awesome lists about all kinds of interesting topics.

Repo: https://t.co/C2jbOLJpmt

3. Coding Interview University

A complete computer science study plan to become a software engineer.

Repo: https://t.co/Y2osXEQkPk

4. Developer Roadmap

Roadmap to becoming a web developer in 2020.

Repo: https://t.co/aLeGg5gvEk

5. Public APIs

A collective list of free APIs for use in software and web development.

Repo: https://t.co/Idwi300p0a

6. Awesome Python

A curated list of awesome Python frameworks, libraries, software, and resources.

Repo: https://t.co/kgmrDEMimv

7. JavaScript Algorithms

Algorithms and data structures implemented in JavaScript with explanations and links to further readings.

Repo: https://t.co/L51LYhkKbs

8. Node Best Practices

The Node.js best practices list.

Repo: https://t.co/oIqzPlTm6l

9. Real World

“The mother of all demo apps” — Exemplary fullstack https://t.co/NsePOJopiC clone powered by React, Angular, Node, Django, and many more.

Repo: https://t.co/OeCLd0v8m3

10. Tech Interview Handbook

Materials to help you rock your next coding interview.

Repo: https://t.co/svK6eZq3Bu

11. Clean Code JavaScript

Clean Code concepts adapted for JavaScript.

Repo: https://t.co/14L3szpPGl

12. Free For Dev

A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev.

Repo: https://t.co/WLcw9TJviF

14. Awesome For Beginners

A list of awesome beginners-friendly projects.

Repo: https://t.co/X7139U7cde

Resources to crush the technical interview.;

1. Coding Interview University

A complete computer science study plan to become a software engineer.

Link: https://t.co/Y2osXEQkPk

2. JavaScript Algorithms

Algorithms and data structures implemented in JavaScript with explanations and links to further readings

Link: https://t.co/L51LYhkKbs

3. Tech Interview Handbook

Materials to help you rock your next coding interview

Link: https://t.co/a0t7QmFDZJ

4. OG AWS

Amazon Web Services — a practical guide

Link: https://t.co/r5Z1BjTXeV

5. Javascript Questions

A long list of (advanced) JavaScript questions, and their explanations.

Link: https://t.co/yFsv2yNT1A

6. Interview

Everything you need to prepare for your technical interview.

Link: https://t.co/YWJEzduyzT

7. Awesome Interviews

A curated awesome list of lists of interview questions.

Link: https://t.co/cNdcpNFMa9

8. Interviews

Everything you need to know to get the job.

Link: https://t.co/U6KCpElAHy

9. Coding Interviews

This repository contains coding interviews that I have encountered in company interviews.

Link: https://t.co/fUPdUGBtfP

10. Reverse interview

Questions to ask the company during your interview.

Link: https://t.co/qiLx6k5TUM

11. Front end Interview Questions

Help the front End community to rock interview.

Link: https://t.co/mlkJDzoEgA

12. Back-End Developer Interview Questions

A list of back-end related questions you can be inspired from to interview potential candidates, test yourself or completely ignore.

Link: https://t.co/6Xo4Xg9HGS

List of Top Programming Interview Questions.;

Strings

- How do you check if a string contains only digits?

- How can you a given string be reversed?

- How do you find the first non-repeated character?

- How do you find duplicate characters in strings?

Arrays

- How is an array sorted using quicksort?

- How do you reverse an array?

- How do you remove duplicates from an array?

- How do you find the 2nd largest number in an unsorted integer array?

Linked Lists

- How do you find the length of a linked list?

- How do you reverse a linked list?

- How do you find the third node from the end?

- How are duplicate node removed in an unsorted linked list?

Binary Trees

- How are all leaves of a binary tree printed?

- How do you check if a tree is a binary search tree?

- How is a binary search tree implemented?

Sort arrays of 0s, 1s, 2s

Subarray with sum K

Cyclic rotation of array

Two sum

Coin change

Find the only non repeating number in an array

- Explain Async Await and Promises

- Get this object key out of the array of objects and create a new array with it

- Create a function that accepts a string then returns a randomised version of that string

- What react class methods does useEffect replace

#javascript #reactjs

- How do you reverse an array in place in Java?

- How is a binary search tree implemented?

- If you were an exception, what kind of exception would you be?

- How do you prioritize what's on your "Learn Next" list?

Multithreading

- What is multithreading?

- What are the benefits of multi-threaded programming?

- How can we create a Thread in Java?

- When to use Runnable vs Thread in Java?

- What is the difference between start() and run() method of Thread class?

- What is synchronization?

- Sorted array of ints: find two numbers that add up to a target number

- Sorted array: remove duplicates in-place

- Array of integers: get all subsets/permutations

- Linked list: Remove the n-th node from the end

- Linked list: Find its middle node (list size is unknown)

Feeds

Categories