Question

Scenario Please read this scenario and job description carefully. You are involved in the prestigious but often challenging Google recruitment process. As part of this process you are required to respond to several questions and activities. All your answers must address the context of this scenario and the information given in the individual questions

. Job description - Software development professional at Google There's no such thing as “a normal day" at Google. We work to create and maintain the safest operating environment for Google's users and developers. Users come first at Google! As part of your work at Google, on any day you might be exposed to the full suite of Google products. You will be working on some exciting new products at Google, such as Google Digital Garage, our online learning platform. You will also be working across a growing Internet of Things (IoT) portfolio. You will also work as part of our Advertising and Commerce team: we believe that ads and commercial information can be highly useful to our users if that information is relevant to what our users wish to find or do. Advertisers worldwide use Google Ads to promote their products; publishers use AdSense to serve relevant ads on their website; and business around the world use our products (like Google Shopping, and Google Wallet) to support their online businesses and bring users into their offline stores. We are constantly innovating to deliver the most effective advertising and commerce opportunities of tomorrow. This is “hands-on” work with other systems and security engineers, to proactively identify and fix bugs, flaws and vulnerabilities in our software products. You will be placed in a specialist team where you will focus on the creation of software product development plans, software design reviews, and software development testing design across various Google products. In this role, you will often be analysing software designs and implementations from a user experience (UX) perspective and working to cultivate software development best practices across the company. You will develop solutions to help mitigate software vulnerabilities and promote excellent design and usability for users across Google products. You will work closely with other software engineers, programmers, product managers, legal and policy teams to build new features. The team are advocates of Agile software development but are also versatile enough to work with more traditional development approaches across the organisation and with other partners.

question 5

Below are two examples of basic formatting of Javadoc blocks. A simple single-line format and a multiple line format. The single-line format may be substituted when the entirety of the Javadoc block (including comment markers) can fit on a single line.

A single-line example: /** An especially short bit of Javadoc.

*/ A multiple line example:

/** * Multiple lines of Javadoc text are written here

, * wrapped normally...

*/ public int method(String p1) { ... }

Below is an extract of Google’s automatic documentation generation guides on Javadocs:

Any of the standard "block tags" that are used appear in the order @param, @return, @throws, @deprecated, and these four types never appear with an empty description.

Your Google recruiter asks you - is it possible to use these tags in a simple single-line Javadoc format? Explain why this is or is not possible.

Answer 1

5.

Yes it is possible to use the tags like the  @param, @return, @throws, @deprecated in a simple single-line Javadoc format because you can continue the description of line in a new line with the use of * character but there is no limitation that it cannot be used with the single line javadoc format , but we simply need to ensure that code does not overflow the line and identation is proper , using these tags in single line can overflow the line and cause unncessary course of action in the program.