Group items tagged

slajdy o zaujimavych pripadoch pouzitia gitu - napriklad second-order diff - pride mi to inovativne a zabavne

+ part 2 http://erenyagdiran.github.io/I-was-just-asked-to-crack-a-program-Part-2/ zaujimavy kratky clanok o crackovani neznameho programu.

A curated list of awesome Ruby frameworks, libraries and resources. Inspired by awesome-php & awesome-python.

programovanie v Ruby bez pismen :)

North encourages an agile, content-first, approach to product development and a mobile-first, in-browser, system based approach to design and development.

Overené praktiky a zásady vývoja softvéru vo firme thoughbot.com (via rubyslava)

je tam aj Ruby

Rails engine - moznost pouzit conzolu v prehliadaci... (Tato verzia je pre Rails 4, existuje vsak aj projekt pre Rails3.2)

It all sounds so straightforward: Put your code up on GitHub or start/join a project at the Apache Software Foundation (ASF), build a community of like-minded individuals, start a company, take in some funding, and then IPO. Or maybe not. One thing is certain: Running an open source company has unique challenges and opportunities.

Pomocka pri pisani rychlejsieho Ruby kodu. V ramci moznosti... :o)

na ubuntu 14.04 som to nainstalovat takto: apt-get install npm npm install -g gitjk ln -s /usr/bin/nodejs /usr/bin/node alias gitjk="history 10 | tail -r | gitjk_cmd"

commity Kernighana, Ritchieho, Bournea .. The goal of this project is to create a git repository representing the Unix source code history, starting from the 1970s and ending in the modern time. To fulfill this goal the project brings data from early snapshots, repositories, and primary research. The project aims to put in the repository as much metadata as possible, allowing the automated analysis of Unix history. The following table illustrates the type of material that can be gathered and integrated into the repository.

skype-poll-fix - Reduce Skype CPU load on Linux and Mac OS - ak vam je kazdy kusok cpu timeu dobry, fix skutocne funguje

The official Ruby interpreter is written in C. That means that everything you can do in Ruby, you can also do using function calls to Ruby's C API.

Testing distributed systems under hard failures like network partitions and instance termination is critical, but it's also important we test them under less catastrophic conditions because this is what they most often experience. Comcast is a tool designed to simulate common network problems like latency, bandwidth restrictions, and dropped/reordered/corrupted packets. It works by wrapping up some system tools in a portable(ish) way. On BSD-derived systems such as OSX, we use tools like ipfw and pfctl to inject failure. On Linux, we use iptables and tc. Comcast is merely a thin wrapper around these controls.

has_many is an anti-pattern which leads straight to monolithic applications. However, a simple inversion can free us from its grasp. What is the first model you added to your application? Probably User, right? So, once you wrote user.rb and its corresponding tests, and committed it - why did you ever open that file up again to tell it about something that it did not need to know existed? Rails keeps you from reopening user.rb if you add a column to the User table, and this is good, right? So why, when you added a Posts table far away, did you open up User again to make it aware of Posts? Did the definition of being a user change? Did you did not realize you were violating the Open-Closed Principle, one of the 5 principles of SOLID design? Somewhere inside I bet you knew it felt dirty to keep opening up User and making it aware of things that it had been blissfully unaware of.