Python for me was fun at the beginning but I kind of hit a wall and it took me a few years to figure out what had happened.
I wasn't able to solve (or mentally model) problems past a basic level of complexity.
This was primarily caused by dynamic typing, but was probably exacerbated by a culture that's obsessed with abstract meta programming magic than down-to-earth data processing.
It's unbelievable how easy programming is (comparatively speaking) when you just think of it as data modelling and data processing to solve specific problems.
Most of the complications that arise during implementation are invariably caused by having to deal with libraries or sub-systems that insist on hiding data behind obtuse abstracted interfaces and just refuse to be cooperative.
💯My brother and I grew up watching this sport in Nepal. It was all about racing. We used to go online and print the maps of Monza and Siverstone tracks.
Today, I was writing about crucial interview tips and one of the topics is about "Tell me about yourself" question.
This is something I personally struggled with during in my early days, prompting a deep dive into articles and videos for the perfect strategy.
Even with subject matter expertise, this question can still trip you up. It's like asking someone to sum up their life in 2 mins.
Here are the quick and clever points I gathered.
Your answer unfolds in three parts. Past, Present, and Future.
Past: Unveil your journey - What you have done? How have you got here? Share snippets of your past roles, experiences, and tech encounters, emphasizing those technologies that align with your current role you applying for.
Present: This is about letting them peek into your current role and life. What you are doing now. This is about your current roles, and what the most recent things you been working on.
Future: Reveal your purpose. Why are you here? Why are you interviewing here? What are you looking forward to in this role? Sometimes this part answered well can set you apart from other candidates.
Prepare an answer keeping about three parts in mind and practice saying it a few times in front of mirror.
Aim for no more than one minute for each part. The whole answer shouldn't last more than three minutes. After all it's an icebreaker question - your introduction to a more in-depth discussion.
Extra points if you can sprinkle in tech and experiences that match the job description from your past experiences. It leads the way for subsequent questions into the area of your strengths.
And, yes, there are variations to this based on your experience level, and also variations of the question itself, like interviewer asking "walk me through your cv" or "give me brief introduction of your experiences" or "tell me about your past experiences". All these means the same thing and answering them wrong can make you miss the opportunity.
Let me know what your experiences have been in interviews or if there is anything I missed and should include?
Chandrayaan-3 Mission:
'India🇮🇳,
I reached my destination
and you too!'
: Chandrayaan-3
Chandrayaan-3 has successfully
soft-landed on the moon 🌖!.
Congratulations, India🇮🇳!
#Chandrayaan_3#Ch3
This visualization uses the visual metaphor of a submerged porthole window to observe how far our oceans rose between 1993 and 2022.
[NASA, read more: https://t.co/1ERdtKPB9z]
I’ve written to @Keir_Starmer to request he pays for the criminal damage the Just Stop Oil attacks on the Energy Security Department caused this morning
As the political wing of Just Stop Oil, it is the Labour Party not the taxpayer that should be paying the bill