It's still work in progress but new posts will be published on https://kula.blog/ Thanks to 11ty base blog RSS is working from the start so it should be easy to add to your reader if you still use any :) If now then I hope you can sign up to the newsletter where I'll be publishing new posts and interesting articles to it from time to time. Please use kula.blog from now on.
Get link
Facebook
Twitter
Pinterest
Email
Other Apps
Simplicity Talk from Meet.js Summit 2016
Get link
Facebook
Twitter
Pinterest
Email
Other Apps
By
K
-
Video of my Meet.js Summit talk is finally online, so if you missed please let me know what you think about it.
I have learned a lot from feedback at the conference and I have heard some great comments that I feel add a lot of value to my talk.
Important message from @krzychukula: Learn the language well and don't expect frameworks be solution for your laziness #meetjs16
First, I really like the tweet by Mariusz Nowak. That's something that I haven't mention in the talk because I have assumed that people would do that before going for frameworks. Only when I've seen this tweet I've realized that it's not always the case and I should have emphasized that before moving to new tools and frameworks.
I have advised people to use Editors instead of IDEs but many people told me later that they don't want to miss on refactorings and all the ease of use they provide. To me that was the exact reason why I want to work without them. Later at the conference Michał Płachta he told me why he is using Atom editor himself instead of IDE. It's really easy to 'refactor' 30 places in your code without seeing them, and IDEs make it really easy but can you really know if your change fits nicely in those places? Is your refactoring improving one place you're looking at and making 29 others unreadable mess? If you use editor you have to go to every of those places and sometimes while doing that he realizes that his initial idea wasn't really good. I really like his example, thanks Michał!
All in all, it was great to be there and I want to thanks organizers for accepting my talk!
If you have any good feedback please let me know in the comments.
Probably this is default for cygwin (at least I think that Git Bash uses somehow cygwin). In windows to change drives You use: D: And this is done! In Git Bash drives are "mounted" in root :) cd /D
Using Node.js you want to use NPM packages for reusable parts of the apps you create, that is a common sense. At the same time not everything makes sense as a public module unfortunately. Right now we are using Bitbucket at work for private repositories but there is a problem. How to use them as NPM modules? We do not want to publish them to the public npmjs.org but still want to have an ability to install them easily. After googling and experimenting I have found simple solution. First create new user in your organization with obscure password and give it read access to the repo. It is best to assign really obscure password but do not fool yourself. This is convenient but you must sacrifice security a bit. You should always consider how in your context that would be important. Change example from below to: user - username PASS - password of the user organization - owner of the project (you can find it in bitbucket url to your project) project - your project name "de
Update: If you use Chrome then you can use "Throttling" so simulate slow network for all your assets. This should be easier than proxy. Toggle device mode Choose Network type. Refresh the page https://developer.chrome.com/devtools/docs/device-mode Proxy: For some time I wanted to use some proxy for development and testing of eg. slow internet connection, but it was hard to find something useful and free. I know there is Charles but buy it to use it at most one in a month is not for me. I started thinking about Node.js, maybe I can write proxy for me? But fortunately I found one. https://github.com/nodejitsu/node-http-proxy With this module I can write really short code to create slow server: var http = require('http'), httpProxy = require('http-proxy'); httpProxy.createServer(function (req, res, proxy) { var buffer = httpProxy.buffer(req); setTimeout(function () { proxy.proxyRequest(req, res, { host:
Comments
Post a Comment
Comments: