Recycle Bin 101

•Download as PPT, PDF•

0 likes•338 views

The document discusses 3 products that have erroneously achieved immortality: Visual SourceSafe, Visual C++ 6, and Internet Explorer 6. Visual SourceSafe is chatty and has a working folder randomizer. Visual C++ 6 is essentially the same as Visual Studio 1998 and its code identifies it as Visual C++. Internet Explorer 6 became the corporate standard despite being outdated and its use is prolonged by jQuery.

Software Technology

Recycle Bin 101Recycle Bin 101
3 Products That Have3 Products That Have
Erroneously Achieved ImmortalityErroneously Achieved Immortality
Chris OldwoodChris Oldwood
gort@cix.co.ukgort@cix.co.uk

Visual SourceSafeVisual SourceSafe
►10 Analyze.exe –F, 20 GOTO 1010 Analyze.exe –F, 20 GOTO 10
►More chatty than Alan CarrMore chatty than Alan Carr
►Working Folder randomiserWorking Folder randomiser

Visual C++ 6Visual C++ 6
►Visual Studio 1998 (10 is the new 6)Visual Studio 1998 (10 is the new 6)
►#if _MSC_VER < 1300#if _MSC_VER < 1300
► It’sIt’s VisualVisual C++C++

Internet Explorer 6Internet Explorer 6
►The Corporate StandardThe Corporate Standard
►MDI is so 90’sMDI is so 90’s
►jQuery is fanning the flamesjQuery is fanning the flames

Recycle Bin 101Recycle Bin 101
Chris OldwoodChris Oldwood
gort@cix.co.ukgort@cix.co.uk

More from Chris Oldwood

Becoming a Bitter Programmer

Chris Oldwood

The use of branches within a version control system is a risk management technique. They are commonly used to minimise the risk of unanticipated side-effects when releasing critical changes to production, or to minimise the disruption to developer productivity when making changes to the base product. But branching is not the only means of managing risk and that is what this talk addresses – the forces that drives the use of branches, what are their problems and what are the alternatives.

Waltzing with Branches [Agile o/t Beach]

Chris Oldwood

Modern Unit Testing practices act as a conduit for improved software designs that are more amenable to change and can be easily backed by automation for fast feedback on quality assurance. The necessity of reducing external dependencies forces us to design our modules with minimum coupling which can then be leveraged both at the module, component and subsystem levels in our testing. As we start to integrate our units into larger blocks and interface our resulting components with external systems we find ourselves switching nomenclature as we progress from Unit to Integration testing. But is a change in mindset and tooling really required? The xUnit testing framework is commonly perceived as an aid to Unit Testing but the constraints that it imposes on the architecture mean that it is an excellent mechanism for invoking arbitrary code in a restricted context. Tests can be partitioned by categorisation at the test and fixture level and through physical packaging leading to a flexible test code structure. Throw in its huge popularity and you have a simplified learning curve for expressing more that just unit tests. Using scenarios from his current system Chris aims to show how you can use a similar format and tooling for unit, component and integration level tests; albeit with a few liberties taken to work around the inherent differences with each methodology.

Using xUnit as a Swiss-Aarmy Testing Toolkit

Chris Oldwood

It’s been said that the first 90% of a project consumes 90% of the time, whereas the second 10 % accounts for the other 90% of the time. One reason might be because elevating software from “mostly works” to robust and supportable requires an attention to detail in the parts of a system that are usually mocked out during unit testing. It’s all too easy to focus on testing the happy paths and gloss over the more tricky design problems such as how to handle a full disk or Cheshire cat style network. This session delves into those less glamorous non-functional requirements that crop up the moment you start talking to hard disks, networks, databases, etc. Unsurprisingly it will have a fair bit to say about detecting and recovering from errors; starting with ensuring that you generate them correctly in the first place. This will undoubtedly lead on to the aforementioned subject of testing systemic effects. Finally there will also be diversions into the realms of monitoring and configuration as we look into the operational side of the code once it’s running. At the end you will hopefully have smiled at the misfortune of others (mostly me) and added a few more items to the ever growing list of “stuff I might have to think about when developing software”.

Robust Software

Chris Oldwood

