No matter how erratic or mischievous the behavior of a computer seems, there is always a logical explanation: you just haven’t found it yet!
The best keep digging until they find the reason. They might not find the reason immediately, they might never find it, but they never blame external circumstances.
With this attitude, they are able to make incredible progress and learn things that others fail to. When you mistake bugs for incomprehensible magic, magic is what it will always be.

Don’t Be Afraid to Say “I Don’t Know”
In job interviews, I pushed candidates hard to at least say “I don’t know” once. The reason was not that I wanted to look superior (although some people certainly had that impression). No, I wanted to reach the boundary of their knowledge. I wanted to stand with them on the edge of what they thought they knew. Often, I myself didn’t know the answer. And to be honest, I didn’t care about the answer. What I cared about was when people bullshitted their way through the interview.
The best candidates said “Huh, I don’t know, but that’s an interesting question! If I had to guess, I would say…” and then they would proceed to deduce the answer. That’s a sign that you have the potential to be a great engineer.
If you are afraid to say “I don’t know”, you come from a position of hubris or defensiveness. I don’t like bullshitters on my team. Better to acknowledge that you can’t know everything. Once you accept that, you allow yourself to learn. “The important thing is that you don’t stop asking questions,” said Albert Einstein.

Don’t Guess
“In the Face of Ambiguity, Refuse the Temptation to Guess” That is one of my favorite rules in PEP 20 – The Zen of Python.
And it’s so, so tempting to guess!
I’ve been there many times and I failed with my own ambition.
When you guess, two things can happen:
• In the best case you’re wrong and your incorrect assumptions lead to a bug.
• In the worst case you are right… and you’ll never stop and second guess yourself. You build up your mental model based on the wrong assumptions. This can haunt you for a long time.
Again, resist the urge to guess. Ask questions, read the reference, use a debugger, be thorough. Do what it takes to get the answer.

Keep It Simple
Clever engineers write clever code. Exceptional engineers write simple code.
That’s because most of the time, simple is enough. And simple is more maintainable than complex. Sometimes it does matter to get things right, but knowing the difference is what separates the best from the rest.
You can achieve a whole lot by keeping it simple. Focus on the right things.

Final Thoughts
The above is not a checklist or a competition; and great engineering is not a race.
Just don’t trick yourself into thinking that you can skip the hard work. There is no shortcut. Good luck with your journey.

check out:
https://n-o-d-e.net/

1. https://overapi.com/javascript

2. https://overapi.com/nodejs

If you're a Software Engineer and you're targeting TOP JOBS, your CV should be a one-pager.

Here's a framework to build a powerful CV that fits in one page:

1. Choose a minimalistic template in Latex/Gdocs.
2. Have an ideal role in mind that you're targeting with your CV.
3. If you have more than an ideal role in mind, make one CV for each.
4. Gather the best data from your history that shows why you're a great fit.
5. Prioritize and give more space in the CV to the most recent and more "fitting the ideal role" work experiences you have.

Throughout the CV: show, don't tell.

Meaning, show you're good at something by displaying real world scenarios where you've delivered impact thanks to such skills.

Be as specific as possible, using the "Accomplished [X] as measured by [Y], by doing [Z]" framework:

❌ Built a new feature in a web app in a team of 5 developers.

✅ Enabled a 10x+ latency reduction in DB health monitoring by refactoring a Python script to retrieve data from object storage instead of querying various APIs.

Maintenance:
1. Always keep a "brag doc" where you note down the good things you're achieving at your current job.
2. Regularly update your CV with the achievements from your brag doc.

Remove the fluff:
❌ "proactive, independent developer with great communication and leadership skills"
❌ "speak Mandarin, Spanish and French"
❌ photo

Technologies, frameworks and programming languages:
❌ Have a big CV section where you include all the tech you ever used
✅ Keep such a section small, listing only your top skills. Mention the technologies you used throughout your CV in your work experience bullet points.

These are just some tips.

Full guide is here: LINK

Author: Nicola Amadio

Node.js
* https://nodejs.org/en/learn/getting-started/introduction-to-nodejs
* https://www.youtube.com/watch?v=f2EqECiTBL8&ab_channel=DaveGray

JS
* https://nodejs.org/en/learn/getting-started/how-much-javascript-do-you-need-to-know-to-use-nodejs

OS
* https://www.youtube.com/watch?v=4rLW7zg21gI&ab_channel=ByteByteGo
* https://www.youtube.com/watch?v=vLwMl9qK4T8&ab_channel=VisualComputerScience
* https://www.youtube.com/watch?v=5sw9XJokAqw&ab_channel=CoreDumped
* https://www.youtube.com/watch?v=9GDX-IyZ_C8&list=PLIbUZ3URbL0Gqn0q2-MYJd-3nv6zw7GCQ&ab_channel=BrianWilla

601 real-world gen AI use cases from the world's leading organizations

https://cloud.google.com/transform/101-real-world-generative-ai-use-cases-from-industry-leaders

SOLID -

In software programming, SOLID is a mnemonic acronym for five design principles intended to make object-oriented designs more understandable, flexible, and maintainable. Although the SOLID principles apply to any object-oriented design, they can also form a core philosophy for methodologies such as agile development or adaptive software development.

Principles
1. Single responsibility principle - every class should have only one responsibility

2. Open–closed principle - software entities ... should be open for extension, but closed for modification.

3. Liskov substitution principle - functions that use pointers or references to base classes must be able to use objects of derived classes without knowing it

4. Interface segregation principle - clients should not be forced to depend upon interfaces that they do not use

5. Dependency inversion principle - states to depend upon abstractions, [not] concretes

Carl Zeiss Interview Experience - FullStack Intern
January 01, 2021

Carl Zeiss came to IIIT Naya Raipur with 3 positions

FullStack Developer
Machine Learning
Python/C++
Eligibility criteria: 80%+ in 10th and 12th with 7+ CGPA in B.Tech.

I applied for the FullStack role as this is my strong point though I was tempted to go for Python/C++ because I love python but didn't because I don't know C about C++ and felt like I would grow more in the FullStack role.

Since the company came in mid-late November only 19 people in total applied and they all were asked to give the First Round.

First Round - Aptitude Test
It consisted of around 40-45 questions to be solved in 45 Minutes on the Pariksha Platform. You might need some practice beforehand to increase your speed. Almost everyone cleared this round and we were asked to attend the Placement Talk followed by a Technical Test.

Second Round - Placement Talk + Technical Test (Coding + MCQs)
We were told almost everything one could ask to know about the company, they showed the various fields the company works and various achievements of the company like

Images were taken on the moon during Apollo 11 mission used lenses made by Carl Zeiss.
Developing lens to be used by researchers and doctors to do very critical work in their fields
Working on Silicon Technology with companies like Apple
...etc, etc
We were supposed to start the test within 30 minutes after the Placement talk ended. It was conducted on Hackerearch with no camera and no full-screen mode.

Two hours long, it contained 40 MCQ questions based on OS, DBMS, and position specific questions (FullStack and development for me) alongside 3 coding questions of 20, 20, and 50 marks each. Most of the MCQs could be answered in 10-15 seconds if you knew the facts, there wasn't much heavy calculation to be done. Even after having 90 minutes for 3 coding questions, I was only able to partially solve the 2nd one and but completed the 3rd one fully because it was a standard question which I had solved previously. The other two of 20 points were a bit more mathematical (my weakness :p) hence they ended up eating up a lot of my time with just a partial solution.

Luckily the situation was the same with everyone else which is why I was able to move into the next round. A total of 16 people out of 19 were selected for the next round (Quite a good amount).

Third Round: Technical Interview
The technical Interview was taken by two members (say A and B, A was junior to B), though most of the questions were asked by the A and B was just there probably analyzing my answers and behavior.
They outright asked me what things I know so I told them JavaScript, Node, and Python (+ Django). They asked me one simple coding question, if you are close or above to 1700 in CodeChef then you don't need to worry in this section. The part which had me sweating is when they started asking a specific question regarding JavaScript like

How does JS support asynchronous nature being a single-threaded language
Difference between == and ===
How JS stores data and datatypes
and more which I can't remember :p
I was able to answer most questions with confidence and ended the interview by asking some questions from my side about the workstyle, technologies used, and how work from home is affecting them

Fourth Round: HR Interview
It was supposed to happen at least an hour after my third interview ended so I left my laptop and phone to take a stroll and coming back after 15 minutes I see 3 missed calls and a message from HR to call him back. So I did and he asked if we could do the HR round in 5 minutes and we jumped on to a video call.

It was mostly just a confirmation call that yes you have been selected and some random question here and there about my family and how many brothers and sisters I have. After which it was mostly me asking questions and discussing how the internship will take place, their views on PPO opportunity and If we will be given any task or things to learn before the joining date (& more similar questions).

Just a tip
One thing I can recommend after this is that make sure to ask as many questions related to work-life and how the whole internship will take place or even ask about them about what they do (make sure to ask this in the tone) because everyone loves to talk about themselves whoever it might be. Asking a lot of questions even though you might know the answers reduces unknown variables and will make the recruiters confident in deciding to hire you.

Conclusion
In the end, 6 people got to the HR round and 5 were selected for a 6-month internship opportunity.

FullStack: 2
Machine Learning: 2
Python/C++: 1

Oracle’ga qanday tayyorlandim?✍️

Rezyume, muloqot qobiliyati, texnik tayyorgarlik va intervyudagi yondashuv — barchasi muhim bo‘lgan.
Bu jarayon haqida ushbu maqolamda batafsil yozilgan:

🔗 Medium maqola:
https://medium.com/@otabekecma/oraclega-kirish-uchun-qanday-tayyorlandim-6729d2cb0d5e

📌Blog: @otabekbobomurodov99