Information Regarding Software Developers In Programmers From East Europe on Software Development Register

Different Programming Languages Are Used Depending On The Purpose Of The Program. COBOL, For Example, Is Commonly Used For Business Applications Which Are Run On Mainframe And Midrange Computers, Whereas Fortran Is Used In Science And Engineering. C++ Is Widely Used For Both Scientific And Business Applications.

For you information - If you own a website that related to software developers you are welcome to participate in our website. Contact us to be participate in the project and join our partner list: Programmers Wiki, Programmers Online Portal, Programmers Central, etc.

Website about Software Developers - online portal of Internet Technology Architecture and Development. Other useful information: Hiring smart software developers is not easy. If you're not careful you might end up hiring a bunch of moronic mandrills, like I did last year. And you don't want that. Trust me. Stand-up meetings are very hard to do..." / Hiring smart software developers is not easy. If you're not careful you might end up hiring a bunch of moronic mandrills, like I did last year. And you don't want that. Trust me. Stand-up meetings are very hard to do in a tree. The key is to ask challenging questions that enable you to distinguish the smart software developers from the moronic mandrills. And to help you with that, I decided to publish my private list of 100 interview questions for software developers . This list covers most of the knowledge areas as defined by the Software Engineering Body of Knowledge . Of course, if you're just looking for brilliant programmers, you may want to limit the topics to Construction , Algorithms , Data Structures and Testing . And if you're looking for architects, you can just consider the questions under the headings Requirements , Functional Design and Technical Design . Hiring smart software developers is not easy. If you're not careful you might end up hiring a bunch of moronic mandrills, like I did last year. And you don't want that. Trust me. Stand-up meetings are very hard to do in a tree. The key is to ask challenging questions that enable you to distinguish the smart software developers from the moronic mandrills. And to help you with that, I decided to publish my private list of 100 interview questions for software developers . This list covers most of the knowledge areas as defined by the Software Engineering Body of Knowledge . Of course, if you're just looking for brilliant programmers, you may want to limit the topics to Construction , Algorithms , Data Structures and Testing . And if you're looking for architects, you can just consider the questions under the headings Requirements , Functional Design and Technical Design . J2EE: EJB, JSP, Servlets, JSF, JSTL, JCA, JMS, JTA, JNDI, JDBC, JMX, RMI, etc. Frameworks: Struts, Hibernate, JPA, iBATIS, JBoss AOP, Spring, JSF, AJAX, GWT, YUI, Flex/Flash, JUnit, and Jakarta common libraries. Integration: Web Services on Axis and WebMethods; as well as the Web Service Standards such as SOAP, WSDL and UDDI.

NOOP.NL: 100 Interview Questions For Software Developers - Hiring smart software developers is not easy. If you're not careful you might end up hiring a bunch of moronic mandrills, like I did last year. And you don't want that. Trust me. Stand-up meetings are very hard to do in a tree. The key is to ask challenging questions that enable you to distinguish the smart software developers from the moronic mandrills. And to help you with that, I decided to publish my private list of 100 interview questions for software developers . This list covers most of the knowledge areas as defined by the Software Engineering Body of Knowledge . Of course, if you're just looking for brilliant programmers, you may want to limit the topics to Construction , Algorithms , Data Structures and Testing . And if you're looking for architects, you can just consider the questions under the headings Requirements , Functional Design and Technical Design . But whatever you do, keep this in mind: For most of the questions in this list there are no right and wrong answers ! My questions are simply starting points for interesting discussions . For example: there is a question about reasons to use static methods vs. singletons . If this triggers your candidate to start a tirade againt both static methods and singletons, there's a good chance you're dealing with a smart software developer! But if the candidate can produce nothing more than a blank stare and this sound , then he might very well be a moronic mandrill. Likewise, there are many correct ways to find out whether a number is a power of 2. But if the candidate suggests using the mod operator, well... you know what I mean. (And if you don't, no problem. Fancy a banana?) NOOP.NL: 100 Interview Questions for Software Developers NOOP.NL Management, Development, Complexity & Social Stuff « Team Members, Be Predictable! | Main | secretGeek: Read It & Beat It » January 13, 2009 100 Interview Questions for Software Developers Requirements Can you name a number of non-functional (or quality) requirements? What is your advice when a customer wants high performance, high usability and high security? Can you name a number of different techniques for specifying requirements? What works best in which case? What is requirements tracing? What is backward tracing vs. forward tracing? Which tools do you like to use for keeping track of requirements? How do you treat changing requirements? Are they good or bad? Why? How do you search and find requirements? What are possible sources? How do you prioritize requirements? Do you know different techniques? Can you name the responsibilities of the user, the customer and the developer in the requirements process? What do you do with requirements that are incomplete or incomprehensible? Functional Design What are metaphors used for in functional design? Can you name some successful examples? How can you reduce the user's perception of waiting when some functions take a lot of time?