Navigation Menu

Skip to content

Instantly share code, notes, and snippets.

@lazywithclass

lazywithclass/blog-post.md

Last active March 21, 2017 04:06
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save lazywithclass/cb60e95041cbdb7f2836d4b45a65b1a0 to your computer and use it in GitHub Desktop.
Save lazywithclass/cb60e95041cbdb7f2836d4b45a65b1a0 to your computer and use it in GitHub Desktop.
Download ZIP
[RC Diary] Good progress and activism (-82)
Raw
blog-post.md

[RC Diary] Good progress and activism (-82)

Project lamp

Finished introduction and first chapter, the book now looks really amazing, I'm satisfied!

Incoming chapter 2.

Programming democracy

Registered to the slack team responsible for collecting scientific data. Had a look around at a possible project I might contribute to, cloned and started successfully.

I also got in contact with one of the team, seems promising, we'll see.

Helping with tests

A fellow recurser was in need for some help with testing best practices, on a couple projects:

  • test cover a simple one page app that lets you see the difference between two dates
  • create a project from scratch with tests and TDD

This is a wonderful opportunity to be able to speak more about testing, and understand what I don't know about it or what I am not so sure about it.

I am thinking about what could be the best approach here, should I take notes? Should I record the whole thing? (this would be awkward...)

Cerebro

Finished the first era. I can now apply mutations to a project, and I've got the scaffolding to making it a command line tool, meaning that I can also use modules from the project I am mutating!

Next steps are:

  • read sources and tests of the example project I have in Cerebro source code
  • provide a simple diff output of what changed between code and mutation in case of an alive mutant
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment