I hereby claim:
- I am anildigital on github.
- I am anildigital (https://keybase.io/anildigital) on keybase.
- I have a public key whose fingerprint is 8D19 0F1E 9493 9306 6066 96B6 6E1A 604F 82E6 14C6
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
Inspired by Trulia Trends - but with code and using SVG.
Example data shows concurrent user sessions over time, taken from a development environment.
docker rmi $(docker images -q -f dangling=true) |
(by @andrestaltz)
So you're curious in learning this new thing called (Functional) Reactive Programming (FRP).
Learning it is hard, even harder by the lack of good material. When I started, I tried looking for tutorials. I found only a handful of practical guides, but they just scratched the surface and never tackled the challenge of building the whole architecture around it. Library documentations often don't help when you're trying to understand some function. I mean, honestly, look at this:
Rx.Observable.prototype.flatMapLatest(selector, [thisArg])
Projects each element of an observable sequence into a new sequence of observable sequences by incorporating the element's index and then transforms an observable sequence of observable sequences into an observable sequence producing values only from the most recent observable sequence.
// Simple Java program | |
public class Person { | |
private int age; | |
private boolean isFemale; | |
Person(int age, boolean isFemale) { | |
this.age = age; | |
this.isFemale = isFemale; | |
} |
http://fare.livejournal.com/171998.html
Many software development organizations fail to follow these principles and pay the price, which can lead to failure. Google mostly doesn't make the mistakes of going against them, though some projects at ITA used to.
Code reviews not only improve code quality by having more eyes to find bugs, but most importantly they build the mutual knowledge of the code base, and cross-pollinate minds of team members. This may look like it slows you down in the very short term, but is essential in the long run. If you need to check in a critical fix right now, interrupt a colleague and get the just as critical review right now. If it's so urgent that you can't wait for a review when no colleague is available at the moment (in the middle of the night, or they are all sick, in vacation, or in a retreat), then get it reviewed after the fact, but get it reviewed still (and of course run automated tests — your infrastructure won't let yo
Docker 1.0 released yesterday. http://blog.docker.com/2014/06/its-here-docker-1-0/ | |
Google Embraces Docker, the Next Big Thing in Cloud Computing | |
http://www.wired.com/2014/06/eric-brewer-google-docker/ | |
Eric Brewer of Google says | |
- “Google and Docker are a very natural fit” | |
- "Google will combine Docker with its cloud computing services, Google App Engine and Google Compute Engine. " | |
- "That said, the importance of Docker can be hard for even seasoned developers to grasp." | |
- "Brewer says a developer technology hasn’t taken off so quickly and so enormously since the rise of the Ruby on Rails programming framework eight or nine years ago." |
I hereby claim:
To claim this, I am signing this object:
Today morning, I watched a keynote talk given by GitHub CEO and co-founder Chris Wanstrath. I was impressed. Here are his quotes in the talk. | |
'Great coders relentlessly iterate. Best coders relentlessly iterate with other people’ | |
'It's not about fancier code, fancier tests. It's about fancier communication.' | |
'We iterate on software we build, we should also iterate on how we build it' | |
'Focus on your development workflow and collaboration, less on the tools or technology. It's about people.' | |
'Workflow of future: Getting shit done. Shipping awesome software.' | |
'It's not about software, its about people' | |
"It's not about tools, it's not about GitHub, it's about way people communicate with each other. |