Architect at Unbxd Inc.
Nothing here yet.
No blogs yet.
IMO, Python. However, the reward isn't immediate. What I mean by that is you won't be able to make something tangible that you can see or get excited about, initially. One thing that Python will do is teach you is how to translate what you have in mind into a code without much syntactical voodoo. Also, if you really want to put some effort and you understand high school mathematics well enough, I would suggest a read of Structured Interpretation of Computer Programs by Sussman & Ableson. It would connect the dots between Mathematics & Computer Programming and teach you some advance concepts which all JS developers swear by. Although, keep in mind it is almost all Scheme (a very old programming language, but excellent for learning).
Those two things are completely different. Browser just downloads the chunks being hosted on some URL. Torrent on the other hand uses completely different protocol. The P2P protocol specification can be found here . As for how they are able to pause/unpause is simply because the content shared on torrent is not shared as a large chunk, instead it is broken in small blocks of memory and shared which can downloaded independently.
Fuck those who banned or down-voted you. I could understand comments like "RTFM" but banning is just plain idiocy. You know what, if you are really interested and genuinely want to learn, pm me (links are in my profile). I will help you. I don't know much about Node or React but I can help you with Docker + Kube. As for "if it is a good choice or not?" I would say no. It's better to have a guide, however I won't say it isn't possible to build without a senior developer. The problem with completely new team is lack of the vision at larger scale which comes with experience.
Sadly, the reality is, way too few people understand the core language and way too many butt their heads with the framework. Learn the basics, no matter the language. It will always help you in long run.
What exactly did they ask? Did they ask some Data structures/ algorithm, or Java Internals. AFAIK most of the companies stick to DS/Algo, unless you have some extra stuff that you have done. If indeed you are a web developer and understand web really well, put it on top of your resume. Make it crystal clear for anyone who reads it that you know your stuff. Put some previous work that you have done, either as a part-time project or a hobby project. It is not expected out of an engineer coming right out of a college to know a lot about what is not taught in college and I assure you whatever is taught about web in college, in India is horrendously outdated. This is the reason why, interviewers stick to DS/Algo. But for some reason someone asked you to implement custom hashcode() for a random object, that someone is extremely poor interviewer, and doesn't understand CS Engineering himself.
I personally have a different approach. I try to be proactive about my workflow. Debugging when there is an error IMO If I can't read the error message and understand the issue, I am doing something wrong . Simplest way to do this is to not be lazy about handling errors/exceptions. I bubble up all my exceptions and errors and if for some strange reason I find a stack trace without a legit handling issue, I check the exception stack trace. Debugging when there is a business logic mistake TDD - There is no better tool to never make a business logic mistake. It saves a ton of time in long run. Integration Test Cases - Overall runs should yield expected results. If for some reason a mistake escapes your notice after these two, put a debugger and inspect values at each level