This talk discusses the traditional cybersecurity teams and the new ones. This “newly-coined” teams are developer-centric and should be the dream role of each developer and target employees for development companies.
This talk discusses the traditional cybersecurity teams and the new ones. This “newly-coined” teams are developer-centric and should be the dream role of each developer and target employees for development companies.
It is an accepted practice in the machine learning (ML) community to train multiple deep learning models and perform numerous ablation studies in order to find the best model for a certain task.
To the best of my knowledge, the workflow for training and experimenting with multiple deep-learning models is rarely discussed. Check most open-source ML/AI papers and their accompanying Github source code, and you will only see the production-ready version of the AI model. In this session, I will share our experience in how we tailor “”software version control”” to maintain multiple deep learning models. Key discussions include configuring network models to take into account different network architectures, hyperparameter settings, data preparation and pre-processing, and different hardware configurations for training. Version control practices also benefit deep learning, as they allow researchers to track the performance of models more efficiently and train multiple models everywhere (cloud and local PC clusters) at once.
No gimmicky tools and paid software! We’re only going to maximize the open-source libraries available, such as Pytorch, OpenCV, Numpy, Visdom, YAML, and Matplotlib.
This session will be exploring the application of some AI-driven tools in each phase of the Secure Software Development Lifecycle.
We will also discuss the considerations when using AI-driven tools (e.g. in Threat Modeling, Source Code Review, Generating Tests and Test Data, and Hardening Deployment Environments).
This session explores how to efficiently create API endpoints, enabling direct database access without custom backend logic.
Learn to build dynamic, data-driven applications with ease, utilizing REST or GraphQL. Perfect for developers aiming to streamline their workflow and leverage the latest in web technology for enhanced application performance and scalability.
In this session, we will discuss how we were able to implement in a span of 2 months, a problematic system that was being built in 2 years. Many people think it was the tech used. But the answer is no. It was due to the lack of synergy between tech & the client. It is a good reminder that we are hired to solve problems and not just to code.
Ready to embark on a journey through the intricate world of Java debugging? This hands-on session is your roadmap through the maze of effective problem-solving, where logic meets strategy in an epic showdown. Through case studies and real-world examples, uncover the secrets to diagnosing and resolving software anomalies, from unexpected behaviors to performance bottlenecks. Transform your debugging approach with our expert insights, learning to tackle both abstract problems and concrete challenges with confidence.
Some difficulties make automation even less efficient than manual testing unless properly handled. With a lot of people complaining about broken or flaky tests, they are unhappy to spend all their time fixing test failures and not having time for new implementations.
In this talk, I have collected my personal experiences focused on the challenges of test automation in global projects. I will share numerous real-life examples causing trouble in terms of testing and ways to cope with them.
We will discuss ways to avoid broken tests after updated page layouts on the web apps that we are testing, to minimize the number of flaky tests, to automate scenarios where there is a hardware dependency, and to make implementation easier.
This session will discuss the following:
– What is a domain model?
– When should you use a domain model, and when shouldn’t you?
– CQRS Pattern.
– Preventing invalid states.
– Anemic Domain Models & the Entity-Service Anti-Pattern
– When to use a “service”: Domain Service & Application Service
– Bounded Context
* Limited hybrid tickets available.
First-come, first served!