After the text editor and programming language the next most valuable, hotly debated and often poorly used tool is probably the version control system. Some treat it as nothing more than an ad-hoc backup of their source code whilst others endeavour to create a narrative that describes the evolution of their entire software product from inception to decommission. This session takes a walk through the software development lifecycle and examines the role the source control system plays – what we store, why we store it, how we change it and then later how we reconstruct what was changed and why. We’ll look at the various forces that dictate our branching (and subsequent merging) strategies along with some of the less contentious policies we can adopt to ensure our system continues to evolve reliably whilst maintaining a traceable narrative. Despite the range of commercial and open source SCM products out there the patterns and practices I will discuss here are almost universal. For the Software Archaeologist preserving history across file/folder moves and renames is just one aspect where tool specific knowledge matters. But before we can get there we need to deal with their lack of agreement on a common vernacular…

Version Control - Patterns and Practices

Chris Oldwood

Requiem (For Windows XP)

Chris Oldwood

(Re)Reading the Classics

Chris Oldwood

The Art of Code

Chris Oldwood

More from Chris Oldwood (8)

Becoming a Bitter Programmer

Waltzing with Branches [Agile o/t Beach]

Using xUnit as a Swiss-Aarmy Testing Toolkit

Robust Software

Version Control - Patterns and Practices

Requiem (For Windows XP)

(Re)Reading the Classics

The Art of Code

Recently uploaded

BoxLang: Review our Visionary Licenses of 2024

Ortus Solutions, Corp

Agnieszka Andrzejewska - BIM School Course in Kraków

bim.edu.pl

Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.

How to Position Your Globus Data Portal for Success Ten Good Practices

Globus

A Comprehensive Appium Guide for Hybrid App Automation Testing.pdf

kalichargn70th171

How Does XfilesPro Ensure Security While Sharing Documents in Salesforce?

XfilesPro

Using IESVE for Room Loads Analysis - Australia & New Zealand

IES VE

GlobusWorld 2024 Opening Keynote session

Globus

Data privacy is one of the most critical issues that businesses face. This presentation shares insights on the principles and best practices for ensuring the resilience and security of your workload. Drawing on a real-life project from the HR industry, the various challenges will be demonstrated: data protection, self-healing, business continuity, security, and transparency of data processing. This systematized approach allowed to create a secure AWS cloud infrastructure that not only met strict compliance rules but also exceeded the client's expectations.

Designing for Privacy in Amazon Web Services

KrzysztofKkol1

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.

First Steps with Globus Compute Multi-User Endpoints

Globus

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.

Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL

Natan Silnitsky

Breaking the Code : A Guide to WhatsApp Business API.pdf

Meon Technology

Globus Connect Server Deep Dive - GlobusWorld 2024

Globus

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.

Enhancing Research Orchestration Capabilities at ORNL.pdf

Globus

Advanced Flow Concepts Every Developer Should Know

Peter Caitens

Even though at surface level ‘java.lang.OutOfMemoryError’ appears as one single error; underlyingly there are 9 types of OutOfMemoryError. Each type of OutOfMemoryError has different causes, diagnosis approaches and solutions. This session equips you with the knowledge, tools, and techniques needed to troubleshoot and conquer OutOfMemoryError in all its forms, ensuring smoother, more efficient Java applications.

TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERROR

Tier1 app

OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoam

takuyayamamoto1800

NetSage is an open privacy-aware network measurement, analysis, and visualization service designed to help end-users visualize and reason about large data transfers. NetSage traditionally has used a combination of passive measurements, including SNMP and flow data, as well as active measurements, mainly perfSONAR, to provide longitudinal network performance data visualization. It has been deployed by dozens of networks world wide, and is supported domestically by the Engagement and Performance Operations Center (EPOC), NSF #2328479. We have recently expanded the NetSage data sources to include logs for Globus data transfers, following the same privacy-preserving approach as for Flow data. Using the logs for the Texas Advanced Computing Center (TACC) as an example, this talk will walk through several different example use cases that NetSage can answer, including: Who is using Globus to share data with my institution, and what kind of performance are they able to achieve? How many transfers has Globus supported for us? Which sites are we sharing the most data with, and how is that changing over time? How is my site using Globus to move data internally, and what kind of performance do we see for those transfers? What percentage of data transfers at my institution used Globus, and how did the overall data transfer performance compare to the Globus users?

Understanding Globus Data Transfers with NetSage

Globus

Les Buildpacks existent depuis plus de 10 ans ! D’abord, ils étaient utilisés pour détecter et construire une application avant de la déployer sur certains PaaS. Ensuite, nous avons pu créer des images Docker (OCI) avec leur dernière génération, les Cloud Native Buildpacks (CNCF en incubation). Sont-ils une bonne alternative au Dockerfile ? Que sont les buildpacks Paketo ? Quelles communautés les soutiennent et comment ? Venez le découvrir lors de cette session ignite

Paketo Buildpacks : la meilleure façon de construire des images OCI? DevopsDa...

Anthony Dahanne

De mooiste recreatieve routes ontdekken met RouteYou en FME

Jelle | Nordend

Large Language Models (LLMs) are currently the center of attention in the tech world, particularly for their potential to advance research. In this presentation, we'll explore a straightforward and effective method for quickly initiating inference runs on supercomputers using the vLLM tool with Globus Compute, specifically on the Polaris system at ALCF. We'll begin by briefly discussing the popularity and applications of LLMs in various fields. Following this, we will introduce the vLLM tool, and explain how it integrates with Globus Compute to efficiently manage LLM operations on Polaris. Attendees will learn the practical aspects of setting up and remotely triggering LLMs from local machines, focusing on ease of use and efficiency. This talk is ideal for researchers and practitioners looking to leverage the power of LLMs in their work, offering a clear guide to harnessing supercomputing resources for quick and effective LLM inference.

Innovating Inference - Remote Triggering of Large Language Models on HPC Clus...

Globus

Recently uploaded (20)

BoxLang: Review our Visionary Licenses of 2024

Agnieszka Andrzejewska - BIM School Course in Kraków

How to Position Your Globus Data Portal for Success Ten Good Practices

A Comprehensive Appium Guide for Hybrid App Automation Testing.pdf

How Does XfilesPro Ensure Security While Sharing Documents in Salesforce?

Using IESVE for Room Loads Analysis - Australia & New Zealand

GlobusWorld 2024 Opening Keynote session

Designing for Privacy in Amazon Web Services

First Steps with Globus Compute Multi-User Endpoints

Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL

Breaking the Code : A Guide to WhatsApp Business API.pdf

Globus Connect Server Deep Dive - GlobusWorld 2024

Enhancing Research Orchestration Capabilities at ORNL.pdf

Advanced Flow Concepts Every Developer Should Know

TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERROR

OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoam

Understanding Globus Data Transfers with NetSage

Paketo Buildpacks : la meilleure façon de construire des images OCI? DevopsDa...

De mooiste recreatieve routes ontdekken met RouteYou en FME

Innovating Inference - Remote Triggering of Large Language Models on HPC Clus...

Recycle Bin 101

1. Recycle Bin 101Recycle Bin 101 3 Products That Have3 Products That Have Erroneously Achieved ImmortalityErroneously Achieved Immortality Chris OldwoodChris Oldwood gort@cix.co.ukgort@cix.co.uk

2. Visual SourceSafeVisual SourceSafe ►10 Analyze.exe –F, 20 GOTO 1010 Analyze.exe –F, 20 GOTO 10 ►More chatty than Alan CarrMore chatty than Alan Carr ►Working Folder randomiserWorking Folder randomiser

3. Visual C++ 6Visual C++ 6 ►Visual Studio 1998 (10 is the new 6)Visual Studio 1998 (10 is the new 6) ►#if _MSC_VER < 1300#if _MSC_VER < 1300 ► It’sIt’s VisualVisual C++C++

4. Internet Explorer 6Internet Explorer 6 ►The Corporate StandardThe Corporate Standard ►MDI is so 90’sMDI is so 90’s ►jQuery is fanning the flamesjQuery is fanning the flames

5. Recycle Bin 101Recycle Bin 101 Chris OldwoodChris Oldwood gort@cix.co.ukgort@cix.co.uk

6. Recycle Bin 101Recycle Bin 101 Chris OldwoodChris Oldwood gort@cix.co.ukgort@cix.co.uk

Recycle Bin 101

Recommended

Recommended

More Related Content

More from Chris Oldwood

More from Chris Oldwood (8)

Recently uploaded

Recently uploaded (20)

Recycle Bin 101