Relearning is the third of the Seven Wastes of Software Development.
The Seven Wastes were identified by Mary and Tom Poppendieck, the foreparents of Lean Software Development. It grew out of their efforts to understand and apply the principles of Lean Manufacturing to software engineering. Waste elimination is the essence of Lean’s archetype, the Toyota Production System:
All we are doing is looking at the timeline from the moment a customer gives us an order to the point when we collect the cash.
Extra Features are the second of the Seven Wastes of Software Development.
The Seven Wastes were identified by Mary and Tom Poppendieck, the foreparents of Lean Software Development. It grew out of their efforts to understand and apply the principles of Lean Manufacturing to software engineering. Waste elimination is the essence of Lean’s archetype, the Toyota Production System:
All we are doing is looking at the timeline from the moment a customer gives us an order to the point when we collect the cash.
Partially Done Work is the first of the Seven Wastes of Software Development.
The Seven Wastes were identified by Mary and Tom Poppendieck, the foreparents of Lean Software Development. It grew out of their efforts to understand and apply the principles of Lean Manufacturing to software engineering. Waste elimination is the essence of Lean’s archetype, the Toyota Production System:
All we are doing is looking at the timeline from the moment a customer gives us an order to the point when we collect the cash.
Home is where you wake up, and you don’t wonder where you are.
Home is where you look around and you think, “Yes. This is how it should be.”
Home is where your partner in life lives, even when they are away.
Home is where you kid hangs out, just because they want to.
Home is where your 11 year old “puppy” is constantly by your side.
Home is a feeling, but it is also very much a place.
There is a foreign language spoken by the parents at youth baseball tournaments.
I started drafting this piece as I was sitting at yet another opening tournament of what we call “Fall Ball.” My son’s starting at Third Base this year, and he’s also getting some reps as a relief pitcher. As I waited for the game to start, I also waited for the “baseball parent-isms” to start flying.
I didn’t have to wait long.
Waste elimination is critical to delivering value through software.
In the late 1940s, Toyota had a problem. Manufacturing was expensive, so prices were high. But the typical car buyer in Japan was light on cash. Reducing the cost of manufacturing was the only way to sell cars.
Mass production could have solved the problem, but Japan’s economy wasn’t large enough to create demand for thousands of cars. Toyota had to find another way, and they turned to Taiichi Ohno.
As much as I loved my Computer Science curriculum at Ole Miss, it taught me nothing about being an effective software engineer.
When I was in school, Computer Science programs were optimized for producing grad students. Grad students need to excel at research and publishing. Not shipping software.
My career experience has provided no evidence anything has changed. To be an effective software engineer, you must learn on the job.
On September 20, 1998, Cal Ripken Jr. ended his record streak of 2,632 games played. In 1999, he had the highest batting average of his 21-year career.
On July 17, 1941, Joe DiMaggio ended his record streak of 56 consecutive games with a hit. He went on to win the 1941 World Series and American League MVP award.
On October 4, 1988, Orel Hershiser gave up his first run in 67 consecutive innings (regular season and playoffs).
NOTE: I thought about not re-publishing this one. It’s a throwaway essay intended to keep a daily writing streak alive. But it’s kinda funny…
In the spirit of Marshawn Lynch, I’m showing up because the Captain said I had to do this 30 days in a row.
Have I mentioned I’m moving right now? Moving sucks. Especially when you can’t put the rest of your life on hold and focus on just that.
When I got started, I didn’t know a damn thing about software engineering.
It was 2001. I’d just earned my Computer Science degree and was starting my first job. I’d taken the one software engineering course my university offered. I thought I was ready for any coding task they could throw at me.
I couldn’t have been more wrong.
If you do the math, you can tell I’m 20 years into my career.