My main website languishes, having no significant updates in over a decade. I repeatedly give up on my attempts at building even simple new games. And now even this crappy blog goes nearly two years without any updates. Why? Because I’m pretty much in an abyss of hellish real-life stressy balls of shit. A huge part of my lack of motivation (I think) is my day job. Continue reading “I’m not dead! Sadly, neither is Rails…”
Ruby code is beautiful code, not like that ugly Go nonsense
When did Ruby’s “beautiful, readable code” mantra take such a shitty turn? Or has it always been this bad and I just never noticed back in my “OMFG I LOVE RUBY” days? Continue reading “Ruby code is beautiful code, not like that ugly Go nonsense”
Another reason I hate Ruby
I’m working in Rails again. I hate it. It kills me. It drains my soul.
But this time it’s an external dependency that’s got my panties in a wad. Continue reading “Another reason I hate Ruby”
One technology to rule them all
One technology to rule them all
I’ve heard or seen multiple versions of these statements during my time as a developer, and frankly you’re all idiots for buying into it:
- Devs shouldn’t have to learn multiple technologies / program in multiple languages
- Standardize all projects in one language and framework
Rewrite non-conforming legacy code in one tech
Go’s success with the “gofmt” tool
I just ran across a discussion of gofmt, and I feel like the author definitely gets it, but there’s one piece to the puzzle he (or she? “Chris” is pretty ambiguous) neglected to mention. Laziness, pure and simple. He mentions that laziness wins when an opinionated person is trying to fight the convention in the context of the community, but what about those of us who don’t care about the community? Continue reading “Go’s success with the “gofmt” tool”
Amber doesn’t like my website
From my contact form, Amber wrote:
You’re website is by far the most disgusting thing I’ve read. I am talking about your article on anorexia. I weigh 93 pounds and am 18, I am not anorexic but I do have health problems because of my weight. It is not okay for you to tell people they are fat and ugly, you have a right to say what you would like and so do I. You are a terrible fucking person, people like you make others feel discouraged and down, I’d like to see what you look like. You are wrong and fucking disgusting. Thanks for the horrendous read.
So many things to mock here, where do I begin? Continue reading “Amber doesn’t like my website”
Go 1.7.3 supports function overloading!
This is now valid syntax in Go:
var value interface{}
//+overloaded
func setValue(x int) {
value = x
}
//+overloaded
func setValue(x string) {
value = x
}
//+overloaded
func setValue(x int, y string) {
value = fmt.Sprintf("%d %s", x, y)
}
If you don’t believe me, check out the source code on the Go playground.
Ode to bad devs, part 3: It’s more than just writing code
There are so many things a good developer has to do that nobody really understands. Especially bad developers. I’d love to say, “you know who you are”, but most bad developers have somehow managed to skate through life with no fucking idea how bad they are. I’m not sure how this happens.
A good developer isn’t just sitting around churning out code to get the job at hand done quickly. In fact, if that’s all you do when you work on a project, you’re a shitty developer. And you know what else? You’re slower than me. All that time spent rushing around is slowing you down, dumbfuck. Yes, you will finish a discrete task faster, but you will never discover better tools. You’ll never think about what you can automate. You’ll never adapt your workflow. Leaving you wasting time you don’t even know you’re wasting.
You’ll stick to what you know and you’ll call it a job well-fucking-done. You’re a complete waste of my time because you ruin shit you don’t even understand you’re ruining because you refuse to even attempt to learn a better approach. Continue reading “Ode to bad devs, part 3: It’s more than just writing code”
Ode to bad devs, part 2: Docker
Continuing my discussion of stupid developers who are dumb, just a few more words about the problems with software “engineers” these days. There is a general trend among devs lately to just skim documentation, copy some Stack Overflow code, and call it a day. Hell, maybe this “trend” was always a problem and I just didn’t notice it. But it’s definitely a problem and the devs who do it are probably a good part of the reason outsourcing can be a very good idea.
If you are going to do a job, at least pretend to half-ass it. I see developers around me constantly learning the bare minimum of a given tool or process to get the job done so they can move on. Sometimes they do nothing more than refer to a “cheat sheet” so that they never have to understand anything at all. Oftentimes they have no understanding of the inner workings of whatever it is they’re using, which leads to a great deal of the Git hate I see out there.
Git is not today’s topic. Docker is. Continue reading “Ode to bad devs, part 2: Docker”
Ode to bad devs, part 1: Harmony Central
I’d like to discuss shitty developers. Because there’s a rule that’s being violated out there by more than half the devs I’ve ever worked with, and it goes like this: developers are lazy, so we try to find ways to make our work easier.
The problem is some devs are so god damned lazy, they just churn out shit and don’t bother to even notice they’re wasting a ton of time. Continue reading “Ode to bad devs, part 1: Harmony Central”