Today I've learned that I should apply my interview tools
- can I relax some of the contraints on the result?
- can I approach it in more time / more space?
Alberto Zaccagni lazywithclass
It was a success, everyone seemed to have enjoyed it!
I went through the JavaScript project, and we found a few things that might improved in the original library, like for example code coverage, or off by one errors.
This experiment actually validated my point about having a mutation testing library going through github repos, to find
lazywithclass
/ blog-post.md
Last active
April 13, 2017 14:57
[RC Diary] Scheming today is the most appropriate thing to do (-49)
This is plain amazing. The practice of adding bugs and silly code to a fully tested and test covered project allows you to spot problems, not needed code, and inconsistencies so easily!
I think the reason for that is because it's not your code, so it's basically evil-mode on. You are basically acting as a super efficient version of a mutation testing library. It would be great to host an event where people could refucktor some famous libraries and at the end of the day find a way to extract useful hints for the library.
lazywithclass
/ blog-post.md
Last active
April 12, 2017 14:09
[RC Diary] Speed reading app, and then mind blank(-49)
I find working with types extremely enjoyable. I especially treasure those moments when your code type checks and you just refresh the UI and everything works as intended. I just love it.
I decided I am going to rush a bit more into The Little Schemer, so that I could allow more time to learning Idris. I think that everything I am reading / experiencing in these months points towards the fact that I would love to work in an environment where my logic is in the types, so whenever my code type checks I'm almost completely sure it works.
The drawback of this is that it really drains my brain, I've spent the past couple hours staring at the screen, doing minor
lazywithclass
/ blog-post.md
Last active
April 11, 2017 21:14
[RC Diary] Refucktoring, winston-cloudwatch, and jobs (-50)
I am going to host a workshop with a fellow recurser on the practice of refucktoring, which is basically going to be:
- take some good code as starting point
- apply a change to the code, one that makes you giggle or laugh evily
- run tests looking for a green
We worked mainly on this Elm app, me and a fellow recurser.
It is coming up pretty fast, the great thing about the environment are
- when your code compiles chances are it works as intended, and actually it was almost always like this for us
- the capability to explore the values that passed through the app over time
This last one was tremendously useful while developing. Not once we wrote a console.log, not once. Talk about benefits of
lazywithclass
/ blog-post.md
Last active
April 7, 2017 15:20
[RC Diary] winston-cloudwatch, Elm, the little schemer (-55)
The app is coming through pretty fast, we've stopped today when we failed to integrate a node module.
I think there should be a clean way to browserify a node module and all its dependencies. I will come back to this later.
lazywithclass
/ blog-post.md
Last active
April 5, 2017 04:11
[RC Diary] SICP 1.2 and a bit of rage (-56)
I've struggled a lot with SICP today. I don't see the point of teaching something using difficult concepts as examples.
Why would you, for example, give an exercise like Exercise 1.13 in this version of SICP, just search for "Exercise 1.13" in the page to find it.
lazywithclass
/ blog-post.md
Last active
April 4, 2017 00:56
[RC Diary] Hammock speed reading development (-57)
Me and a fellow recurser are coding the speed reading app in Elm, I am getting a lot out of it. It's amazing how types add certainty to your app and terseness. I am not used at all to using a typed language, so for example not having to see if the app actually works by alt tabbing t it is a great relief.
I've wrote a basic app that served as a POC, in Electron, now it's just a matter of writing one in Elm and then putting the compiled code in Electron.