Pune to Raipur showed WL 14. But the same train had seats available for Pune to Nagpur and Nagpur to Raipur. I booked both journey and got the same seat.
If the seat was available, Why wasn't that seat available for Pune to Raipur?
@IRCTCofficial@RailMinIndia@AshwiniVaishnaw
If you sit to code today pick one of two `modes` you are in -
1. Learning mode - turn off ai, read docs, spend time doing tough problems, gratification is learning something new and not the speed of implementation.
2. Implementation mode - Coding tools (cursor etc) have gotten really good. Make it cruise through writing code while you watch netflix or sm.
2 is more fun if you've spent a few hours doing 1.
I cry with tears when I have to take an interview only to see the candidate fumble the most basic syntax.
I'm unsure if its AI but it feels like jr devs or devs in general aren't hands on coding much and I'm unsure how I feel about this.
An argument can be made that we don't need to memorise code anymore, but it just feels sleezy and boring talking to someone who cant code themselves.
API concepts that are discussed in interviews , don't skip these if you are a backend dev :
1. Idempotency: Know why PUT/DELETE are idempotent but POST isn’t. Helps avoid accidental double writes.
2. Pagination: Offset works until scale hits. Cursor/keyset is what you need for big data sets.
3. Versioning: URI vs Header vs Query param. There’s no one right way, just tradeoffs.
4. Rate limiting: Token bucket > naive fixed window if you care about fairness.
5. Error contracts: 400 (bad request) ≠ 422 (validation issue) ≠ 409 (conflict). Don’t just throw 500 everywhere.
6. Caching: ETag + Cache-Control save you from unnecessary DB load.
7. Security: JWTs expire for a reason. Don’t stuff user PII inside them.
8. N+1 Queries: Kill them early. Use batching or joins when returning nested resources.
9. Docs: OpenAPI/Swagger is not optional.
10. Consistency: Sometimes cached data is good enough.