The document discusses an object-oriented approach called "tell, don't ask" where objects publish events to notify other objects of state changes instead of directly querying objects for information. It provides an example of a CreateAction use case object that tells an EventBus of action creations instead of coordinating notifications itself. Various listener objects then receive notifications to perform tasks like speaking on Campfire or sending emails. This allows separating notification logic from the use cases.
Tools For jQuery Application Architecture (Extended Slides)Addy Osmani
Hey guys. I just wrapped up my talk on Tools for jQuery Application Architecture over at Web Directions in London and wanted to make sure everyone interested had access to the slides. Some of the topics I cover include:
MVC & MVVM architecture patterns for client-side development
JavaScriptMVC, Backbone, Spine, SproutCore, Sammy.js
Design patterns for JavaScript applications
Dependency management
JavaScript templating
Cross-browser persistent storage
Feature detection
Widgets & Component libraries
Unit Testing & testing environments
Build Processes, concatenation and minification.
and more!
Tools For jQuery Application Architecture (Extended Slides)Addy Osmani
Hey guys. I just wrapped up my talk on Tools for jQuery Application Architecture over at Web Directions in London and wanted to make sure everyone interested had access to the slides. Some of the topics I cover include:
MVC & MVVM architecture patterns for client-side development
JavaScriptMVC, Backbone, Spine, SproutCore, Sammy.js
Design patterns for JavaScript applications
Dependency management
JavaScript templating
Cross-browser persistent storage
Feature detection
Widgets & Component libraries
Unit Testing & testing environments
Build Processes, concatenation and minification.
and more!
Everything is Permitted: Extending Built-insAndrew Dupont
Adding methods to built-in objects: it’s one of JavaScript’s most powerful features. It’s also a great way to offend the sensibilities of your colleagues. We all hear that it’s irresponsible, that it’s sloppy, that it’s flat-out bad practice and should be avoided.
I’m tired of this one-sided battle. In this talk, I’m going to push back against whatever blog post you read that told you that extending built-ins was unconditionally and universally bad. I’m gonna go all Howard Beale on your asses.
Is your web app drowning in a sea of JavaScript? Has your client-side codebase grown from "a snippet here and there" to "more JavaScript than HTML"? Do you find yourself writing one-off snippets instead of generalized components? You're not the only one. Learn about a handful of strategies you can use to keep your JavaScript codebase lean, modular, and flexible. We'll cover all the major pain points — MVC, templates, persisting state, namespacing, graceful error handling, client/server communication, and separation of concerns. And we'll cover how to do all this incrementally so that you don't have to redo everything from scratch.
These are the slides for this presentation http://www.meetup.com/HardCoreJS/events/133346272/
The goal is to influence the thought process of developers and make them into rockstar engineers by showing how to form the habit of abstraction into one's coding.
Since these presentations were spare time hobby - I've decided to share them :)
Hopefully someone will find them useful.
This part continues 1. part with more design patterns like Command, State, NullObject.
Everything is Permitted: Extending Built-insAndrew Dupont
Adding methods to built-in objects: it’s one of JavaScript’s most powerful features. It’s also a great way to offend the sensibilities of your colleagues. We all hear that it’s irresponsible, that it’s sloppy, that it’s flat-out bad practice and should be avoided.
I’m tired of this one-sided battle. In this talk, I’m going to push back against whatever blog post you read that told you that extending built-ins was unconditionally and universally bad. I’m gonna go all Howard Beale on your asses.
Is your web app drowning in a sea of JavaScript? Has your client-side codebase grown from "a snippet here and there" to "more JavaScript than HTML"? Do you find yourself writing one-off snippets instead of generalized components? You're not the only one. Learn about a handful of strategies you can use to keep your JavaScript codebase lean, modular, and flexible. We'll cover all the major pain points — MVC, templates, persisting state, namespacing, graceful error handling, client/server communication, and separation of concerns. And we'll cover how to do all this incrementally so that you don't have to redo everything from scratch.
These are the slides for this presentation http://www.meetup.com/HardCoreJS/events/133346272/
The goal is to influence the thought process of developers and make them into rockstar engineers by showing how to form the habit of abstraction into one's coding.
Since these presentations were spare time hobby - I've decided to share them :)
Hopefully someone will find them useful.
This part continues 1. part with more design patterns like Command, State, NullObject.
Writing code as an individual and writing code as part of the team are two very different things. Learn the tips and tricks for writing JavaScript code as part of the team so that your code will continue to work for years to come.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
3. “Tell, don't ask”
"Procedural code gets information
then makes decisions. Object-oriented
code tells objects to do things."
— Alec Sharp, Smalltalk by Example
8. A use case object
class CreateAction
def initialize(user)
@user = user
end
def execute(options)
project = @user.open_project(options[:project_id])
action = project.create_action(options[:attrs])
unless action.errors.any?
event = Event.create!(summary: "##{action.id} created", project_id: project.id)
msg = "#{@user.name} created #{action.title}"
project.campfire_room.speak(msg)
PushMessage.instance.publish("action-do.#{action.project.id}.action_item",
{:action_item_id => action})
action.project.users.reject {|u| u == @user}.each do |u|
ActionItemMailer.action_item_created(action, u).deliver
end
end
action
end
end
9. A use case object
class CreateAction
def initialize(user)
@user = user
end
def execute(options)
project = @user.open_project(options[:project_id])
action = project.create_action(options[:attrs])
unless action.errors.any?
event = Event.create!(summary: "##{action.id} created", project_id: project.id)
msg = "#{@user.name} created #{action.title}"
project.campfire_room.speak(msg)
PushMessage.instance.publish("action-do.#{action.project.id}.action_item",
{:action_item_id => action})
action.project.users.reject {|u| u == @user}.each do |u|
ActionItemMailer.action_item_created(action, u).deliver
end
end
action
end
end
10. A use case object
class CreateAction
def initialize(user)
@user = user
end
def execute(options)
project = @user.open_project(options[:project_id])
action = project.create_action(options[:attrs])
unless action.errors.any?
event = Event.create!(summary: "##{action.id} created", project_id: project.id)
msg = "#{@user.name} created #{action.title}"
project.campfire_room.speak(msg)
PushMessage.instance.publish("action-do.#{action.project.id}.action_item",
{:action_item_id => action})
action.project.users.reject {|u| u == @user}.each do |u|
ActionItemMailer.action_item_created(action, u).deliver
end
end
action
end
end
11. A use case object
class CreateAction
def initialize(user)
@user = user
end
def execute(options)
project = @user.open_project(options[:project_id])
action = project.create_action(options[:attrs])
unless action.errors.any?
event = Event.create!(summary: "##{action.id} created", project_id: project.id)
msg = "#{@user.name} created #{action.title}"
project.campfire_room.speak(msg)
PushMessage.instance.publish("action-do.#{action.project.id}.action_item",
{:action_item_id => action})
action.project.users.reject {|u| u == @user}.each do |u|
ActionItemMailer.action_item_created(action, u).deliver
end
end
action
end
end
12. A use case object
class CreateAction
def initialize(user)
@user = user
end
def execute(options)
project = @user.open_project(options[:project_id])
action = project.create_action(options[:attrs])
unless action.errors.any?
event = Event.create!(summary: "##{action.id} created", project_id: project.id)
msg = "#{@user.name} created #{action.title}"
project.campfire_room.speak(msg)
PushMessage.instance.publish("action-do.#{action.project.id}.action_item",
{:action_item_id => action})
action.project.users.reject {|u| u == @user}.each do |u|
ActionItemMailer.action_item_created(action, u).deliver
end
end
action
end
end
14. “Tell, don't ask”
"Procedural code gets information
then makes decisions. Object-oriented
code tells objects to do things."
— Alec Sharp, Smalltalk by Example
15. “Tell, don't ask”
"Procedural code gets information
then makes decisions. Object-oriented
code tells objects to do things."
— Alec Sharp, Smalltalk by Example
16. “Tell, don't ask”
"Sometimes an object will change
its state, and on those occasions
it might be expected to report
that change to others."
— David West, Object Thinking
17. A use case object
class CreateAction
def initialize(user)
@user = user
end
def execute(options)
project = @user.open_project(options[:project_id])
action = project.create_action(options[:attrs])
unless action.errors.any?
event = Event.create!(summary: "##{action.id} created", project_id: project.id)
msg = "#{@user.name} created #{action.title}"
project.campfire_room.speak(msg)
PushMessage.instance.publish("action-do.#{action.project.id}.action_item",
{:action_item_id => action})
action.project.users.reject {|u| u == @user}.each do |u|
ActionItemMailer.action_item_created(action, u).deliver
end
end
action
end
end
18. A use case object
class CreateAction
def initialize(user)
@user = user
end
def execute(options)
project = @user.open_project(options[:project_id])
action = project.create_action(options[:attrs])
unless action.errors.any?
event = Event.create!(summary: "##{action.id} created", project_id: project.id)
msg = "#{@user.name} created #{action.title}"
project.campfire_room.speak(msg)
PushMessage.instance.publish("action-do.#{action.project.id}.action_item",
{:action_item_id => action})
action.project.users.reject {|u| u == @user}.each do |u|
ActionItemMailer.action_item_created(action, u).deliver
end
end
action
end
end
19. A use case object : after
class CreateAction
def initialize(user)
@user = user
end
def execute(options)
project = @user.open_project(options[:project_id])
action = project.create_action(options[:attrs])
unless action.errors.any?
EventBus.announce('action-created', action: action, actor: @user, publisher: self)
end
action
end
end
https://rubygems.org/gems/event_bus
20. The Campfire listener
class CampfireAnnouncer
def action_created(payload)
actor = payload[:actor]
action = payload[:action]
project = action.project
msg = "#{actor.name} created #{action.title}"
project.campfire_room.speak(msg)
end
def action_deleted(payload)
#...
end
#...
end
21. Listener registration
class ApplicationController < ActionController::Base
before_filter do
EventBus.clear
EventBus.register(CampfireAnnouncer.new)
EventBus.register(EventLogger.new)
EventBus.register(EmailNotifier.new)
EventBus.register(PushNotifier.new)
end
#...
end