Podcasts about XSL

Welcome back to another episode of Building Better Developers. Today, we're tackling an issue that every developer faces at some point: panic during software delivery. Whether it's a critical bug or a new feature that isn't functioning as expected, panic can strike anytime your software fails in the hands of a user. Rob and Michael cover handling software delivery panic with practical tips and real-life examples. Listen to the Podcast on Handling Software Delivery Panic The Inevitable Bug: Why Panic Happens Delivering software is a delicate process. Even when you've thoroughly tested your code and believe it to be bulletproof, something can always go wrong. Often, the panic ensues because: Unexpected User Behavior: Users may interact with the software in ways you didn't anticipate. This is particularly common in beta tests or early releases where feedback is crucial. Overlooked Bugs: Some users have a knack for breaking things. These users often find bugs that slipped through your QA processes. Critical Stakeholders: When a manager, CEO, or client encounters a problem, the stakes feel much higher. Their frustration can quickly escalate to panic. Real-Life Panic: A Case Study on Handling Software Delivery Panic Recently, Rob faced this scenario with a technically knowledgeable customer. Despite understanding the development process, the customer encountered a show-stopping bug in an alpha version. Their immediate reaction was that the project was nowhere near completion, creating a sense of panic. During our call, he expressed concerns that none of the features seemed to work. He acknowledged that bugs and design flaws were expected at this stage, but the issue was so severe that it led to a dramatic loss of confidence in the project. Handling Software Delivery Panic Step 1: Stay Calm and Analyze The first and most crucial step when faced with panic is to stay calm. Take a deep breath and focus on understanding the situation: Reproduce the Issue: Identify the user's steps to encounter the bug. Sometimes, it's as simple as a permission issue or an unanticipated input. Prioritize Fixes: Address the most critical issues first, especially those that block user progress. Step 2: Effective Communication Reassure the stakeholders that you're on top of the situation: Acknowledge the Problem: Validate their concerns and show you understand the impact. Outline the Next Steps: Explain how you plan to fix the issue and provide a realistic timeline. Step 3: Learn and Improve Use this experience to strengthen your development and testing processes: Enhance Testing: Incorporate the steps that led to the bug into your testing scenarios. Automated tests can help catch these issues earlier. Add Logging: Improve logging to gather more information if a similar problem arises in the future. Real-Life Tips from Experience Michael shares an insightful story about a shared work experience. Despite rigorous testing, their boss would find bugs within minutes of a release. This constant scrutiny drove home the importance of thorough testing and the psychological pressure of delivering seemingly flawless code. One key takeaway from Michael's story is the value of Test-Driven Development (TDD). By writing tests before the actual code, you ensure that each function meets the specified requirements. This approach not only catches potential issues early but also clarifies the expected behavior for each part of your application. Practical Advice for Developers Before starting on a new feature or bug fix, consider the following: Clarify Requirements: Ensure you have detailed requirements, including user input constraints and expected outputs. Define Acceptance Criteria: Clearly outline what constitutes a successful implementation. Implement Robust Logging: Log critical operations to simplify debugging and provide insights into any issues that arise. Using Static Code Analysis Tools To Handling Software Delivery Panic SonarQube SonarQube Is a code quality assurance tool that performs in-depth code analysis and generates an analysis report to ensure code reliability. Language Support: Java, JavaScript, C#, PHP, Python, C++, and more. Features: Provides comprehensive code quality and security analysis, integrates with CI/CD pipelines, and offers detailed reports. Strengths: Strong community support, extensive plugin ecosystem, and good integration with various development tools. ESLint ESLint statically analyzes your code to quickly find problems. It is built into most text editors and you can run ESLint as part of your continuous integration pipeline. Language Support: JavaScript, TypeScript. Features: Identifies and reports on patterns in JavaScript, customizable rules, and integration with most text editors and build systems. Strengths: Highly customizable, large number of plugins, and widely used in the JavaScript community. PMD PMD is an extensible multilanguage static code analyzer. It finds common programming flaws like unused variables, empty catch blocks, unnecessary object creation, etc. Language Support: Java, JavaScript, Salesforce Apex, PLSQL, XML, XSL. Features: Detects common coding issues like bugs, unused variables, and performance bottlenecks. Strengths: Simple rule configuration, supports multiple languages, and can be integrated into build tools like Maven and Gradle. PyLint Pylint is a static code analyser for Python 2 or 3. The latest version supports Python 3.8.0 and above. Pylint analyses your code without actually running it. It checks for errors, enforces a coding standard, looks for code smells, and can make suggestions about how the code could be refactored. Language Support: Python. Features: Checks for coding standards, errors, and code smells, provides suggestions for code improvements. Strengths: Highly configurable, integrates well with IDEs and CI/CD pipelines, and widely used in the Python community. Final Thoughts on Handling Software Delivery Panic Panic during software delivery is unavoidable, but it's manageable. By staying calm, communicating effectively, and learning from each incident, you can turn these challenging moments into opportunities for improvement. Remember, every bug is a lesson in disguise, pushing you toward becoming a better developer. That's it for today's episode. We hope these insights help you handle panic more effectively and continue building better software. Until next time, keep calm and code on! Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Code Refactoring: Maintaining Clean, Efficient Code Deciphering Code Chaos: Strategies for Writing Maintainable Code Test-Driven Development – A Better Object Oriented Design Approach Behind the Scenes Podcast Video

An airhacks.fm conversation with Kohsuke Kawaguchi (@kohsukekawa) about: running Family BASIC on Nintendo, learning C++, building abstractions, growing up in Tokyo, a Japanese keyboard, selling shareware programs in high school, writing a Text file viewer, earning 5k per month as a kid, PCs stores in Tokyo, learning chinese, Japanese vs. Chinese characters, building software at university, building an XML editor for XSL, reverse transformation from XHTML to XML, XML schema was lacking mathematical elegance, starting at Sun Microsystems in California, Sun didn't liked SOAP, starting at J2EE / Java EE team, working with James Clark on RelaxNG at Sun Microsystems, implementing Java Architecture for XML Binding / JAXB, Java Project Adelard, Java and XML the evil book at JavaOne, YAML vs. XML, using JAXB for generating JSON, working long hours in Tokyo, working times at Sun Microsystems were almost vacations, being a build breaker, getting the idea for Hudson, Hudson started as a leisure project, Hudson - an executable WAR, Hudson was based on the winstone servlet engine, winstone is embeddable, Hudson installation and administration was easy, software was like another person in the team, Hudson was like a British buttler, writing args4j, writing hk2, exploring native Java integration capabilities, working partially at Glassfish team, being part of Oracle, the forgotten developer at Oracle, forking Hudson to Jenkins, large corporations are not always rational, leaving Oracle and joining CloudBees, becoming a CEO of launchable, starting launchable, the confidence in code changes, using ML to sort tests, GraalVM can run Python, Ruby is popular in Japan, Kohsuke Kawaguchi on twitter: @kohsukekawa, Kohsuke on Wikipedia, and Kohsuke's website

Does "Godlua" Use DNS over HTTPS or Not? https://www.golem.de/news/verschluesseltes-dns-falschmeldung-in-propagandaschlacht-um-dns-ueber-https-1907-142358.html https://blog.netlab.360.com/an-analysis-of-godlua-backdoor-en/ Exploit for Cisco Authentication Bypass and RCE https://raw.githubusercontent.com/pedrib/PoC/master/advisories/cisco-dcnm-rce.txt Magento RCE Exploit https://blog.ripstech.com/2019/magento-rce-via-xss/ Malicous XSL Files https://isc.sans.edu/forums/diary/Malicious+XSL+Files/25098/

Does "Godlua" Use DNS over HTTPS or Not? https://www.golem.de/news/verschluesseltes-dns-falschmeldung-in-propagandaschlacht-um-dns-ueber-https-1907-142358.html https://blog.netlab.360.com/an-analysis-of-godlua-backdoor-en/ Exploit for Cisco Authentication Bypass and RCE https://raw.githubusercontent.com/pedrib/PoC/master/advisories/cisco-dcnm-rce.txt Magento RCE Exploit https://blog.ripstech.com/2019/magento-rce-via-xss/ Malicous XSL Files https://isc.sans.edu/forums/diary/Malicious+XSL+Files/25098/

MC Xsälzbrot aka Dennis und meine Wenigkeit wir kennen uns schon lange. Immer wieder kreuzten sich unsere Wege auf unterschiedlichste Art & Weise. Xsläzbrot ist ein schwäbischer Rapper, der schon einige EP´s gepusht hat. Anfangs noch Mundart Rap machte seine Tracks einzigartig. Nun kommt es auch ab & zu zu Akzentfreien Versen. Wie es zu dem XSÄLZBROT Ding gekommen ist, verrät er in dieser Episode. Reinhören ist Pflicht. MC XSÄLZBROT findet ihr wie folgt: Spotify: https://open.spotify.com/artist/0TCTwjW0Ktfb0LRGOaa5qK?si=XDOE3qQwSTykSeea-1jTAw YouTube: https://m.youtube.com/watch?v=nGIBXmwlZF4#menu Insta: https://instagram.com/mcxsaelzbrot?utm_source=ig_profile_share&igshid=v7tdvemul0di Facebook: https://www.facebook.com/Mc-XsälzbrotNordstadt-connected-210007705734801/ Danke für das Gespräch und viel Erfolg Folge direkt herunterladen

