InnoDev

Refactor until you feel you are one step behind the solution you want. Avoid your comfort zone. And while you might see extractions that would probably get you to a better design, don't apply them until you see the need two or three different times. Remember that duplication is cheaper than the wrong abstraction. The best refactors will then naturally arise from the repeated inconveniences, instead of from unbacked ideas of what could potentially be better.

If you've been-there-done-that and you're now building your dream home with your retirement fund, this post really isn't for you. Congratulations are in order. But if, like me, you find yourself getting older and still can't resist the desire to keep coding and building things, then read on.

Workplace stress costs the U.S economy hundreds of billions of dollars per year and is prevalent across all types of organizations and workplaces. If you have adopted or are in the process of adopting the devops methodology and culture, chances are your software developers are burning out as well.

A list of Ruby gems that have memory leaks

Matz is experimenting with three concepts that may or may not be included in Ruby 3.0. 1. Man-machine collaboration through a static analyzer (e.g. rubocop or ruby-lint) that uses soft typing (i.e. inferred typing) to determine if a program will crash or not. 2. Performance enhancements through JIT compilation, but preliminary implementations have shown to increase memory consumption as a side effect. 3. Concurrency improvements through better abstractions like streams and pipelines. When used, the running program would place itself inside an event loop, disable the GIL, and force objects to be immutable. Matz calls it Rube Goldberg Programming.

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

I've never met a developer who complained about code getting faster or taking up less RAM. In Ruby, memory is especially important, yet few developers know the ins-and-outs of why their memory use goes up or down as their code executes.

"It's what the movie studios want for their products, it's what professional writers want for their work, it's what newspapers want - hell, it's what everyone wants: attention. Attention is power." So wrote the actor James Franco in an article on the selfie phenomenon in The New York Times last winter.

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.

With the new Linux 4.0 kernel, you'll need to reboot Linux less often than ever. Uz nikdy viac reboot :)

As of today, all support for Ruby 1.9.3 has ended. Bug and security fixes from more recent Ruby versions will no longer be backported to 1.9.3.

necakane skoro :| som zvedavy, pri ktorej verzii zakotvia nase projekty. Ruby v2.1 ma nejake problemy s GC http://stackoverflow.com/questions/27102565/memory-usage-increase-with-ruby-2-1-versus-ruby-2-0-or-1-9 a webafis uz podporuje Ruby 2.0+ ?

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.

AMERICAN AND BRITISH spies hacked into the internal computer network of the largest manufacturer of SIM cards in the world, stealing encryption keys used to protect the privacy of cellphone communications across the globe, according to top-secret documents provided to The Intercept by National Security Agency whistleblower Edward Snowden. The company targeted by the intelligence agencies, Gemalto, is a multinational firm incorporated in the Netherlands that makes the chips used in mobile phones and next-generation credit cards.

pre porovnanie vizie a misie :)

Aj vas irituje nemoznost menit commit messages? Zaujimalo ma vzdy preco, ci to ma dobre odovodnenie a dnes som to nahodou nasiel: The message from Linus Torvalds may answer your question: Modify/edit old commit messages Short answer: you can not (if pushed). extract (Linus refers to BitKeeper as BK): Side note, just out of historical interest: in BK you could. And if you're used to it (like I was) it was really quite practical. Co ja viem, podla mna nie az tak rozumne, ved moznost commit-ovat davame tym ktorym verime, ja nevidim take velke riziko v tom, ked commiters mozu menit messages. Stava sa mi, ze si pomylil cislo JIRA issue a uz je neskoro, nic sa s tym neda spravit. Vtedy ma mrzi, ze som clovek :)

mercurial na to ma feature ktora je natolko specialna ze ani nie je v beznom release :), ak som to pochopil spravne je to nieco ako meta-verzionovanie: http://mercurial.selenic.com/wiki/EvolveExtension

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.

There's no such thing as an anonymous programmer: your coding style can unmask you, according to research led by Drexel University Comp. Sci. PhD student Aylin Caliskan-Islam. In work that has serious implications for anyone believing their open source project contributions are anonymous, the researchers find that as many as 95 per cent of contributors to a decent-sized code base can be identified.

perfektne vysvetlene ako vizualizovat hru Quake na (lepsom) osciloskope.

Need-to-know (like other security measures) can be misused by persons who wish to refuse others access to information they hold in an attempt to increase their personal power or prevent unwelcome review of their work.