There are no people in juanangosto’s collective.

Huffduffed (101)

  1. Thomas Wolf: AI for Everyone | PIONEERS #06

    Subscribe to my newsletter for the latest developments in Generative AI: https://ninaschick.substack.com

    Thomas Wolf is the co-founder and Chief Science Officer at Hugging Face, a cutting-edge AI company at the forefront of advanced natural language processing.

    00:13 Introduction 02:51 Hugging Face’s mission 06:55 Hugging Face’s partnership with AWS 09:01 Open-source vs private enterprise 11:27 Safety and risk 19:09 Dealing with bias, stereotypes, and real-world impacts of AI 23:14 The pace of progress 25:51 Thomas’ take on recent breakthroughs in AI 30:56 Public perceptions of Generative AI and the need for better education 33:20 Enterprise applications and real-world uses 35:51 What’s next for Hugging Face

    EPISODE LINKS: Thomas' website: https://thomwolf.io Hugging Face: https://huggingface.co

    SOCIAL: Twitter: https://twitter.com/NinaDSchick Instagram: https://www.instagram.com/ninadschick/ LinkedIn: https://www.linkedin.com/in/ninaschick/ YouTube: https://www.youtube.com/@ninadschick

    Original video: https://www.youtube.com/watch?v=WwoB4uDCWFg
    Downloaded by http://huffduff-video.snarfed.org/ on Thu Jun 1 14:22:15 2023 Available for 30 days after download

    Tagged with people & blogs

    —Huffduffed by juanangosto

  2. Absurdism: Life is Meaningless

    Skip the waitlist and invest in blue-chip art for the very first time by signing up for Masterworks: masterworks.art/aperture Purchase shares in great masterpieces from artists like Pablo Picasso, Banksy, Andy Warhol, and more. How Masterworks works: -Create your account with your traditional bank account -Pick major works of art to invest in or our new blue-chip diversified art portfolio -Identify investment amount -Hold shares in works by Picasso or trade them in our secondary marketplace See important Masterworks disclosures: https://www.masterworks.com/about/disclaimer

    Read the story: https://aperture.gg/blogs/the-universe/absurdism-life-is-meaningless Merch: https://aperture.gg/merch

    Stay connected with Aperture: Website: https://aperture.gg/ Instagram: https://www.instagram.com/theapertureyt/ Twitter: https://twitter.com/TheApertureYT

    Check out our other channels: What If: https://bit.ly/youtube-What-If How to Survive: https://bit.ly/how-to-survive-show Crazy Creatures: https://bit.ly/crazy-creatures-show Your Body On: https://bit.ly/your-body-on-show Origins of Food: https://bit.ly/origins-of-food Versus: https://bit.ly/versus-show WTF Did I Just Watch: https://bit.ly/wtf-did-i-just-watch

    Questions or concerns? Contact us at https://underknown.com/contact/ Interested in sponsoring our episode…

    Original video: https://youtu.be/GBoHxeCQHRE
    Downloaded by http://huffduff-video.snarfed.org/ on Thu Jun 1 10:03:21 2023 Available for 30 days after download

    Tagged with entertainment

    —Huffduffed by juanangosto

  3. The Real Danger Of ChatGPT

    Go to https://www.squarespace.com/nerdwriter for 10% off your first purchase. GET MY BOOK HERE: https://amzn.to/3EPDQKt

    Support Nerdwriter videos: https://patreon.com/nerdwriter  Subscribe: http://bit.ly/SubNerdwriter Watch the most popular Nerdwriter episodes: https://youtube.com/watch?v=_aFo_BV-UzI&list=PLwg4AG1KkgLx18HrK7lCOjRXZFpmrdkvV&index=1   Facebook: https://facebook.com/The-Nerdwriter-314141501931192/ Twitter: https://twitter.com/TheeNerdwriter Patreon: https://patreon.com/nerdwriter

    MUSIC (via Epidemic Sound)

    Stationary Sign, "Paint By Imagination" Arthur Benson, "Sneaking Into The Kitchen" Arthur Benson, "Mixed Emotions" Sture Zetterberg "Merry Christmas Baby"

    Watch More Nerdwriter: Latest Uploads: https://youtube.com/watch?v=gqlgf_q3nN4&list=PLwg4AG1KkgLxZ2RPuELOONAszjFfv5DvT Understanding Art: https://youtube.com/watch?v=cLJAXu5OD-c&list=PLwg4AG1KkgLwP5FuUIiVEy-ILMD23AN1v Essays About Art: https://youtube.com/watch?v=cLJAXu5OD-c&list=PLwg4AG1KkgLwv68sdgTCCK8F8OjhSjbMl Essays About Social Science: https://youtube.com/watch?v=hBweUnkfQ2E&list=PLwg4AG1KkgLz2pLNCT97EbZgwCgnTV_kR Popular Videos: https://youtube.com/watch?v=_aFo_BV-UzI&list=PLwg4AG1KkgLx18HrK7lCOjRXZFpmrdkvV   The Nerdwriter is a series of video essays about art, culture, politics, philosophy and more.

    Original video: https://www.youtube.com/watch?v=AAwbvGywdOc
    Downloaded by http://huffduff-video.snarfed.org/ on Fri Dec 30 20:47:34 2022 Available for 30 days after download

    Tagged with entertainment

    —Huffduffed by juanangosto

  4. How ChatGPT changed everything: Thoughts from the frontline of the AI/ML revolution

    This week OpenAI released ChatGPT, its prototype AI chatbot. On this episode of Intercom on Product, Intercom Co-Founder and Chief Strategy Officer Des Traynor sits down to chat with our Director of Machine Learning, Fergal Reid for reaction and analysis on the implications of ChatGPT and what the future holds.

    Chapters 0:00 What is ChatGPT? 4:41 The internet reacts 6:10 Is GPT producing creative work? 7:45 GPT and Facts 9:28 Effect on peoples jobs 13:31 Hallucinations 21:26 How to improve language models 26:01 Is this bigger than Google? 29:30 Customer Support 42:06 Smart Replies 45:28 What other industries will be effected? 50:13 Outro

    Transcript: https://www.intercom.com/blog/podcasts/intercom-on-product-chatgpt-ai-ml-revolution/

    Follow the people: https://twitter.com/destraynor https://twitter.com/fergal_reid

    Follow the podcast: https://podcasts.apple.com/us/podcast/intercom-on-product/id1462264923 https://open.spotify.com/show/6d9s4PBzvdESARqUadlCpo https://www.youtube.com/playlist?list=PLlCIldMZCaFrcO10XuO7JtPpsZ7EyK0fg https://rss.art19.com/intercom-on-product

    Referenced in the episode: https://arxiv.org/abs/2210.11610 https://githubnext.com/projects/hey-github

    Original video: https://www.youtube.com/watch?v=SCsSpqZq_xA&list=TLPQMTYxMjIwMjJ6Ph13_amdfA&index=3
    Downloaded by http://huffduff-video.snarfed.org/ on Fri Dec 16 15:22:53 2022 Available for 30 days after download

    —Huffduffed by juanangosto

  5. Why ChatGPT Clearly Is The Next Big Thing

    ChatGPT is a game-changing innovation in the fields of content creation, search engines, personal blogs, and software engineering. It has the potential to completely disrupt these industries by providing users with a more efficient and effective way to learn and create. However, it also poses ethical and missinformation dangers that must be carefully considered.

    Use ChatGPT here: https://chat.openai.com/

    Follow me on Twitter: https://twitter.com/bPGTill My Lightning Address: ⚡️till@getalby.com

    Video on my second channel about building a blog website with ChatGPT: https://youtu.be/Z6IYxbMdOms

    My Discord server: https://discord.gg/e5KXwadq4s Instagram: https://www.instagram.com/tillmusshoff/

    Further Sources: AI 101: What is Natural Language Processing? | Accenture: https://youtu.be/IIaYk2hIYKk Using AI To Code Better? ChatGPT and Copilot change everything: https://youtu.be/yIZqIMNvqjg Twitter example of wrong answers: https://twitter.com/itstimconnors/status/1599544717943123969

    Original video: https://www.youtube.com/watch?v=L7WnUl-Pgc0
    Downloaded by http://huffduff-video.snarfed.org/ on Wed Dec 21 09:57:31 2022 Available for 30 days after download

    Tagged with art sci

    —Huffduffed by juanangosto

  6. TCJ Audio Archives: Todd MacFarlane Part 2

    It’s a clash of titans as executive editor Gary Groth confronts the Spawn creator and Image Comics co-founder in a no-holds-barred debate over artistic and commercial freedom vs. responsibility, originally recorded in 1992 for TCJ #152.

    —Huffduffed by juanangosto

  7. TCJ Audio Archives: Todd MacFarlane Part 1

    It’s a clash of titans as executive editor Gary Groth confronts the Spawn creator and Image Comics co-founder in a no-holds-barred debate over artistic and commercial freedom vs. responsibility, originally recorded in 1992 for TCJ #152.

    —Huffduffed by juanangosto

  8. #60: Cortex/Upgrade: Dangertown Beatdown

    This time the Snell-O-Tron takes Myke and Grey on a 1980’s cop adventure! Can they save their partner, keep away from corruption, and learn how to ride their motorcycle? Find out in this years text adventure special!

    SPOILERS: Myke's Map: https://dsc.cloud/Mykehurley/RGdXsGJ

    SPOILERS: Grey's First Map: https://dsc.cloud/Mykehurley/K2syXpa

    SPOILERS: Grey's Second Map: https://dsc.cloud/Mykehurley/SS6tkD6apIcXETEqeJG5

    —Huffduffed by juanangosto

  9. Is TDD Dead? #4 - Costs of Testing

    We discuss some downsides of testing and TDD: can you do too much testing, and is there a problem with teams valuing tests more than they value the functional code?


    David starts by saying "to talk about trade-offs, you really have to understand the drawbacks, because if there are no drawbacks there are no trade-offs." He continued by saying that TDD doesn't force you to do things, but it does nudge you in certain directions. The first issue he wanted to raise was over-testing. It's often said you shouldn't write a line of code without a failing test, at first this seems reasonable but it can lead to over-testing, such as where there are four lines of test code for every line of production code. This means that when you need to change behavior, you have more code to change . Kent has said 'you aren't paid to write tests, you just write enough to be confident' - so he asked if Kent and I wrote tests before every line of production code?

    Kent replied "it depends, and that's going to be the beginning to all of my answers to any question that's interesting". With JUnit they were very strict about test-first and were very happy with how it turned out - so he doesn't think you always get over-testing when you use TDD. Herb Derby came up with the notion of delta coverage - what coverage does this test provide that's unique? Tests with zero delta coverage should be deleted unless they provide some kind of communication purpose. He said he'd often write a system-y test, write some code to implement it, refactor a bit, and end up throwing away the initial test. Many people freak out at throwing away tests, but you should if they don't buy you anything. If the same thing is tested multiple ways, that's coupling, and coupling costs.

    I said that I'm sure there is over-tested code, indeed if anyone does it would be ThoughtWorks since we have a strong testing culture. It's hard to get the amount just right, sometimes you'll overshoot and sometimes undershoot. I would expect to overshoot from time to time and it's not something to worry about unless it's too large. On the test-every-line-of-code point I ask the question: "if I screw up this line of code is a test going to fail?" I sometimes deliberately comment a line out or reverse a conditional and run the tests to ensure one fails. My other mental test (from Kent) is only test things that can possibly break. I assume libraries work (unless they are really wonky). I ask if I can mess up my use of the library and how critical are the consequences of the mistake.

    Kent declared that the ratio of lines of test code to lines of production code was a bogus metric. A formative experience for him was watching Christopher Glaeser write a compiler, he had 4 lines of test code for every line of compiler code - but this is because compilers have lots of coupling. A simpler system would have a much smaller ratio. David said that that to detect commenting out a line of code implies 100% test coverage. Thinking about what can break is worth exploring, Rails's declarative statements don't lead to enough breakage to be worth testing, so he's comfortable with significantly less than 100% coverage.

    I replied that "you don't have enough tests (or good enough tests) if you can't confidently change the code," and "the sign of too much is whenever you change the code you think you expend more effort changing the tests than changing the code." You want to be in the Goldilocks zone, but that comes with experience of knowing what mistakes you and your team tend to make and which ones don't cause a problem. I said I like the "can I comment out a line of code" approach when I'm unsure of my ground, it's a starting place but as I work more in an environment I can come up with better heuristics. David felt that this tuning is different between product teams that are stable rather than consulting teams that are handing the code over to an unknown team and thus need more tests. Kent said that it's good to learn the discipline of test-first, it's like a 4WD-low gear for tricky parts of development.

    David introduced the next issue: many people used to think that documentation was more important than code. Now he's concerned that people think tests are more important than functional code. Connected with this is an under-emphasis on the refactor part of the TDD cycle. All this leads to insufficient energy to refactoring and keeping the code clear. Kent described that he just went through an episode where he threw away some production code, but keeping the tests and reimplementing it. He really likes that approach as the tests tell him if the new code is working. This leads to an interesting question: would you rather throw away the code and keep the tests or vice-versa? In different situations you'd answer that question differently.

    I said I'd found situations where reading the tests helped me understand what the code was doing. I didn't think one was more important than the other - the whole point is the double check where there is an error if they get a mismatch. I agreed with David that I'd sometimes sensed teams making the bad move of putting more energy into the testing environment than in supporting the user, tests should be means to the end. I find I get a dopamine shot when I clarify code, but my biggest thrill is when I have to add a feature, think it will be tricky, but it turns out easy. That happens due to clean code, but there is a distance between cleaning the code and getting the dopamine shot. Kent showed a metaphor for this from Jeff Eastman, that is too tricky to describe in text. He got his rush from big design simplifications. He feels that it's easy to explain the value of a new test working, but hard to state the value of cleaning the design.

    David said we often focus on things we can quantify, but you can't reduce design quality to a number - so people prioritize things that are low on the list like test speed, coverage, and ratios. These things are honey traps, and we need to be aware of their siren calls. Cucumber really gets his goat - glorification of a testing environment rather than production code. Only useful in the largely imaginary sweetspot of writing tests with non-technical stakeholders. It used to be important to sell TDD, but now it's conquered all, we need to explore its drawbacks. I disagreed that TDD was dominant, hearing many places where it's yet to gain traction.


    —Huffduffed by juanangosto

Page 1 of 11Older