My presentation at Open Hack Day Bangalore covering the services and products Yahoo offers developers.
My talk at the developer evening at La Cantine in Paris covering all the free services Yahoo offers developers.
My presentation at mashed in London describing the pains I went to to get there and the things Yahoo offers for developers.
A brownbag presentation at IPC media in London about the need to use libraries to make web development much less random and more professional. Get the audio at: http://www.archive.org/details/ProfessionalWebDevelopmentWithLibraries
The Yahoo Developer Network provides APIs and services for many Yahoo products and services, including search, answers, Flickr, and more. It allows developers to access Yahoo's data through RESTful APIs. It also provides tools for mixing and matching data as well as UI frameworks. The document discusses several Yahoo APIs and services that can be used to build applications that incorporate Yahoo data and functionality.
The document summarizes 7 tools that Yahoo provides for web developers to build great user experiences: 1) Yahoo's products are built with a focus on users; 2) patterns and APIs that drive Yahoo's experiences are shared; 3) research on usability and performance is shared; 4) the Yahoo UI library and widgets provide building blocks; 5) tools like YSlow help improve products; 6) YQL provides an easy interface to access web data; 7) the Yahoo search index can be tailored for specific markets. Developers are encouraged to use these free tools and services to build better products and provide feedback to Yahoo.
Presentation for the East London University Hack Day explaining the technologies used to build web interfaces.
1. The document discusses finding and evaluating free software alternatives, providing tips on questions to ask, where to find reviews, licenses and agreements, and safe download locations. 2. It recommends searching sites like Lifehacker, Download Squad, and TechCrunch to find free software and provides examples of free tools for tasks like photo editing, web pages, online storage, and screen sharing. 3. The document stresses the importance of ensuring any software meets needs and system requirements, reading licenses carefully, and only downloading from trusted sources.
This document discusses accessibility and how bringing people together to focus on removing barriers can help move accessibility forward in a meaningful way. It provides examples of how APIs, extensions, and hackathons that focus on understanding different barriers and building solutions can make the web more accessible and improve the experience for all users. The key is finding consensus to push accessibility efforts in the same direction rather than working against each other.
This document provides an introduction to hacking. It defines hacking as "altering a system to do what you want it to do using what is at your disposal" and as having fun innovating and making things do what they weren't designed for. It encourages attendees to build workarounds for things that annoy them using available data feeds, web services, and interfaces. Examples of hacking projects are provided, like enhancing slideshow transcripts to be more accessible and building a service to track Twitter followers. The document promotes hacking as a way to innovate and play that is open to anyone, not just those in technical jobs.
This document discusses hacking and innovation. It defines hacking as solving problems innovatively and describes Hack U as a two day event for uninterrupted coding and innovation. It provides tips for starting a hack such as fixing something used everyday or building something for personal use. Resources mentioned include the Yahoo and GitHub developer sites, YQL for accessing data across services, and YUI for building interfaces. The document encourages attendees to build things that put existing systems together in new ways and to keep their work available for others after the event.
Christian Heilmann gave a talk on hacking and innovation at a university hack challenge. He defines hacking as altering systems to do what you want using available resources, and sees it as a way to have fun and drive unrestrained innovation. He encourages attendees to find something annoying with current systems and build workarounds. To hack effectively, one needs access to data sources, the data itself, and ways to reach users. He provides examples of his own hacks that make systems more accessible or filter data for specific uses. The talk aims to show attendees their potential and get feedback on explanations of development resources.
Presentation at the Geekmeet in Craiova, Romania talking about the adoption of APIs and libraries as a way to prevent unmaintainable products.
This document provides tips and information for participating in a hackathon event called HackU. It discusses what hacks and hacking involve, including developing innovative solutions to real-world problems quickly. Tips are provided for having a successful hack, such as choosing the right tools, sourcing data, tackling difficult problems first, and practicing your pitch. The document also outlines the schedule for HackU and how hacks will be judged, emphasizing the development of a working prototype that solves a real problem creatively. Resources for hacking are shared, such as developer platforms and tools.
Share with college students about how FirefoxOS development works and the procedure and resource to contribute to FirefoxOS
Presented June 8, 2012 (Online) at the 'Access by Touch: Delivering Library Services Through Mobile Technologies' conference sponsored by Amigos Library Services. Description: By the end of 2012, it is expected that more than 80% of the world’s population will have access to a smartphone. Your library users will assume that your library can be accessible from anywhere, at any time, and on any device. Now is the time to be ready! During this webinar, you will: - learn what a mobile framework is. - acquire best practices in mobile Web development. - understand the various technologies (HTML, CSS, JavaScript) and how they work together to build mobile Web apps. - recognize the differences between native and web apps. - have an opportunity to continue to work with Chad after the webinar to demonstrate what you learned. - gain access after the webinar to a free Web server so you can see your mobile Web app live.
Updates about the OpenSocial ecosystem at Google developer days Munich, including presentations from Xing, Lokalisten, netlog and Viadeo.. OpenSocial is an open specification defining a common API that works on many different social websites, including MySpace, Plaxo, Hi5, Ning, orkut, Friendster Salesforce.com and LinkedIn, among others. This allows developers to learn one API, then write a social application for any of those sites: Learn once, write anywhere. In addition, in order to make it easier for developers of social sites to implement the API and make their site an OpenSocial container, the Apache project Shindig provides reference implementations for OpenSocial containers in two languages (Java, PHP). Shindig will define a language specific Service Provider Interface (SPI) that a social site can implement to connect Shindig to People, Persistence and Activities backend services for the social site. Shindig will then expose these services as OpenSocial JavaScript and REST APIs. In this session we will explain what OpenSocial is, show examples of OpenSocial containers and applications, demonstrate how to create an OpenSocial application, and explain how to leverage Apache Shindig in order to implement an OpenSocial container.
The document discusses the Yahoo! User Interface (YUI) library and how the author initially dismissed it as bloated but came to appreciate its benefits for collaboration, cross-browser compatibility, and providing robust reusable components. It provides an overview of the key features of YUI including components for DOM manipulation, events, animation, AJAX, and design patterns. It encourages developers to use YUI APIs in their hacks and provides resources for getting started.
We are obsessed with coding and creating automated workflows and optimisations. And yet our final products aren't making it easy for people to use them. Somewhere, we lost empathy for our end users and other developers. Maybe it is time to change that. Here are some ideas.
This document discusses ways to improve how web developers learn best practices through browser and tooling improvements. It suggests that linting and inline insights directly in code editors could help prevent mistakes by flagging issues early. A tool called webhint is highlighted that provides one-stop checking and explanations of hints related to performance, accessibility, security and more. The document advocates for customizing hints based on a project's specific needs and environment. Overall, it argues for accelerated learning through context-sensitive, customizable best practices integrated into development workflows.
This document discusses privilege in the context of social media and the internet. It acknowledges privileges like internet access, the ability to communicate, and supportive online communities. It warns that machine learning and algorithms risk creating echo chambers and guided messaging if they are not kept in check by human curation. The document advocates taking back the web for decent, thinking and loving humans and using privileges to help others gain access to learning, communication, and communities.
JavaScript is a bigger world than a language these days. Time to take stock and find happiness in that world.
This document discusses artificial intelligence and how it can help humans. It covers that AI is not new, having originated in the 1950s, and is now more advanced due to increased computing power. It also discusses how AI utilizes pattern recognition and machine learning. The document then covers several applications of AI including computer vision, natural language processing, sentiment analysis, speech recognition/conversion and moderation. It notes both the benefits of AI in automating tasks and preventing errors, as well as the responsibilities of ensuring transparency and allowing people to opt-in to algorithms.
The document discusses concerns about the perception and realities of coding careers. It expresses worry that coding is seen solely as a way to get a job rather than as a means of problem-solving. While coding can provide fulfilling work, the document cautions that the need for coders may decrease with automation and that the role may evolve from coding to engineering. It suggests a future where machines assist with repetitive coding tasks and people focus on delivering maintainable, secure products with attention to privacy and user experience.
PWA are a hot topic and it is important to understand that they are a different approach to apps than the traditional way of packaging something and letting the user install it. In this keynote you'll see some of the differences.
This document discusses privilege in technology and perceptions of technology workers. It acknowledges the privileges that tech workers enjoy, such as access to resources and high demand in the job market. However, it also notes problems like peer pressure, lack of work-life balance, and imposter syndrome. Both tech workers and the public have skewed perceptions of each other - tech workers feel others do not appreciate or understand their work, while the public sees tech workers as antisocial or caring only about profit. The document encourages taking small steps to improve the situation, such as being kind to oneself, considering others, sharing knowledge, and focusing on quality over quantity of work.
The document provides five ways for JavaScript developers to be happier: 1) Concentrate on the present and focus on creating rather than worrying about the past or future. 2) Limit distractions by streamlining your development environment and using an editor like VS Code that consolidates features. 3) Make mistakes less likely by using linters to catch errors as you code. 4) Get to know your tools better like debuggers to avoid console.log and gain insights to build better solutions. 5) Give back to others in the community by being helpful rather than causing drama.
The document discusses progressive web apps (PWAs) and provides suggestions for improving them. It notes that while PWAs aim to have engaging, fast, integrated, and reliable experiences like native apps, they still have room for improvement in areas like speed, integration, and reliability. It emphasizes that PWAs should adhere to web best practices and provide actually useful experiences rather than just focusing on technical features. The document encourages helping the PWA effort by providing feedback, using and contributing to tools, keeping messaging up-to-date, and promoting high-quality examples.
Chris Heilmann gave a talk at BTConf in Munich in January 2018 about machine learning, automation worries, and coding. He discussed how coding used to refer to creative programming within technical limitations but now often refers to programming for work. He addressed common worries about new technologies and dependencies, and argued that abstractions are not inherently bad and help more people build products together through consensus. The talk focused on using tools to be more productive and enabling rather than seeing them as dangers, and creating solutions for users rather than fighting old approaches.
The document provides advice and encouragement for someone starting out with JavaScript development. It discusses how JavaScript can be used in many environments like browsers, apps, and servers. It recommends resources like MDN and tools like linting to help avoid mistakes. It emphasizes that this is an exciting time for JavaScript and advises setting priorities and standards, being involved in the community, and bringing new voices and perspectives.
Keynote at halfstackconf 2017 discussing the falsehood of the idea that in order to survive the automation evolution everybody needs to learn how to code. Machines can code, too.
Progressive Web Apps (PWAs) can provide app-like experiences through the web by making web content fast, reliable and engaging. While PWAs may not be necessary for all projects, they can help clean up and speed up current web-based projects. PWAs leverage new web capabilities like service workers to work offline, load fast, and improve the user experience without having to meet all the requirements of native apps.
This document discusses progressive web applications (PWAs) and their advantages over traditional native mobile applications. PWAs use modern web capabilities like Service Workers to deliver native-like experiences to users. Some key benefits of PWAs include their ability to work across platforms, have smaller file sizes for faster loading, support offline use, and provide simple update mechanisms compared to native apps. While PWAs do not have full access to device capabilities like native apps, they allow delivering app-like web content to users in a more accessible and reliable manner than traditional web pages.
Keynote at PNWPHP covering Machine Learning and How we should go about using it to build human interfaces.
This document discusses progressive web apps (PWAs). It notes that PWAs aim to make web apps feel like native mobile apps by being discoverable, installable, linkable, safe, responsive and progressive. The document outlines some key characteristics of PWAs, including that they need to be served from secure origins and have app manifests. It also discusses some common misconceptions around PWAs and notes that as PWAs improve, they will continue to blur the line between web apps and native mobile apps.
This document discusses the differences between CSS and JavaScript and when each is most appropriate to use. It argues that CSS is often underestimated in favor of JavaScript solutions. CSS has advanced significantly with features like calc(), media queries, animations/transitions, flexbox, grid, variables and more. These powerful features allow many tasks to be accomplished with CSS alone without needing JavaScript. The document encourages embracing the "squishiness" of the web and considering CSS more when building interfaces.
This document contains the transcript of a presentation by Chris Heilmann on web development. Some of the key points discussed include: - The benefits of progressive enhancement and using HTML, CSS, and JavaScript together to build robust and accessible websites. - How limitations in early design can foster creativity. - The importance of error handling and defensive coding practices. - Embracing new technologies like Service Workers and Manifests to build Progressive Web Apps. - Rethinking the idea that JavaScript is unreliable and should not be depended on, as modern browsers have made it a capable tool.
The document discusses how machines and software can help humans by doing tasks like preventing mistakes, performing repetitive tasks, filling information gaps, remembering and categorizing information, improving understanding, enabling new communication methods, and providing protection. It describes how advances in AI, APIs, cloud services, and data processing have made it possible to build useful and helpful interfaces. The conclusion encourages developers to use these capabilities to create simple, human-centric interfaces that benefit users.
Everything that I found interesting last month about the irresponsible use of machine intelligence
Have you noticed the OpenSSF Scorecard badges on the official Dart and Flutter repos? It's Google's way of showing that they care about security. Practices such as pinning dependencies, branch protection, required reviews, continuous integration tests etc. are measured to provide a score and accompanying badge. You can do the same for your projects, and this presentation will show you how, with an emphasis on the unique challenges that come up when working with Dart and Flutter. The session will provide a walkthrough of the steps involved in securing a first repository, and then what it takes to repeat that process across an organization with multiple repos. It will also look at the ongoing maintenance involved once scorecards have been implemented, and how aspects of that maintenance can be better automated to minimize toil.
If you’ve ever had to analyze a map or GPS data, chances are you’ve encountered and even worked with coordinate systems. As historical data continually updates through GPS, understanding coordinate systems is increasingly crucial. However, not everyone knows why they exist or how to effectively use them for data-driven insights. During this webinar, you’ll learn exactly what coordinate systems are and how you can use FME to maintain and transform your data’s coordinate systems in an easy-to-digest way, accurately representing the geographical space that it exists within. During this webinar, you will have the chance to: - Enhance Your Understanding: Gain a clear overview of what coordinate systems are and their value - Learn Practical Applications: Why we need datams and projections, plus units between coordinate systems - Maximize with FME: Understand how FME handles coordinate systems, including a brief summary of the 3 main reprojectors - Custom Coordinate Systems: Learn how to work with FME and coordinate systems beyond what is natively supported - Look Ahead: Gain insights into where FME is headed with coordinate systems in the future Don’t miss the opportunity to improve the value you receive from your coordinate system data, ultimately allowing you to streamline your data analysis and maximize your time. See you there!
Recent advancements in the NIST-JARVIS infrastructure: JARVIS-Overview, JARVIS-DFT, AtomGPT, ALIGNN, JARVIS-Leaderboard
Sustainability requires ingenuity and stewardship. Did you know Pigging Solutions pigging systems help you achieve your sustainable manufacturing goals AND provide rapid return on investment. How? Our systems recover over 99% of product in transfer piping. Recovering trapped product from transfer lines that would otherwise become flush-waste, means you can increase batch yields and eliminate flush waste. From raw materials to finished product, if you can pump it, we can pig it.