Marie Choco Lava

Lets start with some choc delicacy... 

All you need to have - 
  • 1 Packet of Marie biscuits
  • 4 cups of Milk
  • 4-5 tbsp. Sugar (Grinned it to powder)
  • 3 tbsp. Custard Powder
  • 4 tbsp. Cocoa Powder
  • And grated cashewnet & almond for garnish.
That's it... isn't that cool....!

Lets see the steps:
1. Take 2 cups of milk. Add sugar powder, Cocoa powder and Custard powder. 
2. Mix them well. Be sure to make fine thick liquid. If required, you can use a blender to mix them well.
3. In a vessel, heat 2 cups of milk.
4. When it comes to boil, add the prepared milk mixture.
5. Stir slowly and continuously, else you will end up making a chocolate liquid having lumps.... a big NO NO!!!
6. Once you see thick liquid, remove it from flame.
7. Place biscuits on plate.




8. With a spoon, pour choco liquid on biscuits
9. Top it with one more layer of biscuit.
10. Repeat 8 and 9 step, till u get 4 layers of biscuits (OR whatever height you wish).
11. Lastly sprinkle some sugar all over and garnish it with grated cashwenet and almond.

Your yummy Maria Choco Lava is ready.....

Comments

Post a Comment

Popular posts from this blog

@Overrride annotation introduced in Java1.5

Whenever we have a subclass that implements parent method it is marked with annotation as @Override. This is to make compiler know that the child overrides the method defined or declared in parent. If @Overrride annotation is commented, the subclass will work as it was. But if in future, the signature of parent class changes, the compiler wont ask to implement the method instead it will think subclass has overloaded the method present in base class. If you uncomment @Override annotation, the compiler will throw compile time error as method signature in parent class has changed. Annotation should be used as standard as- It ensures that for any change in method signature of parent class, compiler will ask to change it for the subclasses.    Also it is better to resolve issue in compile time rather than runtime
Read more

Liskov Substitution Principle (LSP)

Subtypes must be substitutable for their base types. This principle supports the below scenario-    Suppose a method takes parent type and perform some operation on it.    And the subtype is not of type - parent but still wrongly inherits the parent.        If the above subtype object is passed to such method, the operation performed will be weird as the method assumes it is suppose to be parent type. Hence, a class should inherit parent only if its of that type. (eg: Square is not Rectangle programmatically as the area is always side^2) 
Read more