A Success Full Interview

Today at the end of the day I feel a sense of achievement. I screwed up in the interview.

Today I realized,
"What u know is not importnat, What is important is what other thinks what U know".
"There is no justificaiton for failure, Faulure can be justified only with success"
"What ever has happened is for the good, What ever is happening is for the good, What ever will happen is for the good"

A few things learned

1, CHAOS - U dont get enough time to think espp with interviewer on the phone & the fact that U try to keep explaning to him what u are doing.

2, Be well prepared to explain what U want to, U donot have enough time to think.

3, Algorithms and Standard Programs. Make sure that u have memorized them or Make sure that U do them once or twice before the interview date

Loat more I can think about, Any way below is alist of resources.

Software Development Recommendations:

Bentley, Jon. Programming Pearls: Second Edition. Addison-Wesley, Inc., 2000.

Box, Don. Essential .Net, Volume I: The Common Language Runtime. Addison-Wesley Professional, 2003.

Brooks, Fredrick. The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley Professional, 1995.

Cormen, T.H., Leiserson, C.E., Reivert, R.L., Stein, Cliff, eds. Introduction to Algorithms. McGraw-Hill, 1990.

Gamma, E., Helm, R., Johnson, R., Vlissides, J., eds. Design Patterns. Elements of Reusable Object-Oriented Software. Addison-Wesley, 1994.

Howard, Michael, LeBlanc, David, eds. Writing Secure Code. Microsoft Press, 2001.

Kernighan, Brian, Pike, Rob, eds. The Practice of Programming. Addison-Wesley, 1999.

McConnell, Steve. Code Complete: A Practical Handbook of Software Construction. Microsoft Press, 1993.

Maguire, Steve. Writing Solid Code: Microsoft’s Techniques for Developing Bug-Free C Programs. Microsoft Press, 1993.

McConnell, Steve. Rapid Development: Taming Wild Software Schedules. Microsoft Press, 1996.

Tanenbaum, Andrew. Modern Operating Systems. 2nd ed. Prentice Hall, 2001.


Testing Recommendations:

Kaner, Cem, Bach, James, and Pettichor, Bret, eds. Lessons Learned in Software Testing. John Wiley & Sons, 2002.

Kaner, Cem, Falk, Jack, & Nguyen, Hung Quoc, eds. Testing Computer Software (2nd Ed.). International Thomson Computer Press, 1993.

Myers, Glenford. The Art of Software Testing. John Wiley and Sons, 1979.
Patton, Ron. Software Testing. SAMS Publishing, 2000.

Sistowicz, Jon, Arell, Ray, eds. Change-Based Test Management: Improving the
Software Validation Process. Intel Press, 2003.

Viega, John, McGraw, Gary, eds. Building Secure Software: How to Avoid Security
Problems the Right Way. Addison-Wesley, 2001.



Online Testing Resources:
http://www.informationweek.com/756/testers.htm
http://www.qacity.com/General+Testing/Techniques/Links/Links.htm
http://www.softwareqatest.com/qatfaq2.html#FAQ2_6
http://www.sqae.com/Test%20Framework.doc
http://www.testingeducation.org/articles/domain_testing_cseet.rtf
http://www.testingeducation.org/articles/scenario_intro_ver4.doc
http://www.testingeducation.org/coursenotes/kaner_cem/ac_200108_blackboxtesting/
http://www.testingcraft.com/techniques.html

Technical Interview Resources:
http://acm.uva.es/problemset/
http://www.acetheinterview.com/ (do a search on “coding”)