A high-velocity style of software development
Annotations from A high-velocity style of software development
Page 1
I want to have a chat with the computer in its own language right from the start.
I like the idea of coding is a way of having chat with the computer. POCs are touching the real thing, even if it’s a spec file where we’re trying out a new library or a concept. This article also talks about creating playgrounds (as separate projects) to try out new features before implementing them in the main project.
Page 2
Ideally, I would have a project consisting of just a single file that I don’t have to leave for hours on end.
So this means we should keep a project in one file? This can be an Rspec file too. How would one handle UI features?
Page 3
Nobody sees these ugly scraps but me. I can decouple and isolate parts of the project as a result, and work on them independently without the need to keep calling all the different modules all the time or fire-up all parts of the project on each code change.
To me having a spec file which contains experimental code seem better than having it inside the implementation files.
Page 7
Flowing data through pipes allows the execution of functions to also take place without specifying the arguments. They are implicit, like one would flow data through a Linux pipe. There are no intermediate variables and assignments.
This seems interesting. I should ask about this from ChatGPT.
Page 10
That gut feeling is only developed through experience, through trying things out, failing and trying again.
Experience can only be developed via getting our hands dirty, so it’s more important to try out new things than reading about them.
We should aim for trying out something, not read about it.