A lot of talks go about how to work on a big team, but which are the challenges you face when you're the only person working on your platform? What are the stakes when you are on a small team really product-focused?
MasTool, bankaların süreçlerinin Bankacılık Denetleme ve Düzenleme Kurumu (BDDK) yönetmelik ve genelgelerine uygun olarak hazırlanmasını sağlar. Süreçlerin Risk Kontrol Matrislerine (RCM) göre denetimini kolaylaştırır. Bu kapsamda yapılan test sonuçlarının girilmesini, bulguların sorumlu kişilerle / gruplarla paylaşılmasını, cevap / aksiyon planlarının alınmasını ve takibini, yıllık olarak Süreç Sahibi Beyan Mektupları alınarak Yönetim Beyan Mektubunun hazırlanmasını sağlayan bir üründür.
Detaylı bilgi için tıklayınız: http://mirsis.com.tr/Mastool
Yazılım projelerinde çıkan hatalar ne kadar geç fark edilirlerse o kadar yüksek maliyetlere yol açarlar. Yazılım geliştirme yaşam döngüsünün ilk aşamalarında yapılan testlerle ortaya çıkan hatalar projeye efor maliyeti olarak yansır, son aşamalarında ortaya çıkartılan hatalar ise müşterinin bilgisi dahilinde olabileceği için hem yüksek maliyetli hem de itibar zedeleyici bir şekil alabilir.
Test maliyetleri hataların projede tespit edildiği aşamaya bağlı olarak çok değişkenlik göstermektedir. Önemli olan hataları yazılım geliştirme yaşam döngüsünün ilk adımlarından başlayarak gidermeye yönelik test aşamaları ile yürütmek, yönetmek ve raporlamaktır. Bu şekilde amaçlanan kalite ve standart seviyesine ulaşmak ve süreçleri iyileştirmek mümkündür.
Detaylı bilgi için tıklayınız: http://mirsis.com.tr/TestHizmeti
PSU Web 2015: How To Take The Crazy Out Of Your Company's Process Flows #psuwebJennifer Aldrich
Labels, labels everywhere: product managers, product owners, squads, designers, developers, architects, agile, lean, waterfall, roles, methodologies - the list goes on and on.
How do you pick an internal process flow that will work for your company? What do you do when only part of a process flow fits? What do you do when an entire process you've invested time and money in is a total flop?
This talk will cover how our company created a positive, interdepartmentally collaborative, innovation friendly, process flow from the top down.
I'll cover some trial and error stories, some tools that rescued our sanity, and the workflow we uncovered that fits our organization like a glove.
MasTool, bankaların süreçlerinin Bankacılık Denetleme ve Düzenleme Kurumu (BDDK) yönetmelik ve genelgelerine uygun olarak hazırlanmasını sağlar. Süreçlerin Risk Kontrol Matrislerine (RCM) göre denetimini kolaylaştırır. Bu kapsamda yapılan test sonuçlarının girilmesini, bulguların sorumlu kişilerle / gruplarla paylaşılmasını, cevap / aksiyon planlarının alınmasını ve takibini, yıllık olarak Süreç Sahibi Beyan Mektupları alınarak Yönetim Beyan Mektubunun hazırlanmasını sağlayan bir üründür.
Detaylı bilgi için tıklayınız: http://mirsis.com.tr/Mastool
Yazılım projelerinde çıkan hatalar ne kadar geç fark edilirlerse o kadar yüksek maliyetlere yol açarlar. Yazılım geliştirme yaşam döngüsünün ilk aşamalarında yapılan testlerle ortaya çıkan hatalar projeye efor maliyeti olarak yansır, son aşamalarında ortaya çıkartılan hatalar ise müşterinin bilgisi dahilinde olabileceği için hem yüksek maliyetli hem de itibar zedeleyici bir şekil alabilir.
Test maliyetleri hataların projede tespit edildiği aşamaya bağlı olarak çok değişkenlik göstermektedir. Önemli olan hataları yazılım geliştirme yaşam döngüsünün ilk adımlarından başlayarak gidermeye yönelik test aşamaları ile yürütmek, yönetmek ve raporlamaktır. Bu şekilde amaçlanan kalite ve standart seviyesine ulaşmak ve süreçleri iyileştirmek mümkündür.
Detaylı bilgi için tıklayınız: http://mirsis.com.tr/TestHizmeti
PSU Web 2015: How To Take The Crazy Out Of Your Company's Process Flows #psuwebJennifer Aldrich
Labels, labels everywhere: product managers, product owners, squads, designers, developers, architects, agile, lean, waterfall, roles, methodologies - the list goes on and on.
How do you pick an internal process flow that will work for your company? What do you do when only part of a process flow fits? What do you do when an entire process you've invested time and money in is a total flop?
This talk will cover how our company created a positive, interdepartmentally collaborative, innovation friendly, process flow from the top down.
I'll cover some trial and error stories, some tools that rescued our sanity, and the workflow we uncovered that fits our organization like a glove.
Being Test-Driven: It's not really about testingRaj Indugula
Good news: Test-driven practices have jumped the chasm to general acceptance! The bad news, though, is that while TDD, and BDD are prominent buzzwords in the industry today, they are rife with misconceptions, with many people incorrectly assuming that being test-driven is all about testing. Gain a clearer understanding of Test-Driven Development (TDD), Behavior Driven-Development (BDD), and gain practical insights into how these practices can help teams develop better software.
Launching a new feature is a risky proposition. Even the most well designed and researched features can initially tank your applications' performance and business metrics. Rolling back a poor performing feature can be time consuming and costly. However, it doesn't have to be. Implementing feature management and experimentation into your development lifecycle can help your team reduce risk when launching new features. Feature management isn't just for developers. Product managers can attend this webinar to discover how implementing feature management and experimentation can help prove impact across the product cycle.
Attend this webinar to learn:
- Best practices for launching products with velocity and quality using feature management
- Guidelines for limiting your blast radius when rolling out new or redesigned features
- How using experimentation and feature management in tandem enable you to iterate faster and ship better performing products
Selenium Testing your Kubernetes Apps with Machine Learning and TestimCodefresh
**WATCH THE FULL WEBINAR HERE: https://codefresh.io/testim-lp/
Sign up for a FREE Codefresh account today: https://codefresh.io/codefresh-signup/
There are two big hurdles to solve when adding UI testing to your software delivery pipeline:
1) How to stand up an environment and
2) How to create tests that scale
In this webinar, testing expert Oren Rubin will join Kubernaut Dan Garfield to present how machine learning, Kubernetes pipelines, and Testim can make test creation painless and easy to accomplish. We'll make continuous delivery a reality.
Dragons & Knights - Calabash and Cucumber as Automation Tools for Hybrid Apps...Ron Werner
Slides for the demo talk Ron Werner gave at European Testing Conference 2017 (Feb 8-10).
Consists of two parts: a) the story (which you need to hear live), and b) the cross-device iOS and Android automation live demo
Taming scary production code that nobody wants to touchMike Clement
Most dev teams “own” some code that they don’t really want to work with. However it got there, the code is scary but pretty stable and requires updates. Perhaps your team draws straws to each time to figure out who is going to have to put on the metaphorical hazmat suit and deal with the problem. Or worse yet, your team relies on one developer to always do it and he or she is getting burned out and could leave at any minute.
Mike will share some techniques that will help you modify the code with confidence using a few core refactorings and characterization test.
"Free from the shackles of Test Driven Development" was I quote I heard from a younger colleague of mine whilst introducing him to BDD using SpecFlow as an automation tool.
In this session we shall look at some of the lessons learnt whilst introducing BDD with a full automated test system including both UI and Unit testing into a greenfield project. We shall see how the teams attitudes changed over time and how one person went from wanting to be "free from the shackles of test driven development" to being one of the most prolific specification writers on the team.
We shall also take a deeper dive into the use of SpecFlow an show how it can be used to successfully implement the automation of specfications - creating living documentation. Finally we shall look at how you could structure your test projects in order to help ensure that your tests remain maintainable over time for both Unit and UI tests.
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
In software engineering, the right architecture is essential for robust, scalable platforms. Wix has undergone a pivotal shift from event sourcing to a CRUD-based model for its microservices. This talk will chart the course of this pivotal journey.
Event sourcing, which records state changes as immutable events, provided robust auditing and "time travel" debugging for Wix Stores' microservices. Despite its benefits, the complexity it introduced in state management slowed development. Wix responded by adopting a simpler, unified CRUD model. This talk will explore the challenges of event sourcing and the advantages of Wix's new "CRUD on steroids" approach, which streamlines API integration and domain event management while preserving data integrity and system resilience.
Participants will gain valuable insights into Wix's strategies for ensuring atomicity in database updates and event production, as well as caching, materialization, and performance optimization techniques within a distributed system.
Join us to discover how Wix has mastered the art of balancing simplicity and extensibility, and learn how the re-adoption of the modest CRUD has turbocharged their development velocity, resilience, and scalability in a high-growth environment.
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.
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
Enhancing Research Orchestration Capabilities at ORNL.pdfGlobus
Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.
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/
Exploring Innovations in Data Repository Solutions - Insights from the U.S. G...Globus
The U.S. Geological Survey (USGS) has made substantial investments in meeting evolving scientific, technical, and policy driven demands on storing, managing, and delivering data. As these demands continue to grow in complexity and scale, the USGS must continue to explore innovative solutions to improve its management, curation, sharing, delivering, and preservation approaches for large-scale research data. Supporting these needs, the USGS has partnered with the University of Chicago-Globus to research and develop advanced repository components and workflows leveraging its current investment in Globus. The primary outcome of this partnership includes the development of a prototype enterprise repository, driven by USGS Data Release requirements, through exploration and implementation of the entire suite of the Globus platform offerings, including Globus Flow, Globus Auth, Globus Transfer, and Globus Search. This presentation will provide insights into this research partnership, introduce the unique requirements and challenges being addressed and provide relevant project progress.
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
In the ever-evolving landscape of technology, enterprise software development is undergoing a significant transformation. Traditional coding methods are being challenged by innovative no-code solutions, which promise to streamline and democratize the software development process.
This shift is particularly impactful for enterprises, which require robust, scalable, and efficient software to manage their operations. In this article, we will explore the various facets of enterprise software development with no-code solutions, examining their benefits, challenges, and the future potential they hold.
Check out the webinar slides to learn more about how XfilesPro transforms Salesforce document management by leveraging its world-class applications. For more details, please connect with sales@xfilespro.com
If you want to watch the on-demand webinar, please click here: https://www.xfilespro.com/webinars/salesforce-document-management-2-0-smarter-faster-better/
Top 7 Unique WhatsApp API Benefits | Saudi ArabiaYara Milbes
Discover the transformative power of the WhatsApp API in our latest SlideShare presentation, "Top 7 Unique WhatsApp API Benefits." In today's fast-paced digital era, effective communication is crucial for both personal and professional success. Whether you're a small business looking to enhance customer interactions or an individual seeking seamless communication with loved ones, the WhatsApp API offers robust capabilities that can significantly elevate your experience.
In this presentation, we delve into the top 7 distinctive benefits of the WhatsApp API, provided by the leading WhatsApp API service provider in Saudi Arabia. Learn how to streamline customer support, automate notifications, leverage rich media messaging, run scalable marketing campaigns, integrate secure payments, synchronize with CRM systems, and ensure enhanced security and privacy.
Quarkus Hidden and Forbidden ExtensionsMax Andersen
Quarkus has a vast extension ecosystem and is known for its subsonic and subatomic feature set. Some of these features are not as well known, and some extensions are less talked about, but that does not make them less interesting - quite the opposite.
Come join this talk to see some tips and tricks for using Quarkus and some of the lesser known features, extensions and development techniques.
First Steps with Globus Compute Multi-User EndpointsGlobus
In this presentation we will share our experiences around getting started with the Globus Compute multi-user endpoint. Working with the Pharmacology group at the University of Auckland, we have previously written an application using Globus Compute that can offload computationally expensive steps in the researcher's workflows, which they wish to manage from their familiar Windows environments, onto the NeSI (New Zealand eScience Infrastructure) cluster. Some of the challenges we have encountered were that each researcher had to set up and manage their own single-user globus compute endpoint and that the workloads had varying resource requirements (CPUs, memory and wall time) between different runs. We hope that the multi-user endpoint will help to address these challenges and share an update on our progress here.
Developing Distributed High-performance Computing Capabilities of an Open Sci...Globus
COVID-19 had an unprecedented impact on scientific collaboration. The pandemic and its broad response from the scientific community has forged new relationships among public health practitioners, mathematical modelers, and scientific computing specialists, while revealing critical gaps in exploiting advanced computing systems to support urgent decision making. Informed by our team’s work in applying high-performance computing in support of public health decision makers during the COVID-19 pandemic, we present how Globus technologies are enabling the development of an open science platform for robust epidemic analysis, with the goal of collaborative, secure, distributed, on-demand, and fast time-to-solution analyses to support public health.
Navigating the Metaverse: A Journey into Virtual Evolution"Donna Lenk
Join us for an exploration of the Metaverse's evolution, where innovation meets imagination. Discover new dimensions of virtual events, engage with thought-provoking discussions, and witness the transformative power of digital realms."
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.
A lot of talks go about how to work on a big team.
But sometimes you will be hired on small teams or startups where you have to work alone. Obviously there’s always someone on the team. But what when you are on a one-man team in your platform?
You become the Gunslinger. The guy who has to fight against the bad guys on their own.
You will experience the “Journey of the hero”, which ironically can translate into the “Journey of the developer”.
Rule 1: Never change the deal.
Be a professional. Try to be clear on what are you going to do, and when you will have finished. Shit happens, but as you’re the only one, there is only one responsible. The rest of your team might rely on your deadlines.
Rule 2: No names.
Feedback should be always welcomed. Crticisim, both constructive and destructive should be accepted, no matter where it does come from, and take it as a warning shot before continuing with the same attitude/way of doing things.
Rule 3:
Legacy code. Do not change it unless you know perfectly what you are doing. (On a technical note, never tackle legacy without good practices on refractoring. - Build a reliable test suite of the code beforehand and go refactoring little by little.
Sometimes we didn’t get there first. Sometimes we were not as cunning as we used to be when we did something. Be empathic. No good dev want to do shitty code; but sometimes rush, bad decisions or a bad foundation for a code can lead to “bad” legacy code.
Most of the devs usually fear code they didn’t write. But rebuilding an app or parts of the app might produce two unwanted side effects.
Reappearance of bugs that were already fixed on this “shitty code”.
Losing time on doing the same thing over and over.
Remember that, no matter how good you are, you cannot throw away eg 9 months of work and redo it better on 1.
Let’s talk about Product lifecycle.
Software lifecycle is already a complicated issue (Analysis > Design > Implementation > Testing > Deployment > Maintenance), but building a product is a much more complex issue:
You have a PM who will write a specification of an app or feature
Which a designer will prototype and asset
In the meanwhile your backend team will attempt exactly to do all the work, hopefully before you do yours.
And everybody will want to test and review the work done.
Imagine how many things can go wrong from a technical standpoint.
Source: From Spotify.
But even more things can go wrong from the product standpoint.
A product which is awesomingly good technically can fail because it does not convey the idea correctly.
The difference on this slide is that the people on the top want to build a Car. Obviously a car takes a lot of time and pieces to be built, you start with a wheel, then the body, etc… until you finish. But your customers are not happy because you promised them a car.
However the people on the bottom want to build a “mean of transport”. Obviously a skateboard is not as cool as a sports car; but it fills its purpose: To carry you from one place to the other faster and more effortlessly than a car. And then the only thing you need to do is iterate, iterate, iterate. Faster, more reliable, with more extras...
That’s why Product is about Purpose.
The best example of this is Bricomania TV Programme. They have a lot of professional tools to build the things they build; but they avoid to make the programme a show-off those tools. They USE those tools to show how to build things to improve your home. But the PURPOSE of the programme is about building the stuff, not using the tools.
Don’t make your product become a technical show-off
When you’re working on a small startup; the first golden rule is that: You cannot buy time, no matter how many money do you have.
You have to think carefully your rodamap and your moviements. Invest wisely your time; a misstep might end up messing your time to deliver or mess up with the rest of the teams.
When you work alone, the worst enemy is not the guy from product, the designer who reviews your sceeens or the QA who points your errors.
YOU are your worst enemy.
The best way to avoid you adding mistakes is yo use good practices from the beginning. Try to automatize things as much as possible, Build Systems, Testing suites, Continous integrations.
Use tools that will cushion potential failures like Staged Rollouts and Betas, the sooner the code is in production in a controlled way, the earlier you will receive error reports.
Use tools like Crashlytics to know where the app is failing and Mixpanel to understand cognitive frictions on the product itself.
When everything fails, keep calm.
Try to use your tools to diagnose properly:
Analytics could be of use to understand if it is a certain brand, device or Android version which is failing.
Having a push system from day 0 is advised. You can communicate things through push notifications or use it to enable/disable functionalities or app itself
Try to hold the urge to hotfix every 2 minutes, especially on Android. Too many updates will fragment your userbase and will piss them off.
Have a out-of-app update notification system. It takes little time and will bug the users enough to force them to update.
Eventually your team will grow if things go properly, and will need to find a good partner.
Find a guy who:
Thinks, independently of how skilled on your platform is
Delivers and can do stuff
Is personality-compatible with you.
Don’t feel bad if he’s better than you. You will learn from him. Don’t feel bad if he’s more junior than you. Everyone started learning
Let’s talk about philosophy. What does Testing provide you as a developer?