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…
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.
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 :-)
Not case sensitive.
> 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…
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 most of the development of new…
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 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…
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…
Love Zulip. Structured conversations are possible, which is what i want for a business setting. Topics are a great implementation. Code syntax highlighting and code playgrounds are nifty
This keeps bothering me: >7.1 URL structure >Humans SHOULD be able to easily read and construct URLs. >This facilitates discovery and eases adoption on platforms >without a well-supported client library. The URL is…
>> more direct mapping onto manipulating a DAG of commits That would be a leaky abstraction. The fact that is using DAG should be irrelevant. If they find a better way of doing the work, that shouldn't really affect the…
Wait, that says it took around 0.3 billion years, and when there was only single cell life, we have no clue about the biodiversity at that point in time. It cannot compare in time scale, and we have no clue if it can…
2015: https://www.martinfowler.com/bliki/MonolithFirst.html
As a user with a HiDPI laptop that needs to connect to non-HiDPI external monitors, Xorg is not reasonable. macOS is way ahead.
What productivity? I am here on HN
Furthermore to Klathmon, there is an opportunity cost. Because you don't have the test, changing that method in the future becomes problematic. Is not the bug reappearing, is the refactoring that cannot longer take…
I would say that only Haskell (and derivatives) force you to follow most of these rules. Neither Clojure, nor F#, nor Elixir force you into most.
SOLD!!!!! I will have to add this to my kata collection. That also reminds me of the 8-queen problem. The last solution that I created (C#) years ago did use recursion.
You are right. If you don't follow most of those rules, you are not doing pure FP. My interest on them was because I was writing production code that felt procedural. The rules are there so you can practice with…
In fact, a colleague that is reading SICP at the moment is the one that basically put the idea forward, as he was going through the whole idea of fold/map/unfold on the book exercises
The people that talked about the rules at Codurance was none of the people that defined the original rules. We had to "reverse engineer" the thinking, find reasons and then discard, change or let as they were (one of…
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…
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.
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 :-)
Not case sensitive.
> 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…
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 most of the development of new…
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 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…
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…
Love Zulip. Structured conversations are possible, which is what i want for a business setting. Topics are a great implementation. Code syntax highlighting and code playgrounds are nifty
This keeps bothering me: >7.1 URL structure >Humans SHOULD be able to easily read and construct URLs. >This facilitates discovery and eases adoption on platforms >without a well-supported client library. The URL is…
>> more direct mapping onto manipulating a DAG of commits That would be a leaky abstraction. The fact that is using DAG should be irrelevant. If they find a better way of doing the work, that shouldn't really affect the…
Wait, that says it took around 0.3 billion years, and when there was only single cell life, we have no clue about the biodiversity at that point in time. It cannot compare in time scale, and we have no clue if it can…
2015: https://www.martinfowler.com/bliki/MonolithFirst.html
As a user with a HiDPI laptop that needs to connect to non-HiDPI external monitors, Xorg is not reasonable. macOS is way ahead.
What productivity? I am here on HN
Furthermore to Klathmon, there is an opportunity cost. Because you don't have the test, changing that method in the future becomes problematic. Is not the bug reappearing, is the refactoring that cannot longer take…
I would say that only Haskell (and derivatives) force you to follow most of these rules. Neither Clojure, nor F#, nor Elixir force you into most.
SOLD!!!!! I will have to add this to my kata collection. That also reminds me of the 8-queen problem. The last solution that I created (C#) years ago did use recursion.
You are right. If you don't follow most of those rules, you are not doing pure FP. My interest on them was because I was writing production code that felt procedural. The rules are there so you can practice with…
In fact, a colleague that is reading SICP at the moment is the one that basically put the idea forward, as he was going through the whole idea of fold/map/unfold on the book exercises
The people that talked about the rules at Codurance was none of the people that defined the original rules. We had to "reverse engineer" the thinking, find reasons and then discard, change or let as they were (one of…