| Zago |
|
| A design agency, had some interesting projects. | |
| Ruby Patterns |
|
| Examples of Patterns in Ruby. | |
| Idiosyncratic Ruby |
|
| A 31 Parts Story about Ruby Specialities. A New Post Every Day in May 2015!. | |
| Website Style Guide Resources |
|
| Things people have written about style guides. | |
| Glip |
|
| Real-time messaging with integrated task management, video conferencing, shared calendars, etc. | |
| Google Charts |
|
| Google Charts can be an alternative to D3. Maybe. | |
| Google Cloud Bigtable |
|
| Single-indexed, sparsely populated table that can scale to billions of rows and thousands of columns. | |
| Chip |
|
| Raspberry was cheap? Chip is the new cheap, at $9. | |
| pluck_to_hash |
|
| Extend ActiveRecord pluck to return hash. | |
| PolyBelongsTo |
|
| Uniform Omni-Relational ActiveRecord Methods. | |
| inherit_from_matcher |
|
| RSpec matcher for checking whether a class inherits from another. | |
| Quinn |
|
| A web framework designed for things to come. | |
| Archjs |
|
| Web application framework for React. | |
| Marx |
|
| If you don't need the weight of heavy CSS frameworks, Marx is perfect for you. | |
| Ring |
|
| Full control over your communications and an unmatched level of privacy. | |
| Apollo |
|
| Mesos cluster provisioning and orchestration using Packer and Terraform. | |
| How Much Testing Is Too Much? |
may 4
|
| Suggestions on how to keep reasonable size and efficiency of your tests. | |
| What the pack |
may 4
|
| Examples and explanations of Array#pack and String#unpack. | |
| A Complete Guide to SVG Fallbacks |
may 4
|
| Approximately 5% of users browsing the web are doing so with web browsers that can't display SVG. | |
| Building an Event Sourced application using rails_event_store |
may 5
|
| Event sourcing and CQRS by using rails_event_store. | |
| Transforms on SVG Elements |
may 5
|
| Just like HTML elements, SVG elements can be manipulated using transform functions. | |
| Top 10 Elasticsearch Metrics to Watch |
may 5
|
| How to monitor Elasticsearch, or, in many cases, who is watching the watcher? | |
| Object hierarchy in Ruby |
may 6
|
| Default ancestry chain in Ruby, how to create your own ancestors, what the base level objects in Ruby actually do. | |
| Rails 5: what’s new |
may 7
|
| Test runner, where.or, new test request API, Render From Anywhere and no more alias_method_chain. | |
| Speed up ActiveRecord with a little tweaking |
may 7
|
| When a page of mostly simple content takes a second or more to come back from the server. | |
| Immutability in React |
may 7
|
| Immutability truly shines in tracking changes. | |
| Large-scale cluster management at Google with Borg |
may 7
|
| If you wonder where Kubernetes comes from, Borg is the answer. | |
| Self Improvement |
may 8
|
| Differences between module_function and extend self. | |
| Timeout: Ruby's Most Dangerous API |
may 8
|
| Ruby’s Timeout is a giant hammer and will only lead to a big mess. | |
| Chaining an Array into Arel ors |
may 9
|
| Build complex query by chain/build arel parts. | |
That's a few weeks now that we are getting organized better, with Xenor and Tysliu, on the preparation of this newsletter. The guys are now putting more attention to the news gathering and preformatting the yaml source file that I use to generate the letter and the website. After some time of practice, it is much better for me, as now I don't spend 5 hours each sunday anymore and I can manage the publication process in less than 2 hours. I still gather some extra links after the editors push their contributions. Then I verify the links, the categories, edit the comments sometimes, add dots at the ends of line, such tiny things. A huge thanks to Xenor and Tysliu!
Now we have 1312 subscribers to the newsletter. Plus an unknown number of RSS subscribers, maybe around 200. We get 250 visits per day on the website (according to webalizer), and most of them come from rss readers of many sorts. As the mailchimp is still free until we reach 2000, there is some margin. When we reach 1600 I think I swill begin a cleaning campaign, to help people that actually don't read the letter to unsubscribe. I kind of like the idea of throwing accounts away. Usually in web business, an account is an asset and they are never thrown away. There is so much to be told about numbers, and their reality, in our industry.
But the reality about numbers is usually the consequence of the over simplification required by marketeers. Things are never so simple as just a single number. The technicians among us are always in pain when we need to provide numbers, because they come with a strict definition of what they count, and that definition is never respected by the people that just want to use the number and put a sexy label on it. When we say 'registered accounts' they say 'users'. Do you see the difference? Damn, I hate that system that forces salesmen to become a liars.
