I hereby claim:
- I am lassediercks on github.
- I am lassediercks (https://keybase.io/lassediercks) on keybase.
- I have a public key ASCx7zeS5hS-vZMRxauXi-EEQ4ZmmErUv6Qz98EKWwkooAo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
| [ | |
| { | |
| "featureType": "administrative", | |
| "elementType": "labels", | |
| "stylers": [ | |
| { | |
| "color": "#000000" | |
| }, | |
| { | |
| "visibility": "off" |
Github announced the facebook-a-like emojii reactions a little while ago. I watched. I've got an opinion now:
Here is my problem: when I ask for something or create a proposal, I need feedback to know if this is the right direction. I expect a github notification that tells me someone answerered me. A reaction does not trigger that notification so another task on my list is to go to that specific issue again and look if someone reacted with 👍 or not.
This could be solved by enabling notifications for meaningful reactions or by defining with your co-workers that meaningful feedback must be in form of comments.
Imo the ux of the reactions creates a unpleasant experience here
#Visual regression testing idea
Visual regression testing is pretty asked in big applications because of several reason but I expierienced that they're pretty hard to setup. I'm thinking of a way easier approach than screenshoting and doing pixel diffs.
The idea is the following:
| 0 - none | |
| 1 - basic knowledge about what the language is for and what not | |
| 2 - ability to read the language | |
| 3 - small modifications of existing code | |
| 4 - able to write low-level functionalities | |
| 5 - adapting & execution of best practices | |
| 6 - solid execution of given tasks executed with quality proportional to given time | |
| 7 - able to refactor components written in the language |