For further actions, you may consider blocking this person and/or reporting abuse
🛠️ Bring your solution into Docusign. Reach over 1.6M customers.
Docusign is now extensible. Overcome challenges with disconnected products and inaccessible data by bringing your solutions into Docusign and publishing to 1.6M customers in the App Center.
Read next
Blockchain and Patent Management: A New Era for Intellectual Property
JennyThomas498 -
To test or not to test, "How" is the question!
Pooyan Razian -
"Unlocking Efficiency: LServe's Breakthrough in Long-Sequence Language Models"
Gilles Hamelink -
The Future of Server-Side WebAssembly
Kartik Mehta -
Top comments (2)
LeetCode builds skills for solving fairly narrow technical problems. These are the types of questions you'll likely get in an interview, so it's valuable to practice and prepare. I wouldn't be concerned about getting a high score. Just make sure you're comfortable tackling common types of questions and can explain your process.
Side projects demonstrate a (mostly) different set of capabilities. Do you have the knowledge to build a complete application? Did you persevere when nothing was working? Can you write documentation? Can you debug real-world issues and find solutions? Are you creative? Able to make reasonable compromises to ship something?
The role and the opinions of those who are hiring will decide the relative importance of coding challenges and side projects. It's best to have both. A complete failure on the challenge can cost you the job, while a side project is your best bet at pushing yourself ahead of others. Use it as an opportunity to explain your process, decision making, and talk about challenges you faced.
Interesting reply
You are right both helps build certain skills