best practices Obvious Programming A technique to know how much refactoring you need on a piece of code. Refactor your code until it looks obvious to you and your team
best practices A case against nameless objects We name objects, we name variables, we name classes, messages, functions, and types. We name all the time because names allow us not only to reference "something" but also to understand what that "something" means.
css Featured “Is it CSS? Yes? Next.” - Tips for CSS code reviews CSS can make stuff look super cool... but is the code that makes cool stuff cool too? Not sure what to check? Some tips to do so might help!
cultura ¿Por qué escribimos inclusivo? Como personas que programamos apasionadas por la calidad, nos comprometemos en la búsqueda de la mejor abstracción en nuestro código. Ahora, como integrantes de esta sociedad sentimos la responsabilidad de extender este compromiso a nuestras comunicaciones oficiales.
naming The Art of Naming Today we all know now that variables should not be called x or y, not even i nor n, when we use the famous “for”... but do you really know why? have you ever had trouble naming a variable? and what about a method (message) or a class? The truth
naming Featured About names when designing with objects One of the recurrent problems I see when teaching OO design is the “names” used by the programmers to name classes, methods, etc.
