A tab completion script that works for Bash. Relies on the BSD md5
command on Mac and md5sum
on Linux, so as long as you have one of those two commands, this should work.
$ gradle [TAB]
/** | |
* Original source: | |
* [[https://gist.github.com/oxbowlakes/970717]] | |
* | |
* Modifications: | |
* - use scala 7.0.5 | |
* - use toValidationNel | |
* - use sequenceU and traverseU instead of the lambda trick | |
* | |
* Part Zero : 10:15 Saturday Night |
vagrant@ubuntu-12:/docker-pub/redis$ cat base/2.8.1/Dockerfile | |
FROM ubuntu:12.10 | |
MAINTAINER James McKernan [email protected] | |
RUN apt-get update | |
RUN apt-get install -y build-essential | |
ADD redis-2.8.1.tar.gz redis-2.8.1.tar.gz | |
RUN tar xvfz redis-2.8.1.tar.gz | |
RUN cd redis-2.8.1 && make | |
RUN cd redis-2.8.1 && make install |
Philosophical: | |
* writing lines of code is one of the least valuable things I can do | |
* cultivate your impatience | |
* reject the status quo, unless we can re-derive it from first-principles | |
* engineers imprint on the first languages (techniuqes, frameworks or technology) that we find success with (unconsciously seen as caregivers, which we defend w/o always knowing why) | |
* we tend to overvalue the familiar/known; we tend to undervalue the unfamiliar/unknown, this interferes with our receptiveness to new ideas and personal growth | |
* we're 90% composed of bad habits; many of our best habits become bad as time passes; this allows us to filter for the fundamental; the great | |
* make doing the right thing easier than any other thing, or we will fail to achieve greatness, or break bad habits | |
* be conscious, be intentional | |
* "is this the highest we can aim?" (I prefer this over "is this the best we can do", the former is aspirational, the latter is judgemental) |
A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.
I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.
I'd love comments and suggestions about any of these.
I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.
I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".
##Cake Pattern and Why Cake Patterns Sometimes Look Different The cake pattern is typically described as a way to use small layers of functionality to create a larger, more complex program. This area of application design is typically designed with application scalability not in the pure performance sense, but in the sense of scaling the application up to more complex functionality and maintainability over time.
There have been many papers and blogs on this aspect, but a few especially helpful blogs include:
Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.
Companies hiring Scala developers in the Bay Area. | |
Created in response to a thread on scala-base. | |
My favorites: | |
- CloudPhysics | |
- Wordnik | |
Unbiased list: | |
- 10Gen | |
- Audax Health |
curl -s https://api.github.com/orgs/twitter/repos?per_page=200 | ruby -rubygems -e 'require "json"; JSON.load(STDIN.read).each { |repo| %x[git clone #{repo["ssh_url"]} ]}' |