3 ms·
I always felt that there is a hierarchy for working with numbers that goes something like this Ease of use: 1. Excel 2. SQL 3. Functional programming (e.g.
by fifilura 2y ago
I always felt that there is a hierarchy for working with numbers that goes something like this
Ease of use:
1. Excel
2. SQL
3. Functional programming (e.g. Scala, Python to some measure e.g. Pandas)
4. Imperative programming (C/C++/Java)
But then there another hierarchy that (roughly) goes in the other direction, which is about quality, repeatability, tooling.
If you are at 1 or 2, you responsibility will not be about writing tests and verifying your code using traditional engineering methods.
However! You are responsible for cross checking your results based on the input. This may be a manual process. But actually looking at the numbers from several different angles can give higher quality than writing contrived testcases (in 3 or 4).
- anthk 2y ago2 s,SQL,j https://www.jsoftware.com/indexno.html https://www.jsoftware.com/indexno.html Also: https://www.jsoftware.com/help/dictionary/intro.htm https://www.jsoftware.com/help/dictionary/intro.htm EDIT: The help section has 6 books. If you want, you can do self-teach yourself advanced math stuff with very few lines. I suggest to install Gnuplot as a dependency, for plots.
- fifilura 2y agoVery good! I believe you. Unfortunately I feel like it would be irresponsible to transition our stack to working with J because of available competence and relearning. I can see it being used in research though.