Have you ever added a file to svn:ignore and then immediately screamed "Noooooo! Command Zee!" (Or "Noooooo! Control Zee!" for you Windows folks...) I just did.
SVN:ignore is great for making sure you don't accidentally commit a configuration file containing passwords to your Subversion repository. You can get to it by right-clicking on the file you want to ignore in Eclipse/CFB's Navigator pane, and choosing "Add to svn:ignore..." from the "Team" menu.
This is all well and good until you accidentally ignore a file that you want in your repository. Whoops! Command Z!
Unfortunately, removing files from svn:ignore is not as intuitive. But don't fret, it's still pretty easy.
I am using Subversive for SVN integration in CFB, but I got the tip from someone using Subclipse, so I assume it's only some labels that are different, if anything.
- Right click on the project folder, and choose properties.
- In the dialog that comes up, choose the item "SVN Info" item in the left pane.
- SVN properties will be displayed in the listbox at the bottom-right of the dialog. Find "svn:ignore" and double-click it.
- A dialog displays the current value and allows you to edit it. Find the offending line, remove it, and hit the OK button to save your changes.
- Your file should now go back to the not-added-to-svn state, and you can commit it at will. If you don't see it, try refreshing the project.
Posted in
| No Responses Yet
August 04 2010
Yesterday's post exposed an embarrassing flaw in my own blog setup: High-ascii characters didn't display correctly. Previously, nobody had tried to post a high-ascii character in a comment; and I hadn't used any in a post. Now that it's happened, though, I've fixed the problem.
My first thought was that my database (MS SQL Server 2005 Express) hadn't been properly configured to allow the characters. But on inspection, each necessary column was the appropriate nvarchar / ntext type.
As it turns out, the culprit was my CF Datasource settings. If you edit the datasource properties, and then click the "Show Advanced Settings" button, you'll find the confusingly named setting: "String Format" that enables high-ascii characters and unicode.
Enabling this feature opened the door for high-ascii characters, and now they will display correctly here. Special thanks to Ben Nadel for exposing the flaw, and to Oğuz Demirkapı for being our community's i18n test case for as long as anyone can remember.
Posted in
ColdFusion |
Databases
| No Responses Yet
August 03 2010
A recurring theme at CFUnited this year seemed to be proper pronunciation of community members' names. It came up at keynotes, during sessions, and even in line for breakfast. I've always lamented the fact that the internet doesn't come with a pronunciation guide. Just for kicks, I thought it might be fun to put one together for oft-mispronounced names in our community. I'll start, and you can continue adding in the comments, if you know more or have seen a name and aren't sure how to pronounce it.
- Pete Freitag -- owner of Foundeo and frequent speaker on Security. Apparently his last name is pronounced "Fry-tag". I had always said "Free-tag" in my mind.
- Ben Nadel -- the one person in the community who seems to blog more than Ray Camden. He pronounces his name "Nay-dl" (like "Navel").
- Doug Boude even lists in the
<title> element of his website that his last name rhymes with 'loud'.
What others do you have no idea how to pronounce, or have you often heard mispronounced?
Posted in
ColdFusion
| 8 Responses
August 02 2010
If you've ever worked at an organization with a large team of programmers, chances are that you've come across both the passionate and the dispassionate ones.
Programmers are not all created equal. Well, ok, maybe we are created equal -- we are just men and women. But through training and study, some excel while others flounder in mediocrity. And if there's one thing we should have learned from The Mythical Man Month, it's that fewer great programmers are more valuable than more average programmers.
It is my personal opinion that organizations should want to take advantage of that, and hire fewer great programmers. The pie-in-the-sky theory is that the organization ends up paying each individual more -- in recognition of their talent -- but a lower combined total for the fewer great programmers than the combined total of more average programmers, all while accomplishing the same work at a higher quality. Not many organizations realize the amount of Technical Debt that they are taking on by hiring dispassionate programmers. But in order to hire great programmers, you have to be able to tell them apart from the average programmers. With the assumption that everyone wants to hire great programmers, let's take a moment to explore how exactly you can identify them.
I think the mark of a programmer with the potential for greatness is passion. Not accomplishment, or involvement, or even any relative level of knowledge. Accomplishment can be obtained. Involvement can be generated. Knowledge can be learned. But passion comes from within. Either you have discovered it in yourself, or you haven't. The funny thing is that accomplishment, involvement, and knowledge tend to happen naturally and organically when passion is present.
You can lead a horse to water, but you can't make him drink.
There are different reasons that the horse may not drink.
Some horses only drink coffee, or Mountain Dew, or peppermint tea. Your offer of water simply doesn't interest him. Likewise, some programmers are passionate about other things, like Cryptography, Compression, or Compiler algorithms; and your offer of free training in CAD is just not interesting to them. It's not that she doesn't have the passion, her passion is for something else, and there's nothing wrong with that.
Some horses just aren't thirsty. You can stand by the water all day and he will just stand there doing horse stuff. Likewise, some programmers don't have the thirst. The passionate programmer seeks out opportunities to learn or try something new. The dispassionate programmer is happy to rest on her laurels. Why should she learn something new when she's getting "satisfactory" marks on her yearly reviews? Her bills are paid, her children are fed, and she gets to spend her weekends doing that thing she really loves to do.
The thirsty horse will not only drink the water you lead him to; but he will remember the trail, follow it back later by himself, sometimes bring friends, and eventually exhaust the water supply. He'll take it upon himself to find other watering holes. A passionate programmer will pore over presentations, books, blogs, articles, and magazines; apply what she learns and build on it, and in some cases she will even make a hobby out of what started as an occupation. Eventually, she may even turn her passion into an opportunity to teach: presenting, and writing for books, blogs, articles, and magazines.
And she will do all of these things not because they are her job, or because they bring her tremendous amounts of success; but because she enjoys doing them.
How do you find passionate programmers? One way is to look to Open Source software. These are programmers that enjoy what they do so much that after they are done getting paid for it from 9-5, they go home and do more for free. If that isn't passion, I don't know what is.
Need someone to come in and overhaul your intranet? Start looking at the developers of Open Source content management systems. Need a great architect to whip your team into shape? Start looking at framework developers. These people have the skills you're looking for and the passion you need. Who cares if they'll need to learn a new programming language? That's the type of thing they do over the weekend -- for fun -- remember?
However, not all passionate programmers develop open source software. Some people just don't want to put themselves out there in the public eye; but that doesn't mean they aren't hiding in the shadows, sharpening their saws. Open Source contributions are one indicator for passion, but anything she does on her own time that makes her a better programmer (not limited to programming) is also a good indicator. That includes things like reading blogs, trade magazines, and books, and attending conferences or user group meetings. If she has made a hobby out of her job, then it's clear that she's passionate about that job.
Not everyone wants great programmers.
I prefaced all of that by saying that we were assuming that everyone wants great (passionate) programmers. But we know this not to be the truth. Not all organizations believe they can afford great programmers (in which case, see paragraph 3), and still others just don't believe that programmers are close enough to their bottom line to worry about it. And if there are dispassionate programmers, then it stands to reason that there are dispassionate managers, too.
I imagine that dispassionate managers are threatened by passionate people, because passionate people change things. And passionate programmers can be particularly unruly. In these cases, there may just be a culture of dispassion. That's an unfortunate situation to be stuck in if you're passionate, and if I ever find myself stuck there I'll start looking for another job.
But she didn't apply!
What I'm proposing here is flipping the hiring process on its head. When you post a job on your company website or Monster.com, or run an add in the paper, the only people that will see it are those who are in need of work or who are looking for something better. If you're lucky, every now and then coincidence will deliver a rockstar to you via these channels, but more often than not there's a reason that people are out of work or stuck in crappy jobs.
There are a lot of people out there that would be willing to take a great opportunity if it came up and smacked them in the face, but instead your opportunity is sitting on a street corner with a dirty cardboard sign that reads, "Will food for work."
I would encourage you to seek out the rockstar that you want on your team. You never know, she might just say yes, and might even be willing to relocate to come work for you. Telecommuting is also an option, but that's a rant for another day.
I am not a hiring manager.
I realize that one of the biggest problems with this article is that there are very few hiring managers likely to see it; so I'm preaching to the choir in some ways. Short of sending it to your hiring manager, here are some ideas that can at least help you apply the idea of seeking out passionate people in your situation.
My organization is fairly large, and the interview process is quite thorough. With a few exceptions you have to interview with almost everyone you would be working with, and we usually do two rounds of in-person interviews per candidate, after phone-screening, unless it's clear that you aren't what we're looking for. Since that means I get to participate in interviews for potential coworkers and give my input to the hiring manager, I will be using that opportunity to try and find out if the person is passionate, or just doing the bare minimum; in addition to my normal questions about technical ability and personality. If you are passionate and open minded, then you can learn any language and best practices necessary to do the job.
If you're not already involved in interviewing people that you would have to work with every day, ask if you can get involved. Show an interest in selecting the best candidate, and then work hard to find the right one. As I mentioned before, you can find passionate programmers by asking them about their interest (or lack of interest) in user groups, conferences, blogs, magazines, and so on. Even if they don't contribute to open source projects, they could be passionate and flying under the radar. Sometimes you have to prod a little bit to find these things out.
Don't be afraid to say no! Think of hiring someone like buying a house. If you're going to be homeless in a week, then it's more important to get something lined up --any crappy motel room will do-- and then worry about finding the right place when you have time to do your homework. But if you aren't in dire need of someone to fill a chair and do work that is a fifth of the quality of a great programmer, then take your time. If all of the applicants suck, say so. Just be prepared to back up your claims. You wouldn't buy a house in a hurry, go through all of the settlement costs, and then realize that the roof leaks and the basement smells like dead fish... would you?
You probably can't offer anyone a job, but you can find someone that you'd love to work with and convince them to apply. That's about as close as you can get; and something I've done on a few occasions. It doesn't always work out, but I've been happy with the results so far.
Do you have any other ideas for how to affect positive change in the hiring process? I'd love to hear them.
Posted in
Meta
| 7 Responses
July 16 2010