winton
I think the intention of "in my culture" is to allay a fear in the listener. The speaker is worried that there is a strong expectation of change in the listener by stating something as an axiom. The speaker's hope is that the listener will see a possibility instead of a demand.
Some people think it should be obvious that what a person states should never be seen as a demand to conform. Some believe this is a necessary life skill, especially in business.
Some people are interested in finding ways of speaking in a more sensitive way in an era that seems to be embracing sensitivity.
Its interesting to me that both sides can see each other's ways of communicating as an affront, when it is likely not the intent on either side.
This lead me to the creation of DotStore (https://github.com/invrs/dot-store#readme), along with extensions to use it with React [1] and the filesystem [2].
"Dot prop" strings have proved to be an elegant solution to detect which props changed on the store. Usually this means doing a regex match in `shouldComponentUpdate`. We almost never use React's state anymore.
[1]: https://github.com/invrs/dot-store/tree/master/packages/dot-...
[2]: https://github.com/invrs/dot-store/tree/master/packages/dot-...
We are a sports media site that is revolutionizing journalism. We are the 2nd largest sports site (right behind ESPN) and a top 30 web site, reaching 80 million unique users per month. We love technology, we love to learn, and we love to have fun.
We are primarily a Ruby shop, but as we implement a service oriented architecture, we use increasingly diverse technologies. These technologies include Rails, Node.js, Redis, PostgreSQL, Backbone, Marionette, Docker, DynamoDB, Elastic MapReduce, Redshift, and more.
See our listings at http://eng.bleacherreport.com/jobs
We are the 3rd largest sports news site in the United States, just behind ESPN, Fox Sports, and Yahoo.
Work on a site that reaches 70 million people per month while getting exposure to a variety of technologies (we routinely play with Ruby, Node.js, Elixir, and Go). We encourage our employees to contribute to open source as apart of their work at Bleacher Report, and most importantly, always be learning.
Email [email protected] or visit http://bleacherreport.com/careers/engineering
We are the 4th largest sports web site in the United States, just behind ESPN, Fox Sports, and Yahoo.
Work on a site that reaches 20 million people per month while getting exposure to a variety of technologies (we routinely play with Rails, Node.js, Redis, eventmachine, and Sinatra). We encourage our employees to contribute to open source as apart of their work at Bleacher Report.
Did not realize framous had not saved my picture orientation properly. Emailed to cancel order so I could place a new one. No response.
Now I will not be placing a new order at all.
We are the 4th largest sports web site in the United States, just behind ESPN, Fox Sports, and Yahoo.
Work on a site that reaches 20 million people per month while getting exposure to a variety of technologies (we routinely play with Rails, Node.js, Redis, eventmachine, and Sinatra). We encourage our employees to contribute to open source as apart of their work at Bleacher Report.
We are the 4th largest sports web site in the United States, just behind ESPN, Fox Sports, and Yahoo.
If you are a Rubyist who is looking to play with a wide variety of technologies, make big decisions on a relatively small team, and work on a site that reaches 20 million people per month, this is your place.
It can do everything nanoc does, but the execution is much simpler and much more natural. This is not just my opinion, but what I have heard from lots of people.
My apologies for the self-promotion, just trying to get the word out.
There is distinction between filters for content and layouts, simply use the layout filename in a before block.
You can execute any Ruby you want. You can use ActiveRecord, Redis, whatever. Load YAML for metadata. None of this stuff needs to be baked in, Ruby already does it.
There are inherent constraints to the framework because it must be "safe" enough for GitHub's environment. For example, an issue close to my heart: