Trials and tribulations of a successful open-source project

•Download as PPTX, PDF•

0 likes•260 views

Over the last 10 years, I've been maintaining several .NET open-source projects, of which one, Fluent Assertions, has been very successful. This year, it crossed the 20 million downloads on NuGet. This may sound like a trivial thing, but I can tell you first hand that maintaining a successful open-source project requires patience, perseverance and a lot of private time. In this talk, I'll share a bit of history about this project. I'll talk about the challenges I've faced around .NET framework compatibility, release strategies and preventing breaking changes. But I will also talk about the dilemma on how to be open to contributions without jeopardizing on the quality of the project. And what about documentation, marketing and how to say no to the community sometimes? Are you also embarking on a new open-source project, or struggling with an existing one? Or do you just want to hear about real-world software challenges? Join me in this little trip through memory lane.

Technology

Dennis Doomen | @ddoomen | Aviva Solutions | The Continuous Improver

var numbers = new[] { 1, 2, 3 };
numbers.Should().Contain(item => item > 2, "at least 1 item should be larger than 3");
action.Should().Throw<InvalidOperationException>()
.WithInnerException<ArgumentException>()
.WithMessage("whatever");
typeof(MyController).Methods()
.ThatDoNotReturn<ActionResult>()
.ThatAreNotDecoratedWith<HttpPostAttribute>()
.Should().NotBeVirtual().And.NotBeAsync().And.NotReturnVoid();
graph.Should().BeEquivalentTo(new
{
RelevantProperty = “ImportantValue”
});

“Custom Assertions”
.bat build file
MSTest
CodeBetter TeamCity
2009
CodePlex with TFS
2010
Linked files with #ifdef
First version on NuGet
1.3 (.NET 3.5, 4.0, SL4)
2011
1.7 (.NET 3.5, 4.0, SL4)
CodePlex with Git
2012 (H1)
2.0 (.NET 3.5, 4.0, 3.5, SL4,
SL for WP7.5, WinRT 4.5)
2012 (H2)
Github with Pull Requests
2013
3.0 (.NET 4.0, 4.5, SL5,
Win8, WP8, MonoTouch,
MonoAndroid,)
Psake
David Fowler structure
Shared Projects (.shproj).
2014

3.5 (.NET 4.0, 4.5, Mono, Win
8.0/8.1, WP8 for SL, WP 8/8.1
Store, Sl5)
AppVeyor
GitVersion
2015 H1
4.0 (dotnet5, Mono, Xamarin, .NET
4.0, 4.5, SL5, WP8 SL, WP 8.0/8.1,
Win 8.0/8.1)
PCL + framework-specific +
shared project
Package.json
2015 H2
Cake
xUnit.NET
4.19 (.NET 4.0, 4.5, .Standard 1.3,
Profiel328, Profile32, SL5, UAP
10, WIN81, WP8, WPA8.1)
2017
5.0 (.NET 4.5, Standard 1.4, 1.6,
2.0)
Cross-compilation + #ifdef
PackageReference
2018
Nuke
5.9 (.NET 4.5, 4.7, Core 2.0,
Standard 1.3, 1.6, 2.0)
2019
6.0 (.NET Standard 2.0, 2.1).
2020

develop
4.1.0
dogfooding
release-5.0
5.0.04.2.0
5.0.0-rc.1
X
5.0.0-rc.2
master
5.1.0
X
breaking changes
enhancements & fixes
GitHubFlow
GitFlow
SemVer.

• .NET Standard https://docs.microsoft.com/en-us/dotnet/standard/net-
standard
• David Fowler’s project structure
https://gist.github.com/davidfowl/ed7564297c61fe9ab814
• .NET long-term support
https://dotnet.microsoft.com/platform/support/policy/dotnet-core
• .NET 5 https://devblogs.microsoft.com/dotnet/introducing-net-5/
• Overload resolution bug
https://github.com/fluentassertions/fluentassertions/issues/964
• .NET Core 3 Preview 7 bug
https://github.com/fluentassertions/fluentassertions/issues/1047

More from Dennis Doomen

I don't have to tell anybody how awesome Event Sourcing is as an architecture style. But those that have been using it in production must have experienced the pains of keeping the upgrades fast enough, especially if you use a more traditional relational database like SQL Server. I've once heard somebody say: "If it's slow, make it faster", but rebuilding a big projection is simply a very expensive operations and involves a lot of network traffic between the application and the database servers. Over the years since we adopted Event Sourcing, we've been experimenting a lot and have implemented various improvements to make those reprojections faster. And we haven't stopped. We're already working on some new ideas lately. So in this session, I'd like to share those techiques, their pros and cons and how we implemented them on a more detailed level.

Slow Event Sourcing (re)projections - Just make them faster!

Dennis Doomen

Enough books have been written, articles have been published and Youtube videos have been posted about how you should be behaving as a software developer, Scrum Master or team lead. To be original in this unoriginal world, I started thinking about the things you should NOT be doing. I came up with 50 tools, practices and principles covering topics like dealing with complexity, productivity, architecture, testability, traceability, maintainability, transparency and predictability that I believe hamper you as a professional. That sounds like a lot, but I promise you a fun and entertaining session that I'm sure will trigger a lot of recognition.

50 things software teams should not do.pptx

Dennis Doomen

Whether you're just writing your first unit test or have been practicing Test Driven Development for many years, I'm sure your biggest challenge is to find the right scope for testing. Unfortunately a lot of books and guidance seem to imply that every class or type should be tested separately. Well, I can tell you from 15 years of unit testing experience that that's the best way to shoot yourself in the foot. In this session, I'm going to show you some concrete examples and why I chose a certain boundary for the "unit" in unit testing. I will also share design heuristics I use myself to find those boundaries and why those are not guidelines. I'll also illustrate how principals like DRY and SOLID can be both a blessing and a curse that may lead to the wrong design choices.

What is the right "unit" in unit testing and why it is not a class?

Dennis Doomen

Writing maintainable code is not something that is easy to do. Not only is a pretty subjective, a lot of the techniques like Clean Code, SOLID and such can be misinterpreted resulting in unconstructive dogma. I've made it my career's goal to find a good balance between all those different patterns, principles, practices and guidelines. In this talk, I'd like to share my own ideas on what it takes to write maintainable code. I'll talk about architecture, class design, automated testing and any consequences on your development process. If you care about your code, be there with me.

A lab around the principles and practices for writing maintainable code

Dennis Doomen

It’s 2021, so practices like Test Driven Development (TDD) have long found their way into organizations. However, the practices and principles to keep those unit tests maintainable haven’t really changed. Still, Dennis regularly talks to developers that somehow ended up with an incomprehensible unmaintainable set of unit tests that they once believed in, but are now holding them back. So in this session Dennis likes to provide a refresh of those fundamental ideas and talk about why you should practice TDD, revealing intentions, naming conventions, state versus interaction based testing, and how to stay out of the debugger hell with proper mocking and assertion frameworks.

How to Practice TDD Without Shooting Yourself in the Foot

Dennis Doomen

If I have to name a single biggest hype in software architecture land then it would be "microservice". They are supposed to be small and focused, can be deployed independently, can work with any technology and will solve all your monolithical problems. But we all know that silver bullets don't exist, plus technology should never be a goal, but merely a means to an end. Nonetheless, following the path towards real microservices is a great strategy for decomposing a monolith without the deployment complexity of the first. So how do you do that? What technologies does the .NET realm offer for us? In this talk, I'll show you some of the pros and cons of micro-services and its ingredients to leverage modern-day .NET and Event Sourcing to move your monolith into a bright new future.

Decomposing the Monolith using modern-day .NET and a touch of microservices

Dennis Doomen

Over the years I've spoken many times about what Event Sourcing is and shared many of the good, the bad and the ugly parts of it in blog posts and various talks. However, I've never talked about how to actually build a system based on this architecture style. I keep getting the same questions over and over again. Like when to apply Event Sourcing and at what architectural level. How to deal with transactional boundaries within and outside the domain. How to build projections that are autonomous, reliable and self-supporting. How to deal with upgrades and blue-green deployments. But also on how to handle bugs, design mistakes and crashing projections. Having made a lot of these mistakes myself over these years, it's time to share my current thoughts and opinions about this. Since the .NET space has a pretty rich set of open-source projections to support this, the examples and code will be .NET. But the concepts are universal, so don't let that scare you off.

Event Sourcing from the Trenches (DDD Europe 2020)

Dennis Doomen

