Lots of meaningful things take thousands of programmer hours. Projects where those thousands of hours are meticulously planned for by non-programmers (whether by using "Agile" or any other process that sits on top of the process of programming) are fucking doomed from the jump.
I enjoy programming with other programmers. But I don't collaborate well with people who don't know a fucking thing about programming who try to put process on top of the process of programming.
Cowboy is a complement. It doesn't mean "lone ranger" or "asshole", it means lazy, hard worker who takes the shortest path to greatest output. So, yup. Cowboy here.
> [Obligatory plug and disclaimer: Agile professional
You sell process for a living. You claim, "After all, it's not like you can have no process at all. Whatever you're doing already is a process." When you said that, you accidentally got something right.
Programming is a process. It's the only one that fucking matters if you're a shop that sells software. All the other process comes from snake oil salesmen as yourself, or pointy haired bosses who don't know a fucking thing about programming.
Programming. Either learn and do it, or get the fuck out of its way.
The lettering is what makes the original poster. The original poster was most probably hand lettered by a talented lettering artist. Arial doesn't come remotely close.
Especially the capital "r". Arial's "R" makes me want to turn away. "I'm a capital p, but have a protuberance!" Its leg is about as graceful as a heavy duty shoring rod that has been heaved to, propping up an obese person. "Spare me that next step!".
I apologize if you feel my post was "Go is great!"
You shouldn't apologize for the feelings of others. DHowett started us in the wrong direction here with his snark (nothing else, just snark), and now none of the responses in the subthread demonstrate reading comprehension.
Oh, well. It was an interesting perspective. I'd be interested in hearing from you again, after a few months of using Go as the primary language for your exploratory programming. I've been keeping a running list of things that trip me up as I plod along. So far it's mostly that initially I didn't fully grok how interfaces and types and functions work together, so I ended up working around the type system instead of enjoying it. That's slowly changing. It would be fun to compare notes.
Having good programmers who can't agree on a consistent style is problematic, but good programmers can follow a reasonable style guide, even if they have quibbles about it.
I'm not surprised to see this reaction. The folks who react strongly against this announcement have ideas, and think these ideas make them special.
We've all worked with that girl who succeeded at everything she touched. We'd hire her in a heartbeat, for any project, because she figures out how to make it work the best it can. If she's around, we can step back a bit and trust, and the project turns out better than if we'd run it our self.
She's worth way more than the guy who farts great ideas.
> Why on earth would you
> Really, it sounds like you just
You don't come off very nice.