Blog Home  Home Feed your aggregator (RSS 2.0)  
Software Code Help
Blog
 
# Friday, January 22, 2010

Note: - This is an interview question where the interviewer wants to know why you have chosen XML. Remember XML was meant to exchange data between two entities as you can define your user friendly tags with ease. In real world scenarios XML is meant to exchange data. For instance you have two applications who want to exchange information. But because they work in two complete opposite technologies it’s difficult to do it technically. For instance one application is made in JAVA and the other in .NET. But both languages understand XML so one of the applications will spit XML file which will be consumed and parsed by other applications You can give a scenario of two applications which are working separately and how you chose XML as the data transport medium.

Friday, January 22, 2010 5:24:34 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   XML Interview Question  | 

No, they both go together one is for describing data while other is for displaying data.

Friday, January 22, 2010 5:23:55 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   XML Interview Question  | 

XML describes data while HTML describes how the data should be displayed. So HTML is about displaying information while XML is about describing information.

Friday, January 22, 2010 5:22:08 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   XML Interview Question  | 

Yes, they are case sensitive.

Friday, January 22, 2010 5:21:37 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   XML Interview Question  | 

No, every tag in XML which is opened should have a closing tag.

Friday, January 22, 2010 5:21:13 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   XML Interview Question  | 

XML (Extensible markup language) is all about describing data. Below is a XML which describes invoice data.

<?xml version="1.0" encoding="utf-8"?>
<
Product>
   <
productname>Shoes</productname>
   <
qty>12</qty>
   <
totalcost>100</totalcost>
   <
discount>10</discount>
</
Product>

An XML tag is not something predefined but it is something you have to define according to your needs. For instance in the above example of invoice all tags are defined according to business needs. The XML document is self explanatory, any one can easily understand looking at the XML data what exactly it means.

Friday, January 22, 2010 5:20:13 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   XML Interview Question  | 
# Wednesday, January 20, 2010

In software engineering (or computer science), a design pattern is a general repeatable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved. Algorithms are not thought of as design patterns, since they solve computational problems rather than design problems.

 

Design patterns can be classified in terms of the underlying problem they solve.

 

 

  Creational Patterns -- concern the process of object creation.

  Abstract Factory

Provide an interface for creating families of related or dependent objects without specifying their concrete classes.

 

 

  Builder

 Separates the construction of a complex object from its representation so that several different representations can be created, depending on the needs of the program.

 

  Factory Method

Define an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation

 

  Prototype

The Prototype pattern starts with an instantiated class and copies or clones it to make new instances. These instances can then be further tailored using their public methods.

 

  Singleton

The Singleton pattern is a class of which there can be no more than one instance. It provides a single global point of access to that instance.

 

 

  Structural Patterns -- describe how classes and objects can be combined to form larger structures.

  Adapter

Convert the interface of a class into another interface clients expect.

Adapter lets classes work together that couldn't otherwise because of incompatible interfaces.

 

  Bridge

Decouple an abstraction from its implementation so that the two can vary independently.

 

  Composite

Compose objects into tree structures to represent part-whole hierarchies. Composite lets clients treat individual objects and Compositions of objects uniformly.

 

  Decorator

Attach additional responsibilities to an object dynamically. Decorators provide a flexible alternative to subclassing for extending functionality.

 

  Facade

Provide a unified interface to a set of interfaces in a subsystem. Façade defines a higher-level interface that makes the subsystem easier to use.

 

  Flyweight

Use sharing to support large numbers of fine-grained objects efficiently.

  Proxy

Provide a surrogate or placeholder for another object to control access

to it.

 

  Behavioral Patterns -- characterize the ways in which classes or objects interact and distribute responsibility

  Chain of Resp.

Avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along the chain until an object handles it.

 

  Command

Encapsulate a request as an object, thereby letting you parameterize clients with different requests, queue or log requests, and support undoable operations.

 

  Interpreter

Given a language, define a representation for its grammar along with an interpreter that uses the representation to interpret sentences in the language.

 

  Iterator

Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation.

 

  Mediator

Define an object that encapsulates how a set of objects interact.

Mediator promotes loose coupling by keeping objects from referring to each other explicitly, and it lets you vary their interaction independently.

 

  Memento

Without violating encapsulation, capture and externalize an object's internal state so that the object can be restored to this state later.

 

  Observer

Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically.

 

  State

Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.

 

  Strategy

Define a family of algorithms, encapsulate each one, and make them interchangeable. Strategy lets the algorithm vary independently from clients that use it.

 

  Template Method

  Define the skeleton of an algorithm in an operation, deferring some steps to subclasses. Template Method lets subclasses redefine certain steps of an algorithm without changing the algorithm's structure.

 

  Visitor

  Represent an operation to be performed on the elements of an object structure. Visitor lets you define a new operation without changing the classes of the elements on which it operates.

 

 

Wednesday, January 20, 2010 6:48:52 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   Interview Question .Net  | 

