1,895 karma · joined March 30, 2009
Click on the up arrow at the bottom edge to choose which wall to view.
I agree that some conflicts are much better handled via synchronous voice conversation. And I think that's acceptable, if not desirable. However, I make sure that after the call we write down some notes what decision we made, and why we decided the way we did. This makes sure that parties not present at the meeting (i.e. other developers, and our future selves) can pick up the context quickly and save us the pain of working through the decision process again.
And then there is always the issue of dysfunctional team communications where the channel doesn't matter. In asynch conversations poor/obstinate communicators don't need everybody in the room to keep adding to a controversial conversation. So you just can't stop them..
And I just learned a new word: 'in·tran·si·gent': unwilling or refusing to change one's views or to agree about something. Thanks.
> more awkward for decision-makers to assert themselves
That has probably more to do with team culture than the communication channel used. I'd think that a capable and respected decision maker can assert themselves easily via written word.
On the other hand, I think every team benefits from clear written communications. Having a remote team enforces this best practice where having a co-located team lets communication practices slip and become sloppy.
I created a flowchart that illustrates this strategy: http://rails-recipes.clearcove.ca/pages/how_to_change_object...
My only concern is that such a generic term negatively affects findability. E.g., it makes brand monitoring or web-searching very hard. You won't rise above the noise.
You could address the findability problem by adding a unique token to the name (e.g., 'Experiment42').
1) Strategy is primarily about saying "No" to activities that are not aligned with your goals and values. Here is a great example for saying no in a pretty gutsy way. 2) I have used Basecamp since its launch for my client work and like it quite a bit. However, lately I have preferred to work with Trello. I'm curious to see how Basecamp will change in the near future. Maybe I'm not their target customer any more...
I wonder by how much this will increase exposure times, and if it works at all...
* I am a programmer and I care about my health * I am a startup founder and I am impressed with the package Joe Kutner provides: A book, a website and a (free) IOS app with lots of resources and features.
Slashdot has a review of the book: http://books.slashdot.org/story/13/08/12/1239250/book-review...
Intigi gives you the power of Lucene indexed search on the newest articles on the web. You can subscribe to Intigi curated sources, or add your own RSS feeds or Twitter home timeline, and then filter results using powerful Lucene queries (fields, boosting, phrases, slop, wildcards, stop words) and other filters (social signals, word count, publishing date, presence of image or video). Intigi delivers results once per day or once per week via email, or you can view results in realtime through the web interface.
Disclaimers: I'm one of the co-founders and it's a for-pay product.
Often these patterns are treated and discussed as an either/or decision, which I don't agree with. There are many places in an app where the default and simple Rails way is the right choice. However as apps get more complex, there is also a need for approaches like the one presented here.
My rule for choosing the right approach is this:
If it's just a simple CRUD controller where it receives input from a simple form and writes attributes to a single model, with no AR callbacks involved, then omakase is perfectly acceptable. In that case I don't want to have to jump through all kinds of hoops and overcome unnecessary friction added by enterprisey patterns.
However, as soon as I have to use AR callbacks, add more lines to my controller action, or touch more than one model, that's a clear indication that a service object makes sense.
Mutations looks like a great solution for the latter case. It brings in some DCI goodness as well. The key is that some operations require complex context (object graphs, permissions, dependent operations), and that context should be treated as a first class citizen.
a) share long URLs via twitter and
b) track clicks on shared links.
The downsides to URL shorteners are:
a) single point of failure for links. This one is very significant, more below.
b) obscurity of a link's destination. This is mostly annoying and enables spammers to obfuscate their spam URLs.
We can't overestimate the seriousness of having a single point of failure on web links: URL shorteners are a man-in-the-middle, or a choke point for the connection to a web page. All traffic has to go through the server that hosts the shortened link. And if that man-in-the-middle for some reason doesn't want to, or can't redirect to the next destination, your link is broken. And nobody can tell where it pointed to. So not only is the link broken for as long as the man-in-the-middle is not available, but nobody can find out where it led to originally. There is no workaround! So why would the man-in-the-middle not redirect the link? Here are a few reasons:
* the server is down for technical reasons. This happens all the time, most recently with bit.ly.
* the company that runs the server goes out of business. What do you know about the financial situation of your link shortening service provider? How can you be sure that they will still be paying for and looking after their servers in a month, a year, in 10 years?
* somebody who doesn't like what you are linking to makes sure that your links are not being redirected. The incredible democratic power of the internet is being subverted by installing choke points on the internet that allow selective disabling of certain locations on the internet. And how convenient would be the ability to disable all links that point (via a choke point) to an unwanted URL. Not only could somebody break those links, but they could also destroy the information about the location of that unwanted URL with an encrypted string like "bit.ly/SDJHGe65sef". Nobody would know where the link pointed to without access to bit.ly's database.
* the URL shortening service's DNS stops working. Bit.ly is registered in Libya. Who knows what regime will be in power there in a few months. Will they continue to allow Western companies to use '.ly' TLDs?
By sharing shortened links on twitter, you're not dealing with one man-in-the-middle, but two: Your own shortening service and Twitter's t.co shortener. So you have two single points of failure in series. You just doubled the probability of your links being broken.
It seems to me that the disadvantages and risks far outweigh the benefits of using shorteners (at least for links that I hope to be around for a while).
So what are the alternatives to using shorteners? Twitter already distinguishes between displayed and expanded URLs, so there is really no need to apply choke-point shortening. The click tracking is a bit more complex. If you share links on a platform you control, you could do something similar to what google does with their search results click tracking. Or, if you want to share your links on somebody else's platform, make sure that the platform can provide you with non-invasive click analytics.
%w(word1 word2 word3)
with %w[word1 word2 word3]
both result in ["word1", "word2", "word3"]
I prefer the bracket delimiters since they better indicate the array nature than the parens. In % notation you can choose your own delimiters, so why not use brackets?