mythhabit

We have that now. We did not for the formative years of the field.

Because everything (except SSDs now a days) in a computer, on a fundamental level is either 0 or 1. So when you want something that maps to that, 2 to the power of 10 is exactly 1024 bits. Somewhere along the line, someone decided that accuracy of that mapping was more important than adherence to the exact meaning of kilo.

The alternative, would have been to use something else than kilo, mega ect., that represented the base 2 magnitudes. It would be awkward to say you have 8.306.688 bytes of ram if you need to be exact.

For many people that live where there is no chlorine in the water, it's immediately obvious when there is added chlorine to the tap water. I'm not sure I can taste it, can't remember I've actually tried, but I can absolutely smell it.

"I forgot the password, sorry". I really do not hope they will start putting people in jail for being forgetful.

99.99999% not a coincident. These far reaching proposals almost always have critical stages when the public is concerned by something else.

Some of the main benefits of shipping every day, is:

  1. Develop a system where you can turn codepaths on and off with a toggle.
  2. Become better at architecture. Learning to split a task into smaller chunks that are easier to reason about, both overall and individually.
  3. Learn to do multi phase increment.
  4. Develop an automatic deploy/rollback system.

All are good practices, and essential if you need HA. It also gets the velocity into your daily work, so if you need to deploy extra logging, a bugfix ect, you can do it in minuts and not hours/days/weeks.

Can you do all of that and ship on a weekly basis? Absolutely, I just haven't met anyone that do that.

It's unfortunately often people that recover from some serious traumatic experiences, that are the most emphatic. They know what it is like to be completely lost with no one to help.

Children are too, but somewhere along growing up, many unlearn that.

That is fine to do, if you prepare the child. I mean, start by taking all the steps with them, gamify it, and at some point I'm sure most children would be proud to do it.

But just doing it with minimal preparation... That's bad parenting. I doubt that experience alone is the reason for being fiercely independent - that usually (and unfortunately) comes from the person being unable to rely on their care takes for their needs as children.

I agree. And it's worth remembering that Scrum is a starting point. The entire point is to adapt the process such that it fits the team/product/organisation, through retrospectives.

If you have the tools to work with metal, you can use those tools with few, if any, modifications and do the same thing with nylon.

Abstract math (type B) is a very rigorous discipline that underpins the other kind used by engineers (type A). Type A is indeed learned by repetition along with understanding. It is very important to simply do the math to become better at it and understand what you can expect from your calculations.

Type B on the other hand far more about understanding. You will never understand the theory of a mathematical space and how to apply it, by simple repetition. That is a far more theoretical and creative endeavour. You need to learn it and apply it to understand it. I suppose you could call the process of applying it some kind of repetition, but in my opinion the insights comes from applying it to concepts you already know.

A formal learning path is a very good idea, because people with more knowledge know what order you can progress in, in such a way that you actually apply your knowledge in a natural way and build on previous learnings. And it is definitely a huge help that teachers can help you guide your learning when you are stuck.

Not saying USA is not doing it, and both Germany and France is doing it as well in the wake of Corona. But the amount is visible and until we get more transparency, we can only assume that China is doing it even more, because they are known to do that for strategically important sectors.

That not hard if your production and/or materials is subsidised by the state, in an attempt to outcompete western companies.

Just going of the Wikipedia page on unit testing, in the 1956 paper on programming for the SAGE project, refers to testing as: Parameter testing, assembly testing, shake down testing. In the context, parameter testing is testing of individual sub routines (functions/methods). From there the term unit test was used in the Mercury System as unit testing of "individual programs outside and inside the system". I suppose here, the ethos is the same.

Obviously, when reading the rest of the papers, they are clear on the fact, that it is the specifications that the programmer have developed for, that should be tested. That was at the time, synonyms with individual sub routines, and as such it was both the smallest unit and a logical testable unit at the same time. Since then, we've come a long way with programming smaller units with better composability.

I'm not sure I agree that the original meaning of a unit test was lost. Perhaps, only one part of the definition was carried over to modern development practices. In any case, I always stand by the fact that long term value is in tests of the "API". Everything else is implementation details.

I believe that the original definition, way back before most of us were born, was a test of the smallest possible unit, i.e a single function ect. At least according to Wikipedia, in 1969, it was defined at unit tests, component tests and integration tests.

In todays development world, the unittest is primarily a developer tool to help speed up development. One should not be afraid to delete unittests if they are doing refactorings. But the long term value is always in the integration tests.