Killing the golden calf of coding - We are Developers keynote

DevDay (http://devday.pl), 20th of September 2013, Kraków Video at http://www.youtube.com/watch?v=L4eTOvq2WmM&feature=c4-overview-vl&list=PLBMFXMTB7U74NdDghygvBaDcp67owVUUF

Most software development processes are focused on tracking and delivery. Unfortunately, writing code is no longer the bottleneck. The real bottleneck is the team ability to learn about the domain complexity and do the right thing.

This document discusses key concepts for building high-performing systems, including DevOps, microservices, and organizational culture. It emphasizes that technology choices influence culture and that culture is a key factor in performance. Bounded contexts, loosely coupled systems, and alignment of goals across teams and over the long term help promote autonomy, mastery, and a clear sense of purpose. Feedback loops and organizational structures should support seeing the impact of work, learning from mistakes, and continually improving.

1) EventStorming is a technique that uses modeling with sticky notes, markers and paper to surface domain events and capture hotspots in a system. It enables cross-perspective conversations and can lead to unexpected insights. 2) Analyzing bottlenecks is important because most bottlenecks are found in business processes, policies, user interfaces and read models. However, simply documenting a bottleneck may not solve the problem, as organizational culture and emotions also influence whether issues are actually addressed. 3) When modeling legacy systems, it is important to identify bounded contexts and focus modeling and improvements within safer contexts first to minimize risk. Addressing technical issues alone may not be enough, as unaddressed cultural and emotional aspects can hinder

The document discusses various topics related to visual design for developers including layout, images and icons, colors, typography, and feedback. It provides examples and recommendations for each topic. Some key points covered include using whitespace for emphasis, following design principles like the golden ratio, using consistent and recognizable icons, establishing a color scheme, experimenting with different fonts and weights, and getting feedback through usability testing. The overall message is that visual design is important for products and that developers should learn design principles to create attractive interfaces that work better.

This document discusses principles of design and provides tips for creating effective designs. It covers topics like layout, images, color, typography, and feedback. Key points include that attractive designs work better because they create emotional reactions and meet users' expectations. Design is presented as similar to coding, involving patterns, practices, and feedback cycles. Junior and senior designers are compared, with senior designers able to emphasize appropriately and drive user attention. Specific design tips are provided around whitespace, emphasis, the golden ratio, rounded vs square elements, consistency, and optimizing images. Color theory basics and creating engaging typography are also outlined. The importance of usability testing and not just asking for likes is emphasized.

This document summarizes Matt Stine's presentation on the seven wastes of software development based on lean manufacturing principles. The seven wastes are: partially done work, extra processes, extra features, handoffs, delays, task switching, and defects. Stine provides examples of each waste and solutions to eliminate them, such as limiting work in progress, continuous integration, avoiding handoffs, minimizing task switching, and early defect detection. The goal is to reduce non-value adding activities and continuously improve productivity and quality.

The document provides tips for surviving a hackday event. It begins with defining what a hacker is, noting that hackers are passionate technologists who build solutions to real problems. It then lists 15 tips for hackday survival, including knowing the schedule, scratching your own itch by solving problems you face, building a team, choosing tools, asking for help, learning new skills, preparing for issues, practicing your demo, and staying memorable. The overall message is that hackdays are opportunities to be creative and build things while learning from others in the developer community.

Practical tips for Digital Designers - Corporate Innovation Summit Bangkok March 28-29 Centara Grand at Central World.

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.

My closing talk for this year's Fronteers conference in Amsterdam, the Netherlands about just how cool it is to be someone who builds things for the web.

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.

This document provides advice and recommendations from an expert on various topics related to web development and Drupal. Some of the key points covered include: - Testing, especially automated testing, is very important for quality assurance and maintaining reliability. Simplicity is also important for reliability. - Small teams and clients are preferable to large ones, as they have less bureaucracy, noise and agendas interfering with objectives. - Planning is essential, especially software architecture planning, but plans will change over time as the project evolves. - Tools like Ansible, PHPQA tools, Robo, and JetBrains PHPStorm can help with tasks like provisioning, testing, deployment and development. Drupal tools like Drush

My presentation from InfoShare 2016 conference. For many years I was a software developer. I would concentrate on the code, software projects and the interactions with my closes team and the users. I was sure that Agile solves all world’s problems. I would laugh over Scott Adam’s Dilbert comics with his Point Hair Boss. Life was simple, life was good. Now for 8+ years I have been running a software company, not a small one anymore. I became myself a full-time boss who only codes sometimes at home or during hackathons. This session is about sharing with you those critical lessons which I painfully learnt when trying to grow into this new role - transitioning from being a software engineer into being an entrepreneur and top manager. Wheres not all of the lessons may or will (if you dream about your own startup) apply to your case, being aware of them may save you tons of time, energy, money or even help you to avoid the total disaster - burying your own company or dreams. And after all, sharing war stories from the past is fun … when these stories are the past.

Whether you like it or not, JavaScript is here to stay and has evolved from a fringe programming language to the most used one in our market. Its versatility both in use and in dealing with syntax are reasons why that is the case and why some people have a hard time getting their head around it. In this talk you'll learn a few tricks and ideas how you can cast aside your dislikes and worries and find a way to embrace the wild world of JavaScript.

