Delhi NCR in general looks like a pretty nice place to source tech in India. The Bangalore counterpart of Nehru Place, SP Road felt expensive and a bit less competent than I expected.
Spare parts are expensive in general in India. Add to the fact that there are unscrupulous repair centers, I am certain that the theft of genuine parts happen regularly.
Probably institutes teaching IT stuff. They used to be popular (still?) in my country (India) in the past. That said, there are plenty of places which train in reasonable breadth in programming, embedded etc. now (think less intense bootcamps).
Reminds me of the Indian public discourse when the government wanted to tax caramel popcorn in movie theatres at 18% when the normal ones were taxed at 5%.
It's a fine surprise that I just ordered the book independently and then discovered the podcast and found the book being discussed on HN all in the same day. Pretty nice coincidence.
Pardon me for not getting your context, but are compile times a big issue in software development? I have never programmed professionally and all my experiences with code is from a couple of classes taken in college a decade ago.
When doing UI things, a common workflow is to have code and the app side-by-side, make a small tweak in the code, recompile/hot-reload, look at he result, repeat. A long compile time makes workflow a pain.
In general, you're right. But there are at least 2 times where they're absolutely vital- anytime you're dealing with a UI and data exploration in data science (since you make a lot of frequent, small changes in the goal of fine tuning something.) Everything else, best practices has good testing and partial compilations to make it moot. There's probably some other contexts that make it valuable, but I've never had to deal with those.
I am curious how perplexity handles the rate limiting. I use it a lot during the course of the day and find no rate limiting while Claude 3 Opus set as the default model.
