tag:blogger.com,1999:blog-7183516873938699150.post4330640545048148639..comments2013-04-17T19:01:21.735+05:30Comments on BE Project / Early Career: Why work (hard) on a BE Project?Kedar Sovanihttp://www.blogger.com/profile/06720656914623203587noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7183516873938699150.post-53937976930291529342013-04-17T19:01:21.735+05:302013-04-17T19:01:21.735+05:30Arun, Indeed! A lot of good companies do things th...Arun, Indeed! A lot of good companies do things this way: hire after the project is completed. It is actually a very good way to determine the good ones from the bad ones. That way the chances of a bad hire are much lesser and the company has a better control over their hiring decisions because they aren't hiring an year in advance.<br /><br />The other trend is mass-hiring. If a company is determined to hire 50 students from a batch of 120, even the tests and interviews are a farce. <br />Kedar Sovanihttps://www.blogger.com/profile/06720656914623203587noreply@blogger.comtag:blogger.com,1999:blog-7183516873938699150.post-9035329706849125622013-04-16T12:41:33.816+05:302013-04-16T12:41:33.816+05:30Kedar, I couldn't agree more with you. This is...Kedar, I couldn't agree more with you. This is exactly what I have been feeling. Another thing I strongly feel is - placement being done by the industry after the third year is the main reason why most of the students have lost motivation in doing their project seriously. For example, a large company comes and says that only those having more than 60% marks can appear for placement and gives placement to a few. These people now know that all they need is 60 marks in their project - and a job is waiting. Instead, if the companies were to choose based on the final year projects (and not marks - which don't reflect how good or bad a developer is - as you have rightly said), the students would remain motivated. Unfortunately, the HR guys in the large companies have a very short term vision of meeting their own targets - and in the bargain, they are destroying a few generations. Hiring after third year is also detrimental to the industry. Consider a case where a company hires a person based on only marks - without knowing what technology is known to a guy as against a company who requires, let us say, a .Net developer hiring a person who has done a project in .Net. Who would be benefited more? Who would require lesser training to be imparted? Which person would be more happy - the one who is directly put on a client project or who is put on training even after doing B.E.?<br /><br />I think the industry also needs to reflect on this!<br /><br />However, I hope at least some people who read your blog would realize the benefits of doing their B.E. project seriously. Well written.<br /><br />Arun Kadekodi<br />CEO, Soft Corner<br />www.soft-corner.com<br />Arun Kadekodihttp://www.soft-corner.comnoreply@blogger.comtag:blogger.com,1999:blog-7183516873938699150.post-14875232190156633752012-02-14T10:10:38.810+05:302012-02-14T10:10:38.810+05:30This is what the doctor ordered (or should I say t...This is what the doctor ordered (or should I say the engineer ordered?)<br />Students do get ample time to work on their last year projects. They must utilize this time to learn the tools of their trade, to make their hands dirty by dabbling into a real world programming problem.<br /><br />Kedar has done a nice job not only of just pointing the drawbacks but also of giving an outline as to how a willing student can set himself/herself for the task of overcoming these drawbacks.<br /><br />Thanks and regards,<br />-Damodar Kulkarni<br />PUCSD (http://cs.unipune.ac.in/)damodarhttps://www.blogger.com/profile/07093923362446963626noreply@blogger.com