I’m starting this blog here to make a coder-friendly open conversation with contributors and enthusiasts about flow’s design. This blog will be doing two things in one move: A source of fresh input, so feedback, so inspiration. An output about progress on this line of work, so relevance of the mission. But lets back up a bit, what is flow after all? I like to say that flow is a mission with a framework. Here is flow’s mission from the project’s readme:

When I was doing engineering, I had a very good algebra teacher.* Those were the days full of vectors and subspaces and subspaces of polynomials and matrices and subspaces of matrices of polynomials. All from 7 a.m to 12 p.m. In the middle of that math trench he said once something that my head really saved. The teacher was explaining yet another concept while the sky was still dark in the morning and there was this guy that asked him to clarify a detail. ...

When you trust your content is when you can forget it. At that point you’ll get that Context is King. …to make a Leonardo you need more than his innate ability. You also need Florence in 1450. Paul Graham. Yes I know… we are not da Vinci, we don’t have Florence in 1450 nor we have a Medici patron for our talent.