After several in-depth talks about Event Sourcing, I realized that there's a large group of developers that may have heard about Domain-Driven Design, Command-Query Responsibility Segregation and Event Sourcing, but have not really connected the dots yet. So in this talk, I'd like to take a practical example of a simple domain and gradually introduce functional requirements to see how the principles behind DDD affect the way your entities are going to protect the business rules. After that, I'll introduce some real-world non-functional requirements and see if and how Event Sourcing and/or CQRS may or may not help to accomplish those.

Practical introduction to DDD, CQRS and Event Sourcing

Dennis Doomen

It’s 2019, so practices like Test Driven Development (TDD) have long found their way into organizations. However, the practices and principles to keep those unit tests maintainable haven’t really changed. Still, I regularly talk to developers that somehow ended up with an incomprehensible unmaintainable set of unit tests that they once believed in, but are now holding them back. So in this session I like to provide a refresh of those fundamental ideas and talk about why you should practice TDD, revealing intentions, naming conventions, state versus interaction based testing, and how to stay out of the debugger hell with proper mocking and assertion frameworks. And even if you believe you are well versed in the testing realm, join me anyway. Maybe we can learn some tips & tricks from the audience as well. Looking forward to it!

How to practice TDD without shooting yourself in the foot

Dennis Doomen

A micro-service architecture is a great strategy for decomposing a monolith. In this talk, I’ll show you some of the pros and cons of micro-services and how you can leverage OWIN, .NET, Event Sourcing and the Onion Architecture to gradually move your monolith into a bright new future. If I have to name a single hype in software architecture land then I would have to mention the micro-service architecture. Micro-services are supposed to be small, have a very focused purpose, can be deployed independently, are completely self-supporting and loosely coupled. Ideally, micro-services are technology agnostic, but hey, we’re in the .NET space, aren’t we? And they are not a goal, but a means to an end. In fact, a micro-service architecture has many benefits and are a great strategy for decomposing a monolith. So how do you build a micro-service? What technologies does the .NET realm offer for us? And what if you don’t want to deploy them independently? In this talk, I’ll show you some of the pros and cons of micro-services and how you can leverage OWIN, .NET, Event Sourcing and the Onion Architecture to gradually move your monolith into a bright new future.

Decomposing the Monolith (Riga Dev Days 2019)

Dennis Doomen

Writing maintainable code is not something that is easy to do. Not only is a pretty subjective, a lot of the techniques like Clean Code, SOLID and such can be misinterpreted resulting in unconstructive dogma. I've made it my career's goal to find a good balance between all those different patterns, principles, practices and guidelines. In this talk, I like to share you my own ideas on what it takes to write maintainable code. I'll talk about architecture, class design, automated testing and any consequences on your development process. If you care about your code, be there with me.

A lab around the principles and practices for writing maintainable code (2019)

Dennis Doomen

I recently was asked what I would do differently if I had the experience I have now. This got me thinking about the mistakes I've made, the traps I fell for and the dogmatism I became part of over the last 22 years of professional software developer in the Microsoft realm. In this talk, I'll be going down memory lane with you and share everything I've learned on architecture, tools, technologies, agile software development, maintainable code, automated testing, documentation and anything else that I think you should know. Prepare yourself for an event of stories, both good and bad.

Lessons learned from two decades of professional software development

Dennis Doomen

In 2009, I first learned about Event Sourcing and Command Query Responsibility Seggregation (CQRS) at a training Greg Young gave in Utrecht, The Netherlands. I remember being awed by the scalability and architectural simplicity those styles provided. However, I also remembered the technical complexity that comes with it. In 2012, I was in charge of transitioning a CQRS-based system to Event Sourcing. I knew it would be non-trivial, but boy was I in for a surprise. So, over the last four years, I've experienced first-hand how a large group of developers had to deal with the transition. It's a brilliant solution for high-performance or complex business systems, but you need to be aware that this also introduces challenges most people don't tell you about. In this talk, I'd like to share you some of the most powerful benefits of ES, but also show you the flipside of the coin and cover some of the smaller and bigger challenges you'll run into it. Again, I love it and would apply it again without any doubt, but I really want you to understand the trade-offs before you jump on the Event Sourcing train.

The Good, The Bad and The Ugly of Event Sourcing

Dennis Doomen

Event Sourcing from the Trenches (with examples from .NET)

Dennis Doomen

