Wonderful essay on how to build a good software.

Loved the introduction:

Bad software is one of the few things in the world you cannot solve with money. Billion dollar airlines have flight search apps that are often inferior to those built by groups of students. Established taxi companies the world over have terrible booking apps despite the threat they face from ride-sharing services. And painful corporate IT systems are usually projects with massive budgets, built over the course of many years. Whatever the cause of bad software is, it does not seem to be a lack of …

The feature developer should draw a Sketch wireframe first.

• This keeps us on same page.

• This gives them better understand of the required output

• It also makes it easier for a person to delegate tasks as each part

• Each person can pick the task visually

How and when can it succeed?

It is easy to reject new ideas. The natural instinct is to find holes in any new idea and criticise it. Best VCs and investors force themselves to see the opposite.

Trick is to ask ourselves, "how and when can it succeed?”

I often see my dad and brother do that subconsciously.

Avoiding groupthink and decision paralysis

Problem with groups is that everyone is unsure. Everyone likes to have other's opinions before expressing their own. This stumbles decision making. No-one is able to reach a decision because everyone is waiting …

Wow! Django has a proper page on coding style.

I love Django's documentation. It have learned most of the best practices from their documentation. This too looks amazing.

Didn't know about isort. Trying it out.

What an article on fake Tethers in crypto market.

Tether Ltd. also says one Tether is worth exactly one US dollar. Can they do that? Well they say they can, because they hold $1 worth of assets for each Tether. But are those assets actual dollars? No, they are not. So what if the assets go down in value? Don’t worry; they will not. Okay, but can we at least see the assets? No, you may not.

Plus it explains so many other concepts so well.

A website can be ruined if it gets blacklisted. It is more possible where we allow users to upload content.

A lot of the cases of blacklisting that I found while researching this issue were caused by SaaS customers unknowingly uploading malicious files onto servers. Those files are harmless to the systems themselves, but their very existence can cause the whole domain to be blacklisted. Anything that your users upload onto your apps should be hosted outside your main domains. For example: use companyusercontent.com to store files uploaded by customers.

TIL (today I learned) Google has specific guidelines on how to handle subscription or paywalled content.

Are there any advantages of getting the paywalled content indexed?

I think so.

While the free content will be prioritised over paywalled content, the paywalled content should still show up in results where it is unique.

Plus, I beilve that it will imporove the overall page ranking which might otherwise appear as lean page to a bot.