Skip to main content

Design Patterns: The art of making TV serials or masala movies

After being tortured to sit through one too many series of never ending serials, here are a few rules or patterns that I had observed:

Design patterns on serials or movies
  • The-Not-Good-as-it-seems Pattern: If it is too good to be true, it is a dream and in real-world, it will happen exactly the opposite
  • The-One-is-not-enough Pattern: One of the primary character will have two wives and will struggle between the two (or more?).
  • Medical-Miracle Pattern: Someone will get amnesia and later will be always be cured.
  • Double-Trouble Pattern: If twins are born, they will get separated to meet again 20 years later. Of-course, there will be scope for impersonation.
  • The-Cryptic-Prophet Pattern: Swamijis, gypsies, sadhus will usually be able to give cryptic clues on what is about to happen next
  • The-Cycle-of-Life Pattern: If a primary actor's family is portrayed as being very rich, chances are they will become poor. Conversely, the family opposing the hero / heroin will have the lifestyle opposite to them.
The art of extending airtime
  • The-Matrix-Bullet-Time Pattern: When the situation becomes tense, you get into slow-motion mode with background accompaniment *after* every statement / action made by the actors.
  • Manic-Mondays Pattern: Friday (for serials that are aired on weekdays) sessions will usually be a cliffhanger, ending just before a pretty tense moment which will usually fizzle out on Mondays.
  • Bored-With-the-Existing-Faces Pattern: When things become too dull, introduce a new set of characters and follow a side storyline
  • The-Forget-Me-Not Pattern: On long running soaps, introduce a recap session that compresses all major moments that had happened earlier which the actor will ruminate
Now a days, a lot of reality shows have made it into our TV channels. Here are a few patters that I have observed here:
  • The-Blunt-in-Your-Face Pattern: The judges make it an effort to be rude while pointing out the participants faults, with closeups of both the judges as well as the participants at the recieving end with again, background accompaniments.
  • The-Let's-Cry-Together Pattern: When a participant or pair is bumped out of the contest, you should watch the emotional drama. The relatives and friends of the bumped out participants hurling verbal assaults towards judges and the judges themselves get into an emotional state deciding to quit and all others wooing them to come back. This is something that you should not miss . OK, OK, I was kidding about the last statement!
  • You-Have-Yet-Another-Chance Pattern: When the participants are dropping off the chart like flies after you switch on the repellent, the organizer will decide to pardon the non-performers and continue to the next session.

Comments

Shoban Jayaraj said…
The Mute Pattern: When two people start discussing the plan, your TV goes mute. This likely means that the topic under discussion will likely succeed.

Popular posts from this blog

Inside a Text Editor Ever since my college days, after dabbling with vi and a few other editors, I always had an yearning to create my own. Now, I am still stuck with XEmacs and jEdit and had a chance to compile / study the sources and documentation of EMACS and a free editor component called Scintilla. Until now, I was under the the belief that text editors used a doubly linked list to represent the text in memory. The advantages of this approach being insertions and deletions are much more easier which is just a matter of just un-linking a node off the list. But the shortcomming is that they tend to fragment memory with each node or line take a bit of memory. The other alternative approach is to have a dynamic array which is a contiguous space of memory and can sometimes be directly written off to a file. The disadvantages are that insertion and deletion are costly and you need to reallocate quite frequently. While goint throug the source and documentation of text editors, I chanced ...
Battle of Wesnoth Been on the lookout for a free turn based strategy game and chanced upon the Battle of Wesnoth . Despite it being an open source game (meaning, you get the source), it was incredibly polished akin to any of the other turn based strategy game (Alpha Centauri), be it the background score or the graphics or the tutorials. The game itself is set in a period similar to the D&D or nethack era. For the film buffs, if you have read or seen the Lord of the Rings, you would probably be able to relate to the clans that populate the game world. The game play, as with any turn based strategy game requires background information on each of the units that you own, their strengths and weaknesses and a lot of planning (a kin to chess, but with a lot more parameters) where factors like day - night cycles are taken into account (e.g, humans fight well during the day, but the orcs are better during the night). It is encouraged to keep your older units as they gain experience and beco...
Learnings on software development http://www.taylor.se/reddit.html and Digg posted an article on the learnings from ten years of software development. May I add: 2. The difficult part of software development is communication Primarily, this boils down to both verbal and written communication. Both are used at different combinations at different scenarios. When you are discussing features or effort or schedule with your customer, it makes sense if these are written as it allows you to archive the information and refer to it at a later point of time. Who knows, six months down the lane, it would be you who would be scrambling down your e-mail chain trying to figure out why a feature has to be implemented the way it is. Even if you have a verbal discussion, it is a good idea to follow up with the minutes or a gist along with a set of action items. On the other hand, when it comes to appraisals, evaluation or goal setting sessions, it is primarily verbal communication followed with the a...