Podstawy Google Tag Managera, czyli dlaczego warto korzystać, co się na niego składa, jak rozwiązywać ewentualne problemy + kilka zaawansowanych technik.
Prezentacja pomocnicza, pokazywana podczas spotkania z cyklu Web Analytics Wednesdays.
This document discusses challenges in software maintenance and ways to improve the process. It notes that changes in business requirements will lead to changes in development. Maintaining software is about maximizing return on investment by meeting stakeholder goals. Lack of proper communication between business and development teams and moving too quickly can result in technical debt and bugs. The document recommends focusing on simplicity, continuous deployment, automation, monitoring, and ensuring the IT department is viewed as a partner rather than secondary to improve maintenance.
The document provides an overview of common reasons for IT project failures based on research findings. It discusses that 75% of business and IT executives anticipate software project failures and fewer than a third of projects are completed on time and on budget. Around 33% of projects meet failure due to lack of senior management involvement. The document also shares testimonies from failed startups about reasons like not scaling fast enough, being dependent on another platform, and running out of money too soon. It emphasizes the importance of communication, avoiding fast development that leads to technical debt, getting developer feedback, and having a product roadmap built by the whole team to achieve common goals and understanding.
This document discusses code quality and metrics tools that can be used to analyze code and detect code smells and anti-patterns. It introduces NDepend and Code Maat as tools that can measure code metrics, analyze code dependencies, detect code issues, and visualize changes over time. The document also provides examples of analyzing a codebase with these tools to identify hot files, module ownership, author contributions, and other insights that can help improve code quality.
Podstawy Google Tag Managera, czyli dlaczego warto korzystać, co się na niego składa, jak rozwiązywać ewentualne problemy + kilka zaawansowanych technik.
Prezentacja pomocnicza, pokazywana podczas spotkania z cyklu Web Analytics Wednesdays.
This document discusses challenges in software maintenance and ways to improve the process. It notes that changes in business requirements will lead to changes in development. Maintaining software is about maximizing return on investment by meeting stakeholder goals. Lack of proper communication between business and development teams and moving too quickly can result in technical debt and bugs. The document recommends focusing on simplicity, continuous deployment, automation, monitoring, and ensuring the IT department is viewed as a partner rather than secondary to improve maintenance.
The document provides an overview of common reasons for IT project failures based on research findings. It discusses that 75% of business and IT executives anticipate software project failures and fewer than a third of projects are completed on time and on budget. Around 33% of projects meet failure due to lack of senior management involvement. The document also shares testimonies from failed startups about reasons like not scaling fast enough, being dependent on another platform, and running out of money too soon. It emphasizes the importance of communication, avoiding fast development that leads to technical debt, getting developer feedback, and having a product roadmap built by the whole team to achieve common goals and understanding.
This document discusses code quality and metrics tools that can be used to analyze code and detect code smells and anti-patterns. It introduces NDepend and Code Maat as tools that can measure code metrics, analyze code dependencies, detect code issues, and visualize changes over time. The document also provides examples of analyzing a codebase with these tools to identify hot files, module ownership, author contributions, and other insights that can help improve code quality.
Goal of the session is to show ways of identifying badly written code in long term perspective. As an example a OSS e-commerce platform was examined and the results will be discussed during session. I will also show waht we, as developers, should pay attention while doing out daily programming routines. Both programmers and other team members will be able to identify committed code crimes :)
Main goal of this session is to explain in details core aspects of SOLID principles. Code samples are in C# , but SOLID principles are language agnostic and should be applied by any software engineer regardless used programming language.
The goal of the session is to show the history, theory and practice of the SOLID principles in business and technical context of created software system.
Examples will be presented in C# language, but SOLID principles can and should be applied by every software engineer regardless of the used programming language
The document announces GeekWeek events in Wroclaw and Krakow, Poland from April 18-24, 2016. It promotes GeekWeekFEST which will take place in Krakow, Wroclaw, and Luxembourg featuring programming and technology-related activities.
The document announces GeekWeek events in Wroclaw and Krakow, Poland from April 18-24, 2016. It promotes GeekWeekFEST which will take place in Krakow, Wroclaw, and Luxembourg featuring events and activities for technology and startup enthusiasts.
Goal of the session is to show ways of identifying badly written code in long term perspective. As an example a OSS e-commerce platform was examined and the results will be discussed during session. I will also show waht we, as developers, should pay attention while doing out daily programming routines. Both programmers and other team members will be able to identify committed code crimes :)
Main goal of this session is to explain in details core aspects of SOLID principles. Code samples are in C# , but SOLID principles are language agnostic and should be applied by any software engineer regardless used programming language.
The goal of the session is to show the history, theory and practice of the SOLID principles in business and technical context of created software system.
Examples will be presented in C# language, but SOLID principles can and should be applied by every software engineer regardless of the used programming language
The document announces GeekWeek events in Wroclaw and Krakow, Poland from April 18-24, 2016. It promotes GeekWeekFEST which will take place in Krakow, Wroclaw, and Luxembourg featuring programming and technology-related activities.
The document announces GeekWeek events in Wroclaw and Krakow, Poland from April 18-24, 2016. It promotes GeekWeekFEST which will take place in Krakow, Wroclaw, and Luxembourg featuring events and activities for technology and startup enthusiasts.