France Baril joins us for this episode of the #InVinoFab podcast where she shares a bit about how she became a digital nomad and what her first year as an entrepreneur was like. France is a DITA/XML documentation architect who helps organizations analyze their content and processes, select tools, learn about DITA and/or XML, manage the change process. She is owner of Architextus where she helps to develop supporting material (from DTDs or schemas to XSL transformations). She has a unique background with a BA in Communication from University of Ottawa and a BSc in Computer Science from Université de Sherbrooke. Over the years she has worn many hats from writer/translator to programmer analyst and product manager.Website: http://architextus.com/ LinkedIn: https://www.linkedin.com/in/francebaril/ We had a brilliant conversation about how tinkering with computers and codes sparked France's interest to get into a technical field from an interdisciplinary background in social science and computer science. She managed to push forward on her career journey by ignoring advisors who doubted the future of computers and combined her talents to enter into technical writing. Although this collaboration is more common now, it was cool to learn about her path to becoming a documentation architect. Much of her work is very transferrable to the things we do for teaching, learning, research, and design in higher education. Additionally, we learn about how she left the cold Canadian winters to be a digital nomad living/working in Panama, Mexico, and France. So of course, we talk about virtual work, relocation, and what to consider if you are considering being remote from work for some or part of the year.“If you have a computer in the house, put it somewhere where every kid can play with it.” ~France BarilHere are a few links and resources of things we talked about in this semi-technical, wine-infused conversation: Beginner's All-purpose Symbolic Instruction Code (BASIC) https://en.wikipedia.org/wiki/BASIC  What is documentation architecture and what does a documentation architect do? http://www.ditawriter.com/what-is-documentation-architecture-and-what-does-a-documentation-architect-do/  TC World Conference 2018 http://www.tcworld.info/  How To Become a Digital Nomad and Travel the World https://www.forbes.com/sites/robertadams/2017/01/20/how-to-become-a-digital-nomad-and-travel-the-world/#21e666391ae4  Digital Nomad Reddit thread https://www.reddit.com/r/digitalnomad/  Nomad list https://nomadlist.com/  The Digital Nomad's Guide to Working from Anywhere on Earth https://www.fastcompany.com/3068312/the-digital-nomads-guide-to-working-from-anywhere-on-e  Thinking about a digital nomadic life? Here are a few suggestions: https://www.entrepreneur.com/article/307252 Tips from France on being a digital nomad: Research Potential Locations: where do YOU want to go? Is it for warmer weather? Do you want to explore another country or part of the world? Know the Work Laws: This will be of your home country AND the new country you plan to travel and work in. This might impact your passport, visa, residency, or requirements that you have to prepare before you go. Get Advice from a Professional: Find an accountant and/or a lawyer. Let the professionals manage your local and foreign tax laws so you understand where and how you will keep things legal as you travel for taxes, visa requirements, limitations for length of stay, etc.  Learn About Residency Restrictions: This could be a restriction on the length of stay, if you can get an apartment, or if you  or even a required work visa if you are working locally. Live Local, Be Local -- this might start online with research, but be sure to get OFFLINE to connect and make professional contacts and colleagues to support your work Culture of Work: Figure out of the work/life balance and lifestyle fits well with your professional life.  Nourish Your Own Professional Learning: Attend conferences, meet up with colleagues, and network with the people you want to learn from who are sharing what is on the horizon for your discipline or industry. We are grateful that France took a break from her holidays in Portugal to share about her experience at a vineyard during her travels. Apparently we need to book a trip to the Douro Valley wine land in Porto ASAP! There's a number of women making wine and taking the lead in this vine region.  --Conversations with Women Winemakers in Portugal's New Douro https://grapecollective.com/articles/conversations-with-women-winemakers-in-portugals-new-douro--The history of port - in brief https://quintadopego.com/the-history-of-port/ --A local's guide to Porto, Portugal https://www.theguardian.com/travel/2018/jan/29/porto-portugal-city-guide-local-guide-cafe-restaurant-hotel --The Douro Valley http://www.dourovalley.eu/en/wine_enoturism Algerian wine: I couldn't find the exact bottle of Algerian wine; however, I did learn about the rise and fall of vino from Algeria to Canada here; https://www.theglobeandmail.com/life/food-and-wine/wine/the-rise-and-fall-of-a-wine-juggernaut-or-why-your-wine-doesnt-come-from-algeria-any-more/article9076845/If you have any sleuthing information about this homework from the pod -- we welcome it and want to hear from you: invinofabulum@gmail.com Thanks!Stay connected to the #InVinoFab Podcast: Hosts: Patrice (@profpatrice) & Laura (@laurapasquini); pronouns: she/her Twitter: https://twitter.com/invinofab Instagram: https://www.instagram.com/invinofab/ 

This keynote will focus on the unique potential offered to web developers - the ability to use the web platform to build compelling applications that reach across different devices, scenarios and environments. In discussing the approaches necessary to deliver great experiences across all these spaces, we will also uncover unique opportunities in a platform that reaches from mobile phones to the biggest display screen in your house. Chris Wilson is a Developer Advocate at Google Inc. He began working on web browsers in 1993 when he co-​​authored the original Windows version of NCSA Mosaic, the first mass-​​market WWW browser. After leaving NCSA in 1994 and spending a year working on the AIRMosaic web browser for SPRY, Inc., he joined Microsoft’s Internet Explorer team as a developer in 1995. Over the course of 15 years, Chris represented Microsoft in many standards working groups, in particular helping develop standards for Cascading Style Sheets, HTML, the Document Object Model and XSL through the W3C working groups. He also developed the first implementation of Cascading Style Sheets in Internet Explorer – the first, in fact, in any mass-​​market web browser. Beginning in 2001, he spent a few years working on the WPF project, but rejoined the IE team in 2004 to lead the IE Platform and Security team, then moved to work on the Javascript engine team in 2009. In 2010, Chris left Microsoft and joined Google’s Developer Relations team, and is currently working on the Google TV project. In his free time, he enjoys photography and hiking with his wife and daughter, and scuba diving in the cool waters of Puget Sound. Occasionally he remembers to share his thoughts on his blog. Follow Chris on Twitter: @cwilso Licensed as Creative Commons Attribution-Share Alike 3.0 (http://creativecommons.org/licenses/by-sa/3.0/).

The long-awaited but barely anticipated 15th episode of Four At The Back is available now, in which Dan Loney and I talk about the USA/Mexico game, Don Garber‘s decade as Commissioner of Major League Soccer, the just-completed “Summer of Soccer” and the future of our little show. Who knew Landon Donovan had Swine Flu? Not... (read more)

So is David Beckham really a bad captain and teammate? And what will happen now that he’s due back in the States soon and will return to his contractually-obligated, short-term-stint MLS career next week against the Red Bulls in New York? Dan Loney and I will discuss that and other topics in the latest episode... (read more)

Back after a week’s vacation, Dan Loney and I pick up with Episode 13 of Four At the Back by looking at the US Nats’ shocking run to the Confederations Cup final, the potential demise of the Xtreme Soccer League and third-round results in the Lamar Hunt US Open Cup, plus we talk to soccer... (read more)

Just our luck – the US pulls off a miracle, and we’re going to be on vacation this week. So no new Four At The Back this time around (sorry), but on the second Four At The Back Extra, we bring you our entire interview with former star goalkeeper and current star analyst Shep Messing.... (read more)

The plight of the National Team, branding Giuseppe Rossi a traitor, the top team in USL-1 and Mount Rushmore redux are the topics on this week’s episode of Four At The Back. Dan Loney and I look at the first two games of the Confederations Cup for the US and ask “What’s next?” Also, Andrew... (read more)

Josh Hakala from usopencup.com and Rob Penner from WPS are our guests on Episode #11 of Four At The Back. We also talk about the US Men’s National Team’s qualifier against Honduras and their prospects in the upcoming Confederations Cup, and, just for fun, ask “Who’s on your Mount Rushmore of American soccer?” Download the... (read more)

Falling between World Cup qualifiers, episode #10 of Four At The Back features discussion of the US Nats’ loss in Costa Rica and a look ahead to the game with Honduras. Also, the best subbuteo player in the country, Zach Walker, is our guest (visit the American Subbuteo Association to find out more about this... (read more)

Shep Messing is our guest on the latest episode of Four At The Back (sorry it took an extra day to get it online – but, hey, you’re not paying for it, so simmer down). We also discuss the US National Team’s upcoming busy summer and ask what can be done about the US Open... (read more)

The Steven Cohen affair, ties in Major League Soccer, proFANity in the stands and an NASL reunion are the topics Dan Loney and I cover on the 8th episode of Four At The Back. In honor of the season finale of American Idol, we even ran a little long this week. Sorry about that. Notes... (read more)

Die Vorlesung führt in die wichtigsten Konzepte von Webdokumenten anhand des Standards XML ein.

Die Vorlesung führt in die wichtigsten Konzepte von Webdokumenten anhand des Standards XML ein.

Dennis Sterzenbach ist heute zu Besuch im Technikwürze-Studio. Themen dieser Sendung sind XML und XSL. Was ist das, wofür nutzt man das und wie wendet man das an?