- Видео 29
- Просмотров 45 345
Adam Zerner
США
Добавлен 28 июл 2012
Educational videos about coding (and basketball sometimes).
Premium Poker Tools - Equity calculator guide #3
Premium Poker Tools - Equity calculator guide #3
Просмотров: 333
Видео
Louis S3E11 Wife Conversation
Просмотров 1407 лет назад
Louis talks to his ex wife about taking the Tonight Show job, hoping she'd tell him that he can't because he needs to do his part in taking care of the kids. She does the opposite, reasoning that the kids need a role model more than a father.
The What and Why of ngrok
Просмотров 25 тыс.8 лет назад
- Running out of IP addresses: www.howtogeek.com/119619/htg-explains-why-the-internet-is-running-out-of-ipv4-addresses-and-why-ipv6-is-important/ - Port forwarding: www.howtogeek.com/66214/how-to-forward-ports-on-your-router/
Data Binding: AngularJS
Просмотров 5188 лет назад
How data binding works in AngularJS Resources: - stackoverflow.com/questions/27216294/what-gets-added-to-scope-watchers-by-default-in-angular-and-what-triggers-d - stackoverflow.com/questions/33908800/how-does-angular-update-the-view-after-a-digest-cycle - teropa.info/build-your-own-angular
CORS
Просмотров 14 тыс.8 лет назад
UPDATE: Since making the video, I've learned two important things that I didn't mention/emphasize in the video: 1. The point of the same origin policy is NOT to prevent you from _making_ requests. It's to prevent you from _reading the responses_. It sucks, but unfortunately, cross origin requests are possible regardless of whether or not we limit XMLHttpRequest (see guides.rubyonrails.org/secur...
Intro to Algorithm Analysis
Просмотров 528 лет назад
Other resources: - ruclips.net/p/PL2_aWCzGMAwI9HK8YPVBjElbLbI3ufctn - ruclips.net/video/6Ol2JbwoJp0/видео.html - bigocheatsheet.com/
The "new" operator in JavaScript
Просмотров 8738 лет назад
How the "new" operator works in JavaScript More info: - MDN: developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/new - Front End Masters: ruclips.net/video/WUmuwAv3WCY/видео.html
Hash Tables
Просмотров 4158 лет назад
Slides: docs.google.com/presentation/d/1Wrgs9u9CuclGDSXfMXwN5-ahAwI2AOQL5b9R1Gjm4vY/edit?usp=sharing Good intros: - ruclips.net/video/MfhjkfocRR0/видео.html - ruclips.net/video/h2d9b_nEzoA/видео.html Great for more detail: - ruclips.net/video/UPo-M8bzRrc/видео.html - en.wikipedia.org/wiki/Hash_table What data structure to use for Chaining: - en.wikipedia.org/wiki/Hash_table#Separate_chaining_wi...
Request-Repsonse: Some Context Before You Learn HTML
Просмотров 378 лет назад
Request-Repsonse: Some Context Before You Learn HTML
Skimmable Videos: How to Create a Skim
Просмотров 2549 лет назад
Skimmable Videos: How to Create a Skim
thanks!
COOL TUTORIAL. GOOD LUCK ALWAYS....💯👍👍👍👍👍👍👍
Thank you so much Adam for this video. Thats great video. Respect ++
Great video with clear and detailed analysis
Thank you
This was actually very helpful! I knew what ngrok was but I didn’t really get how it worked without port forwarding.
very helpful bro thank you so much : )
This was amazing! Thank you so much! Wish you were making more content, you've got a gift!
14:34 in JavaScript the call stack actually uses the heap?! Is this true?
Great explanation
Nicely explained. Thanks
Superb! Thank you for a very clear tutorial A*****
Very Helpful...thanks buddy!
Hello Sir, A fan here. Read your article about "Computer Networking" some days back and you got me there. I hear you aloud in your endeavor or in your dreams, including this video. That tells me enough that you know how to live greatly. You're inspiring me to do something great too. Thanks for that. Lots of love. <3
Thank you Lokesh, I appreciate that. Dream big!
Very Helpful!
very under rated tutorial/explanation well done!
Best explanation ever
Thanks a lot, good work. Your teaching skills are outstanding. Keep doing more videos on angular 🙂
Superb explanation. It doesn't get simpler than this. Thanks bro.
Great explanation.. keep posting videos about networking
It's awesome! Thanks for sharing it man
Awesome explanation. Thank you!!!!
A doubt brother. If our router can remember who requested what, then why can't ESPN remember?
The Router DOES "remember" (hence the name Router). ESPN is not the router in this case.
Okay bro. Got it. Thanks bro.
Thank You
very nice Adam.. thanks for the detailed information..
Excellent explanation... Thanks adam
Good explanation
Awesome thank you
Very helpful me to understand ngrok. Thanks Adam
You have the vast amount right, I think. Your idea of "private addresses" is simply called an "non routable IP address" and there are three standard ranges. Anything in the ranges 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 will not be forwarded by any Internet router - they are intended for internal use only and are not routed. Your average home network is 192.168.0.*, for example. This has two key safeties: your home network doesn't get out so a bad network card won't take down your ISP, and no one outside can address your home computer since the router won't forward the packets. NAT is the process of "network address translation" on a connection from one side of the router to the other. A computer connection is generally 4 numbers: my IP and a port, and a remote IP and port. The router/firewall uses 8 numbers... 4 inside and 4 outside your network. As traffic crosses the router, it replaced the non-routable address with a public IP (routable). Generally, the other end of the connection will also pass through another router or firewall, too. So it all works to make private IP services safer, just like it does for home. The FROM port used for requests are pretty random, but generally more than 1024 (of 65,000 available). The TO port is usually a "well known" port (less than 1024) either specific to an application, or issued by "Internet Assigned Number Authority" (IANA). That's why normal web servers use port 80, and ssl uses port 443... If I know the public IP address of Google, I can reach their web server running on normal ports, and their email has a standard port. So, a request starts on a private address and random port, to a public address and common port and my firewall translates my address from private to public. On the other end, the firewall forwards/translates to a private IP and an internal port (maybe not the common one). This let's the server provide more websites as a hosting service, or load balancing, or what have you. But that's all just the jargon... you've got it right in you explanation.
Thanks for the information! To be clear, I'm no networking expert, so it's good to get the thoughts of someone more knowledgeable.
I'm not what you call an expert, just a little less lost, or under the delusion I am :-). Being able to name things is useful to understand and discuss complicated stuff. Like being able to ask for meat or gravy rather than growling "food...!" :-) The ngrok tunnel is simply an outward connection to a streaming server, too. Your firewall generally allows any connection to leave, and only port-forwarded connections inward; by keeping the connection open, you're opening a "tunnel" through the wall, and allowing traffic from ngrok to use that connection. The only difference between a "request" and a "tunnel" is duration. A request is usually a brief transaction, and a tunnel is more durable, no different than watching RUclips or Netflix. Once you get over the hurdles of firewalls and routers, you dig into protocols and the abstract stuff in the network stack :-) thence comes the rabbit hole and many multicolored rabbits.
> Being able to name things is useful to understand and discuss complicated stuff. Like being able to ask for meat or gravy rather than growling "food...!" :-) For sure! > The only difference between a "request" and a "tunnel" is duration. A request is usually a brief transaction, and a tunnel is more durable, no different than watching RUclips or Netflix. Huh, that's a great insight! That definitely clears things up for me. One less black box that I take for granted. - - - I appreciate your contribution. Most people with my level of understanding wouldn't make videos or write blog posts, because they fear that they don't know enough. The way I see it, you don't necessarily have to know _that_ much in order to help others. As long as you can contribute something, it's better than nothing. And often times beginners do a good job of teaching other beginners because they know what the likely points of confusion are. But it is great when more experienced people like you contribute and clarify things. That way, you kinda get the best of both worlds (the friendly perspective of the less experienced person, and then the more experienced person to fill in the gaps). That was a little rambly, I hope it made sense. Just wanted to reflect on a good experience on the internet and express my thanks :)
As I said, pretty much on the money without the jargon :-). Nothing worth building a fire or putting you down. When I went to college, I learned the real value of writing papers was to clearly "connect the dots" of and idea (aka support the thesis). I see your video the same way, just more animated... connecting the dots. Getting the terms right helps, but if the dots don't make a cat video/gif ... Terms don't help. Jargon without the rest is just BS and usually accompanied by bragging and bullying. I'd rather see understanding how it works in simpler terms than a boat of jargon without a clue :-) and you know you've seen it.
Ur very clear
Perfect!
Hello adam. I have few questions about ngrok. Im trying to breakdown a script I found on github. And I would appreicate if you could help me solve the mystery. Thanks -jad.
Now what is the node that lets me connect to ngrok ? Does it my router ?
i think so. probably
It was a great and clear explanation, thanks a lot, you deserve more and more subscribers ❤
Thank you so much! Explained the conceptions very clearly!
By far, best explanation I've read. Great work! Thanks!
Best explanation. High five Adam! Thank you.
You really know your shit. Great stuff
Wonderful explanation. Makes things very clear. Thanks!!
awesome work
thats really awesome explanation. thanks
But if we need the data like json, what we suppose to do for to solve this error "Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access." We can't change the header on someone server.
Thanks! I've been writing JavaScript for years and never thought of it this way before!
I am confused that "Is it compulsory for website to use the Same Origin policy while making Cross Request?"
The browser enforces the same origin policy. There's nothing a website can do to enable or disable it.
Okay so you mean that browser enforces it, no interfere of the website? this is SOP?
Very easily explained..The content I was searching for.Sometimes Somethings should be explained very easily.Thank you!
Thank you Adam. This is the best explanation we can get from the web.
Solominh ,
Thank you adam! anyway, do you have an example of this but using basic authentication?
Thank you Adam .. that was very usefull
great explanation. Thank you.