How can a crappy site with boring games waste more space?
When you need a static site, is your first thought “can I use Rails”? If so, you’re a fucking idiot just like the author of the worst article on static sites ever written.
In particular, this passage makes me weep bitterly:
What if your requirements don’t require a dynamic server but you still want to use a mature web application framework your familiar with and trust such as Express or Rails.
…
Continue reading “Is it time for “Building a Static Site for Dummies”?”
tl;dr: Explaining terms you don’t understand makes smart people ignore your article. And I’m not even all that smart, so… this must be pretty fucked.
Please don’t start your articles with a “What is X” when you have no god damn idea what the fuck you’re talking about. For instance, if you were wondering to yourself one day, “what is transpiling?”, you’d be making a huge mistake by reading the first paragraph of Hail, Babel! The Transpiling Overlord.
The author’s just plain stupid. Continue reading “Transpilers are not what you think”
I’m diggin’ Go, but I’ve noticed there’s a tendency to “freeze” third-party code directly into one’s repositories on github. This is absolutely awful in my opinion – the code isn’t a part of your project, so it has no place in your repository! I do understand the problems, trust me, but this approach has some issues a lot of folks won’t realize until they’re hit HARD by a show-stopper. Continue reading “Go Dependency Freezing”
Oops….
s/IS AWESOME/considered harmful/
Much better. Continue reading “Ruby’s Object#tap IS AWESOME”
Ruby Weekly once again confirms my belief that Ruby developers are actually getting dumber by the week. And considering you fuckups were already as dumb as rocks, that’s saying something. Continue reading “Three more reasons I hate you shitty little “developers””
Ah, DHH. A lovely series of articles showing off your inexperience once more.
And this from an “industry leader” who should know better.
There are some wonderful quotes from the father of Rails that tell me he’s still the same douchebag he’s always been, and still has no idea how quickly complex projects go bad when built with his OMFG COUPLE EVERYTHING YAY mentality. Continue reading “This just in: DHH is still a douchebag”
I have a serious issue with Ruby magic.. no, wait, Rails magic… hmm, well no, maybe magic within the funky “sub-framework” I use?
Oh FUCKIN’ A, I don’t know. There’s a project I work on and it uses Rails. And it’s using an unnamed and incredibly shitty “sub-framework” (referred to henceforth as “Cyclops”) that forces us to use very specific gems whether we like it or not. In some cases the gems are cool, and in some cases they are the fucking devil himself. Continue reading “HI IM RAILS I CAN HAZ MAGIC?”
Dependency Injection is still Dependency Injection even if you use an approach that’s specific to Ruby 2.1 and decide to call it “Interception Injection”. Just like incompetent developers are still incompetent even if they start inventing fake patterns. Continue reading “Dependency injection by any other name… still means you’re an idiot”
Here ya go:
:%s/:\(\w\+\) => /\1: /g
You can also do cool stuff to run this across all buffers, tabs, etc. via something like this:
:tabdo %s/:\(\w\+\) => /\1: /g
I’m working on a Ruby on Rails application, where automated testing is an absolute must. Unlike Java or C++, you don’t have any kind of useful compile-time warnings and errors to tell you where you’ve screwed up, made a typo, etc. Most errors in a Rails web app happen when a user interacts with your code, so if you don’t test, you don’t know about bugs until it’s too late. This is one of many reasons I’m wishing for a nice C++ project to play with… but that’s another topic for another day…. Continue reading “Automated testing saves the day”