From 6591790e20a429fb6a2f4b2e2130fe8c80187c09 Mon Sep 17 00:00:00 2001 From: Edward Delaporte Date: Sat, 18 Jul 2026 11:03:18 -0500 Subject: [PATCH] Getting some chapter titles added --- 02-who-am-i.Rmd | 6 ++-- 03-late.Rmd | 3 ++ 04-overstays.Rmd | 5 +++ 05-talent-drain.Rmd | 5 +++ 06-stuck.Rmd | 9 +++++ coding-is-stupid.Rmd | 81 ++++++++++++++++++++++++++++++++++++++++++++ index.Rmd | 2 +- 7 files changed, 107 insertions(+), 4 deletions(-) create mode 100644 03-late.Rmd create mode 100644 04-overstays.Rmd create mode 100644 05-talent-drain.Rmd create mode 100644 06-stuck.Rmd create mode 100644 coding-is-stupid.Rmd diff --git a/02-who-am-i.Rmd b/02-who-am-i.Rmd index 43aaf62..83b3155 100644 --- a/02-who-am-i.Rmd +++ b/02-who-am-i.Rmd @@ -1,4 +1,4 @@ -# Who Am I +# Who Does This Guy Think He Is? > And why should you listen to me? @@ -12,6 +12,6 @@ But ignore all of that. Here's my real credentials: As a bonus - If you read far enough, you will get my thoughts on how juggling fire applies to managing engineers. -You can learn more about my art and personal interests at [https://edward.delaporte.us][1] +You can learn more about my art and personal interests at [https://edward.delaporte.us][edus] -[1]: http://edward.delaporte.us +[edus]: http://edward.delaporte.us diff --git a/03-late.Rmd b/03-late.Rmd new file mode 100644 index 0000000..1159f6b --- /dev/null +++ b/03-late.Rmd @@ -0,0 +1,3 @@ +# We Have No Idea How Long This Will Take + + diff --git a/04-overstays.Rmd b/04-overstays.Rmd new file mode 100644 index 0000000..869037f --- /dev/null +++ b/04-overstays.Rmd @@ -0,0 +1,5 @@ +# Great Softwave Overstays It's Welcome + +> "We are building the Legacy Software of tomorrow, today!" + + diff --git a/05-talent-drain.Rmd b/05-talent-drain.Rmd new file mode 100644 index 0000000..3ae0788 --- /dev/null +++ b/05-talent-drain.Rmd @@ -0,0 +1,5 @@ +# Our Best Talent Left + +> Our best talent will leave, and the cost to everyone who stays will be in incalculable. + + diff --git a/06-stuck.Rmd b/06-stuck.Rmd new file mode 100644 index 0000000..3cfc095 --- /dev/null +++ b/06-stuck.Rmd @@ -0,0 +1,9 @@ +# We Got Stuck, Again + +> We all get stuck, over and over and over. + +Being stuck is the natural default state of any software engineer whose typing speed and choice of tool are not embarrassingly slow. + +Great processes help us get to the next point of "stuck" faster and with less waste. + +Getting from "stuck" to unstuck is a more interesting discsussion. diff --git a/coding-is-stupid.Rmd b/coding-is-stupid.Rmd new file mode 100644 index 0000000..56efea0 --- /dev/null +++ b/coding-is-stupid.Rmd @@ -0,0 +1,81 @@ +--- +title: "Coding Is Stupid" +author: "Edward Delaporte V" +--- +# Coding Is Stupid + +> "How I Learned to Stop Worrying, and Love Software Engineering." + +This is a concise guide to navigating painful truths to achieve elegant software. + +While my career managing software engineers benefitted greatly from them, this book will not attempt to cover topics from [Extreme Programming Explained][2] +or [The Dragon Book (Compilers: Principles, Techniques and Tools)][3]. + +[2]: https://isbnsearch.org/isbn/9780134051994 +[3]: https://isbnsearch.org/isbn/9780321486813 + +I have heard that 19 out of 20 software projects fail, by any reasonable success critera. My own experience suggests that this statistic may honestly be generous. Software automation updates are frequently buggy, late, and all-together too expensive. + +When I first heard the 19/20 statistic, I assumed this meant that any given team, on any given project, faced 95% odds of failure. + +But I put to you this awful insight: + + - On any given project, 19 out of 20 software teams face around 99.9% odds of failure. + - On any given project, 1 out of 20 software teams face around 99.9% odds of success. + +The composition and management *of the team* is by far the leading predictor of software automation success. + +If your developer team, in all honesty, delivers consistent reliable bug free solutions before they are needed - then this book may not be for you. + +[Kingdom Come by Mark Waid and Alex Ross][1] is pretty great. + +[1]: https://isbnsearch.org/isbn/9781401290962 + +But if your team matches the industry status quo: + If they are stressed, overworked, over budget, and often produce buggy outputs much too late - then by all means, keep reading. + + + + +# Who Does This Guy Think He Is? + +> And why should you listen to me? + +I have been writing software since 1988, and managing software developers since 2011. I am personally capable of producing effective automation in around 40 development environments. The worst, by far, is `Friendship is Magic / FIM++`. + +I have presented at professional conferences on wide ranging topics around the creation, maintenance, and sun-setting of automation, connecting the dots between usability, accessibility, cybersecurity, and software development practices. + +But ignore all of that. Here's my real credentials: + +> My teams consistently deliver correct effective solutions on time. + +As a bonus - If you read far enough, you will get my thoughts on how juggling fire applies to managing engineers. + +You can learn more about my art and personal interests at [https://edward.delaporte.us][edus] + +[edus]: http://edward.delaporte.us + + + +# We Have No Idea How Long This Will Take + + + + + +# Great Softwave Overstays It's Welcome + +> "We are building the Legacy Software of tomorrow, today!" + + + + + +# Our Best Talent Left + +> Our best talent will leave, and the cost to everyone who stays will be in incalculable. + + + + + diff --git a/index.Rmd b/index.Rmd index 0fa2737..f204d85 100644 --- a/index.Rmd +++ b/index.Rmd @@ -6,7 +6,7 @@ author: "Edward Delaporte V" > "How I Learned to Stop Worrying, and Love Software Engineering." -This book contains critical advice that no one told you about getting results from software engineers. +This is a concise guide to navigating painful truths to achieve elegant software. While my career managing software engineers benefitted greatly from them, this book will not attempt to cover topics from [Extreme Programming Explained][2] or [The Dragon Book (Compilers: Principles, Techniques and Tools)][3]. -- 2.47.3