1MW 1 Microsoft Way
1TBS 1 True Brace Style
21D teach yourself ___ in 21 Days
3COM COMputer, COMmunication, COMpatibility
3Dwm 3-Dimensional Window Manager
3G 3rd Generation
3GIO 3rd Generation Input/Output
3GL 3rd Generation Language
3LD 3rd-Level Domain {IANA}
3NF 3rd Normal Form (databases)
3W World Wide Web
4GL 4th Generation Language
4WCD 4 Wire Conditioned Diphase
A/D Analog/Digital
A/UX Apple UniX
A2A Application TO Application
AA Administrative Authority
AA AntiAliasing
AAA Administration, Authorization, and Authentication (security)
AAA Asp Application Aggregator
AAAI American Association for Artificial Inelligence
AAB All-to-All Broadcast
AAC Advanced Audio Coding
AAEPS Anywhere Anytime Email Proxy Server
AAF Advanced Authoring Format
AAL Atm Abstraction Layer
AAMOF As A Matter Of Fact {chat}
AAP Application Access Point
AARP Appletalk Address Resolution Protocol {Apple}
AART Aggregate Average Response Time
AAS All-to-All Scatter
AAS Auto Area Segmentation
AASE Associate Accredited Systems Engineer {Compaq}
AASP Ascii Asynchronous Support Package
AAT Average Access Time
AAUI Apple Attachment Unit Interface {Apple}
ABA Address Book Archive
ABAP Advanced Business Application Programming
ABC A Bit Cypher
ABC Atanasoff-Berry Computer
ABCPP ABC PreProcessor
ABEL Advanced Boolean Expression Language
ABEND ABnormal END
ABGP
ABI Abstract Binary Interface
ABI Adaptive Brain Interface
ABI Application Binary Interface
ABIOS Advanced Basic Input/Output System
ABIST Automatic Built-In Self Test
ABLE Adaptive Battery Life Extender
ABM Anything But Microsoft
ABM Asynchronous Balanced Mode
ABNF Augmented Backus Normal Form
ABNF Augmented Backus-Naur Form
ABR Area Border Router
ABR Auto Band Rate
ABR Available Bit Rate
.
.
.
And retrieve the complete list fromt the attached Word document.

The definitive Acronym list.doc (1.06 MB)

Wednesday, January 20, 2010 5:19:02 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   General  | 
# Monday, January 18, 2010

TYPES OF QUESTIONS
1. Close-ended questions. These questions may sometimes be helpful when an interviewer(s) wants to know certain information at the onset or needs to determine specific kinds of knowledge. Example: "Could you name the five specific applications involved in...?"
2. Probing questions. These questions allow the interviewer(s) to delve deeper for needed information. Example: "Why?", "What caused that to happen?", or "Under what circumstances did that occur?"
3. Hypothetical questions. Hypothetical situations based on specific job-related facts are presented to the applicant for solutions. Example: "What would you do if..", "How would you handle..."
4. Loaded questions. These questions force an applicant to choose between two undesirable alternatives. The most effective way to employ a loaded question is to recall a real-life situation where two divergent approaches were both carefully considered, then frame the situation as a question starting with, "What would be your approach to a situation where...".
5. Leading questions. The interviewer(s) sets up the question so that the applicant provides the desired response. When leading questions are asked, the interviewer cannot hope to learn anything about the applicant.
6. Open-ended questions. These are the most effective questions, yield the greatest amount of information, and allow the applicant latitude in responding. Example: "What did you like about your last job?"
Examples of open-ended effective probing:
1. What are/were the three main responsibilities in your current/last position? Which responsibilities do/did you enjoy the most? Why?
2. Of the three main responsibilities, which do/did you enjoy the least? Why?
3. Describe your supervisor's management style. Did/Do you like his or her style of management? Why or why not?
4. Describe your particular style of management, or the style of management you would choose if you were a manager.
5. In the past have you worked in a team environment or independently? Which did you prefer and why?
6. What amount of hours do you/ did you put in at your current/last position? How did you feel about working those hours? 
7. What are three of your strongest work related qualities and how were you able to demonstrate these on your job?
8. What are three areas, with regard to your work, that you would like the opportunity to develop?
9. Why did you/are you leave/leaving your last/present position?
10. Of all the jobs you've held, which one did you like the most and why?
11. What major problems have you encountered so far in your professional life and how did you deal with them?
12. What have you learned from your mistakes?
13. How do you react to pressure?
14. What types of decisions are most difficult for you?
15. How have your prior experiences and education prepared you for this job?
16. What has been your biggest work-related frustration to date? How did you handle the situation?
17. Have you ever supervised anyone in a work setting? Have you ever hired or fired anyone?
18. What experience do you have in this field? How have you prepared yourself to switch fields?
19. How have you influenced productivity and results in your previous work experiences?
20. How have you prepared yourself to assume the challenges of this position?
21. How do your current skills apply to this position?
22. In what ways do you expect your relationships with current peers to change? How will you manage this shift?
Repeated Questions break rehearsed answers
1. What did you like about your previous job/manager?
2. What else did you like about your previous job/manager?

Monday, January 18, 2010 8:35:21 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   General  | 

In some cases, using view state is not feasible. The alternative for view state is session state. Session state is employed under the following situations:

o        Large amounts of data - View state tends to increase the size of both the HTML page sent to the browser and the size of form posted back. Hence session state is used.

o        Secure data - Though the view state data is encoded and may be encrypted, it is better and secure if no sensitive data is sent to the client. Thus, session state is a more secure option.

o        Problems in serializing of objects into view state - View state is efficient for a small set of data. Other types like DataSet are slower and can generate a very large view state.

Monday, January 18, 2010 6:02:46 AM (GMT Standard Time, UTC+00:00)  #    Comments [0]   Interview Question ASP.NET  | 
Copyright © 2010 SoftwareCodeHelp. All rights reserved.
DasBlog 'Portal' theme by Johnny Hughes.
Pick a theme: