Sacrificing the golden calf of "coding"

The document discusses ways to work smarter in software development. It argues that many current practices are "unsmart" and promotes an agile, lightweight approach focused on the essentials. It emphasizes that software is developed by people and that processes should focus on what is most useful to teams rather than following templates or models rigidly. The key to becoming smarter is continuous learning from diverse sources and improving work in small, incremental steps.

This document discusses an incremental approach to implementing CLM projects. It notes that project teams typically learn important lessons too late: whether the team can complete the work (along the way), technical flaws in their ideas (toward the end), accurate costs (at the end), and whether they built the right thing (unfortunately, last). It proposes breaking the work into questions to accelerate learning about the right scope, costs, teamwork, and assumptions through early prototyping, user feedback, and delivery. The goal is to trim the tail of late learning and get better results.

The document discusses the disadvantages of an anemic domain model, where business logic is separated from the domain objects, making the model hard to maintain, test, and prone to duplication. It also suggests that a domain model should contain behavior, use the ubiquitous language, define aggregates as consistency boundaries, and protect the model with bounded contexts.

This document discusses the themes of lifelong learning, teaching, and work in the digital age. It notes that in pre-industrial times, education and work were observable and connected, but in the post-industrial era they became non-observable and disconnected. However, with technologies like web publishing and digital media, some teaching and work is now observable and connected online through blogs, videos, and digital sharing of processes. The document advocates for students to become lifelong teachers and learners who produce educational content and courseware to spread knowledge through network effects.

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.

Presentation at the Geekmeet in Craiova, Romania talking about the adoption of APIs and libraries as a way to prevent unmaintainable products.

This document outlines the process of industrializing an open source software and selling it as a product. It discusses securing the intellectual property of the code, improving development practices through version control, continuous integration, testing and documentation. It also covers challenges of determining customer needs when no existing market exists, balancing innovation and technical capabilities with market demands, and the importance of user satisfaction over technical features alone. The conclusion reflects on how research labs can foster innovation and how 13 jobs have been created by building a company around code originally developed through academic research.

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.

The document discusses various topics related to developing a technology product, including hiring an engineering team, creating a product, technical development challenges, and setting up processes. It provides advice on tuning your setup by considering human resources, available technologies, tools, and processes. It discusses common pitfalls and emphasizes focusing on users and testing. Technical concepts discussed include infrastructure, programming languages, servers, APIs, storage, desktop development, and mobile development.

When going into the development of a software product, a possible source of mistake is the incorrect evaluation of the complexity that lies behind an idea , as well as a clutter coming from the massive amounts of technologies enabled. This presentation explains a possible way to deal with such issues.

As a Software Architect and consultant I designed software with some artefacts in mind. As an entrepreneur I found myself on the other side of the fence. I'd improve distribute holistic knowledge through EventStorming and Domain-Driven Design rather than partition the system with User Stories.

This document discusses rethinking approaches to enterprise software development. It argues that learning is the primary constraint in software development, not coding or waiting, as learning is non-linear and can't be estimated with traditional models. It advocates using approaches like event storming and domain-driven design to facilitate collaborative learning between developers and domain experts, and developing loosely coupled architectures using techniques like CQRS and event sourcing to reduce organizational complexity and dependencies. The overall message is that there needs to be a model for enterprise software that better facilitates ongoing learning within development teams.

A recap of interesting points and quotes from the May 2024 WSO2CON opensource application development conference. Focuses primarily on keynotes and panel sessions.

Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1fjTxvB. Trisha Gee and Todd Montgomery attack the technology industry’s sacred cows by exposing the motivations that hide behind them. They discuss how these motivations lead us into practices that hinder rather than help us deliver quality software. Also, they discuss why some organisations seem to be achieving things that the traditional corporate IT departments can only dream of. Filmed at qconnewyork.com. Todd Montgomery is Ex-NASA researcher, Chief Architect at Kaazing. Trisha Gee is Java Champion and Engineer.

My presentation covering several ways how you can use nowaday's free web offers to save money and time for your company and thus securing your job.

Dans cette présentation, Chris Heilmann nous parlera des problèmes liés à l'adoption de standards du web récents, et décrira des façons de contourner ces difficultés. Un exemple simple est le manque de prise en charge native de l'audio et de la vidéo, et les problèmes des implémentations actuelles. La session illustrera concrètement comment régler des problèmes a priori sans solution en les attaquant sous un autre angle. Il s'agit essentiellement de trouver une façon pragmatique de vendre, implémenter et utiliser les standards plutôt que d'attendre que le marché adopte des technologies dont l'utilisation devrait être d'une évidence complète. Présentation originale : http://www.slideshare.net/cheilmann/working-in-the-now-presentation/

The document discusses the emerging role of social software within IBM and its use to foster collaboration and innovation. It outlines IBM's transition to more informal and open culture and describes various social tools and platforms adopted by employees, from internal instant messaging and blogs to experimental uses of metaverse environments and reputation systems. It highlights IBM's Technology Adoption Program for encouraging early adoption of new tools and sharing of internally developed solutions.

My keynote talk at the 2007 IA Konferenz in Stuttgart, Germany, I argued we need to create fewer final designed artifacts and more tools to help everyone design. The audio can be downloaded from here: http://www.iavoice.com/2007/11/27/ia-konferenz-2007-keynote-english/

The document discusses the author's path from working on smaller open source projects like libwpd to becoming a mentor for Google Summer of Code with OpenOffice.org. Some challenges of contributing to OpenOffice.org included its complex codebase and lengthy build times. The author advocates improving modularity, providing coaching for new developers, and streamlining contribution processes.

Greg Sheremeta Red Hat - Senior Software Engineer POSSCON 4/14/2015 Open 101 Track - 1:00 PM Talk

This document discusses ways to raise the bar of software development by combining it with other disciplines. It proposes 6 intersections between software design and other fields: 1) Software Design and UX, 2) Other design disciplines, 3) Materials Science, 4) Math, 5) Engineering principles of built-in self-testing, and 6) Reaching out to scientists. It argues that considering ideas from other domains could improve software design and help address challenges like dependencies in legacy code. The document also suggests ways to fundamentally change development by precisely defining requirements and generating code from them.

The document discusses various topics related to analysis and design processes including front-end analysis, analysis paralysis, evaluation models, performance analysis quadrants, agile development principles, flashcard software options, and open source development practices. It provides resources and information on needs assessment, instructional design, project management, and software development.

1. The document summarizes a keynote presentation on whether Python is still production ready. 2. It discusses that Python has evolved significantly since its creation in 1990 to better support modern programming patterns like asynchronous programming. 3. It argues that Python can be considered "production ready" because it has a large community and ecosystem that helps reduce maintenance costs, libraries are well documented and tested, and the language continues to be improved while maintaining backwards compatibility.

Javantura v7 - Learning to Scale Yourself: The Journey from Coder to Leader - Daniel Strmečki Your success depends on others, a 1-man army can only achieve so much. The only way to progress from coder to leader is to learn how to scale yourself. Nowadays, you can become a Senior Developer with just a few years of experience. After that, there are many roads and possibilities you can take. Whether you decide for a developer, architect, manager or a mixed career, at one point, you will need to become a leader. In the first chapter of the lecture we will start a discussion on how to get there. Since your time is limited, you need to mentor, coach, motivate and engage others. Start with making a stable foundation, like setting up a proper onboarding process. If you help people around you, they will for sure talk about it, and your manager will hear it. Also, demonstrate ability in everyday work: coding, project management, client-focus, communication and care about others. Always stick to your values and keep high standards. In the second chapter we will discuss the challenges that turn up once you get there. At that point you will deal with people more than technology. You will need to step away from coding for meetings very often. Interruptions will happen every day and it we be very hard to maintain “the flow”. You will need to learn how to delegate and drive topics without implementing them yourself. Visit the lecture to find out some techniques for dealing with interruptions, meetings, prioritization, people and their motivation.

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.

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.

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.

“If Tetris has taught me anything, it’s that errors pile up and accomplishments disappear” is a common quote and it seems we’re living this to its full extend as web developers. We fail to celebrate the successes we have and the tools that are at our disposal but we’re never short of finding reasons why things don’t work. We also tend to pile on technology on technology to solve problems that may actually not exist and thus clog up the web. In this talk Chris Heilmann wants to remind us what we achieved and how we should celebrate it and how we should stop trying to solve problems that are simply beyond our control.

The document discusses the challenges facing the progressive web and introduces progressive web apps (PWAs) as a solution. PWAs are built using modern web standards to provide native app-like experiences through features like push notifications, offline support, and app installation. They address issues with native apps like high installation friction, lack of control for publishers, and app store policies. PWAs are gaining adoption from companies like Alibaba and Housing.com who saw increases in user engagement metrics after implementing PWAs. The document outlines the core components of PWAs and provides an overview of browser and platform support.

Microsoft has become more open in recent years by open sourcing many products, making products cross-platform, and making training materials openly available. This open approach makes business sense for Microsoft as it attracts developers, allows employees flexibility, and taps into outside skills. Examples of Microsoft's success with open source include the Edge browser, Visual Studio Code editor, TypeScript transpiler, and ChakraCore JavaScript engine. The presenter encourages attendees to help promote Microsoft's open products and projects through conference talks, writing, and contributing translations and code.

This document provides tips for becoming an effective conference presenter. It discusses finding a topic to present on, writing a proposal to submit to conferences, creating presentation materials, writing the presentation, and delivering the presentation. The key steps covered are finding an exciting topic, researching it, crafting a compelling proposal, developing slides and other visual aids to enhance the story and message, writing the presentation to have a clear structure and narrative arc, and practicing delivery techniques to engage the audience. The overall goal is to give attendees a memorable experience that leaves them feeling they learned something valuable.

Pie

Configuring Single Sign-On (SSO) via Identity Management | MuleSoft Mysore Meetup #48 Event Link:- https://meetups.mulesoft.com/events/details/mulesoft-mysore-presents-configuring-single-sign-on-sso-via-identity-management/ Agenda ● Single Sign On (SSO) ● SSO Standards ● OpenID Connect vs SAML 2.0 ● OpenID Connect - Architecture ● Configuring SSO Using OIDC (Demo) ● SAML 2.0 - Architecture ● Configuring SSO Using SAML 2.0 (Demo) ● Mapping IDP Groups with Anypoint Team (Demo) ● Q & A For Upcoming Meetups Join Mysore Meetup Group - https://meetups.mulesoft.com/mysore/YouTube:- youtube.com/@mulesoftmysore Mysore WhatsApp group:- https://chat.whatsapp.com/EhqtHtCC75vCAX7gaO842N Speaker:- Vijayaraghavan Venkatadri:- https://www.linkedin.com/in/vijayaraghavan-venkatadri-b2210020/ Organizers:- Shubham Chaurasia - https://www.linkedin.com/in/shubhamchaurasia1/ Giridhar Meka - https://www.linkedin.com/in/giridharmeka Priya Shaw - https://www.linkedin.com/in/priya-shaw

for educational purposes only

Principles of Rood’s Approach Treatment technique used in physiotherapy for neurological patients which aids them to recover and improve quality of life Facilitatory techniques Inhibitory techniques

Front desk officers are responsible for taking care of guests and customers. Their work mainly involves interacting with customers and business partners, either in person or through phone calls.

"DANH SÁCH THÍ SINH XÉT TUYỂN SỚM ĐỦ ĐIỀU KIỆN TRÚNG TUYỂN ĐẠI HỌC CHÍNH QUY NĂM 2024 KHỐI NGÀNH NGOÀI SƯ PHẠM"

...

Presented as a plenary session in iTELL 2024 in Salatiga on 4 July 2024. The plenary focuses on understanding and intepreting relevant TPACK competence for teachers to be adept in teaching multimodality in the digital age. It juxtaposes the results of research on multimodality with its contextual implementation in the teaching of English subject in the Indonesian Emancipated Curriculum.

Reading Presentation

Howe Writing Center - Orientation Summer 2024

 Integrated Marketing Communications (IMC)- Concept, Features, Elements, Role of advertising in IMC  Advertising: Concept, Features, Evolution of Advertising, Active Participants, Benefits of advertising to Business firms and consumers.  Classification of advertising: Geographic, Media, Target audience and Functions.

eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

NLC Lessons Grade 10