Viewing profile — MiyamotoAkira

That's interesting. Whenever I have an issue with a flag it gets picked up on dev/test/uat environments (all gets tested, especially around the code behaving the same as before wit…

Regarding checklist people like Hollnagel, Wears, Braithwaite, Dekker, ... have done a bit on investigation (Hollnagel mostly on Healthcare, Dekker started on air industry but spre…

I've used quite extensively Pair Programming, and at its best is better when both people tend to be senior, as you can bounce design ideas out of each other much easier, and is mor…

Going from nothing to some quality control is always an improvement. The point being made is that is not as good as other options.

After having used both PRs and Pair programming with a strong CI setup I found the later much better for quality, design and efficiency.

Pascal had indexes starting at 1 too. Starting indexes at 0 makes sense when you want to enable the developer to manipulate memory (for example, C) Indexes starting at 1 matches wi…

Bulk, for a mail delivery company, refers exclusively to volume. You get discount on volume. Creating massive volumes of customized mails has been trivial for years.

GDPR is the best thing since sliced bread

done today on python someMock = SomeMock() Also, inconsistency. The example that they put is SHOWLN and showln, and they use all over the place showln, but then they write ReadLN. …

Not case sensitive.

> This might be unusual but I would prefer to read someone's mental model of how the code works than the code itself. The hypothesis under Peter Naur's (the N on BNF) "Programming …

> as a code-input robot while developers around him bark commands at him is actually productive. Nothing to do with mob/ensemble programming. At the end, is a discussion that a) ma…

Some writing from Martin Fowler about the project: https://www.martinfowler.com/bliki/C3.html

> Sounds like you would just have people breaking `master` constantly to me. And how do you do code review? Or don't you? Pair and Ensemble programming

I love TBD. But it has its places. For mobile apps I've used (and would use) release branches. You have a hard requirement on the way that app stores work. You can still do TBD for…

Point two: Alternatives to source control branches are dark launches, branch by abstraction and feature flags. Point three: The best results that I have had on developing systems w…

Is even easier with a small team to do TBD. Because the amount of integration is reduced the possible need of branches (or their TBD equivalents dark launch/branch by abstraction/f…

Sadly that is the case with most ideas/techniques, because we misinterpret them or we hear about them 10 reinterpretations down from the original. Nothing like going back to the so…

The Agile manifesto was created by devs, for the benefit of creating software. Everyone gets the benefits. After having used release and feature branches, and trunk based developme…

So the problem is not the feature flags. If the code/system doesn't get improved bit by bit (is ok to have technical debt), then, whatever the technique, you are going to end in a …

Release integration branches bring the behaviour of big releases. The bigger the release, the bigger the risk, therefore the less you want to do it. With release integration branch…

I like that write up on [2]. I have not really been exposed to C in a very long time, and that has been quite informative. I also like that Set of Unit Testing Rules. That is basic…

I just want to point about that sentence of "goal posts get shifted". In his book Test Driven Development by Example (2003), Kent Beck, on the preface, page X says: "Red-Write a li…

Being in the bench is not unusual for Consultancy companies, where there is no necessarily alignment between finishing with a client and starting with the next one. Or even startin…

Rebranding wouldn't help. The same people doing Fauxagile will be doing FauxX after. The underlying issues of why Fauxagile exists don't get removed because of rebranding