danielgh7

One interesting twist: you can choose whether you want the experience to be less scary, standard, or more intense.

It’s a very small event with limited seats, so please only RSVP if you’re pretty sure you can make it.

We’ll have snacks during the screening and pizza after. We’ll also ask attendees to fill out a short survey so we can learn what worked and what didn’t.

If you’re curious: https://partiful.com/e/ydTGBueYzwm19nv4XYrq

ChatGPT does a great job organizing and simplifying the results. It handles nuance really well and knows when to say "You'd have to ask your doctor for that" We found out my mom's tumor was grade 4 from chatGPT. The doctors released the results on a Thursday, none of us could really understand what was being said it was full of medical jargon, and we weren't seeing the doctor until the next Tuesday

So we just dumped it into chatgpt and got the info.

Not every experience is going to be best suited to fit in a chat box like ChatGPT which opens the door for startups like this one to build something new.

I'm excited when I see products like this, and I think we really need to retire the critique of "Its just an API call to OpenAI". While yes that is a core part of it, there is a lot of time and effort that goes into developing these experiences that has value

Would love to see your channel if you are open to sharing it.

WRT the handwriting: I may end up switching to a typed format since its supported in workrooms and everything is remote nowadays anyway.

My thoughts with watching the failures: it helps to see what doesn't work during an interview.

Ex. So many people jump straight into coding before even thinking about the problem or asking clarifying questions. This is a big red flag during interviews. It might make the value prop clearer if I add some commentary over the failures to explain what went wrong and why.

I'm still trying to suss out whether it makes sense to post the failure vids, so thanks for pointing that out

I'm probably going to NIX the actual whiteboarding portion and lean more into a text based approach based off all the feedback here.

I guess its time for a hair cut and a shave(About a month into trying to grow my hair out)

Would love some honest thoughts on whether it seems like there is something actually interesting here or not. (or tips on how to improve). My biggest "improvement" to date has been using canva to make half decent thumbnails haha

14.1% channel pages

11.7% direct

5.1% Browse Features

2.0% Youtube Search

2.4% Others

Not too sure what to make of it, but it looks like my search indexing isn't providing much value. Thanks for raising the point I need to investigate how youtube search works a bit more

2. Skip the second half of the book when the chapters switch to being real world examples

3. Having trouble on a particular section? Watch the youtube video to get a cleaner read: https://www.youtube.com/watch?v=22hwcnXIGgk&list=PLOtl7M3yp-...

4. Don't spend too much time on NP/NP-Complete/NP-Hard topics

5. Over learn chapter 2. This is arguably the most important chapter having a deep understanding of runtime analysis helps you in every other chapter and on the interview

6. Don't spend too much time on writing proofs in Chapter 1. Understand them and be able to work through them and understand how the math comes together, but writing a specific proof isn't too valuable.

7. Sometimes the interview problems at the end of the chapter are silly. If it feels dumb, example: 1.36. How much does the ice in a hockey rink weigh? Skip it. These are older school programming interview questions and have been largely phased out

Sadly, different tactics should be employed when trying to land a job. I've conducted over 100 interviews with people studying for programming interviews over the last 2 months and its wild how many people are just going to leetcode and solving random problems. They think if they solve enough problems, they will get the job, and thats just not the best way to maximize your odds. You need to cement your fundamentals and actually understand the concepts. I usually recommend the algorithm design manual by steven skienna and a few other resources.

The goal of this article was to help those people who are aimlessly solving problems to add some structure to their studying. Hope that clears things up!

CTCI has its place if you have limited time and are targeting mid-size companies, but for anything more serious ADM is the way to go

I've been developing this 3D streaming pipeline that lets users livestream scenes out of the Unity Editor to WebXR. You can see a customized example here: https://hyperplane.live/tk/vods/097aef

## Why build this

I was an engineer at FB on FB Live & IG Live & I worked at Oculus on VR Media. A trend I started to notice was people using the Unity editor as a recording studio! The recent rise of Vtubers as an example. I wanted to give people a way to share these Unity experiences in WebXR!

## Why Post?

I'm looking for developers interested in partnering to build some cool products on top of the streaming platform! This will enable me to focus on improving the core streaming pipeline and adding features, which is where my passion is.

## How it works

The streaming pipeline is composed of 3 key pieces

1. Unity recording software. (An SDK + desktop application, Mac & Windows supported)

2. Custom file format spec, think DASH but for fully described 3D videos

3. A 3D video player that knows how to read the custom files and manages playback & overlays.

## Currently supported features

Meshes, Skinned Meshes, dynamic lighting, textures, materials, animations, audio

Setting up new users is still a manual process, so feel free to reach out if interested and I can set you up.