I’m a Rails developer by trade, launching my way into the world of Elixir and Phoenix. While I aim to approach each problem through a fresh, non-Railsy pair of eyes, I typically find myself searching for ways to do Rails-like things in Phoenix, rather than stepping back to first principles and opening my eyes to the new paradigm.
Models in Phoenix can be tested in two ways:
A big part of spiking on a startup idea is getting out and exploring the business domain. So I’ve been taking advantage of these urban months and visited a number of meetup groups and networking events.
The web app has been up and running for a few few weeks now and our beta testers are plugging in bits of data. It’s all on track, but slow going. The features are complete-ish, so now it’s all about the shiny surfaces.
Today is a marketing day, so the most obvious place to start is with this. A blog post. I anticipate (fear, actually) that there will be many more such days as the burden of labour shifts from the familiar world of step-by-step development towards the lesser known world of marketing.
They’ve not gone anywhere, the tests are right where they started. And they are up to date. And SimpleCov reports 96%.
Today began picking up the pieces of a spontaneous (but effective) domain name purchase over the weekend. Am happy with the name and brand it could inspire. And I got the development app up and running on the www subdomain pretty easily.
Today I put down the development tools and patted myself on the back. I’ve reached a very rough stage one of the MVP. The product now does - very roughly - everything the old one did. And some.
Working on a solo project is a bit like jumping into the sea and waving your arms about madly. Hoping lots will get done and that there’ll be no missed turns along the way.
Actually, just the one meeting today. I met up with the application’s prime-user, both of us arriving with folders stuffed full of notes and an awful lot to say.
Today I did some work upgrading an old application to Rails 4 / Ruby 2. It was reasonably easy and there were only a couple of gotchas.
The customers are the people who will be building the screens. We could call them users but that gets confusing because everyone is a user. The same could be said for customers. The only difference between the two is that one might be a paying example of the other. Users who pay -> Customers.
There is an idea, an intention, an understanding of the technology and an inkling as to what that technology will do.