It's 2018, so practices like Test Driven Development (TDD) have long found their way into organizations. However, the practices and principles to keep those unit tests maintainable haven't really changed. Still, I regularly talk to developers that somehow ended up with an incomprehensible unmaintainable set of unit tests that they once believed in, but are now holding them back. So in this session I like to provide a refresh of those fundamental ideas and talk about why you should practice TDD, revealing intentions, naming conventions, state versus interaction based testing, and how to stay out of the debugger hell with proper mocking and assertion frameworks.

How To Practice TDD Without Shooting Yourself In The Foot

Dennis Doomen

If I have to name a single hype in software architecture land then I would have to mention the micro-service architecture. Microservices are supposed to be small, have a very focused purpose, can be deployed independently, are completely self-supporting and loosely coupled. Ideally, microservices are technology agnostic, but hey, we're in the .NET space, aren't we? And they are not a goal, but a means to an end. In fact, a microservice architecture has many benefits and are a great strategy for decomposing a monolith. So how do you build a microservice? What technologies does the .NET realm offer for us? And what if you don't want to deploy them independently? In this talk, I'll show you some of the pros and cons of microservices and how you can leverage Event Sourcing, OWIN and .NET to move your monolith into a bright new future.

Decomposing the monolith into embeddable microservices using OWIN, WebHooks, ...

Dennis Doomen

Concepts like the Dependency Inversion Principle, Inversion of Control containers and Dependency Injection libraries are often mixed up, but they are not the same. You shouldn’t use a DI library until you understand the problems your solving, nor is it always the best solution. Since I’ve felt this pain many times myself, I’d like to use this session to create some clarity. First, I’ll demonstrate the reason why people typically use libraries like Unity and Autofac in their code bases. Then I’ll show you that those same people often use the Dependency Inversion Principle in the wrong way (and need to revert to mocking libraries to compensate). Then I’ll show you how to apply the principles properly by carefully designing the seams in your architecture. And finally, I’ll show you how an advanced library can connect the dots in a very elegant way.

Strengths and weaknesses of dependency injection

Dennis Doomen

Frameworks are supposed to help you build things more quicker and hide a lot of complexity around cross-cutting and infrastructural concerns. They are supposed to make it easier for inexperienced developers to join a running projection. But frameworks also introduce a lot of magic, and that magic is going to backfire at some point. At least, that's my experience. And when it backfires, your code is so entangled with that framework, that you can't get rid of it anymore. So, instead of building and using frameworks, build and use libraries. That's easier said then done, and I'll can talk about many great and not so great examples. So let me share some of the practices I use to build composable libraries myself. I'll talk about principles of package design and scoping, keeping your NuGet package dependencies in check, and how to use layered APIs to increase usability without hiding the magic.

Build Libraries That People Love To use

Dennis Doomen

If I have to name a single hype in software architecture land then I would have to mention the micro-service architecture. Microservices are supposed to be small, have a very focused purpose, can be deployed independently, are completely self-supporting and loosely coupled. Ideally, microservices are technology agnostic, but hey, we're in the .NET space, aren't we? And they are not a goal, but a means to an end. In fact, a microservice architecture has many benefits and are a great strategy for decomposing a monolith. So how do you build a microservice? What technologies does the .NET realm offer for us? And what if you don't want to deploy them independently? In this talk, I'll show you some of the pros and cons of microservices and how you can leverage OWIN and .NET to move your monolith into a bright new future.

Decomposing the Monolith using Microservices that don't give you pain

Dennis Doomen

Build Libraries, Not Frameworks

Dennis Doomen

More from Dennis Doomen (20)

Slow Event Sourcing (re)projections - Just make them faster!

50 things software teams should not do.pptx

What is the right "unit" in unit testing and why it is not a class?

A lab around the principles and practices for writing maintainable code

How to Practice TDD Without Shooting Yourself in the Foot

Decomposing the Monolith using modern-day .NET and a touch of microservices

Event Sourcing from the Trenches (DDD Europe 2020)

Practical introduction to DDD, CQRS and Event Sourcing

How to practice TDD without shooting yourself in the foot

Decomposing the Monolith (Riga Dev Days 2019)

A lab around the principles and practices for writing maintainable code (2019)

Lessons learned from two decades of professional software development

The Good, The Bad and The Ugly of Event Sourcing

Event Sourcing from the Trenches (with examples from .NET)

How To Practice TDD Without Shooting Yourself In The Foot

Decomposing the monolith into embeddable microservices using OWIN, WebHooks, ...

Strengths and weaknesses of dependency injection

