War and Software development strategies — Intro

Jack S
1 min readMay 30, 2021

--

Disclaimer This article was written in a world without war, and this is not something the author support, by any means or results

War is father of all —Heraclitus

This is all going to be far-fetched and highly debatable, as all good things are, but you can still keep reading, right?

This is about the carnage, blood, and the unfortunate good things that come as a result.

Releasing on Friday evening

I am going to argue that a big part of the methodologies we use for project management in software development, the methodologies that strike success and allow effective management and delivery come from war and the lessons that came along after.

Of course, it’s not like sapper engineers invented the TDD’s fail first principle, or did they?

TDD - fail first — principle

We are going to put that cliffhanger question aside and focus on more simple things.

Starting with the first part

Or jump straight away to part 2

--

--

Jack S

Team lead and Android developer to the bone for six years and counting. In a never-ending search for the right architectural design pattern