Ignoring external libraries Chrome debugger allows you to ignore library code and do the stepping only on your custom code. To activate that feature, do the following: Open dev tools Click on three dots menu on the right side Select Settings from the menu and find Blackboxing Check the Blackbox content scripts checkbox and add a pattern using Add pattern button. (I usually use that with node_modules as a pattern).

I decided to migrate my blog tu Hugo. One of the main reasons was to support multiple languages, since I decided I want to write also in Czech from time to time. It hasn’t been exactly easy transition as I hoped for, but I will describe what I did and how it worked out. Conversion tool I tried to use scripts mentioned on the Hugo official documentation, but wasn’t much successful with them.

In my current work we use self hosted Gitlab CE instance and Jenkins CI. We wanted to set up some integration between Gitlab and Jenkins to would build merge requests for us. There are quite a lot of articles on the internet on that topic, but we had one major problem - our self hosted Jenkins is on private network, while Gitlab is on different, public, network. So using webhooks and after push notifications is not going to work in that case.

In this post, I would like to explain some tips on successful git workflow. Feature branches Feature branches is very common and I think one of most important concepts of successful git workflow. Before you start working on new feature, create a new branch for it based on latest master. Then commit all work into this feature branch. If master changes and feature branch gets outdated, rebase it to current master (it is safe to do so with your private branch, but be careful when working with shared branches).

Aurelia Video: Aurelia: Next Generation Web Apps by Ashley M Grant - Great video explaining basics of Aurelia Vue.js VueJS Router - Documentation of VueJS router. It seems like the only Router in current JS frameworks I know, which supports components being really fully decoupled from it. Huge thumbs up for Vue for that! I’ve been blaming Angular for not having it for while… Git git - the simple guide - Nice git guide for beginners Other Good UI

I’m experiencing some Jekyll related issues. I’m trying to get docker image up and running on my machine, but it doesn’t seem to work properly. Currently generated pages look differently then they look live on github pages. And also the watch mode doesn’t work and I have to restart docker container all the time, when I want to rebuild the site. I also have to delete already generated files. I believe these are just temporary birth issues and won’t be blocking me for long.

This time it is mostly list of interesting articles I found. Interesting articles TypeScript TypeScript at Slack - how Slack moved to TypeScript Glimmer.js: What’s the Deal with TypeScript? - Article describing what TypeScript is about It’s time to give TypeScript another chance - Yet another article about TypeScript :) Rich Typescript Logger Decorators for Easy Coding - Great TypeScript decorator for simple logging Decorators & metadata reflection in TypeScript: From Novice to Expert - Article series focused on TypeScript decorators Angular Automagically Unsubscribe in Angular - Decorator for automatically unsubscribing Observables Angular — Stop using observable when you should use a promise - Article about caveats of overusing Observables especially for HTTP requests ngConf2017 Information - Links to videos, slides and information about ngConf2017 CSS http://cssgridgarden.

On my last project I had a chance to work with Aurelia. I needed to use some frontend framework capable of being easily used with existing server rendered application. This single requirement automatically crossed out Angular, so I had to look for some alternative. Since I knew little bit about Aurelia and I found out it is easily embeddable ito existing app, I decided to use it. I think it was right decision and it has been quite pleasant to work with Aurelia.

Properly commenting workarounds Sometimes you need to do some workaround - maybe because of some bug, or lack of features in framework you use… There might be many reasons for it. It is necessary to properly document such a workaround and describe reasons why you used it. It might seem obvious at the beginning, but when you return to that code after some time, you might not understand it rigt away.

This is the first article of “What I have learned series” I would like to start. I would like to write weekly (even though I’m not sure if I will have enough time for that). I will try to post interesting things I learned in that week and also some articles I read. Java Java streams cannot be reused CSS A Complete Guide to Flexbox - flexible CSS positioning GIT Break up changes into multiple git commits with git add -p