Who were the most influential bands of Rock history? Which bands could not exist if there was no Velvet Underground? How much Shoegazing subgenre is related to the Drone music?
Rock music history was perhaps full of drugs and alcohol but we are sobering up to represent it in terms of (social) networks and find mathematical relationship between artists, trends and subgenres. Full of DataViz and interesting relationships, we will pick up a few common clustering and network analysis algorithms to analyse the publicly available Wiki data. Expect lots of air guitar power chords and virtuoso solos.
Who were the most influential bands of Rock history? Which bands could not exist of there was no Velvet Underground? How much Shoegazing subgenre is related to the Drone music?
Rock music history was perhaps full of drugs and alcohol but we are sobering up to represent it in terms of (social) networks and find mathematical relationship between artists, trends and subgenres. Full of DataViz and interesting relationships, we will pick up a few common clustering and network analysis algorithms to analyse the publicly available Wiki data. Expect lots of air guitar power chords and virtuoso solos.
Autonomous agents with deep reinforcement learning - Oredev 2018Ali Kheyrollahi
Even if AlphaGo’s victory over the go’s world champion was viewed dubiously as hype by a one-trick pony, AlphaZero’s ability to learn chess in 4 hours and beat the strongest computer using not-of-this-owrld techniques has silenced the strongest of critiques. DeepMind has proved a track record with a trajectory to conquer more complex aspects of human mind.
But really, how do they do it? While many aspects of their technology remains unpublished, they for the most part use common Machine Learning techniques that can be used to build intelligent agents. In this talk, we not only cover tools and techniques but also build an agent to play and compete with humans. See if you can beat the machine!
Buildstuff - what do you need to know about RPC comebackAli Kheyrollahi
While REST has enjoyed a decade of popularity and proliferation, we see a recent resurgence of RPC - mainly advocated and evangelised by large software companies such as Google and Uber.
Our industry has a tendency of going full circle on pretty much anything and everything so this is not exactly a surprise. But before adopting RPC - or any other hype for that matter - it is important to understand why it is making a comeback and what problem it is trying to address. And this is the exact topic we will address in this talk: we will review the RPC and REST, look at key arguments for using and it and in the end we discussion gRPC, one of the main proponents of RPC comeback.
Deep Learning has taken the world of Computer Science by storm yet for many of us it remains an elusive sci-fi-like buzzword. After years of feature engineering in Computer Vision and Natural Language Processing, we have finally come to the point where, we can feed raw data to a Neural Network, similar to how our brains work, and expect results that can surprise us in their high accuracy.
This talk is about de-mystifying Deep Learning for developers many of whom could benefit from understanding and using Deep Learning in their day-to-day job. It covers the background and brief theoretical grounds in the first third but shows actual working code and examples in the rest. We will overview convolutional Neural Networks and then cover network design techniques such as pooling, dropout and local connections.
The examples of this talk are in Keras and aimed to build real-world models in the field of Natural Language Processing.
Who were the most influential bands of Rock history? Which bands could not exist of there was no Velvet Underground? How much Shoegazing subgenre is related to the Drone music?
Rock music history was perhaps full of drugs and alcohol but we are sobering up to represent it in terms of (social) networks and find mathematical relationship between artists, trends and subgenres. Full of DataViz and interesting relationships, we will pick up a few common clustering and network analysis algorithms to analyse the publicly available Wiki data. Expect lots of air guitar power chords and virtuoso solos.
Autonomous agents with deep reinforcement learning - Oredev 2018Ali Kheyrollahi
Even if AlphaGo’s victory over the go’s world champion was viewed dubiously as hype by a one-trick pony, AlphaZero’s ability to learn chess in 4 hours and beat the strongest computer using not-of-this-owrld techniques has silenced the strongest of critiques. DeepMind has proved a track record with a trajectory to conquer more complex aspects of human mind.
But really, how do they do it? While many aspects of their technology remains unpublished, they for the most part use common Machine Learning techniques that can be used to build intelligent agents. In this talk, we not only cover tools and techniques but also build an agent to play and compete with humans. See if you can beat the machine!
Buildstuff - what do you need to know about RPC comebackAli Kheyrollahi
While REST has enjoyed a decade of popularity and proliferation, we see a recent resurgence of RPC - mainly advocated and evangelised by large software companies such as Google and Uber.
Our industry has a tendency of going full circle on pretty much anything and everything so this is not exactly a surprise. But before adopting RPC - or any other hype for that matter - it is important to understand why it is making a comeback and what problem it is trying to address. And this is the exact topic we will address in this talk: we will review the RPC and REST, look at key arguments for using and it and in the end we discussion gRPC, one of the main proponents of RPC comeback.
Deep Learning has taken the world of Computer Science by storm yet for many of us it remains an elusive sci-fi-like buzzword. After years of feature engineering in Computer Vision and Natural Language Processing, we have finally come to the point where, we can feed raw data to a Neural Network, similar to how our brains work, and expect results that can surprise us in their high accuracy.
This talk is about de-mystifying Deep Learning for developers many of whom could benefit from understanding and using Deep Learning in their day-to-day job. It covers the background and brief theoretical grounds in the first third but shows actual working code and examples in the rest. We will overview convolutional Neural Networks and then cover network design techniques such as pooling, dropout and local connections.
The examples of this talk are in Keras and aimed to build real-world models in the field of Natural Language Processing.
Microservice Architecture at ASOS - DevSum 2017Ali Kheyrollahi
For the past 3 years, ASOS has been on a journey of moving its monolithic architecture to Microservices - and what has been driving this change is not just the buzzword: as with any monolith, the spiraling cost of change stifles the business and innovation. And in this market, advancing your competitive edge by constant improvement is a big factor in the overall success of your business.
Probably not many know that ASOS website drives more traffic (and way more bandwidth) than the showcase Stackoverflow. Some of the services are built to serve up to 10K RPS (request/second). And the services are spread around the globe currently on more than 4 Azure DCs. And on the top, we have pretty thick data pipelines moving many GBs of data to enable traditional BI - as well as the trendy Machine Learning algorithms powering recommendations and personalisation.
This talk will be a brief intro to the overall view of what +20 2-pizza teams are doing and in specific, goes into some of the details of ML-enabled recommendations platform. Underneath the success of the transition, has been a Logging/Monitoring/Alerting system (Elasticsearch+ConverorBelt+Kibana) to empower platform teams to ensure health of the system and keeping Mean-Time-to-Recovery low.
As with any such talk, there will be a section on lessons learned...
5 must have patterns for your microservice - techoramaAli Kheyrollahi
"Netflix is actually a log generating application that just happens to stream movies"
Building a service/Microservice is itself easy. Scaling it on the cloud is not that hard either but operating, maintaining and iterating a production large scale service is not just about linearisation. As Cockcroft points out, telemetry and monitoring is the most important aspect of building Microservices
We discuss 5 patterns that any serious Microservice should have:
- Canary (an endpoint reporting health of underlying dependencies)
- IO monitor (measuring all calls from Microservice to external dependencies)
- A circuit breaker
- An ActivityId-Propagator
- An exception and short timeout retry policy
Real time monitoring-alerting: storing 2Tb of logs a day in ElasticsearchAli Kheyrollahi
Building any average complex system in the cloud requires telemetry to be the number one concern: you would probably even start with planning and building it first (or perhaps you wish you had!). As quoted by Werner Vogels “Netflix is a log generating application, that happens to stream video quote” - Logging/Monitoring/Alerting has been central to the success of Netflix.
In ASOS, we currently generate more than 1TB of logs daily that gets stored and analysed in our Elasticsearch cluster for monitoring and alerting purposes. ELK stack (Elasticsearch, Logstash and Kibana) has been a very popular tool for logging and monitoring but tuning ELasticsearch for handling such a load is an art form in itself.
In this talk, we start with an overview of ELK stack (we in ASOS use CoveyorBelt instead of logstash so ECK for us) and then move to sharing what we have learned from trying to scale our Elasticsearch for this load: from tuning various configuration parameters to planning your shards and mapping strategy, this talk has quite a bit to equip you to build or tune an ELK stack in your own company.
5 must-have patterns for your microservice - buildstuffAli Kheyrollahi
"Netflix is actually a log generating application that just happens to stream movies"
Building a service/Microservice is itself easy. Scaling it on the cloud is not that hard either but operating, maintaining and iterating a production large scale service is not just about linearisation. As Cockcroft points out, telemetry and monitoring is the most important aspect of building Microservices
We discuss 5 patterns that any serious Microservice should have:
- Canary (an endpoint reporting health of underlying dependencies)
- IO monitor (measuring all calls from Microservice to external dependencies)
- A circuit breaker
- An ActivityId-Propagator
- An exception and short timeout retry policy
Apart from the Microservice buzzword, there is a saddening lack of understanding of what a successful Microservice architecture requires in terms of monitoring and telemetry. MTR in case of a Microservice can be much more than a monolith if these 5 patterns are not in place.
From Hard Science to Baseless Opinions - OredevAli Kheyrollahi
From the mathematicians and scientists of the 20th centuries to today's ninja craftsmen/craftswomen, Software community has lost something along the way. Instead of carefully observing scientific methods and maintaining objectivity, we have tangled ourselves in web of hype and celebrity culture - as if adopting today's YOLO motto. We have completely forgot how to reason scientifically about matters of technical dispute, instead, whoever is more opinionated or shouts louder wins - as if software is an abstract art where you can only form an opinion.
This talk is a critique of the status quo. With a survey of the history of modern culture, we will try to find the origin of our mindset which is very much rooted in the postmodern thought. Then we review the steps we have taken wrong and at the end, we exemplify the techniques of formal/scientific reasoning. A sobering talk yet not without sprinkles of fun and sense of humour...
If you have always felt something is wrong... here is the red pill for you...
"Netflix is actually a log generating application that just happens to stream movies"
Building a service/Microservice is itself easy. Scaling it on the cloud is not that hard either but operating, maintaining and iterating a production large scale service is not just about linearisation. As Cockcroft points out, telemetry and monitoring is the most important aspect of building Microservices
We discuss 5 patterns that any serious Microservice should have:
- Canary (an endpoint reporting health of underlying dependencies)
- IO monitor (measuring all calls from Microservice to external dependencies)
- A circuit breaker
- An ActivityId-Propagator
- An exception and short timeout retry policy
From the mathematicians and scientists of the 20th centuries to today's ninja craftsmen/craftswomen, Software community has lost something along the way. Instead of carefully observing scientific methods and maintaining objectivity, we have tangled ourselves in web of hype and celebrity culture - as if adopting today's YOLO motto. We have completely forgot how to reason scientifically about matters of technical dispute, instead, whoever is more opinionated or shouts louder wins - as if software is an abstract art where you can only form an opinion.
Journey of ASOS to migrate legacy ball of mud / monolith to Microservice Architecture. Also review of our Logging Monitoring Alerting (LMA) framework .
5 Anti-Patterns in Api Design - NDC London 2016Ali Kheyrollahi
This talks elaborates on the Client-Server tenet of REST which focuses on separation of concerns between the client and the server. In the first third of the talk, I will talk about what the ideal client and servers are and examples of how their responsibilities. I will touch on how the word Server has lost its meaning of "serving" and the client has been overshadowed by the focus to the API. I will also compare the API to a restaurant and how its menu is the API's REST resources.
In the rest of the talk, I look at some important anti-patterns commonly seen in the industry (each with at least one example):
1) Chauvinist Server: designing the API from server's perspective failing to hide its complexity behind its API (API designed from the server's perspective)
2) Demanding client: client enforcing its special need onto the signature of the API (certain client's limitation becomes server's default behaviour)
3) Transparent Server: server exposing its internal implementation to its clients (server's underlying or private domain bleeds into the public API)
4) Presumptuous Client: The client assuming the role of a server and engage in taking responsibilities that cannot guarantee
5) Assuming Server: Server that assumes the responsibility of tailoring the response based on what it assumes client is (e.g. browser sniffing)
This talks elaborates on the Client-Server tenet of REST which focuses on separation of concerns between the client and the server. In the first third of the talk, I will talk about what the ideal client and servers are and examples of how their responsibilities. I will touch on how the word Server has lost its meaning of "serving" and the client has been overshadowed by the focus to the API. I will also compare the API to a restaurant and how its menu is the API's REST resources.
In the rest of the talk, I look at some important anti-patterns commonly seen in the industry (each with at least one example):
1) Chauvinist Server: designing the API from server's perspective failing to hide its complexity behind its API (API designed from the server's perspective)
2) Demanding client: client enforcing its special need onto the signature of the API (certain client's limitation becomes server's default behaviour)
3) Transparent Server: server exposing its internal implementation to its clients (server's underlying or private domain bleeds into the public API)
4) Presumptuous Client: The client assuming the role of a server and engage in taking responsibilities that cannot guarantee
5) Assuming Server: Server that assumes the responsibility of tailoring the response based on what it assumes client is (e.g. browser sniffing)
This talks elaborates on the Client-Server tenet of REST which focuses on separation of concerns between the client and the server. In the first third of the talk, I will talk about what the ideal client and servers are and examples of how their responsibilities. I will touch on how the word Server has lost its meaning of “serving” and the client has been overshadowed by the focus to the API. I will also compare the API to a restaurant and how its menu is the API’s REST resources.In the rest of the talk, I look at some important anti-patterns commonly seen in the industry (each with at least one example)
1. Chauvinist Server: designing the API from server’s perspective failing to hide its complexity behind its API (API designed from the server’s perspective).
2. Demanding client: client enforcing its special need onto the signature of the API (certain client’s limitation becomes server’s default behaviour).
3. Transparent Server: server exposing its internal implementation to its clients (server’s underlying or private domain bleeds into the public API).
4. Presumptuous Client: The client assuming the role of a server and engage in taking responsibilities that cannot guarantee.
5. Assuming Server: Server that assumes the responsibility of tailoring the response based on what it assumes client is (e.g. browser sniffing).
Graspan: A Big Data System for Big Code AnalysisAftab Hussain
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
Mobile App Development Company In Noida | Drona InfotechDrona Infotech
Looking for a reliable mobile app development company in Noida? Look no further than Drona Infotech. We specialize in creating customized apps for your business needs.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
Custom Healthcare Software for Managing Chronic Conditions and Remote Patient...Mind IT Systems
Healthcare providers often struggle with the complexities of chronic conditions and remote patient monitoring, as each patient requires personalized care and ongoing monitoring. Off-the-shelf solutions may not meet these diverse needs, leading to inefficiencies and gaps in care. It’s here, custom healthcare software offers a tailored solution, ensuring improved care and effectiveness.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️Łukasz Chruściel
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Microservice Architecture at ASOS - DevSum 2017Ali Kheyrollahi
For the past 3 years, ASOS has been on a journey of moving its monolithic architecture to Microservices - and what has been driving this change is not just the buzzword: as with any monolith, the spiraling cost of change stifles the business and innovation. And in this market, advancing your competitive edge by constant improvement is a big factor in the overall success of your business.
Probably not many know that ASOS website drives more traffic (and way more bandwidth) than the showcase Stackoverflow. Some of the services are built to serve up to 10K RPS (request/second). And the services are spread around the globe currently on more than 4 Azure DCs. And on the top, we have pretty thick data pipelines moving many GBs of data to enable traditional BI - as well as the trendy Machine Learning algorithms powering recommendations and personalisation.
This talk will be a brief intro to the overall view of what +20 2-pizza teams are doing and in specific, goes into some of the details of ML-enabled recommendations platform. Underneath the success of the transition, has been a Logging/Monitoring/Alerting system (Elasticsearch+ConverorBelt+Kibana) to empower platform teams to ensure health of the system and keeping Mean-Time-to-Recovery low.
As with any such talk, there will be a section on lessons learned...
5 must have patterns for your microservice - techoramaAli Kheyrollahi
"Netflix is actually a log generating application that just happens to stream movies"
Building a service/Microservice is itself easy. Scaling it on the cloud is not that hard either but operating, maintaining and iterating a production large scale service is not just about linearisation. As Cockcroft points out, telemetry and monitoring is the most important aspect of building Microservices
We discuss 5 patterns that any serious Microservice should have:
- Canary (an endpoint reporting health of underlying dependencies)
- IO monitor (measuring all calls from Microservice to external dependencies)
- A circuit breaker
- An ActivityId-Propagator
- An exception and short timeout retry policy
Real time monitoring-alerting: storing 2Tb of logs a day in ElasticsearchAli Kheyrollahi
Building any average complex system in the cloud requires telemetry to be the number one concern: you would probably even start with planning and building it first (or perhaps you wish you had!). As quoted by Werner Vogels “Netflix is a log generating application, that happens to stream video quote” - Logging/Monitoring/Alerting has been central to the success of Netflix.
In ASOS, we currently generate more than 1TB of logs daily that gets stored and analysed in our Elasticsearch cluster for monitoring and alerting purposes. ELK stack (Elasticsearch, Logstash and Kibana) has been a very popular tool for logging and monitoring but tuning ELasticsearch for handling such a load is an art form in itself.
In this talk, we start with an overview of ELK stack (we in ASOS use CoveyorBelt instead of logstash so ECK for us) and then move to sharing what we have learned from trying to scale our Elasticsearch for this load: from tuning various configuration parameters to planning your shards and mapping strategy, this talk has quite a bit to equip you to build or tune an ELK stack in your own company.
5 must-have patterns for your microservice - buildstuffAli Kheyrollahi
"Netflix is actually a log generating application that just happens to stream movies"
Building a service/Microservice is itself easy. Scaling it on the cloud is not that hard either but operating, maintaining and iterating a production large scale service is not just about linearisation. As Cockcroft points out, telemetry and monitoring is the most important aspect of building Microservices
We discuss 5 patterns that any serious Microservice should have:
- Canary (an endpoint reporting health of underlying dependencies)
- IO monitor (measuring all calls from Microservice to external dependencies)
- A circuit breaker
- An ActivityId-Propagator
- An exception and short timeout retry policy
Apart from the Microservice buzzword, there is a saddening lack of understanding of what a successful Microservice architecture requires in terms of monitoring and telemetry. MTR in case of a Microservice can be much more than a monolith if these 5 patterns are not in place.
From Hard Science to Baseless Opinions - OredevAli Kheyrollahi
From the mathematicians and scientists of the 20th centuries to today's ninja craftsmen/craftswomen, Software community has lost something along the way. Instead of carefully observing scientific methods and maintaining objectivity, we have tangled ourselves in web of hype and celebrity culture - as if adopting today's YOLO motto. We have completely forgot how to reason scientifically about matters of technical dispute, instead, whoever is more opinionated or shouts louder wins - as if software is an abstract art where you can only form an opinion.
This talk is a critique of the status quo. With a survey of the history of modern culture, we will try to find the origin of our mindset which is very much rooted in the postmodern thought. Then we review the steps we have taken wrong and at the end, we exemplify the techniques of formal/scientific reasoning. A sobering talk yet not without sprinkles of fun and sense of humour...
If you have always felt something is wrong... here is the red pill for you...
"Netflix is actually a log generating application that just happens to stream movies"
Building a service/Microservice is itself easy. Scaling it on the cloud is not that hard either but operating, maintaining and iterating a production large scale service is not just about linearisation. As Cockcroft points out, telemetry and monitoring is the most important aspect of building Microservices
We discuss 5 patterns that any serious Microservice should have:
- Canary (an endpoint reporting health of underlying dependencies)
- IO monitor (measuring all calls from Microservice to external dependencies)
- A circuit breaker
- An ActivityId-Propagator
- An exception and short timeout retry policy
From the mathematicians and scientists of the 20th centuries to today's ninja craftsmen/craftswomen, Software community has lost something along the way. Instead of carefully observing scientific methods and maintaining objectivity, we have tangled ourselves in web of hype and celebrity culture - as if adopting today's YOLO motto. We have completely forgot how to reason scientifically about matters of technical dispute, instead, whoever is more opinionated or shouts louder wins - as if software is an abstract art where you can only form an opinion.
Journey of ASOS to migrate legacy ball of mud / monolith to Microservice Architecture. Also review of our Logging Monitoring Alerting (LMA) framework .
5 Anti-Patterns in Api Design - NDC London 2016Ali Kheyrollahi
This talks elaborates on the Client-Server tenet of REST which focuses on separation of concerns between the client and the server. In the first third of the talk, I will talk about what the ideal client and servers are and examples of how their responsibilities. I will touch on how the word Server has lost its meaning of "serving" and the client has been overshadowed by the focus to the API. I will also compare the API to a restaurant and how its menu is the API's REST resources.
In the rest of the talk, I look at some important anti-patterns commonly seen in the industry (each with at least one example):
1) Chauvinist Server: designing the API from server's perspective failing to hide its complexity behind its API (API designed from the server's perspective)
2) Demanding client: client enforcing its special need onto the signature of the API (certain client's limitation becomes server's default behaviour)
3) Transparent Server: server exposing its internal implementation to its clients (server's underlying or private domain bleeds into the public API)
4) Presumptuous Client: The client assuming the role of a server and engage in taking responsibilities that cannot guarantee
5) Assuming Server: Server that assumes the responsibility of tailoring the response based on what it assumes client is (e.g. browser sniffing)
This talks elaborates on the Client-Server tenet of REST which focuses on separation of concerns between the client and the server. In the first third of the talk, I will talk about what the ideal client and servers are and examples of how their responsibilities. I will touch on how the word Server has lost its meaning of "serving" and the client has been overshadowed by the focus to the API. I will also compare the API to a restaurant and how its menu is the API's REST resources.
In the rest of the talk, I look at some important anti-patterns commonly seen in the industry (each with at least one example):
1) Chauvinist Server: designing the API from server's perspective failing to hide its complexity behind its API (API designed from the server's perspective)
2) Demanding client: client enforcing its special need onto the signature of the API (certain client's limitation becomes server's default behaviour)
3) Transparent Server: server exposing its internal implementation to its clients (server's underlying or private domain bleeds into the public API)
4) Presumptuous Client: The client assuming the role of a server and engage in taking responsibilities that cannot guarantee
5) Assuming Server: Server that assumes the responsibility of tailoring the response based on what it assumes client is (e.g. browser sniffing)
This talks elaborates on the Client-Server tenet of REST which focuses on separation of concerns between the client and the server. In the first third of the talk, I will talk about what the ideal client and servers are and examples of how their responsibilities. I will touch on how the word Server has lost its meaning of “serving” and the client has been overshadowed by the focus to the API. I will also compare the API to a restaurant and how its menu is the API’s REST resources.In the rest of the talk, I look at some important anti-patterns commonly seen in the industry (each with at least one example)
1. Chauvinist Server: designing the API from server’s perspective failing to hide its complexity behind its API (API designed from the server’s perspective).
2. Demanding client: client enforcing its special need onto the signature of the API (certain client’s limitation becomes server’s default behaviour).
3. Transparent Server: server exposing its internal implementation to its clients (server’s underlying or private domain bleeds into the public API).
4. Presumptuous Client: The client assuming the role of a server and engage in taking responsibilities that cannot guarantee.
5. Assuming Server: Server that assumes the responsibility of tailoring the response based on what it assumes client is (e.g. browser sniffing).
Graspan: A Big Data System for Big Code AnalysisAftab Hussain
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
Mobile App Development Company In Noida | Drona InfotechDrona Infotech
Looking for a reliable mobile app development company in Noida? Look no further than Drona Infotech. We specialize in creating customized apps for your business needs.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
Custom Healthcare Software for Managing Chronic Conditions and Remote Patient...Mind IT Systems
Healthcare providers often struggle with the complexities of chronic conditions and remote patient monitoring, as each patient requires personalized care and ongoing monitoring. Off-the-shelf solutions may not meet these diverse needs, leading to inefficiencies and gaps in care. It’s here, custom healthcare software offers a tailored solution, ensuring improved care and effectiveness.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️Łukasz Chruściel
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptxrickgrimesss22
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
Utilocate offers a comprehensive solution for locate ticket management by automating and streamlining the entire process. By integrating with Geospatial Information Systems (GIS), it provides accurate mapping and visualization of utility locations, enhancing decision-making and reducing the risk of errors. The system's advanced data analytics tools help identify trends, predict potential issues, and optimize resource allocation, making the locate ticket management process smarter and more efficient. Additionally, automated ticket management ensures consistency and reduces human error, while real-time notifications keep all relevant personnel informed and ready to respond promptly.
The system's ability to streamline workflows and automate ticket routing significantly reduces the time taken to process each ticket, making the process faster and more efficient. Mobile access allows field technicians to update ticket information on the go, ensuring that the latest information is always available and accelerating the locate process. Overall, Utilocate not only enhances the efficiency and accuracy of locate ticket management but also improves safety by minimizing the risk of utility damage through precise and timely locates.
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
Enterprise Resource Planning System includes various modules that reduce any business's workload. Additionally, it organizes the workflows, which drives towards enhancing productivity. Here are a detailed explanation of the ERP modules. Going through the points will help you understand how the software is changing the work dynamics.
To know more details here: https://blogs.nyggs.com/nyggs/enterprise-resource-planning-erp-system-modules/
E-commerce Application Development Company.pdfHornet Dynamics
Your business can reach new heights with our assistance as we design solutions that are specifically appropriate for your goals and vision. Our eCommerce application solutions can digitally coordinate all retail operations processes to meet the demands of the marketplace while maintaining business continuity.
Launch Your Streaming Platforms in MinutesRoshan Dwivedi
The claim of launching a streaming platform in minutes might be a bit of an exaggeration, but there are services that can significantly streamline the process. Here's a breakdown:
Pros of Speedy Streaming Platform Launch Services:
No coding required: These services often use drag-and-drop interfaces or pre-built templates, eliminating the need for programming knowledge.
Faster setup: Compared to building from scratch, these platforms can get you up and running much quicker.
All-in-one solutions: Many services offer features like content management systems (CMS), video players, and monetization tools, reducing the need for multiple integrations.
Things to Consider:
Limited customization: These platforms may offer less flexibility in design and functionality compared to custom-built solutions.
Scalability: As your audience grows, you might need to upgrade to a more robust platform or encounter limitations with the "quick launch" option.
Features: Carefully evaluate which features are included and if they meet your specific needs (e.g., live streaming, subscription options).
Examples of Services for Launching Streaming Platforms:
Muvi [muvi com]
Uscreen [usencreen tv]
Alternatives to Consider:
Existing Streaming platforms: Platforms like YouTube or Twitch might be suitable for basic streaming needs, though monetization options might be limited.
Custom Development: While more time-consuming, custom development offers the most control and flexibility for your platform.
Overall, launching a streaming platform in minutes might not be entirely realistic, but these services can significantly speed up the process compared to building from scratch. Carefully consider your needs and budget when choosing the best option for you.
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...Crescat
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
AI Genie Review: World’s First Open AI WordPress Website CreatorGoogle
AI Genie Review: World’s First Open AI WordPress Website Creator
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-genie-review
AI Genie Review: Key Features
✅Creates Limitless Real-Time Unique Content, auto-publishing Posts, Pages & Images directly from Chat GPT & Open AI on WordPress in any Niche
✅First & Only Google Bard Approved Software That Publishes 100% Original, SEO Friendly Content using Open AI
✅Publish Automated Posts and Pages using AI Genie directly on Your website
✅50 DFY Websites Included Without Adding Any Images, Content Or Doing Anything Yourself
✅Integrated Chat GPT Bot gives Instant Answers on Your Website to Visitors
✅Just Enter the title, and your Content for Pages and Posts will be ready on your website
✅Automatically insert visually appealing images into posts based on keywords and titles.
✅Choose the temperature of the content and control its randomness.
✅Control the length of the content to be generated.
✅Never Worry About Paying Huge Money Monthly To Top Content Creation Platforms
✅100% Easy-to-Use, Newbie-Friendly Technology
✅30-Days Money-Back Guarantee
See My Other Reviews Article:
(1) TubeTrivia AI Review: https://sumonreview.com/tubetrivia-ai-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
#AIGenieApp #AIGenieBonus #AIGenieBonuses #AIGenieDemo #AIGenieDownload #AIGenieLegit #AIGenieLiveDemo #AIGenieOTO #AIGeniePreview #AIGenieReview #AIGenieReviewandBonus #AIGenieScamorLegit #AIGenieSoftware #AIGenieUpgrades #AIGenieUpsells #HowDoesAlGenie #HowtoBuyAIGenie #HowtoMakeMoneywithAIGenie #MakeMoneyOnline #MakeMoneywithAIGenie
7. Data Source - Wiki
4,990,2794,990,279 English Articles
37,583,879 Articles
8. Data Source - Wiki vs Britannica
Feng Zhu (assistant prof at Harvard):
“There has been lots of research on the accuracy of
Wikipedia, and the results are mixed—some studies
show it is just as good as the experts, others show
[that] Wikipedia is not accurate at all.”
“… the editors [of Britannica] are still not
found to be more objective than the crowd
in articles that are sufficiently revised.”
9. Data Source - Wikipedia in scholar papers
0
45000
90000
135000
180000
2005 2006 2007 2008 2009 2010 2011 2012 2013 2014
Source: Google Scholar
10. Data Acquisition - Wiki
List of Rock
Genres
Rock Genres Rock Artists
Store
Store
HTML
Capture
Links
Store
HTML
Python scripts
Postgres
11. Data Source - Content vs. Data
Hyphen
U+002D
figure dash
U+2012
minus sign
U+2015
em dash
U+2014
en dash
U+2013
13. Data Exploration
“I personally … literally just look at the screen,
just like the matrix”
Claudia Perlich, multi-award winner Data
Scientist
14. Data Exploration
“… the dirty little secret that I have won all of them
because I have found something wrong with the
data… I would like to play around with dataset and
get initimately familiar with dataset and its
properties.“
Claudia Perlich
19. Data Models Model
Mathematical representation of a concept
based on parameters that impact that
concept
• Rating of a native app
• Stackoverflow score
• Credit score
• Fraud check
20. “All models are wrong… but
some are useful.
George Box
Data Models Model
21. Data Models Graph 101
Social Network Analysis
and Graph Theory
• Nodes/vertices and edges/lines
• Directedness:
• Directed
• Undirected
• Degree, InDegree/OutDegree
• Weight
A B
23. Graph Codez
import networkx as nx
g = nx.Graph()
g.add_edge(‘a’, ‘b’)
g.add_edge(‘b’, ‘c’)
…
print len(g[‘b’]) # degree
c = nx.betweenness_centrality(g, normalized=True)
# c -> dictionary of node names and their score
DiGraph()
26. Data Models Cited Influence
Most influential Rock Artists Based on out-degree
The Beatles => 188
Black Sabbath => 127
Led Zeppelin => 118
Jimi Hendrix => 114
Bob Dylan => 94
Pink Floyd => 86
Iron Maiden => 77
Metallica => 77
The Rolling Stones => 66
The Beach Boys => 65
Neil Young => 63
Nirvana => 62
Slayer => 60
Queen => 59
27. Data Models Cited Influence
Most influential Rock Artists Based on Betweenness Centrality
Jimi Hendrix => 53476.2014921
The Beatles => 47511.7957531
Bob Dylan => 38107.0298185
Led Zeppelin => 32701.7223273
Nirvana => 29733.9066836
Metallica => 29356.6009213
Queen => 28989.2844223
Robert Smith => 28880.670718
Elvis Presley => 28463.2891497
Slade => 27656.487307
Iron Maiden => 22449.6697023
Ramones => 22437.6112965
Rush => 21125.9481602
Neil Young => 19913.887522
28. Data Models Cited Influence
Most influential Artists Based on Betweenness Centrality
Metallica => 566.06
Iron Maiden => 419.21
Corey Taylor => 146.0
Led Zeppelin => 122.73
Slipknot => 116.58
King Diamond => 94.7
Machine Head => 85.12
Rush => 70.41
Black Sabbath => 68.0
Van Halen => 54.56
Deep Purple => 53.5
Megadeth => 42.63
Guns N' Roses => 24.25
Heavy Metal
Nirvana => 490.08
Muse => 114.5
Weezer => 97.33
Pixies => 94.17
Sonic Youth => 78.5
Rivers Cuomo => 69.5
Siouxsie and the Banshees => 51.67
The Smiths => 51.5
Jeff Buckley => 46.17
The Offspring => 43.0
Placebo => 42.0
My Chemical Romance => 34.0
The Smashing Pumpkins => 32.33
Alternative Rock
Rush => 54.0
Marillion => 34.0
Pink Floyd => 33.0
Yes => 20.0
Porcupine Tree => 19.5
Dream Theater => 19.0
Chris Squire => 16.5
Primus => 15.0
Tool => 12.0
Mahavishnu Orchestra => 8.0
Geddy Lee => 7.0
Neil Peart => 5.0
Keith Emerson => 5.0
Progressive Rock
30. Data Models Page Rank
The Beatles => 0.00837723421839
Blind Lemon Jefferson => 0.00837369035189
Josh White => 0.00824945015047
Bessie Smith => 0.00717743996144
Louis Armstrong => 0.00692897940193
James P. Johnson => 0.00628676810257
Little Richard => 0.00584677302727
Muddy Waters => 0.005773172933
Tampa Red => 0.00572032424174
Robert Johnson => 0.00523579252974
Big Bill Broonzy => 0.00516075834679
Moon Mullican => 0.0050657751593
Black Sabbath => 0.00498789229732
Elvis Presley => 0.00497932058047
Duke Ellington => 0.00465800760107
Bo Diddley => 0.0044496675634
Jimmy Page => 0.00437658472459
Frank Zappa => 0.00431978608953
Miles Davis => 0.00396303890974
Jimi Hendrix => 0.00391117233916
Sister Rosetta Tharpe => 0.00390833570401
Bing Crosby => 0.00385435213525
Bob Dylan => 0.00358608821536
James Brown => 0.00349870931123
38. Clustering in Networks
Eigenvector: a vector (v) that by getting multiplied in matrix A
does not result in changing its direction (similar to being
multiplied by scalar λ)
u1 u2 u3 u4 u5
-0.7 0.3 -0.2 -0.1 0.7
-0.7 0.3 -0.2 -0.1 0.7
39. Spectral Clustering Codez
from sklearn.cluster import spectral_clustering
import numpy as np
A = [[0.0 for x in n] for x in n]
… # build adjacency matrix
res = spectral_clustering(np.matrix(A),
n_clusters)
# res -> list of cluster indices e.g. [1,1,0,5,…]
40. Spectral Clustering Results
Folk Rock
Country Rock
Blues
Folk
Country
Americana
Roots Rock
Blues Rock
Southern Rock
Power Metal
Progressive Metal
Symphonic Metal
Black Metal
Melodic Death Metal
Groove Metal
Nu Metal
Thrash Metal
Death Metal
Metalcore
Industrial Metal
Gothic Metal
Christian Metal
Doom Metal
Speed Metal
Alternative Rock
Indie Rock
New Wave
Synthpop
Electronica
Rock
R&B
Pop
Pop Rock
Funk
Soul
Heavy Metal
Hard Rock
Alternative Metal
42. word2vec Model
Skip-gram: a proximity-based probability model trained
using Neural Networks (Deep Learning)
Pink Floyd were an English rock band formed in London
X XX
45. Album Genre Model
Fun Happy Saturday
We Are Friends Electronic
Frozen Blood In My Veins
Redneck Dance
Chaos and Mayhem
Basement Dub
Sentiment Analysis in text
Predicting the genre based on name of the album
46. Deep Learning Basics
1) Traditional Neural Networks with many layers
2) Often uses convolution as the node function
3) Training on Big Data can take weeks even on GPU
0) A method of supervised learning
4) Huge success attributed to improved training,
powerful computation and above all Big Data
5) Pooling, Dropout and local connections important
51. References
•All pictures from wikipedia.org used under Creative Commons
•Source of all data is from wikipedia.org collected online using a single call and then stored and processed
•Efficient Estimation of Word Representations in Vector Space. Mikolov et. al. http://arxiv.org/abs/1301.3781
•Gensim's word2vec
•networkx lib
•word2vec blog post (500K docs): Five crazy abstractions my Deep Learning word2vec model just did
•word2vec on Rock music blog: Daft Punk+Tool=Muse: word2vec model trained on a small Rock music corpus
•code for word2vec on wiki data
•Highcharts: highcharts
•word2vec paper: PDF
•Automatic real-time road marking recognition using a feature-driven approach PDF
•Video of the road marking recognition: here and here and here
•Future of Programming - Rise of the Scientific Programmer (and fall of the craftsman)
•Deep Learning articles
•code for Deep Learning genre analysis
•…