Posts by JonKernPA

DARPA suggests turning old C code automatically into Rust – using AI, of course

Adding any Test-driven aspects?

I wonder if TRACTOR is considering first writing a test suite to cover the original codebase's functionality (if none exists).

Then TRACTOR BEAM the tests to Rust as well, and therefore have a closed-loop means of ensuring the translation is a functional equivalent...

Agile Manifesto co-author blasts failure rates report, talks up 'reimagining' project

Re: The more process you have the less agile you are.

A subtle tweak is:

"The more non-value-add process you have the less agile you are."

Or, put another way, you should create the minimal process required for you to be effective at delivering value.

Sadly, before we had all this certified process framework-in-an-expensive-box stuff, folks got together to do a thing (aka, achieve some goal, some flag in the distance product vision).

After a bit of time working together, they may have noticed some things they could repeat in a common way of working. Maybe they needed to add new people and wanted to "loosely" show them how they worked -- so they drew a process flow chart. They may have even written some documentation.

Then, some tedious crap that happened frequently started to annoy some of the folks. So it was automated -- and even better, a tool was invented to make it suck less.

Now the team has honed in on the right amount of process.

And as the months go on, they adjust up or down as needed in their process.

Re: The more process you have the less agile you are.

> "I'm a middle manager at a large fintech, and I trust my engineers."

Bingo. Enough said. Trust.

Re: Agile misconceptions are rife

It looks like a test question... Or a question to weed out the drive-by candidates.

It could have been a great opportunity to have had a conversation with the "powers that be" -- if for no other reason than to cement your decision that this is a lousy opportunity.

Or to see if there was any chance that the box that the project was in was doable. And where were the biggest concerns in the constraints?

And did the company have a great attitude and were they nice folks who could learn how to control the "gas and the brakes" for a product development process?

Anyway, the optimist in me could make this opportunity work out if it was mildly reasonable in a few other attributes.

Or they may have been fabulously delusional. So "moving along" was the right call...

Study finds 268% higher failure rates for Agile software projects

Strawman Arguments always win...

Hmmm. As a co-author of the Manifesto, what you cite here (at least in the beginning as I didn't get very far) is anything but agile practices.

So yea, if one practices in a non-agile way, you get lots of failures.