Build Libraries That People Love To use

Decomposing the Monolith using Microservices that don't give you pain

Build Libraries, Not Frameworks

Recently uploaded

Tata AIG General Insurance Company - Insurer Innovation Award 2024

The Digital Insurer

Partners Life - Insurer Innovation Award 2024

The Digital Insurer

Join our latest Connector Corner webinar to discover how UiPath Integration Service revolutionizes API-centric automation in a 'Quote to Cash' process—and how that automation empowers businesses to accelerate revenue generation. A comprehensive demo will explore connecting systems, GenAI, and people, through powerful pre-built connectors designed to speed process cycle times. Speakers: James Dickson, Senior Software Engineer Charlie Greenberg, Host, Product Marketing Manager

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

DianaGray10

How to Troubleshoot Apps for the Modern Connected Worker

ThousandEyes

Top 10 Most Downloaded Games on Play Store in 2024

SynarionITSolutions

Artificial Intelligence Chap.5 : Uncertainty

Khushali Kathiriya

This presentations targets students or working professionals. You may know Google for search, YouTube, Android, Chrome, and Gmail, but did you know Google has many developer tools, platforms & APIs? This comprehensive yet still high-level overview outlines the most impactful tools for where to run your code, store & analyze your data. It will also inspire you as to what's possible. This talk is 50 minutes in length.

Powerful Google developer tools for immediate impact! (2023-24 C)

wesley chun

Three things you will take away from the session: • How to run an effective tenant-to-tenant migration • Best practices for before, during, and after migration • Tips for using migration as a springboard to prepare for Copilot in Microsoft 365 Main ideas: Migration Overview: The presentation covers the current reality of cross-tenant migrations, the triggers, phases, best practices, and benefits of a successful tenant migration Considerations: When considering a migration, it is important to consider the migration scope, performance, customization, flexibility, user-friendly interface, automation, monitoring, support, training, scalability, data integrity, data security, cost, and licensing structure Next Wave: The next wave of change includes the launch of Copilot, which requires businesses to be prepared for upcoming changes related to Copilot and the cloud, and to consolidate data and tighten governance ShareGate: ShareGate can help with pre-migration analysis, configurable migration tool, and automated, end-user driven collaborative governance

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

sammart93

Manulife - Insurer Innovation Award 2024

The Digital Insurer

