It is said that anyone ever involved in setting up a process of managing software development had an idea of coming up with his own custom tool and workflow. Specifically in web software development.
We’ve all been there. We’ve gone through all existing tools and, this way or another, found our best shot. Heard of kanban? It’s as easy as 1–2–3 to tear it into pieces, take what fits, and call yourself agile. Daily inertia inside a busy software house hive has proved it all right.
In our line of business, we work on various projects simultaneously and have to stay ABC at all times, therefore well-optimized workflow is a must. It’s also a moral boost and sanity check for developers. Top-down and bottom-up — both have to meet.
It’s another Monday, so we figured it might be the right time for the new issue of From Monterail with Love. We’re announcing something special this time:
If you like the series, subscribe to our newsletter so you’ll have a similar digest delivered right to your mailbox once a month.
But for today, we’ve got some free e-books, and a couple of security and tests-related links. Enjoy.
Something to read
If you are a regular developer, chances are that occasionally you need to transform yourself into a sever admin. To make this less painful, I recommend diving into The Debian’s Administrator Handbook.
Do you remember the beauty march in Wrocław last year? The amazing event happened and we’re proudly announcing that its sequel is coming in less than a month: the “fresh Ruby-oriented conference in Wrocław, Poland” will take place on March 1–3rd, 2013.
Visit this year’s website.
There’s a dashboard in one of our applications that shows data from various external services. The more data we were adding to this dashboard, the worse its performance and user experience was getting until the site eventually became unusable. It got to the point where its user had to wait 10 seconds or even more for the content to show up. Unfortunately, caching didn’t help much.
Here’s the story of what we did to reduce the load time.
It seems like it happened yesterday. I arrived at the flat in a crumbling tenement located in the Old Town of Wrocław and my journey into the Ruby world began. The community was already large and very active, so I wouldn’t call myself Columb, but—at least—I can tell you about my first year experience and share both bright and dark sides of the story.
I didn’t join the awesome Monterail guys as a complete novice. I was working in the industry since 2007, mostly as a PHP programmer. As the world was moving forward, I felt like PHP kept standing in the same place, and to stand still is to move back.
RubyGems.org has been compromised.
The exploit could potentially tamper with some gems, therefore all of them are assumed to be unsafe to use at the moment. Which means that any deployment involving downloads of any gems from RubyGems.org should be carried out with extreme caution. All downloaded gems have to be verified in order to remain on the safe side.
The Ruby community reacted quickly— it’s now possible to compare checksums of downloaded gems with the checksums of their known-to-be-safe versions hosted on mirroring sites.
We recently launched the redesign of our blog, but Codetunes is still work in progress. This is a post kicking off the unordered series of articles outlining some of the decisions we’ve made during this ongoing process.
It’s amusing how seemingly trivial things can lead to the most exhaustive discussions and disagreements.
I don’t like making New Year’s resolutions, therefore I haven’t been making them at all. But I realized that setting goals to achieve—especially when they are split into smaller pieces—is a good idea. Like in the agile methodology, you can extract what is important for you and move forward step by step to the next epic year as a better person.
So… What are my goals?
1. Participate in the open source
I haven’t contributed lots to open source yet. Shame on me, I know. Making a single commit every month should be good start, at least getting this into habit.
An excerpt from our internal documents and our job offer template. One of our goals for 2013 is to make Monterail one of the best places to work — we put efforts into this constantly but we want to organise stuff and make it clear to everyone, both inside and outside.
We try to make sure that every member of our team fits and agrees with those values.
It’s time for New Year’s edition of our summary of the content found in couple of the last weeks. While you are getting back into ordinary flow you can read about Vim, objects in Rails and improve your hacker’s toolbox. Enjoy!