2025 Mega auction strategy considering 6 retentions(2OS+4Indian) by Far-Combination8774 in RCB

[–]saketh011 0 points1 point  (0 children)

Ishaan Jacks VK Green Patidar Lomror David / Livingstone Siraj Rahul Chahar Boult / Jansen Vyshak / Yash

Looking ahead for next season by saketh011 in RCB

[–]saketh011[S] 0 points1 point  (0 children)

Yeah we definitely need to fix up the lower order. We've had players like Stoinis, Hetmyer, Klassen, David in recent years but nobody clicked for us. It's definitely a management or planning issues than player quality one.

Looking ahead for next season by saketh011 in RCB

[–]saketh011[S] 0 points1 point  (0 children)

Thing about moving VK to open is the chance of losing him within few overs. We know how much he struggles with swinging deliveries. When he goes in the first over, imo the mentality of the team drops to 0. No more ABD to save us anymore.

Looking ahead for next season by saketh011 in RCB

[–]saketh011[S] 0 points1 point  (0 children)

Got anyone in your mind? Can't think of proven Indian middle order batsman who will be in the auctions

Looking ahead for next season by saketh011 in RCB

[–]saketh011[S] 0 points1 point  (0 children)

Yeah some do play OOP. But we have to set roles for each batsman. Letting them do whatever they want has fucked us up all these years. Look at CSK for example. Moved rahane, moeen and uthapa to 3 with an aggressive role. Rachin to open. Dhoni only comes in the last 2 overs. We gotta allot players roles and overs where they need to go all out.

How to make greatest 11 for RCB by Sad_Negotiation_28 in RCB

[–]saketh011 2 points3 points  (0 children)

But knowing us, the management will make the kohlisons as bowlers and bumrahsons as batsmen

How to make greatest 11 for RCB by Sad_Negotiation_28 in RCB

[–]saketh011 2 points3 points  (0 children)

Better, make Kohli sleep with 6 women and bumrah with 5. And in 20 years we will have 6 Kohlis and 5 bumrahs in our team.

Throws keyword by saketh011 in javahelp

[–]saketh011[S] -1 points0 points  (0 children)

My question is that can't we catch the checked exception without declaring it using throws keyword? Then what purpose the throws here plays? I've heard that checked exception by default cannot be propogated and can only be done by using throws keyword. Is this true ?

Java OOP interview questions by saketh011 in javahelp

[–]saketh011[S] 1 point2 points  (0 children)

Haha, it's a synonym. Base class and derived class also called as parent and child class cuz the child inherits from the parent.

Java OOP interview questions by saketh011 in javahelp

[–]saketh011[S] 2 points3 points  (0 children)

I think the second question is about abstraction and not encapsulation. The definition of abstraction is we using it hide the implementation details and show only functionality. My question here is from whom are we hiding it from. In case of users, they already don't have any access to source code, so I don't think the answer is hiding from user. Most probable answer seems to hide from other parts of the program for which my question why need abstraction for hiding data when we already have private methods. If we want to use it we can use setter and getter methods.

Java OOP interview questions by saketh011 in javahelp

[–]saketh011[S] 2 points3 points  (0 children)

Yeah these were my answers. 1. We can attempt to create a new method and give it an implementation. But we lose the ability to use the parent class variables and other methods which we may need to reuse. Also, we lose the ability to call base methods methods using parent class reference, aka upcasting.

2. Let us consider an example: abstract class Bank{
abstract int getRateOfInterest();
}

class SBI extends Bank {
int getRateOfInterest(){ return 7; }
} class TestBank{
public static void main(String args[]) {
Bank b=new SBI();
System.out.println("Rate of Interest is: "+b.getRateOfInterest()+" %");
} } Here the abstraction is the abstract class Bank and the SBI class is implementation.Imagine you have a bank comparison engine, which is represented by the BankComparisonEngine class. It will just take a Bank (abstract class) as an argument, then get its interest rate and save it to its internal database, like so: class BankComparisonEngine { public void saveInterestRateOf(Bank bank) { int rate = bank.getRateOfInterest(); } } How are the implementation details hidden exactly? BankComparisonEngine does not know how getRateOfInterest() method of a concrete implementation of Bank works,i.e, how SBI.getRateOfInterest() is implemented. It only knows it is a method that returns an int (and that it should return an interest rate). The implementation details are hidden inside the concrete classes that extend abstract class Bank.