jdudek

This is what Siri should have been.

It’s a sane scripting language. It encouraged me to automate simple tasks, create handy functions etc. I don’t have to google the for loop syntax every time I need it.

Yes, switching networks can indeed cause users to receive different versions within the 3 hour window. In general we ship small, incremental changes that rarely even are visible to the user, so a small likelihood of serving inconsistent version is acceptable.

Interesting idea with geo restrictions. Does this allow more granularity than country-level filtering? Most of our audience is based in the US, so country-level setting does not give us enough flexibility.

There is also value in knowing the percentage of users receiving the new version. It’s just more predictable and easier to analyze the data if the ratio of new-to-old is known beforehand.

Hey, blog post author here.

Good question. We just tested with ab (ApacheBench) and consistently observed the difference between Lambda enabled and disabled. We wanted to be sure this system does not incur any significant overhead and that’s why we made sure to only run the Lambda when it is needed.

We hope to see Amazon improving this, as there can be use cases for Lambda@Edge where you can’t restrict URLs so easily.

Here’s a similar write-up on building a BitTorrent client in Haskell: https://blog.chaps.io/2015/10/05/torrent-client-in-haskell-1...

Yay, no more using single repo with orphan branches to save on number of repositories :-)

The story of this checklist has been covered in “The Checklist Manifesto” by Atul Gawande. It’s a great read on how diligence in work can literally save lives. We can advance medicine by breakthrough discoveries that push our knowledge further, but improving how we apply the existing knowledge is just as (or even more) important.

My recommendation: configure the shell prompt (add __git_ps1 to $PS1), this saves a ton of time and makes it much easier to understand what is going on. Especially recommended for beginners (but obviously not limited to).

> We could insert new list items into the existing DOM, but finding the right place to insert them is error-prone, and each insert will cause the browser to repaint the page, which is slow.

I don’t think the last part is true. Browsers don’t repaint (nor they reflow) the page until it’s really needed. So if you have a loop that modifies the DOM multiple times, but does not read from the DOM, there performance hit described by the author should not occur.

One can argue if it’s a misuse or not. It’s quite handy to have such utility classes that rely on !important and can be used in markup directly. I have plenty of those in my stylesheets.

[1] http://davidtheclark.com/on-utility-classes/

I wrote a JavaScript-to-C compiler: https://github.com/jdudek/tatende-js. It supports a limited subset of the language—just enough to compile itself.

It was my university project. It’s not really useful, but it was extremely fun to work on.

Pardon my ignorance, but why is cross-compilation not an option in this case?

Do you happen to remember what was the idea of that approach alternative to Elm Architecture?

Elm is a much, much smaller community than React. You won’t find as many libraries and ready-made components in Elm as you would in React. On the other hand, when there is an Elm library for something, it’s often of very high quality.

Impressive that you can find such low quality article. Reads almost like it was written by a machine.

It is very safe. People are extremely friendly—for example, I was invited by strangers for a dinner a few times. The police is not corrupt. According to my guidebook, wild dogs and rabies are the biggest concern.

Be prepared to see a lot of poverty, though. Especially if you’ve never been to a formerly soviet country.

I’m from Poland and I have visited Georgia in 2011.

This is quite similar to how we hire Ruby on Rails developers. We organise two-weeks long Bootcamp where we train people in Rails. At the end we offer some of them to join us as junior developers, with further training during next year. Those who are not hired still win—they receive two weeks of training which helps them find jobs elsewhere. We’ve had some fantastic hires this way over the past two years.

This article made my think that maybe we can do better and provide more assistance to those we do not hire after Bootcamp.

More details about our Bootcamps are available at http://pilot.co/bootcamp.

It’s been an interesting comparison. However, there are programming Bootcamps that are free of charge, like http://pilot.co/bootcamp (disclaimer: I work for Pilot). The ROI comparison is quite interesting in that case… :)

I don't think it is semantics, setting vertical margin: auto here has just no effect.

It's worth noting that the last example with margin:auto can be used for centering within any div that has position: relative (there's nothing special about the whole page). It also works for intrinsic dimensions, so you can center an image without knowing its size, see http://jsfiddle.net/jdudek/hfbnS/1/.

There are a few more useful techniques not covered by this article, for example:

* line-height + vertical-align: middle + display: inline-block (which allows you to center vertically an element with dynamic height)

* display: table-cell (mentioned by others in this thread, although without stating its disadvantages).

While I appreciate the effort, calling the article "complete guide to centering a div" is an overstatement.