Home » Software Development (page 211)

Software Development

Continuous Delivery – Part 5 – Startup – Self Test

Previous Chapter: A/B Testing So far we discussed Feature Toggle and A/B testing. These two methods enable safe guards that your code does not harm your system. Feature toggles enable to gradually use new features and gradually expose it to users, while monitoring that the system behaves as expected. A/B testing on the other hand let you test how your ...

Read More »

The Dev-QA Delicate Relationship

Success to your product is directly influenced by the ability of your QA and Dev teams to work well together. This is even more tightly coupled in the agile world when QA and Dev work and deliver under the same team. Symbiosis between QA and Dev will accelerate delivery time, create a more robust product, and overall will increase team ...

Read More »

Continuous Delivery – Part 4 – A/B Testing

Previous chapter: Continuous Delivery – Part 3 – Feature Toggles From Wikipedia: In web development and marketing, as well as in more traditional forms of advertising, A/B testing or split testing is an experimental approach to web design (especially user experience design), which aims to identify changes to web pages that increase or maximize an outcome of interest (e.g., click-through ...

Read More »

Latency number that you should know

Latency number that you should know Many of you work on low latency & high throughput systems. The key to developing such systems is understanding latency, be it of CPU cache, RAM, disk or network. I found some interesting latency numbers, understanding these numbers is very important because all these are based on speed of light and we all know that ...

Read More »

Testing triangles, pyramids and circles, and UAT

A few months ago Markus Gartner introduced me to the Testing Triangle, or Testing Pyramid. It looks like this: If you Google you will find a few slightly different version and some go by the name of Testing Pyramid. Now a question: where did this come from? Who should I credit with the original? Markus thinks it mike be Mike ...

Read More »

Continuous Delivery – Part 3 – Feature Toggles

Previous chapter: The Road To Continuous Delivery – Part 2 – Visibility One of the key elements in Continuous Delivery is the fact that you stop working with feature branches in your VCS repository; everybody works on the MASTER branch. During our transition to Continuous Deployment we switched from SVN to Git, which handles code merges much better, and has ...

Read More »

How to easily optimize Task Management

When dealing with different types of tasks and priorities, often happens to mistakenly consider urgency and importance as synonyms and hence manage tasks, resources and time with a wrong approach. Urgency is normally driven by external or emergent factors: a customer request, a short deadline, a blocking bug. Importance is usually driven by internal factors: a well known technical debt, ...

Read More »

Multilayered Architecture (3) – The Application Layer

Introduction As Business Documents are considered the input for the Domain Layer, System Requirement Specifications are the main input document for the Application Layer. Scope of this layer is to provide an implementation of the defined requirements for the system. So it is easy to understand that most of the logic contained is process oriented and so linked to a ...

Read More »