Day 0: The 100 in a 100 Project

April 21, 2013 — Posted by Al Shalloway

I have been in software development for almost 43 years now.  This doesn't mean I'm smarter than anyone, it just means I'm older, er, I mean I've seen a lot..  One thing I've seen repeatedly is arguments and discussions about how to do things.  Re-entrant code in the 70s, structured code in the 70s as well.  4th generation languages in the 80s, object-oriented code in the 80s and patterns in the 90s. Waterfall, Agile, XP, Scrum, Lean, Kanban and other development systems for 4+ decades. Slowly, over time, some in the industry have figured out how to do things well.  Typically it takes a couple of decades (at least) for the world to catch up.  By the end of the 20th century, the principles you needed to follow for designing and writing code were pretty well known (albeit not generally followed).  A decade ago, how to have a team develop software effectively and efficiently was known (again, not generally followed).  Now, a decade after that, how to do it at scale is known (and again, not generally followed).   These gaps are great examples of  the technology gap - the difference between what is possible and what is being practiced.

I am beginning a series of blogs that will flesh out 100 Things You Must Know to Be Effective In Software Development.  I intend to  add 1 a day until I get to what ends up being the final number (just guessing at 100, but I think that'll be reasonably close).  I'll admit to cheating - I started this a few days ago so I could get a head start in case I missed a day.  Also, many of these have already been discussed by myself or other Net Objectives' personnel so I may end up just pointing to something that already exists.  I suggest you not look ahead, but instead read one a day -  think of it as vitamins for your brain. 

We can't close this gap without understanding the gap exists.  This series is intended to do that.  I promise if you read these blogs every day you will not look at software in the same way after the series is completed.  

Today's entry is the base page from which all of these items will link: 100 Things You Must Know to Be Effective In Software Development. It will describe how to comment on this series and how to commit to learning.  Please take a look and I'll have the first one ready for you tomorrow.

I am hoping people will declare they are taking up the challenge and will read these blogs - one a day. If you are wiling to do that, please add a comment to this one and let me know, it'll add energy to the process.

Al Shalloway
CEO, Net Objectives

 

 

Subscribe to our blog Net Objectives Thoughts Blog

Share this:

About the author | Al Shalloway

Al Shalloway is the founder and CEO of Net Objectives. With over 40 years of experience, Alan is an industry thought leader in Lean, Kanban, product portfolio management, SAFe, Scrum and agile design.


Comments

I'll be reading these entries.

count me in :-)

Alan,

I will be reading along. Right away, I struggled creating a cohesive vision of the end product based on the description. It appears to be a pearls of wisdom collection. I will continue to read and form a larger picture as I go.

Richard

Count me in

This is the stuff that I need to get reminded of as I get mired down in the day-to-day slog of just getting things done... or at least trying to.

A few years ago I was told that the best salesmen are always spending their own money going to how to be a better salesmen events. They believe if learn just one useful thing at a 3 day conference the whole price was worth it.

I'm not in sales, so I don't attend those events. However I do spend a little bit of time every night, attend classes, and travel to conferences: all because I don't know enough to solve all the problems I'm going to face in the future. I don't know what I will learn, but one thing that will help is all I ask. The time spent will be worth it if you can help me understand just one thing.

I really like the concepts outlined. Not sure I can effectively deal with 100 ideas at the forefront of my mind in day-to-day work. Short term memory 5+-2 items, right?

I really want to see where this leads and how it gets there. May help me in my work. I'll try to stick with it every day. Keep up the good work!

Thanks for doing this.

Hi Alan. I may have to cheat on occasion to catch up after missing a day, but don't take a day off on my account!

Pages

Blog Authors

Al Shalloway
Business, Operations, Process, Sales, Agile Design and Patterns, Personal Development, Agile, Lean, SAFe, Kanban, Kanban Method, Scrum, Scrumban, XP
Cory Foy
Change Management, Innovation Games, Team Agility, Transitioning to Agile
Guy Beaver
Business and Strategy Development, Executive Management, Management, Operations, DevOps, Planning/Estimation, Change Management, Lean Implementation, Transitioning to Agile, Lean-Agile, Lean, SAFe, Kanban, Scrum
Israel Gat
Business and Strategy Development, DevOps, Lean Implementation, Agile, Lean, Kanban, Scrum
Jim Trott
Business and Strategy Development, Analysis and Design Methods, Change Management, Knowledge Management, Lean Implementation, Team Agility, Transitioning to Agile, Workflow, Technical Writing, Certifications, Coaching, Mentoring, Online Training, Professional Development, Agile, Lean-Agile, SAFe, Kanban
Ken Pugh
Agile Design and Patterns, Software Design, Design Patterns, C++, C#, Java, Technical Writing, TDD, ATDD, Certifications, Coaching, Mentoring, Professional Development, Agile, Lean-Agile, Lean, SAFe, Kanban, Kanban Method, Scrum, Scrumban, XP
Marc Danziger
Business and Strategy Development, Change Management, Team Agility, Online Communities, Promotional Initiatives, Sales and Marketing Collateral
Max Guernsey
Analysis and Design Methods, Planning/Estimation, Database Agility, Design Patterns, TDD, TDD Databases, ATDD, Lean-Agile, Scrum
Scott Bain
Analysis and Design Methods, Agile Design and Patterns, Software Design, Design Patterns, Technical Writing, TDD, Coaching, Mentoring, Online Training, Professional Development, Agile
Steve Thomas
Business and Strategy Development, Change Management, Lean Implementation, Team Agility, Transitioning to Agile
Tom Grant
Business and Strategy Development, Executive Management, Management, DevOps, Analyst, Analysis and Design Methods, Planning/Estimation, Innovation Games, Lean Implementation, Agile, Lean-Agile, Lean, Kanban