Building Digital Trust in a Digital Economy Veronica Tan, Director - Cyber Security Agency of Singapore Apidays Singapore 2024: Connecting Customers, Business and Technology (April 17 & 18, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

apidays

With more memory available, system performance of three Dell devices increased, which can translate to a better user experience Conclusion When your system has plenty of RAM to meet your needs, you can efficiently access the applications and data you need to finish projects and to-do lists without sacrificing time and focus. Our test results show that with more memory available, three Dell PCs delivered better performance and took less time to complete the Procyon Office Productivity benchmark. These advantages translate to users being able to complete workflows more quickly and multitask more easily. Whether you need the mobility of the Latitude 5440, the creative capabilities of the Precision 3470, or the high performance of the OptiPlex Tower Plus 7010, configuring your system with more RAM can help keep processes running smoothly, enabling you to do more without compromising performance.

Boost PC performance: How more available memory can improve productivity

Principled Technologies

A Domino Admins Adventures (Engage 2024)

Gabriella Davis

The presentation explores the development and application of artificial intelligence (AI) from its inception to its current status in the modern world. The term "artificial intelligence" was first coined by John McCarthy in 1956 to describe efforts to develop computer programs capable of performing tasks that typically require human intelligence. This concept was first introduced at a conference held at Dartmouth College, where programs demonstrated capabilities such as playing chess, proving theorems, and interpreting texts. In the early stages, Alan Turing contributed to the field by defining intelligence as the ability of a being to respond to certain questions intelligently, proposing what is now known as the Turing Test to evaluate the presence of intelligent behavior in machines. As the decades progressed, AI evolved significantly. The 1980s focused on machine learning, teaching computers to learn from data, leading to the development of models that could improve their performance based on their experiences. The 1990s and 2000s saw further advances in algorithms and computational power, which allowed for more sophisticated data analysis techniques, including data mining. By the 2010s, the proliferation of big data and the refinement of deep learning techniques enabled AI to become mainstream. Notable milestones included the success of Google's AlphaGo and advancements in autonomous vehicles by companies like Tesla and Waymo. A major theme of the presentation is the application of generative AI, which has been used for tasks such as natural language text generation, translation, and question answering. Generative AI uses large datasets to train models that can then produce new, coherent pieces of text or other media. The presentation also discusses the ethical implications and the need for regulation in AI, highlighting issues such as privacy, bias, and the potential for misuse. These concerns have prompted calls for comprehensive regulations to ensure the safe and equitable use of AI technologies. Artificial intelligence has also played a significant role in healthcare, particularly highlighted during the COVID-19 pandemic, where it was used in drug discovery, vaccine development, and analyzing the spread of the virus. The capabilities of AI in healthcare are vast, ranging from medical diagnostics to personalized medicine, demonstrating the technology's potential to revolutionize fields beyond just technical or consumer applications. In conclusion, AI continues to be a rapidly evolving field with significant implications for various aspects of society. The development from theoretical concepts to real-world applications illustrates both the potential benefits and the challenges that come with integrating advanced technologies into everyday life. The ongoing discussion about AI ethics and regulation underscores the importance of managing these technologies responsibly to maximize their their benefits while minimizing potential harms.

Artificial Intelligence: Facts and Myths

Joaquim Jorge

The value of a flexible API Management solution for Open Banking Steve Melan, Manager for IT Innovation and Architecture - State's and Saving's Bank of Luxembourg Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The value of a flexible API Management solution for O...

apidays

GenAI Risks & Security Meetup 01052024.pdf

lior mazor

Effective data discovery is crucial for maintaining compliance and mitigating risks in today's rapidly evolving privacy landscape. However, traditional manual approaches often struggle to keep pace with the growing volume and complexity of data. Join us for an insightful webinar where industry leaders from TrustArc and Privya will share their expertise on leveraging AI-powered solutions to revolutionize data discovery. You'll learn how to: - Effortlessly maintain a comprehensive, up-to-date data inventory - Harness code scanning insights to gain complete visibility into data flows leveraging the advantages of code scanning over DB scanning - Simplify compliance by leveraging Privya's integration with TrustArc - Implement proven strategies to mitigate third-party risks Our panel of experts will discuss real-world case studies and share practical strategies for overcoming common data discovery challenges. They'll also explore the latest trends and innovations in AI-driven data management, and how these technologies can help organizations stay ahead of the curve in an ever-changing privacy landscape.

TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery

TrustArc

MINDCTI Revenue Release Quarter One 2024

MIND CTI

Strategies for Landing an Oracle DBA Job as a Fresher

Remote DBA Services

This presentation explores the impact of HTML injection attacks on web applications, detailing how attackers exploit vulnerabilities to inject malicious code into web pages. Learn about the potential consequences of such attacks and discover effective mitigation strategies to protect your web applications from HTML injection vulnerabilities. for more information visit https://bostoninstituteofanalytics.org/category/cyber-security-ethical-hacking/

HTML Injection Attacks: Impact and Mitigation Strategies

Boston Institute of Analytics

Following the popularity of "Cloud Revolution: Exploring the New Wave of Serverless Spatial Data," we're thrilled to announce this much-anticipated encore webinar. In this sequel, we'll dive deeper into the Cloud-Native realm by uncovering practical applications and FME support for these new formats, including COGs, COPC, FlatGeoBuf, GeoParquet, STAC, and ZARR. Building on the foundation laid by industry leaders Michelle Roby of Radiant Earth and Chris Holmes of Planet in the first webinar, this second part offers an in-depth look at the real-world application and behind-the-scenes dynamics of these cutting-edge formats. We will spotlight specific use-cases and workflows, showcasing their efficiency and relevance in practical scenarios. Discover the vast possibilities each format holds, highlighted through detailed discussions and demonstrations. Our expert speakers will dissect the key aspects and provide critical takeaways for effective use, ensuring attendees leave with a thorough understanding of how to apply these formats in their own projects. Elevate your understanding of how FME supports these cutting-edge technologies, enhancing your ability to manage, share, and analyze spatial data. Whether you're building on knowledge from our initial session or are new to the serverless spatial data landscape, this webinar is your gateway to mastering cloud-native formats in your workflows.

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Safe Software

Recently uploaded (20)

Tata AIG General Insurance Company - Insurer Innovation Award 2024

Partners Life - Insurer Innovation Award 2024

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

How to Troubleshoot Apps for the Modern Connected Worker

Top 10 Most Downloaded Games on Play Store in 2024

Artificial Intelligence Chap.5 : Uncertainty

Powerful Google developer tools for immediate impact! (2023-24 C)

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Manulife - Insurer Innovation Award 2024

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

Boost PC performance: How more available memory can improve productivity

A Domino Admins Adventures (Engage 2024)

Artificial Intelligence: Facts and Myths

Apidays New York 2024 - The value of a flexible API Management solution for O...

GenAI Risks & Security Meetup 01052024.pdf

TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery

MINDCTI Revenue Release Quarter One 2024

Strategies for Landing an Oracle DBA Job as a Fresher

HTML Injection Attacks: Impact and Mitigation Strategies

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Trials and tribulations of a successful open-source project

1. Dennis Doomen | @ddoomen | Aviva Solutions | The Continuous Improver

5. var numbers = new[] { 1, 2, 3 }; numbers.Should().Contain(item => item > 2, "at least 1 item should be larger than 3"); action.Should().Throw<InvalidOperationException>() .WithInnerException<ArgumentException>() .WithMessage("whatever"); typeof(MyController).Methods() .ThatDoNotReturn<ActionResult>() .ThatAreNotDecoratedWith<HttpPostAttribute>() .Should().NotBeVirtual().And.NotBeAsync().And.NotReturnVoid(); graph.Should().BeEquivalentTo(new { RelevantProperty = “ImportantValue” });

9. “Custom Assertions” .bat build file MSTest CodeBetter TeamCity 2009 CodePlex with TFS 2010 Linked files with #ifdef First version on NuGet 1.3 (.NET 3.5, 4.0, SL4) 2011 1.7 (.NET 3.5, 4.0, SL4) CodePlex with Git 2012 (H1) 2.0 (.NET 3.5, 4.0, 3.5, SL4, SL for WP7.5, WinRT 4.5) 2012 (H2) Github with Pull Requests 2013 3.0 (.NET 4.0, 4.5, SL5, Win8, WP8, MonoTouch, MonoAndroid,) Psake David Fowler structure Shared Projects (.shproj). 2014

10. 3.5 (.NET 4.0, 4.5, Mono, Win 8.0/8.1, WP8 for SL, WP 8/8.1 Store, Sl5) AppVeyor GitVersion 2015 H1 4.0 (dotnet5, Mono, Xamarin, .NET 4.0, 4.5, SL5, WP8 SL, WP 8.0/8.1, Win 8.0/8.1) PCL + framework-specific + shared project Package.json 2015 H2 Cake xUnit.NET 4.19 (.NET 4.0, 4.5, .Standard 1.3, Profiel328, Profile32, SL5, UAP 10, WIN81, WP8, WPA8.1) 2017 5.0 (.NET 4.5, Standard 1.4, 1.6, 2.0) Cross-compilation + #ifdef PackageReference 2018 Nuke 5.9 (.NET 4.5, 4.7, Core 2.0, Standard 1.3, 1.6, 2.0) 2019 6.0 (.NET Standard 2.0, 2.1). 2020

11. develop 4.1.0 dogfooding release-5.0 5.0.04.2.0 5.0.0-rc.1 X 5.0.0-rc.2 master 5.1.0 X breaking changes enhancements & fixes GitHubFlow GitFlow SemVer.

12.

13. HTTPS via CloudFare. Logo by Ben Palmer Github Pages + Jekyll Minimal Mistakes Jekyll Theme DNS via GoDaddy

14.

15.

16.

17.

18.

19.

20.

21.

22.

23.

24. • .NET Standard https://docs.microsoft.com/en-us/dotnet/standard/net- standard • David Fowler’s project structure https://gist.github.com/davidfowl/ed7564297c61fe9ab814 • .NET long-term support https://dotnet.microsoft.com/platform/support/policy/dotnet-core • .NET 5 https://devblogs.microsoft.com/dotnet/introducing-net-5/ • Overload resolution bug https://github.com/fluentassertions/fluentassertions/issues/964 • .NET Core 3 Preview 7 bug https://github.com/fluentassertions/fluentassertions/issues/1047

Trials and tribulations of a successful open-source project

Recommended

Recommended

More Related Content

More from Dennis Doomen

More from Dennis Doomen (20)

Recently uploaded

Recently uploaded (20)

Trials and tribulations of a successful open-source project