Notes on the Elixir and Phoenix Bootcamp, part 1
These notes come as breadcrumbs left along my journey through the Complete Elixir and Phoenix Bootcamp. This is the first part that covers discovering Elixir. The second part will cover Phoenix. Here we go:
There are no objects in Elixir (nor methods). If they are about structs, then they . . .
Last Saturday, the Global Day of Code Retreat—Toronto Edition happened; #gdcr16.
- today is about practicing your craft, design
- today is not about delivering
- Conway's Game of Life
- base rules
- Any live cell with fewer than two live neighbours dies, as if caused by underpopulation.
- Any live cell with more than three live neighbours . . .
- base rules
JEG2's take on coding interviews, and how to pass them
At RailsConf earlier this year, James Edward Gray II talked about coding interviews, and how to pass them:
If you apply for a programming job, you may be asked to complete a take home code challenge, "pair program" with another developer, and/or sketch out some code on a whiteboard. A lot has been said of the validity and fairness . . .
From the Fixture level
Our hypothetical Rails app: the Foo Club
Let's imagine that Foo Club wants you to build an application to display events. These events are of two types—public and private:
- Public events are visible to anyone visiting our application.
Say someone prospecting, to determine if the Club is a right fit.
- Private events are only visible . . .
The Nice and Accurate Prophecies of Agnes Nutter, Witch
All work and no play makes Marius a dull boy
This is one comes somewhat complementary to the other articles that are mostly focused on either technical subjects or around team/company culture or craftsmanship.
So much more complementary as life tends so much more than work, than passions, than what you live, than what lives you…
And there was . . .
Posted in: reading
SimpleCov: how to add it to your tool belt and (the 5) why(s)
Why am I reading this?
Popular software development culture advises us that 100% test coverage of our code is no reason for pride. It's not even a goal to be pursued on high priority. Either taught by our experience already, or we've overheard at least an elder (developer) say say it before: having test that provide complete code . . .
for it will shape you
Michael Hartl mentions in his Rails Tutorial that Rails comes equipped with three environments:
Then an aside shows how to run a console, a server and a rake task in an environment different from the implicit
development because, as he confesses
I find it confusing that the console, server, and migrate . . .
Posted in: rails