Skip to main content

One cannot judge the backend complexity by looking at the frontend.

I've seen people saying "this one is pretty easy to implement" by looking at the frontends of some awesome applications. Making frontend and user interface clean and KISS (keep it simple and stupid) is essential for an application to win the users. By that it never meant that it was easy. To make an app more user-friendly, developers has to write extra code to balance the "things" that they have abstracted.

For an instance, consider www.google.com page. How simple and stupid that page is...
6 large letters and a text box. What else in it?! By that would you conclude Google is easy?

I do also have personal experience from a guy, who comments after evaluating our project of 5000 LOC that "is it only this much to do that? Child's play". He also suggested a new feature to add, which was a nice one. On the implementation phase of that feature, we pulled him to find a bug. And after spending 30 mins on our code his reaction - "Someone's callin me…" - was worth experiencing.

If we feel an app as simple is because some guys made it simple. In fact it may have a terrible backend!

Popular posts from this blog

How to pass variables to res.render() in Node.js

I was trying to figure out how to render a view inside a view, as I was stuck with this issue.

Horrible Effects of Misplaced Extensions ;)
I was using Node.js platform with ejs template engine.

My index.ejs file has an included header.ejs file.
Everything works well except that I can't pass values to the variable status in header.ejs.

Here is my abstract code...

index.ejs

header.ejs

app.js

The most funniest solution ever!
The solution is as easy as this.
Just remove .ejs extension from the include command.
I spent at least an entire night to figure it out.

Talky Messenger Documentation & Setup

(Github)
Just created a chat app that runs in Node and Socket. By the Grace of God, this attempt was worthy.

Talky is a messenger app built with Node, Express, Socket, Angular & Bootstrap.
It's like a server-client structure. (But obviously not like the one we done at OS lab using shared memory). It has a broadcasting structure. Talky does not keep a log on chat. i.e., It doesn't have a memory or database. When we close the browser window, chat history is lost. There I also added a basic console, protected by a password, to send real-time notifications to active clients.

The name 'Talky' was suggested by a friend of mine. (hey, thank you for that. The fact is that I am not really good at naming...😝)

What if sometimes your college blocks WhatsApp? Try Talky.

(There is also a website on internet in the name of 'Talky' which has no connection with this one.)




Download Talky Messenger To use Talky, all you need is 3 things:

Node serverSource code.Three commands.