2,068 karma · joined September 29, 2009
Web front-end specialist looking for a job with an ethically-aligned company
http://eleven-twelve.net
http://github.com/alxndr
http://drwxrxrx.bsky.social
email: YWx4bmRyK2huQGdtYWlsLmNvbQo=
[ my public key: https://keybase.io/alxndr; my proof: https://keybase.io/alxndr/sigs/B-vRl0kOw2kpqag-RlOReucueGiSJi-u5Ef4CTQ_TkI ]Personal gripe: I always, always, forget to `git bisect reset`.
Very much agree. I was a client at Pivotal for a few months, and learned a ton from them while pairing. We brought their XP style (slightly tweaked) back to our office once our contract with them was up, and continued pairing about half of the time. We could all get along well enough, and had agreed on using the same editor, so the only pain point I felt was when working with people with a different skillset. Though the different skillset problem made development go slower, but the more experienced people are teaching the less experienced people, hopefully making the tradeoff worth it.
Another advantage to pairing is that it keeps developers honest -- if you're supposed to be doing TDD, then ideally your pair helps you stick to it instead of taking shortcuts you "know" are okay.
Edit: oops, grandparent asked for negative experiences. The only ones I had were frustration when working with people who were already frustrating to work with. (Ideally, while pairintg they'd be learning, and would become less frustrating to work with...) I do agree with parent's point about it being less useful when banging out boilerplate or obvious solutions, but that's not really a horrible experience, just a little wasteful feeling.
A project could have a standard of, say, 0.5% for typo fixes, 1% for documentation, 2% for refactoring which improves Code Climate or coverage statistics...
Only 15 projects with a nonzero tipjar at the moment.
That reminds me of Airbrake.io, whose lowest-cost pricing plan was higher than I wanted to spend on a toy site I made recently. On my phone I can't find the text on their site, but in small print on the pricing page it said something like "or, we have a developer plan, which is free for one site and one user."
It was exactly what I was looking for, and I wish there were more ultra barebones plans available for otherwise-paid services.
> "Some people think Ars Technica forces me to break my article up into many tiny pages. That’s not the case. I choose how to paginate the article. I like to break it up on logical section boundaries, which means that the “pages” vary widely in length. I do try to keep any single “page” from being too short, however."
Posted without comment: this was written just before Matz wrote this email, but here's someone saying that Ruby is an acceptable LISP: http://www.randomhacks.net/articles/2005/12/03/why-ruby-is-a...