This document discusses progressing web development and applications. It talks about some common criticisms of the web, including that browsers differ too much and the web is too flexible. However, it argues that browser differences allow for innovation and flexibility is one of the web's strengths. It promotes an approach of focusing on capabilities rather than browsers. The document also discusses progressing technologies like service workers and progressive web apps that can make applications work offline and feel more like native apps while still being web-based. It concludes by arguing the web is not going away and is a great platform to build upon.

Although DevOps practices have gained wide adoption across industries, many organizations are still failing in their digital transformation efforts because they focus on tools over people and processes. You can avoid this trap by providing DevOps as a platform that is built and maintained by experts who provide standardized tools, templates, and processes to teams across the organization—regardless of those teams’ roles within the company, the type of applications or environments they work with, or the software delivery patterns they’ve adopted. A centralized DevOps platform allows developers to leverage predefined delivery processes, so they don’t have to reinvent the wheel to get their apps into Production. It also helps ensure the right processes are followed and the right people are involved at the right times. A DevOps platform can provide both technical users and business stakeholders with end-to-end visibility into the software delivery process—promoting information sharing and collaboration across the organization. Learn how to successfully implement a DevOps platform in your organization, so that every team gets the tools, templates, and visibility they need to deliver software faster than ever before.

My presentation from Devoxx Poland 2016 conference - the newest, slightly revised version. For many years I was a software developer. I would concentrate on the code, software projects and the interactions with my closes team and the users. I was sure that Agile solves all world’s problems. I would laugh over Scott Adam’s Dilbert comics with his Point Hair Boss. Life was simple, life was good. Now for 8+ years I have been running a software company, not a small one anymore. I became myself a full-time boss who only codes sometimes at home or during hackathons. This session is about sharing with you those critical lessons which I painfully learnt when trying to grow into this new role - transitioning from being a software engineer into being an entrepreneur and top manager. Wheres not all of the lessons may or will (if you dream about your own startup) apply to your case, being aware of them may save you tons of time, energy, money or even help you to avoid the total disaster - burying your own company or dreams. And after all, sharing war stories from the past is fun … when these stories are the past.

[Originally Polish lecture with English slides - with a few exceptions] Przez wiele lat byłem software developerem. Koncentrowałem się na kodzie, projektach software'owych oraz interakcjach w moim zespole i z klientami. Byłem pewny, że Agile rozwiązuje wszystkie problemy tego świata. Śmiałem się z komiksów Scotta Adamsa i stworzonej przez niego karykatury szefa (PHB). Życie było proste i piękne... Teraz od ponad 8 lat prowadzę firmę software'ową, którą przy blisko 90 osobach trudno już nazwać maleństwem. Sam stałem się "szefem" na pełen etat. Podczas prezentacji podzielę się z Wami różnymi doświadczeniami oraz naukami (nieraz bolesnymi) jakie wyniosłem w ostatnich latach podczas mojej stopniowej przemiany z developera/inżyniera w przedsiębiorcę i szefa firmy. O ile zapewne nie wszystkie sytuacje i wnioski mają lub mogą mieć (o ile marzysz o własnym startupie czy zespole) zastosowanie w Twoim życiu, same sobie ich uświadomienie może oszczędzić Ci w przyszłości straty mnóstwa czasu, energii i pieniędzy oraz uniknąć przykrych rozczarowań.

On this era of industrial changes, we all know that software is eating the world, and the world is small, or at least, not so big. So how to manage to make great technical choices on this era where giants apply the marketing of the Shame on us? How do we keep best developper in our organisation when it's a furious competition on hiring out there? More important, how do we make sure people we work with are both happy and productive? Beyond marketing, we will try to figure out how we do to compete and create value for us and our users.

JavaScript is a bigger world than a language these days. Time to take stock and find happiness in that world.

The document discusses several topics related to technology disruption and advancement. It begins by predicting that in 2018, companies will continue to struggle with security operations center deployments, incident response, and log fatigue. It also predicts that skills gaps in security will deteriorate further and that phishing attacks will remain common. The document goes on to discuss the lack of accountability and consumer rights issues with the technology industry. It raises concerns about vendor lock-in effects from increased API and cloud integration.

Slides from my DevOpsExpo London talk "From oops to NoOps". They tell you in these conferences that DevOps is not about tools, but about culture. And they are partially right. I am going to tell you that it’s not only about culture or tools but also abstractions. It is a lot about how you see software and its value. About our mental model of what software is: how it runs, evolves, and interacts with the other facets of an enterprise. We used to view software as code. As a state of code. Now we think about software as change, as a flow. A dynamic system where people, machines, and processes interact continuously. At Platform.sh we spend a bunch of time asking ourselves not “How do you build?” - or even “How do you build consistently?” - but rather “What does it mean to consistently build in a world where change is good?” A world that lets you push security fixes into production as soon as they’re available because you don’t want to be an Equifax but you do want stability. In this presentation, I will go over what we think software is and why having the right ideas about software will help you get your culture right and your tooling aligned, as well as gain in productivity, and general happiness and well-being.

Mr. Hani Hmede delivered a lecture with PMI Lebanon Chapter in December 2019 about: I, the project manager - the rise of artificial intelligence in the world of project management.