I have worked at Micromax before, personally with @rahulsharma too, when we launched @YUplaygod

It was exciting because we wanted to launch a product based on the merits of the product (price, features, style) and not just "nationalism" as a feature.
And I have no grudge against @Micromax__India or @rahulsharma for the new brand "inMobile", because I have seen this man being able to impeccably pick out gaps in market for features and at unimaginable price points, and I would love to see "truly" made in India hardware more.
But it is sad that we are ready to skimp over pricing and quality of products and simply use "nationalism" as a feature to ship products.
This is exactly the opposite of what globalisation and liberalisation was all about. Heck even @Micromax__India wouldn't exist without that
More manufacturing in India is needed - but so that we can make world class products and compete internationally, not just because our citizens have shut down their brains and happy to use substandard products, simply because they are built in India.

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with Arnav Gupta

Arnav Gupta Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @championswimmer

17 Oct
Ok weekend thread 🧵 time 👉

Since college days, I have launched 4 products (2 fail + 2 sold), started up thrice (1 failed, 1 sold, 1 running), lead a team at a $1B+ startup and worked as lead engineer at a Fortune 100 giant

Here are some learnings (tech/management/product)👇
Everything is a people problem. Always. 100% of the time. It isn't the code, the market, the product fit, the idea, the money. None of that.

BUT BUT BUT, do not blame 'a person' for it. That's a cop out. Fix it structurally, in the process, so it isn't repeated.
The single short term fix for 99.99% problems is money.

From cofounder problems to team bandwidth, to bad code. More money can stop a leaving cofounder from leaving, let you hire more people, or scale your server 10x.

It is a bandaid. Fix it properly eventually though.
Read 17 tweets
22 Aug
I have been teaching #FullStack #WebDevelopment for over 5 years, and taking interviews for #FullStack developers for over 3 years now.
Here is a tiny thread 🧵 for aspiring #Developers 👇
1. 📜 Take up frontend first, easier to see results. Take up backend later

I personally learnt #NodeJS to support my #Android work, and later got into #Frontend. But if I only had to be a web developer, I'll redo it with frontned first.
2.💡 Focus on basics before frameworks. Framework ninjas with 0 in basics get thrown out in interviews

It is nothing short of depressing how many people cannot even start making a simple project with #react or #vue scaffolding. Don't be that guy.
DOM events, semantic HTML ftw!
Read 14 tweets
27 Jun
The concept of "live" classes exist only because we keep trying to emulate physical interactions into digital ones.

Companies that have worked for years remotely know that you cannot replace 10 physical meetings with 10 zoom meetings. You need more asynchronous communication.
When you move from physical offices to digitally connected remote ones. You need to invest into good project management tools (Trello, Jira, Basecamp, Asana... something), good documentation repository and create an email thread culture rather than Zoom culture.

Same in edtech
The reasons are same. Networks get disrupted, not seeing each others face and body language hinders communication and speeds of delivery of information and absorption of it do not match. The loudest voice is the one with best internet.

The solution is to reduce "live" events.
Read 13 tweets
7 Jun
A lot of us Indians are looking at the current situation in USA, and a lot of us on the better side of the spectrum (not Islamophobics, not Modi fanbois, not Hindustani-Bhau-following rabid hindu rashtravadis either) are also thinking we are kinda better off

Here's a thread 👇
Not sure if you are noticing beneath the layers of outrage and hashtag and the noise and headlines something succinct, something really important to take note of - even the racist themselves DO NOT want themselves to be called racists.

Trump is shouting "I am not a racist".
This is an important lesson in how far, literally how far a society has gone. Yes today's protests are to take it further, towards the ideals of racism not just being gone on paper, but gone in practice.

But you are looking at a society having progressed enough to detest racism
Read 19 tweets
22 Feb
Over the last few years, having seen and been part of tech teams that have grown and scaled (in size of team and in userbase), I've come to my own set of conclusions on microservices, microfrontends, monoliths, team communication and DX (developer experience).

A 🧵thread 👇🏽
As we enter into 2020, a few hyped up words and terms in the info-system ecosystem are

- microservices
- microfrontends
- serverless
- cloud-native
- containers
- orchestration

All of these terms are in the bucket of "the better way to do things" as per the mainstream today
I think we often do the mistake of looking at trends from the lens of pure technology, when we should be looking at them as a function of work culture, team communication, and the way companies are growing and working at this time

These "trends" are more abt org struct than tech
Read 21 tweets
31 Jan
1/ So it has been 9 years now I am tinkering with Android, and close to a year working at @Zomato - an app with 100M+ downloads and close to 5M active users on most days. Here is a 🧵 thread 👇🏼
@Zomato 2/ There have been multiple learnings, re-learnings, obliteration of firmly-held-on practices over the years. The differences between working on 6 month old codebases and 9 year old ones, and between 1-screen apps to 50-screen ones.
@Zomato 3/

First of all, the concept of "at scale" on frontend is always very different from backend. You are not spinning up AWS instances here as the traffic hits. But scale matters here. Especially when you need to support 500+ different devices from 50+ OEMs.
Read 17 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!