4 ms·
I have worked with a couple. A first in zoology who moved to code and wrote games in assembler, and also complete compiler systems for minified versions of the
by ggm 4y ago
I have worked with a couple. A first in zoology who moved to code and wrote games in assembler, and also complete compiler systems for minified versions of the languages of interest: Algol, Fortran, C -He also tinkers in hardware at all levels and can re-frob a radio into a theramin from the principles of how circuits work, or can make a magnetometer based 3D action glove from bits in his toolbox. Another who coded C compilers for a living before GNU destroyed the marketplace. A third who uses FP (Haskell) to reason about systems as types, before even considering code to mutate those typed objects.
The first thing is, they all tended to have a really strong grounding in mathematics, around logic, statistics and related subjects. They had underlying conceptual models grounded in the formalisms of a maths discipline.
The second thing is that they had very high functioning reasoning skills. If <this> then <that> was very strong in their ability to see inherent linkages between specific and general, to take an abstraction and apply it, or to find a mapping to that concept in another domain, work in that domain, and map back into the field which applied in the first instance.
The third thing is that they seemed to go from solution hypothesis to code very naturally: they didn't hesitate to follow a code path, there was no sense of "suck it and see" -To me, this is the bit which makes me really wonder WTF was going on because my own code is littered with "this failed" attempts to get to the functional outcome.
So, there's a lot of maths, a bit of process in abstract reasoning and a giant ocean tanker of confidence.
I have watched these people sit for 6 hours exploring how to use assembler to shave two instruction cycles off a task. The focus required to model the behaviour of the system and do this in a pre-omptimising compiler world, in the tools of the machine, were amazing.
- inphovore 4y agoAs a life long programmer who has also led teams of other programmers I would say lighten up on the expectation of formal math. While this example sounds a real good one, there are different kinds of programmers who excel and conventional maths aren’t consistently their strong suit (though logic and algorithmic thinking may be imperative.) One thing which is curious, how many good programmers aren’t formally trained as programmers. I once worked for a guy who began as a finance geek who started his own million dollar company by teaching himself how to program. One thing that impressed me was his ability to sit down and power through things until he got them done. Unlike myself, who avoids doing work until the perfect solution emerges from the problems’ complexity (and then writes the minimum amount of code in the most abstract form to get the job done.) Success takes many forms, so exclude nothing by expectation!
- lagrange77 4y ago> They had underlying conceptual models This is so important for every STEM subject. Ideally, having working mental models of [computers, processes, the nature] should be the goal of education. Besides that, i observed really good natural language skills in people, who are good at programming. I guess, this ability (to write good code), complements conceptual understanding. In some papers you can observe, that the authors master the concepts, but their code looks like written by a novice.
- eurasiantiger 4y ago”The third thing is that they seemed to go from solution hypothesis to code very naturally” Functional thinking tends to do that, irrespective of the language. Once you have the ”pipeline” in your head, you can just write it out.
- curious16 4y ago> Functional thinking tends to do that, irrespective of the language. Can you expand on this a bit more? And if possible, some books that teach this kind of thinking?
- eurasiantiger 4y agoA good and practical first step is to learn to use map, filter and reduce to solve everyday problems, such as transforming an array of recursive definitions to an array of React component trees. Hint: define the function separately from where it is applied, and also apply it recursively.
- debanjan16 4y agoDo you have any book recommendations?
- eurasiantiger 4y agoNot really. References are enough. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/Map https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/Reduce https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...