Group items tagged

Learn how security is designed into Google's technical infrastructure. Google uses this infrastructure to build its internet services, including both consumer and enterprise services.

Jednoduchy design pattern

Making everything easy to change makes the entire system very complex. Technical debt is a metaphor developed by Ward Cunningham, who uses the term to describe the design tradeoffs we make in order to meet schedules and customer expectations.

paradny writeup use caseov, kedy je vhodne pouzit sqlite DB

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

uplne suhlasim, osobne si tu informaciu skoro nikdy nestihnem precitat a nemam rad, ked mi to rychlo uteka na dalsi polozku

Pouzitelny pri volani vzdialenych procesov a sluzieb (cez siet), ktore mozu dostat timeout alebo inak zlyhat.

jednoducho a zrozumitelne vysvetlene ako pisat html+css+js tak aby browser rendroval obsah co najrychlejsie

ten blogpost je o niecom uplne inom (mikroformatoch), ale je tam zaujimavy kapitolka o tom, ze sa im email ako nastroj na vymenu informacii a brainstorming neosvedcil: Perhaps the most important is that as a community we are far more efficiently productive using just IRC and the wiki, than any amount of use of email. In fact, the microformats drafts that were developed wtih the most email (e.g. hAudio) turned out to be the hardest to follow and discuss (too many long emails), and sadly ended up lacking the simplicity that real world publishers wanted (e.g. last.fm).

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.

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.