Posts in this welcome thread are not eligible for the drawing. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I'd like to personally thank Pragmatic for being party to both our server upgrades/moves over the past two years. Not expecting problems with the forum this time, but I really appreciate your patience during the last one.
Kun All wrote:The name of the book itself attracted my attention.
I'm glad to hear it. Naming the book was one of the hardest parts, but I knew I wanted the word "love" in the title, as you'll see below.
The book came about for two reasons. First, I'd been interviewing programmers for years, and I'd seen far too many come through my office and interview terribly. They'd sit quietly and just answer questions, without having any passion for their work. They'd be unable to translate their technical work into the language the business speaks: Time and money. It seemed like many just came through, winging it as they went.
Second, I'd talked to so many of my friends and colleagues in technical jobs and industries who were unhappy with their jobs. I heard complaints that their jobs were boring, or they felt unappreciated, or they hated the kind of work they were doing. Nobody complained about money, because that was an easy benchmark to work on. Happiness was something else. I loved the job I was in, and I believe that everyone can and should love what they do. Life is too short to spend working in a crappy job.
I looked at the books available at my bookstores and on Amazon, and I noticed that very few were aimed at techies. These authors cast a wide net across anyone looking for a job, but I knew techies had a higher hurdle to clear when job hunting because other techies are fierce competition. Worse, the technical books seemed to be crib sheets as if studying for a test, giving answers to memorize. What a terrible way to prepare for an interview!
I pulled it all together to write the book that I would want to read myself. I wanted it to be direct talk, without fluff. I wanted it to be specifically for techies. And I wanted it to include some of the funny horror stories from real people that I couldn't have made up if I tried.
It's a guidebook, but it's not recipes. There's no appendix of "sample resumes", because you can get those anywhere. Instead, I talk about the parts of the resume you may want to put in, and leave the specifics up to you, because your situation is different than anyone else's. There is no right or wrong way to do a resume. In fact, the idea of having "a resume" is wrong in itself. You send out a different resume every time, tailored to the job you're pursuing. We're all smart, we all work in the brainwork industry, so why do we turn off our brains and expect easy pat answers when looking for a job?
Finally, I talk a lot about communications and relationships during the process. Too often I see techies who seem to treat the interviewing process as a game, or a puzzle to be defeated, with the interviewer as a defender of a prize. That's 100% wrong. Instead, think of the interview as the first day on the job, and you're going to a business meeting with your boss-to-be. Reframing the process in this way puts you far above everyone else. It helps you prepare by learning to think like the hiring manager, and considering her needs and those of the company.
I'm hoping that it answers a need, especially coming out as it does during this rotten financial situation. The competition is higher, and if you're not applying these ideas to finding a job, chances are you'll lose the next gig to someone who is.
Hello Andy and welcome !
I don't usually enter here ! but the title of this book glued to me not expensive to buy too !
(offcaurse i would like a free copy) but dont mind buying it
what i would like to know about your book is !
Can this book Cover situations in other places except US or UK !
Here in Greece lots Are un Organized and some companies do not work with Standards !
can this book be helpfull In a NON US or NON UK Country ?
Time is relative so there is no way i can be late.
Joined: Jun 03, 2009
peter kosmas wrote:can this book be helpfull In a NON US or NON UK Country ?
I tried to keep everything country-neutral, but there may be differences between the US and Greece, I'm sure.
That said, it's as much a book about attitude and finding your own direction and working your own enthusiasm as anything else. The ideas about translating your programming skills into business value translate to any company in any country.
Joined: Aug 26, 2008
That is true and Correct !
That is what i need i supose !
Good work i allways was looking a such kind of book ! i purchased the Rapid Development book for that job but
it was mostly for managers not for employes ! !
Now i supose i can get this Book to know how to act when i meet
1. Stupid Managers
2. Bad Team Members
3. Un organized people !
4. People that don't want to help you !
Attitude is a very difficult part when Working with people !
I'check for it on Amazon The price is very acceptable!
The book title aroused my curiosity to find out more about the book. The contents and editorial reviews increased my inquisitiveness. I have seen many people (including me) who are really good in writing code and executing projects but may not succeed a techie interview.
[please ask question in a separate topic]
Joined: Jun 03, 2009
sanker san wrote:Could you please comment about the role of technical certifications in a job interview?
It all depends on what the hiring company wants. Some companies find certifications to be very important, and some think they're not worth the paper they're printed on.
I'm not sure how they'd relate to an interview, though.