I don't have a Facebook, WhatsApp, Twitter or Instagram account now. But to me it seems like this is the new cool factor rather than choice, where quitting Facebook seems to make someone cool or distinct than using it.

I had to try very to read the article and not skim it.

I think you accidentally a word.

It's interesting, I feel like most of the time when someone leaves out a word in English it's the verb.

I saw that after posting. Left it as is to see if people will skim it or not.

Also, I am not a native English speaker. So most times as I formulate something in my mind, the speed difference between mind and hand causes me to miss words.

If I do a search and replace of China with India, this article would still be real and same.

Recurring meetings are bad. Most people come unprepared and since it is recurring unless you have made any progress, you are wasting time just for the sake of it.

Publishing agenda before meeting is a must. There is no point in starting a meeting on a blank note.

Many meetings can just be conducted over threads on slack or Microsoft team. What I mean by this is, the type of meeting where you want to confirm or come to an agreement over something, that chat thread can help flush out details before you waste everyones time over it.

In short, move most of your meeting and emails to your collaboration tool.

> In short, move most of your meeting and emails to your collaboration tool.

Even old-fashioned collaboration tools like e-mail can be used effectively to avoid meetings. A discussion of an issue that doesn't need to be decided immediately can just as easily be done asynchronously via e-mail.

I've gotten countless meeting requests that are just some product manager wanting to get a specific item of information from a group of developers. I've averted many of these meetings just by declining the meeting request with "Here's the information you need, no need to have a meeting about this. E-mail me if you need more information."

Any code that you write now will need to be edited in future for enhancement or bug fixes. If you are able to split individual steps or sub tasks of the main function into smaller sub functions, you would not be required to scan through the entire code in future for any modifications. If the functions are named properly, you can directly go to the function and edit it as required.

Also, assume that this big function breaks for some reason. Having sub functions will make it easier for you or anyone else maintaining the code to isolate it and track the source error in a much easier way.

So for me, functions are not just about re-usability, but also about maintenance and readability of code.