Skip to main content

Finding the seat opposite to you in a train.



package ae.naveed;

import java.util.Scanner;

public class SeatingArrangement {

    enum seatPositions {
        WS, MS, AS;
    };

    public static void main(String[] args) {
        Scanner scanner = new Scanner(System.in);
        int testCases = Integer.parseInt(scanner.nextLine());

        int[] seatNumberArray = new int[testCases];

        for (int i = 0; i < testCases; i++) {
            seatNumberArray[i] = scanner.nextInt();
        }

        for (int i = 0; i < testCases; i++) {
            System.out.println(getOppositeSeat(seatNumberArray[i]));
        }
    }

    public static String getOppositeSeat (int seatNumber) {
        int seatNumberFactored = seatNumber % 12;

        switch (seatNumberFactored) {
            case 1:
                return "" + (seatNumber + 11) + " " + seatPositions.WS;
            case 2:
                return "" + (seatNumber + 9) + " " + seatPositions.MS;
            case 3:
                return "" + (seatNumber + 7) + " " + seatPositions.AS;
            case 4:
                return "" + (seatNumber + 5) + " " + seatPositions.AS;
            case 5:
                return "" + (seatNumber + 3) + " " + seatPositions.MS;
            case 6:
                return "" + (seatNumber + 1) + " " + seatPositions.WS;
            case 7:
                return "" + (seatNumber - 1) + " " + seatPositions.WS;
            case 8:
                return "" + (seatNumber - 3) + " " + seatPositions.MS;
            case 9:
                return "" + (seatNumber - 5) + " " + seatPositions.AS;
            case 10:
                return "" + (seatNumber - 7) + " " + seatPositions.AS;
            case 11:
                return "" + (seatNumber - 9) + " " + seatPositions.MS;
        }

        return "" + (seatNumber - 11) + " " + seatPositions.WS;
    }
}

Comments

Popular posts from this blog

@MappedSuperclass vs. @Inheritance

MappedSuperClass must be used to inherit properties, associations, and methods. Entity inheritance must be used when you have an entity, and several sub-entities. You can tell if you need one or the other by answering this questions: is there some other entity in the model which could have an association with the base class? If yes, then the base class is in fact an entity, and you should use entity inheritance. If no, then the base class is in fact a class that contains attributes and methods that are common to several unrelated entities, and you should use a mapped superclass. For example: You can have several kinds of messages: SMS messages, email messages, or phone messages. And a person has a list of messages. You can also have a reminder linked to a message, regardless of the kind of message. In this case, Message is clearly an entity, and entity inheritance must be used. All your domain objects could have a creation date, modification date and ID, and you could thus ...

Some good links

https://www.html5rocks.com/en/tutorials/internals/howbrowserswork/ http://taligarsiel.com/ClientSidePerformance.html -- Client side performance tips https://ariya.io/ https://vertx.io/docs/ -- New exciting Framework, Must read. https://javaee.github.io/ -- Very good resource to see various javaee projects and explore enterprise architecture and design concepts. https://projects.eclipse.org/projects/ee4j -- Lots of interesting open source projects by eclipse http://openjdk.java.net/projects/mlvm/ -- the main project for supporting more dynamic languages to jvm. http://esprima.org/ -- EcmaScript parser http://c2.com/ppr/ and http://hillside.net/ -- Good place to learn patterns http://cr.openjdk.java.net/~briangoetz/lambda/Defender%20Methods%20v4.pdf https://validator.w3.org/nu/ -- This will validate your website css and js https://www.cellstream.com/intranet/reference-reading/faq/216-what-is-2-128.html http://shattered.io/ -- An example of SHA1 collision attack.

String.format or String concat?

I'd suggest that it is better practice to use `String.format()` . The main reason is that `String.format()` can be more easily localised with text loaded from resource files whereas concatenation can't be localised without producing a new executable with different code for each language If you plan on your app being localisable you should also get into the habit of specifying argument positions for your format tokens as well: "Hello %1$s the time is %2$t" This can then be localised and have the name and time tokens swapped without requiring a recompile of the executable to account for the different ordering. With argument positions you can also re-use the same argument without passing it into the function twice: String.format("Hello %1$s, your name is %1$s and the time is %2$t", name, time) Because printf-style format strings are interpreted at runtime, rather than validated by the compiler, they can contain errors that result in the wrong str...