Leetcode 24 Hour Challenge (while learning Golang)

Coding leetcode problems for 24 hours straight because I enjoy the pain. And I get to learn about Golang, which is such a great language for leetcoding.

0:00 - Stream starts
17:50 - Challenge starts
24:14:15 - Challenge ends

#leetcode #neetcode #golang

[NeetCode]

In 24 hours we learned that Go might not be the best language for leetcode problems... :^)

This is my second and hopefully last 24 hour leetcode stream

0:00 - Stream starts
17:50 - Challenge starts
24:14:15 - Challenge ends

[elitecoder]

This video is about pushing the human mind to the absolute limit, legend!

[VthePeople]

* 00:01 - 02:36: Stream Start and Initial Chat Interaction
* 00:01 - Stream begins, visual and audio check.
* 00:10 - Streamer acknowledges the recording.
* 00:20 - First chat messages appear.
* 00:45 - Streamer reads and responds to initial chat questions.
* 01:30 - Initial technical setup or settings adjustments.
* 02:00 - Streamer announces the plan for the stream.
* 02:37 - 03:30: Chat Delay Implementation
* 02:37 - Streamer mentions implementing chat delay.
* 02:45 - Streamer navigates to chat settings.
* 03:00 - Explanation of why delay is necessary.
* 03:15 - Streamer sets the delay duration.
* 03:30 - Streamer confirms the delay is active.
* 25:55 - 28:00: First Problem Solved
* 25:55 - Streamer declares the problem solved.
* 26:00 - Streamer reviews the solution.
* 26:30 - Explanation of the solution's logic.
* 27:00 - Code walkthrough.
* 28:00 - Q&A about the solution from the chat.
* 01:32:11 - 01:34:30: ChatGPT Assistance
* 01:32:11 - Streamer opens ChatGPT.
* 01:32:30 - Streamer inputs the problem into ChatGPT.
* 01:33:00 - Streamer analyzes ChatGPT's response.
* 01:33:45 - Streamer integrates ChatGPT's suggestions into their code.
* 01:34:30 - Streamer reflects on the effectiveness of ChatGPT.
* 01:34:55 - 01:38:00: Google Experience Discussion
* 01:34:55 - Streamer begins discussing their time at Google.
* 01:35:30 - Anecdotes about work environment.
* 01:36:15 - Discussion of specific projects.
* 01:37:00 - Insights into Google's engineering culture.
* 01:38:00 - Advice for aspiring Google employees.
* 02:06:11 - 02:08:00: Importing Slices
* 02:06:11 - Streamer initiates the import of slices.
* 02:06:30 - Navigation through file systems or project directories.
* 02:07:00 - Code implementation of the import.
* 02:07:30 - Debugging or troubleshooting import errors.
* 02:08:00 - Verification of successful import.
* 02:54:12 - 02:57:00: LeetCode and Book Recommendations
* 02:54:12 - Streamer begins discussing LeetCode.
* 02:54:45 - Discussion of specific hard LeetCode problems.
* 02:55:30 - Book recommendations related to coding or algorithms.
* 02:56:15 - Personal insights on learning strategies.
* 02:57:00 - Chat interaction regarding LeetCode and book choices.
* 03:25:14 - 03:28:00: Drug Discussion
* 03:25:14 - Streamer broaches the topic of drugs.
* 03:25:30 - Anecdotal stories or personal experiences.
* 03:26:00 - Discussion of related social issues.
* 03:27:00 - Chat reactions and interactions.
* 03:28:00 - Streamer changes subject.
* 04:09:50 - 04:13:00: Coco Eating Bananas Problem
* 04:09:50 - Streamer introduces the Coco eating bananas problem.
* 04:10:15 - Problem analysis and breakdown.
* 04:11:00 - Code implementation of the solution.
* 04:12:00 - Debugging and testing the solution.
* 04:13:00 - Solution explanation and optimization.
* 24:12:09 - 24:13:30: Firebase and Stripe Discussion
* 24:12:09 - Streamer begins the Firebase and Stripe discussion.
* 24:12:30 - Explaining the uses of Firebase.
* 24:13:00 - Explaining the uses of Stripe.
* 24:13:30 - Showing code implementation using those services.
* 24:13:52 - 24:15:15: Recursion Fun
* 24:13:52 - Start of the recursion fun.
* 24:14:15 - Simple recursion examples.
* 24:14:45 - Complex recursion examples.
* 24:15:15 - Chat interaction concerning recursion.
* 24:16:11 - 24:17:00: Stream Conclusion
* 24:16:11 - Streamer announces the end of the stream.
* 24:16:30 - Final chat interactions and goodbyes.
* 24:17:00 - Streamer ends the recording.

[yurabezhentsev]

I'm proud of YouTube - eventually, it saved the full stream... LOL

[simmiig]

I just found you today!!!! I got a coding assessment from IBM and I'm using your vids to grind out my prep!! Thank you for all your content, I feel like I can actually do good for once in my life!!! lol

[VijayKumar-dnpz]

By practicing leetcode daily, he has turned what is often a weakness of a developer into his strength! What a legend! I'm practicing Leetcode and Codechef daily too now. Will start using your website too.

[aryansharma-qecn]

This is insane man....hope your channel reach a million subs soon

[myanch]

lol I thought the title is clickbait, because youtube says 1:00:17:15 and my stupid head thought it means 1 hour, this is insane dude

[grandparick]

Just wanna say I was present in the live stream periodically. Giving you my powerful support.

[Suraj-Singh]

I just finished watching your video and I'm so impressed! Your authenticity, inspiration, and motivation are truly contagious. Your video gave me a positive energy boost that I really needed. Thank you for creating such a great video!

[wenwenzhang]

If you are doing a fans-meet-up event in Seattle that will be super fun! The admission requirement would be...complete all NeetCode 150 problem LOL

[_vdgazer]

That's insane! Do you plan to do more content on system design? :)

[tusharsingh]

5th Problem: 3:15:49
7th Problem : 3:41:46
best time to buy and sell stock : 4:40:39

[Respect_Mah_Authoritah_]

Just curious why you think Go is an awful language- I’m just staring to learn it now, and wondering if I should, still.

[wenwenzhang]

The one and only coding channel I follow on youtube. Pro account as well!

[simontam]

Wow, the chat was a bit toxic.
Go revels in its simplicity, but it has some quirks that seem to come from the creators' opinions like the weird (yet easy to read) syntax, and tabs instead of spaces. Much of the reason for the lack of helper built-in / standard library stuff like `slices.Contains()` is the lack of generics, which have only recently been added to the language. Perhaps you would have had a better experience if you went through "A Tour of Go" from the official site or had "Go by Example" as a reference. Or even writing the code in an editor that had language server diagnostics. But I definitely agree it's not the best language for leetcode problems.
Props for making it to 24hrs. I feel exhausted after only a couple of hours of leetcode.

[yyy]

Dude, please do one more at least 6-hour leet code stream with Typescript if not 24 hours.

[nodarimosia]

As someone invested in programming education, chat "helping" but giving totally wrong and hallucinated hints made me so irritated (for example, what was this chatter smoking at 38:14 ?). They were just confusing learner (NeetCode) and made him question everything he learned until then.

Still, impressed by you resiliency and hope you give learning Golang more structured approach in the future.

[VidyaBhandary]

Dropped in a few times during the live stream. And in the last couple of hours - leetcoding (in python ). Was fun. And yes I am in the minority for that early Q.

[DJdopeMike]

This guy is best! Thank you for all the explanations and valuable content.