Game of Thrones Daily
Origami Around
⁂
Acquired Stardust
trying on a metaphor
Today's Document
hello vonnie
Product Placement
Kiana Khansmith
art blog(derogatory)
Discoholic 🪩
No title available
Andulka
Janaina Medeiros
cherry valley forever
Three Goblin Art
taylor price
Peter Solarz
Cosimo Galluzzi
roma★
seen from Malaysia
seen from Israel
seen from Malaysia
seen from United Kingdom
seen from United States
seen from Vietnam
seen from United States
seen from Argentina
seen from Vietnam
seen from Brazil
seen from Malaysia
seen from T1
seen from United States
seen from United States
seen from United States
seen from Malaysia
seen from United States
seen from Germany
seen from Türkiye
seen from Ukraine
@rubypostit
Design Patterns and Refactoring articles and guides. Design Patterns video tutorials for newbies. Simple descriptions and full source code examples in Java, C++, C#, PHP and Delphi.
In the modern engineering profession, more than half of the job involves human communication and resolving people issues. The management AntiPatterns identify some of the key scenarios in which these issues are destructive to software processes.
Yagni ("You Aren't Gonna Need It") is the principle that we should not build presumptive features. It should not be used as a justification for neglecting internal quality.
Yagni originally is an acronym that stands for "You Aren't Gonna Need It". It is a mantra from ExtremeProgramming that's often used generally in agile software teams. It's a statement that some capability we presume our software needs in the future should not be built now because "you aren't gonna need it".
RubyKaigi 2015, 11-13 Dec.
Most applications written in Ruby are great, but also exists evil code applying WOP techniques. There are many workarounds in several programming languages, but in Ruby, when it happens, the proportion is bigger. It's very easy to write Ruby code with collateral damage.
Reading source code is the best way to progress to higher levels of understanding.
In my experience, the most part of Rails developers tend to use just a really limited subset of all the features the Rails framework offers. If you could sum all methods from all the GEMs part of the Rails framework and subtract all methods you have used at least once in your Rails application, you would probably discover that there’s much more goodness to take advantage of.
An interesting post on the FactoryGirl, how build_stubbed works, what's going on with ActiveRecord associations and a few ways for improving stuff if it happens to use FactoryGirl in your project.
define_method is one of the many powerful features of Ruby that makes possible the creation of awesome gems like Rails. Understanding its usage and how to wield it will make you awesome.
In this post, we’ll see all the different ways we can use define_method to define class and instance methods in a Ruby class.
By, Sandi Metz Our code is full of hidden assumptions, things that seem like nothing, secrets that we did not name and thus cannot see. These secrets represe...
Our code is full of hidden assumptions, things that seem like nothing, secrets that we did not name and thus cannot see. These secrets represent missing concepts and this talk shows you how to expose those concepts with code that is easy to understand, change and extend. Being explicit about hidden ideas makes your code simpler, your apps clearer and your life better. Even very small ideas matter. Everything, even nothing, is something.
Maintaining high code quality creates a non-trivial overhead and consumes real development cycles. Many people find it difficult to trade-off this overhead with the benefits and assume you have a binary choice: either move quickly with low code quality or move slowly with high code quality. Since startups optimize for a fast development cycle, people assume you have to do so with low code quality.
Do you rely on syntax highlighting when developing software? If so, you may be shooting yourself in the foot. In this post, I will argue that syntax highlighting, while aesthetically seductive, moves focus from content to form, and discourages those who look at the code from trying to understand it.
In 2011, "Uncle Bob" Martin challenged the Rails community to decouple their business log from Rails machinery. But he didn't much detailed guidance as to how. Here's a talk by Jim Weirich from 201...
In 2011, “Uncle Bob” Martin challenged the Rails community to decouple their business log from Rails machinery. But he didn’t much detailed guidance as to how. Here’s a talk by Jim Weirich from 2013, where demonstrates his implementation of Martin’s ideas.
What are idempotent and/or safe methods?Safe methods are HTTP methods that do not modify resources. For instance, usi...
REST is hot! And REST is finally rediscovered by API programmers all over the world. But REST isn't always as easy as it seems on first look. Dealing with HATEOAS, Code on demand and uniform interfaces can be really tricky and many people will fall back to not-so-restful approaches when things are starting to become more difficult. But it doesn't need to be. Once you get to know REST, you will like it.
Today I’m tired and frustrated. And it’s not the first time that I have those negative feelings. Typically I just complain on twitter, lose some followers, wait a bit to calm down and move on. But today I need to vent and convert my negative emotions...
Today I’m tired and frustrated. And it’s not the first time that I have those negative feelings. Typically I just complain on twitter, lose some followers, wait a bit to calm down and move on.
Refactoring some code so that the lines that call and unpack data from an external service are separated into clear objects.
If you've written Ruby, you've heard it before: Use single quoted strings unless you need string interpolation.
It makes sense, right? When I instantiate strings using double quotes, the Ruby intepreter has to do extra work to figure out if it needs to perform interpolation. Since extra work means reduced performance, it seems reasonable to avoid double-quoted instantiation unless it's a necessity.
Monkey Patching. When you first try Ruby, it’s amazing. You can add methods right to core classes! You don’t have to call Time.now.advance(days: -1), you can write 1.day.ago! It makes Ruby a joy to read and write. Until…
We had a look at some of the basics of making a game using the Processing.js game library, so let's kick it up a notch by just getting down and making our own Super Mario game. When we're done with this part of the tutorial, we'll have a game with koopa troopers, platforms that we can jump up through but not fall down through, a hole with terrible muncher plants, coins, including a mysterious dragon coin, a giant banzai bill bullet that comes out of nowhere, and even some advanced things like not actually putting enemies in the level from the start, but only just before you get to where they're supposed to be.