HNHacker News
TopNewBestAskShowJobs

MiyamotoAkira

91 karma · joined October 19, 2017

submissionscomments
MiyamotoAkira··on Knightmare: A DevOps Cautionary Tale (2014)
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 with the flag off). The code change never reaches production. And if for some reason the code under the flag is wrong, and it has reached production (something unexpected, unseen), undoing the change is whatever long it takes to switch the flag back (and the cache to update if you have a cache).
MiyamotoAkira··on Knightmare: A DevOps Cautionary Tale (2014)
Regarding checklist people like Hollnagel, Wears, Braithwaite, Dekker, ... have done a bit on investigation (Hollnagel mostly on Healthcare, Dekker started on air industry but spread from there). Read the "Safety-I vs Safety-II" paper or the "When a checklist is not enough: How to improve them and what else is needed" paper
MiyamotoAkira··on Why your team doesn't need to use pull requests
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 more likely that a bad decision (or test, or ...) gets caught earlier.

With junior devs is too easy to become something in which the senior dominates the conversation.

MiyamotoAkira··on Why your team doesn't need to use pull requests
Going from nothing to some quality control is always an improvement. The point being made is that is not as good as other options.
MiyamotoAkira··on Why your team doesn't need to use pull requests
After having used both PRs and Pair programming with a strong CI setup I found the later much better for quality, design and efficiency.
MiyamotoAkira··on The Prime Video microservices to monolith story
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 with a more natural ordinal sequencing.

MiyamotoAkira··on Is Gmail killing independent email?
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.
MiyamotoAkira··on OpenAI’s hunger for data is coming back to bite it
GDPR is the best thing since sliced bread
MiyamotoAkira··on Dragon Programming Language
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. Driving me cranky :-)

MiyamotoAkira··on Dragon Programming Language
Not case sensitive.
MiyamotoAkira··on The Lone Developer Problem
> 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 Theory Building" paper is that transmitting (by talking) the mental model is far more important than other format of documentation to understand a system.

MiyamotoAkira··on The Lone Developer Problem
> 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) make code easy to understand b) create shared knowledge c) avoid unnecessary work.

MiyamotoAkira··on The age of cargo cult Agile must end
Some writing from Martin Fowler about the project:

https://www.martinfowler.com/bliki/C3.html

MiyamotoAkira··on Trunk-Based Development: Game Changers
> 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

MiyamotoAkira··on Trunk-Based Development: Game Changers
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 most of the development of new features, though.

MiyamotoAkira··on Trunk-Based Development: Game Changers
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 were doing exactly that. You need more discipline (like make sure that you run test and linters locally), but my experience is that makes the whole process easier.

CI is continuous integration, there is nothing continuous to coding on your branch and merging after a few days.

MiyamotoAkira··on Trunk-Based Development: Game Changers
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/feature flags) is greatly reduced. So the branches add ceremony where none is needed.

Though those branches could be needed if you are doing mobile, desktop or library/framework development.

MiyamotoAkira··on Trunk-Based Development: Game Changers
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 source.

Edit:it->them

MiyamotoAkira··on Trunk-Based Development: Game Changers
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 development, as a developer I see mostly benefits (there are some drawbacks, there is no perfect technique) with trunk based development.

MiyamotoAkira··on Trunk-Based Development: Game Changers
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 bad place.
MiyamotoAkira··on Trunk-Based Development: Game Changers
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 branches you not only integrate for release (which the bigger the release, the more difficult it is), but also now you have to integrate back from release into main (because bug fixes and what not). The longer that you have had that integration branch, the more likely that you have move forward the main code and the more difficult then becomes the back integration. So you end duplicating the effort.

MiyamotoAkira··on An unexpected benefit of unit tests
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 basically correct, external systems are a no-no on unit testing.

Usually, you deal with mocks through indirections, default arguments, and other stuff like that so you can exclusively test the logic of the function, which is more difficult in C, from what I've seen on your write up, than in other languages. But if you care about not having that on your code for performance reasons, then more likely than not, you will not be able to unit test. And that is fine. You have an integration test (because you are using outside systems). You can still do integration test first, as long as they help you on capturing the logic and flow. The issue is that they tend to be far more involved, and far more brittle (as they depend on those outside systems).

MiyamotoAkira··on An unexpected benefit of unit tests
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 little test that doesn't work, and perhaps doesn't even compile at first"

There is no goal post moving.

More likely, as we transmit information, we don't do it correctly, and knowledge/data gets lost. I found quite enlightening to always go back to the source.

MiyamotoAkira··on Ask HN: Do you hate software engineering but love programming?
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 starting directly on a client when you join them.

Quite useful time to spend learning.

MiyamotoAkira··on Ask HN: Do you hate software engineering but love programming?
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
MiyamotoAkira··on Emacs 29 is nigh
For number 1 I use perspective with projectile.

https://github.com/nex3/perspective-el

https://github.com/bbatsov/persp-projectile

MiyamotoAkira··on Less is more agile
Separate deployment from release (Feature flags). Then you can do QA and show to stakeholders whenever in whichever environment. You can even use it for Code Review, though I prefer pair/ensemble programming to CR (better to correct things as you go than after the fact)
MiyamotoAkira··on Less is more agile
That last example, as you recognise at the end, was an agile flow, as per the Manifesto, they found what worked for them well. However they wanted to call it.

Any other flow in which management wants to standarized the process, fails at agility. I don't consider those Agile. Just because I call the fruit Orange Blue, doesn't make it so.

MiyamotoAkira··on The Zoom installer let a researcher hack his way to root access on macOS
This graph did the rounds on Friday, comparing it to Slack on daily users:

https://twitter.com/Carnage4Life/status/1558054445237149697?...

The graph doesn't include Zoom or Google Meet, so is not a perfect representation.

MiyamotoAkira··on Against Pair Programming
Pair programming is quite intensive when done correctly. You build stamina with time. But even so, using the Pomodoro technique is the way forward. Someone driving for 20/25 minutes, then 5/10 rest, and switch the driver.

Even so, I will still not do it 8 hours a day. Probably 6, to give you time to do other stuff, like investigations, admin, ...

Page 1 of 2Next →