Thursday, June 22, 2006
No peaches for me
The Atlanta job didn't happen. I was not the perfect fit for the project they needed to fill, so they went outside the company and hired an outsourcing company for the duration of the project. However, they really really liked me and was trying to find some way to bring me onboard.
What they decided to do is try to create a contract-to-hire position where I'd work 3 months and then become permanent. Seems the hiring manager fought for me all week, but HR said there just wasn't any place in the budget for this position.
So no Atlanta. I was told that when another position opened I would be the first person on their list. They are expecting to double the size of their department, and I just need to wait.
I am about to exhaust my job opportunities, to be honest. If Minneapolis doesn't work out I will be screwed.
-Mizike-
What they decided to do is try to create a contract-to-hire position where I'd work 3 months and then become permanent. Seems the hiring manager fought for me all week, but HR said there just wasn't any place in the budget for this position.
So no Atlanta. I was told that when another position opened I would be the first person on their list. They are expecting to double the size of their department, and I just need to wait.
I am about to exhaust my job opportunities, to be honest. If Minneapolis doesn't work out I will be screwed.
-Mizike-
Digital Dreams fading away
I am one of those who gave up using his 35mm camera for a new fangled digital one. Digital images can last forever, yes? Seems that's not always the case.
Here's an article on the life expectancy of burned CDs and DVDs. Unless you want to invest in the gold ones, it isn't looking too good.
-Mizike-
Here's an article on the life expectancy of burned CDs and DVDs. Unless you want to invest in the gold ones, it isn't looking too good.
-Mizike-
Burning for the long haul
June 15, 2006
Terry Lane looks at the vexed question of how to store your images.
The black curse of the 21st century has fallen on the house of Imaging. We have a compact disc on which we have recorded pictures and documents - the only copies, naturally - that will not yield up its contents.
We have forked out real American dollars for software that promises to shake loose the information contained on any reluctant disc. Money wasted.
We have handed the disc over to experts who have laughed and promised to restore our files in a nonce, no worries mate. Nothing.
All of which sent a cold shiver down the spine. We have image files stored on 22 CDs and one DVD and this led us to wonder just how long they will be accessible. How long will a homemade CD or DVD last?
Not long, according to Herr Kurt Gerecke, IBM expert on data storage. Mr Gerecke told the magazine PC World that two years is about the average life expectancy of a burned disc, and if you keep it in a dark, cool place it might last for five.
Not very reassuring.
Gerecke says the burned disc has a short lifespan compared with a commercially pressed disc, which fits with our observation. We have compact discs bought on CD Day One in 1983 that are still perfect. On the other hand, we have had DVDs give up the ghost in less than a year.
Discs seem to be another of those consumables that obey the inexorable law of capitalism: You get what you pay for. The el-cheapo discs look attractive but they won't last. The pricier brand-name discs do better but only by five years.
The next big thing in optical writeable discs is Blu-ray, which is not yet available, but even that must be seen as an interim medium between non-volatile memory on revolving discs and memory on solid-state devices similar to camera memory cards or memory sticks. Samsung has announced a notebook with 32GB of flash memory and no rotating hard drive. That's the future. So perhaps all we need is five years of optical storage to tide us over.
If you're worried, it might be worth looking into the Delkin eFilm Gold CD and DVD blanks. These promise a life of 100 years for the DVDs and 300 for the CDs. Their longevity is attributed to the use of gold in the reflective layer of the disc, according to the Australian distributors, Baltronics. Gold is supposed to be impervious to temperature and humidity and therefore resistant to oxidation.
Given the claims made for the Delkin discs they're not that expensive - $1.72 for a CD and $3.50 for a DVD. They are cheaper in bulk and can be ordered from http://www.photo-accessories.com.au
Prints on paper are still the medium most likely to survive in the shoe box. But before investing in a photo ink-jet printer it pays to check the Wilhelm Research webpage (http://www.wilhelm-research.com) for the most recent longevity test results.
The superb Epson 2400 printer - or any of the Epson range that uses pigment rather than dye inks - rates highly for life expectancy. Keep your Epson prints in an album or a box and, depending on the paper used, the pictures will still be there in 200 years' time.
Preliminary tests on the forthcoming Canon pigment ink printer show that colour prints will be in good order in 100 years' time and monochrome prints even longer.
Pigment inks do not produce prints with the same resolution, colour range and snap as dye inks but the dye-based medium fades faster.
The moral of the story is that digital images might not be as ephemeral as once we feared.
Tuesday, June 20, 2006
How to Write a Killer Resume (for Software Engineers)
Another great article by Niniane Wang! Enjoy!
-Mizike-
How to Write a Killer Resume (for Software Engineers)
by Niniane Wang
May 23, 2005 (edited June 2006)
In the past few years working as a software engineer for Google (and previously a dev lead at Microsoft), I've screened hundreds of resumes, to make the decision on whether to proceed with the interview process. Some resumes gave off a great impression, and others didn't.
Increasingly, friends and relatives ask me for suggestions on improving their resumes, so I've created a a list of the most common pitfalls I've seen, and how to avoid them:
1. Include technical details of your work: programming language, your individual contribution, metrics. Sometimes I see job descriptions that contain a single line, such as:
* Worked with a team of 3 on an e-mail plugin.
The screener is reading your resume with the mindset of judging 1. how challenging this work was, 2. how relevant it is to their own company, so you need to be specific. A better way to rewrite this is:
* Implemented in C++ an Outlook e-mail plugin which performs automatic
backups. Along with two other team members who wrote the backup storage
server, shipped the product to 300,000 customers.
2. Don't dilute the impressive details with unimpressive ones. If you write too much fluff, it will drag down the overall quality of your resume. You don't need to say "The task was completed on time and met the original specifications." The reader assumes this, and writing a non-achievement as though it were an achievement weakens your resume.
Sometimes I will see a list of bullet points:
Intern, XYZ Corporation
* Optimized subroutines to improve performance of the ABC widget by 20%.
* Implemented in C++ the frontend to the ABC widget.
* Filed papers and did office administrative work.
If the last point is not as strong as the first two, leave it off. It is okay to have only one bullet point.
3. Showcase your work using facts, not adjectives. The screener wants to judge for themselves how impressive your work is, so use metrics, awards (external or internal to the company), press quotes, revenue growth, and other measurable items, instead of subjective descriptions. This also allows you to hype yourself without coming across as arrogant.
Instead of saying "Developed amazing results rapidly", rewrite it as "Increased application performance by 25% after 3 weeks of work." Instead of "I am regularly called in to save projects where others have failed," say, "I have stepped in on 3 projects that were running behind schedule and shipped them on-time."
Also, don't exaggerate in a ridiculous way, like the following:
Achieved cross-group coordination by organizing an ice cream social.
4. Include all relevant impressive details (awards, pet projects). I have a friend Melody (name changed) that I've known for 10 years. She developed a product that earned her company XXX million dollars, received several industry awards, and became one of her company's flagship products. Even I went to Shanghai, the highways there were lined with billboards advertising her product. Yet when I saw her resume, it said simply:
* Lead engineer on a product which performs X for enterprise solutions.
Include the awards and accolades you have received!
If you've done projects in your spare time that are technically challenging, or that have a sizeable user base (in the hundreds), include those on your resume.
5. Don't lie. This should be obvious, but I've served multiple times on hiring committees where the cover letters says, "Rewrote XYZ Corporation's e-commerce backend." and a member of the hiring committee says, "I worked at XYZ and the candidate didn't do that!"
This was usually sufficient reason to reject the candidate.
--------------------------------------------------------------------------------
Good luck in writing your resume! It's a challenging task, but can be fulfilling.
For an example resume, you can take a look at my own resume.
In closing, I'll name a few of my favorite resume highlights...
One candidate used the word "ass" in the first sentence of his cover letter. (Risky, but he pulled it off! "Does Google need a strong engineer to put boot in ass in developing the next XXX ...")
One candidate's cover letter said, "I don't have time to write a cover letter. I need to go out to party and meet girls." (Risky, and he didn't pull it off!)
One candidate wrote "Proved P=NP." When I interviewed him, he said "For the case where N equals 1."
-Mizike-
How to Write a Killer Resume (for Software Engineers)
by Niniane Wang
May 23, 2005 (edited June 2006)
In the past few years working as a software engineer for Google (and previously a dev lead at Microsoft), I've screened hundreds of resumes, to make the decision on whether to proceed with the interview process. Some resumes gave off a great impression, and others didn't.
Increasingly, friends and relatives ask me for suggestions on improving their resumes, so I've created a a list of the most common pitfalls I've seen, and how to avoid them:
1. Include technical details of your work: programming language, your individual contribution, metrics. Sometimes I see job descriptions that contain a single line, such as:
* Worked with a team of 3 on an e-mail plugin.
The screener is reading your resume with the mindset of judging 1. how challenging this work was, 2. how relevant it is to their own company, so you need to be specific. A better way to rewrite this is:
* Implemented in C++ an Outlook e-mail plugin which performs automatic
backups. Along with two other team members who wrote the backup storage
server, shipped the product to 300,000 customers.
2. Don't dilute the impressive details with unimpressive ones. If you write too much fluff, it will drag down the overall quality of your resume. You don't need to say "The task was completed on time and met the original specifications." The reader assumes this, and writing a non-achievement as though it were an achievement weakens your resume.
Sometimes I will see a list of bullet points:
Intern, XYZ Corporation
* Optimized subroutines to improve performance of the ABC widget by 20%.
* Implemented in C++ the frontend to the ABC widget.
* Filed papers and did office administrative work.
If the last point is not as strong as the first two, leave it off. It is okay to have only one bullet point.
3. Showcase your work using facts, not adjectives. The screener wants to judge for themselves how impressive your work is, so use metrics, awards (external or internal to the company), press quotes, revenue growth, and other measurable items, instead of subjective descriptions. This also allows you to hype yourself without coming across as arrogant.
Instead of saying "Developed amazing results rapidly", rewrite it as "Increased application performance by 25% after 3 weeks of work." Instead of "I am regularly called in to save projects where others have failed," say, "I have stepped in on 3 projects that were running behind schedule and shipped them on-time."
Also, don't exaggerate in a ridiculous way, like the following:
Achieved cross-group coordination by organizing an ice cream social.
4. Include all relevant impressive details (awards, pet projects). I have a friend Melody (name changed) that I've known for 10 years. She developed a product that earned her company XXX million dollars, received several industry awards, and became one of her company's flagship products. Even I went to Shanghai, the highways there were lined with billboards advertising her product. Yet when I saw her resume, it said simply:
* Lead engineer on a product which performs X for enterprise solutions.
Include the awards and accolades you have received!
If you've done projects in your spare time that are technically challenging, or that have a sizeable user base (in the hundreds), include those on your resume.
5. Don't lie. This should be obvious, but I've served multiple times on hiring committees where the cover letters says, "Rewrote XYZ Corporation's e-commerce backend." and a member of the hiring committee says, "I worked at XYZ and the candidate didn't do that!"
This was usually sufficient reason to reject the candidate.
--------------------------------------------------------------------------------
Good luck in writing your resume! It's a challenging task, but can be fulfilling.
For an example resume, you can take a look at my own resume.
In closing, I'll name a few of my favorite resume highlights...
One candidate used the word "ass" in the first sentence of his cover letter. (Risky, but he pulled it off! "Does Google need a strong engineer to put boot in ass in developing the next XXX ...")
One candidate's cover letter said, "I don't have time to write a cover letter. I need to go out to party and meet girls." (Risky, and he didn't pull it off!)
One candidate wrote "Proved P=NP." When I interviewed him, he said "For the case where N equals 1."
Preparing For a Software Engineering Interview
I must say I am loving Digg. Here is a great article that is specific to a Software Engineering Interview, but can be used as a good prep for any IT interview.
-Mizike-
Preparing For a Software Engineering Interview
by Niniane Wang, June 2006
You've used your killer resume to land an interview with a great company. Now how should you go about preparing?
Of the 300+ software engineers I interviewed for Google (and previously Microsoft), some of them really shone, and others seemed ill-prepared. Many of the ill-prepared ones still got offers because they're obviously stars, but it's safer and less stressful to prepare yourself beforehand. Below are some tips that I've gathered over time:
A final story
I'd like to leave you with a story of an unfortunate interview. Draw hope that no matter how your interview goes, you will likely be more lucky than this candidate.
At Microsoft, we always offered drinks to our candidates, and one candidate "Jeff" took a pepsi. We got into my office, and he set it down on the desk. We started discussing his experiences and then launched into the whiteboard coding question, and he didn't get around to opening his pepsi.
We stood at the whiteboard, and Jeff started to write a line of code. He stopped to think about the overall algorithm, and absentmindedly took a step back in order to see the entire whiteboard. In doing so, he inadvertently knocked against the desk, and the pepsi fell off the edge.
This pepsi was still unopened. Thus, when it hit the ground, it exploded on impact.
Pepsi sprayed in foamy gusts in all directions from the can. It was a slow-motion moment as beige spots of soda splashed onto my white walls, my bookshelf, my keyboard. We both stood there frozen, our hands halfway out (too slow to catch the pepsi), looking at the dripping liquid coating the entire inside of my office.
We took a 5-minute break to get paper towels and mop up the mess. (Though my books always stuck together after that day, and my walls were never the same again.)
We then returned to the whiteboard question. Jeff was nervous by this time (do you blame him?). He wrote some code, erased it, wrote more. He erased using his fingers against the board instead of using the eraser. Then sweat formed on his forehead, and he wiped it off using the same hand. By the end of the interview, his face was covered in streaks of red, green, and blue whiteboard marker.
I said, "I think you have some marker on your hands. I'll show you the restroom." and let the bathroom mirror show him the problem.
-Mizike-
Preparing For a Software Engineering Interview
by Niniane Wang, June 2006
You've used your killer resume to land an interview with a great company. Now how should you go about preparing?
Of the 300+ software engineers I interviewed for Google (and previously Microsoft), some of them really shone, and others seemed ill-prepared. Many of the ill-prepared ones still got offers because they're obviously stars, but it's safer and less stressful to prepare yourself beforehand. Below are some tips that I've gathered over time:
1. Practice using the same medium (e.g. paper and pencil) and time limits (e.g. 30 minutes) as the real interview.
Google and Microsoft both use whiteboard coding questions, yet often candidates practice by coding alone at home on a computer with a compiler. During the actual interview, they stand at the whiteboard and forget how to initialize an array, without their trusty syntax highlighter. Or they are so nervous having another person watch them that they panic and can't think straight.
In real life, if you plan to swim the English Channel, would you limit your practice to laps at the local swimming pool? No, you would go test out the ocean waves, the salt water. Do the same here.
Ask your recruiter the format of the interview and any coding questions. If the company gives the candidates an hour alone in a room with an editor and no compiler, practice that at home. If the company does whiteboard questions with an interviewer watching you, ask an engineer friend to be your mock interviewer. It's fine if the friend is a less experienced engineer than you -- they'll still bring out your nervousness about making mistakes in front of others, so you can practice getting used to that.
If you know me in real life and want me to do a mock interview for you, my going rate is dinner at Fuki Sushi if you're in industry, or at Pizza My Heart if you're a strapped-for-money student.
During the interview, don't obsess over little mistakes that happen.
On more than one occasion, when I gave a star candidate a coding question, he zeroed in on the most optimally performant solution, identified the boundary cases, and began writing well-designed code. Midway through the problem, he makes a little error -- getting the order of operations wrong on the first try, or having an off-by-1 error, or forgetting to declare a variable.
When I point it out, the candidate responds with horror and then becomes so nervous that it impacts his performance during the rest of the interview.
The fear is unfounded. An awesome candidate making a little error is like a concert violinist playing a challenging Brahms concerto and hitting two wrong notes. Sure, the audience could tell that he made mistakes, but they don't get confused as to whether he's actually at Twinkle-Twinkle-Little-Star level.
Even if you completely bomb one question, many interviewers ask you multiple questions and will forgive a single mishap. Even bombing an entire interview is recoverable if the other interviews go well.
Recently one of my coworkers (a tech lead for another project) interviewed a candidate and was very curt because he found the candidate's communication style irritating. The candidate proved himself during the interview, and the tech lead ended up being the strongest proponent for this candidate. He advocated harder for that candidate than he has for anyone else in a year.
When things don't go well, just keep at it and don't give up hope.
2. Don't be rude to your interviewer.
This should be obvious, but I have been surprised. One engineering candidate said to me, "Wow, I can't believe you're really my interviewer! You look so young!! I thought you were 18! Once you told me your credentials, I understand now, but at first I thought, 'This person is interviewing me?!?!'"
That wasn't so smart.
Other things that I recommend against saying:
"Wow, you're really my interviewer? You look so old!"
"Wow, you're really my interviewer? You look so fat!"
Another time, the candidate's cell phone rang 15 minutes into the interview. She let it go, and we were both distracted by it ringing for the next 20 seconds. 5 minutes later, it happened again. Another 5 minutes later, it rang for a third time.
She finally reached for her purse and fumbled inside it for the phone. "It's about time", I thought, "she should've turned it off before coming in here." She dug the phone out of the purse and then proceeded to take the phone call right there in the middle of the interview.
The only justification is if there is a family emergency, and in that case, warn your interviewer explicitly at the start of the interview.
3. Don't hijack the interview.
I've had a couple of candidates who came into the interview with the mindset that they MUST tell me all about their recent project Zoolander. I start the interview and they break in with, "I want to tell you about Zoolander. 10 years ago, this project started as a side feature..." and then go on for 5 minutes without taking a breath.
Sometimes they decide that they must tell every interviewer about Zoolander, repeating the same description over and over during the day.
Your interviewer has specific questions that they need to get through. If you hijack the interview, they may not have enough data from their own questions to be able to endorse your hiring. They may also think that you would be difficult to work with.
If you really want to talk about a project, ask your interviewer, "I think project Zoolander really shows off my abilities. Can you or another interviewer fit in 10 minutes for me to explain it?" The interviewer can then refit their plan for the interview, instead of suddenly having their schedule be shanghaied.
4. When answering questions expecting a specific answer, give a high-level summary first.
Sometimes I ask a question expecting a short answer, "How many people worked with you on project Zoolander?" The candidate then gives me an audiobook, "Well, there was Jimmy -- he did the UI and I had to mentor him quite a bit on it. Then there was Mary who ran the backend servers. She worked remotely from Pennsylvania. Two years later, we got another backend person David..."
Three minutes later, the candidate is still talking, and I still don't know the answer of how many people worked on the project.
Give an answer first, and then expound. "There were 3 when I joined, and 12 when I left. First there was Jimmy ..."
Better yet, give the answer and offer to expound. "There were 3 when I joined, and 12 when I left. Would you like me to tell you what each one did?"
5. (Not as important) Wear something comfortable to your interview. Business casual is the most typical.
People sometimes wonder how they should dress. The most important thing is that you feel comfortable. If you still want a recommendation, I say a button-down shirt or even a T-shirt. A suit can come off as too formal in some companies (e.g. Google).
This point is not as important, because people won't really care. They might raise an eyebrow if you come in a three-piece suit, but if you've got the goods in terms of engineering skills, it's not a dealbreaker. One candidate came to an interview wearing a gothic mesh shirt with holes through which his nipples were clearly visible. He still got the job. (I don't recommend taking this risk.)
A final story
I'd like to leave you with a story of an unfortunate interview. Draw hope that no matter how your interview goes, you will likely be more lucky than this candidate.
At Microsoft, we always offered drinks to our candidates, and one candidate "Jeff" took a pepsi. We got into my office, and he set it down on the desk. We started discussing his experiences and then launched into the whiteboard coding question, and he didn't get around to opening his pepsi.
We stood at the whiteboard, and Jeff started to write a line of code. He stopped to think about the overall algorithm, and absentmindedly took a step back in order to see the entire whiteboard. In doing so, he inadvertently knocked against the desk, and the pepsi fell off the edge.
This pepsi was still unopened. Thus, when it hit the ground, it exploded on impact.
Pepsi sprayed in foamy gusts in all directions from the can. It was a slow-motion moment as beige spots of soda splashed onto my white walls, my bookshelf, my keyboard. We both stood there frozen, our hands halfway out (too slow to catch the pepsi), looking at the dripping liquid coating the entire inside of my office.
We took a 5-minute break to get paper towels and mop up the mess. (Though my books always stuck together after that day, and my walls were never the same again.)
We then returned to the whiteboard question. Jeff was nervous by this time (do you blame him?). He wrote some code, erased it, wrote more. He erased using his fingers against the board instead of using the eraser. Then sweat formed on his forehead, and he wiped it off using the same hand. By the end of the interview, his face was covered in streaks of red, green, and blue whiteboard marker.
I said, "I think you have some marker on your hands. I'll show you the restroom." and let the bathroom mirror show him the problem.
Scientology is full of Lawyers
Seems my link to the "Scientology is not Science" site on Codebot is no longer valid. The Scientology police got to them.
Maybe if I blog about Scientology my blog readership count will go up?
To all you Scientologists, I love "Welcome Back Kotter" and "Risky Business". And I did read the entire Battlefield Earth series, although the movie blowed goats. Nothing but love to all you frea... err, friends of L. Ron.
-Mizike-
Maybe if I blog about Scientology my blog readership count will go up?
To all you Scientologists, I love "Welcome Back Kotter" and "Risky Business". And I did read the entire Battlefield Earth series, although the movie blowed goats. Nothing but love to all you frea... err, friends of L. Ron.
-Mizike-
Church of Scientology Takedown Notice
This office represents the L. Ron Hubbard Library, the owner of the copyrights to a number of scriptures and trade secrets, the founder of the Scientology religion, has issued the following notice to Verio Inc, a subsidiary of NTT Communications. The website "codebot.org" under your control registered to IP address 161.58.73.89 is in violation of federal trademark and copyright laws.
This information summary contains the details necessary for you to understand the events, background and issues of the equity and law that pertains to the Church of Scientology's fight for its property and First Amendment right of free religious exercise.
A small portion of the Church's scriptures were broadly released on said website, and made available to the general public who have not completed the prior steps of religious study and counseling. Conspiracy to disseminate Scientology's copyrighted and trade secret scriptures is a crime and will result in arrest, prosecution, conviction and imprisoned for theft. Additionally, The Church faces economic harm from what would be essentially black market trafficking in its protected works and attempts to dissuade individuals from becoming Scientologists by holding its scriptures up to derision. As a result we request you suspend the account holding this website, and place this notice up in reparation for our damages. Your prompt attention to this matter will result in no further legal action.
We appreciate your attention.
Legal Department
Church of Scientology International
6331 Hollywood Boulevard
Los Angeles, CA 90028
Phone: (323) 960 3500
Fax: (323) 960 3508
LMAO
Haha! I love this comment!
I was reading one of my regularly visited blog when I found this comment to today's post.
I was reading one of my regularly visited blog when I found this comment to today's post.
My ex-boss would not allow us to use blue post-its in notes to her, because...get ready.."blue is a boy color". The only acceptable colors were pink(for obvious reasons), yellow(reminded her of sunshine),green(one of her soriorty colors), and purple (because it reminded her of her mother), and that is just scratching the surface of craziness.
~G
Monday, June 19, 2006
Web based word processors, etc.
Here's a series of very interesting links. Hope you like them!
NYTimes article "Now, Free Ways to Do Desktop Work on the Web"
Google Labs
Zoho Writer (Online Word Processor)
Writeboards: Sharable, web-based text documents
ajaxWrite (Web based word processor)
30 Boxes (calendar, to-do lists, profiles, etc.)
Plum: Collect, Share, Connect
Create your own Wiki - Wetpaint
NYTimes article "Now, Free Ways to Do Desktop Work on the Web"
Google Labs
Zoho Writer (Online Word Processor)
Writeboards: Sharable, web-based text documents
ajaxWrite (Web based word processor)
30 Boxes (calendar, to-do lists, profiles, etc.)
Plum: Collect, Share, Connect
Create your own Wiki - Wetpaint
Put a hose in your tail pipe!
Well... it's been a while, hasn't it. I guess a few things have happened since I last wrote. To be honest, I haven't been in a blogging mood. It means I have to sit down and collect my thoughts about what has happened the past few weeks.
For the more mundane: I wasn't able to make my interview in Minneapolis on Friday. American Eagle cancelled the flights out of Jackson last Thursday evening. We are tentatively scheduling the interview for this Friday, but I haven't purchased the tickets. They want to spend the whole day with me, and I'm not really feeling all that sociable right now. I can do an afternoon, but 9:30am to 8pm? Almost 11 hours!!? ugh!
I gave up trying to find flights and drove back home. Skyprincess flew in the next morning and we had a busy weekend. I spent all morning Saturday catching up on yard work. The lawn needed mowing and the front yard needed a serious raking. Then Skyprincess took the hedge trimmer and made multiple piles of limbs I had to bring to the corner. Then I spent an hour or two digging post holes to repair the fence. I only got one side fixed before the storm hit us.
We had painters over the entire weekend and I got no real downtime to relax. Sometimes all I want to do is veg, watch a little tv and ignor the world. With midterms this week, my spare time was spent studying. We did go out Saturday night to see 'A Prairie Home Companion' and eat an expensive steak dinner. We've really got to cut back our entertainment expenses. There is really no reason to spend that much on one evening. Our spending is getting to be a big concern for me.
For the not so mundane, the person I had asked to serve as my 'best person' (since she's female) sent me an email and backed out of the wedding. To say it hurt is an understatement. I haven't had the chance to talk to them in person (they didn't answer their phone), so I really don't know the entire reason why. They gave so many different reasons that I'm not sure what to think. It puts me in a very ackward position, since it's far too late to ask someone else. Not that I had anyone else in mind to begin with.
This was going to be a not so traditional wedding, and it looks like I'll add one more to that list. I don't see replacing her in my wedding party, which means I won't have a 'best man' in the wedding. Perhaps we'll have a missing man formation wedding photo. *shrug*
Well.. that's it. I guess I'll post another blog after this one with some interesting links I found today. I hope you like them!
-Mizike-
For the more mundane: I wasn't able to make my interview in Minneapolis on Friday. American Eagle cancelled the flights out of Jackson last Thursday evening. We are tentatively scheduling the interview for this Friday, but I haven't purchased the tickets. They want to spend the whole day with me, and I'm not really feeling all that sociable right now. I can do an afternoon, but 9:30am to 8pm? Almost 11 hours!!? ugh!
I gave up trying to find flights and drove back home. Skyprincess flew in the next morning and we had a busy weekend. I spent all morning Saturday catching up on yard work. The lawn needed mowing and the front yard needed a serious raking. Then Skyprincess took the hedge trimmer and made multiple piles of limbs I had to bring to the corner. Then I spent an hour or two digging post holes to repair the fence. I only got one side fixed before the storm hit us.
We had painters over the entire weekend and I got no real downtime to relax. Sometimes all I want to do is veg, watch a little tv and ignor the world. With midterms this week, my spare time was spent studying. We did go out Saturday night to see 'A Prairie Home Companion' and eat an expensive steak dinner. We've really got to cut back our entertainment expenses. There is really no reason to spend that much on one evening. Our spending is getting to be a big concern for me.
For the not so mundane, the person I had asked to serve as my 'best person' (since she's female) sent me an email and backed out of the wedding. To say it hurt is an understatement. I haven't had the chance to talk to them in person (they didn't answer their phone), so I really don't know the entire reason why. They gave so many different reasons that I'm not sure what to think. It puts me in a very ackward position, since it's far too late to ask someone else. Not that I had anyone else in mind to begin with.
This was going to be a not so traditional wedding, and it looks like I'll add one more to that list. I don't see replacing her in my wedding party, which means I won't have a 'best man' in the wedding. Perhaps we'll have a missing man formation wedding photo. *shrug*
Well.. that's it. I guess I'll post another blog after this one with some interesting links I found today. I hope you like them!
-Mizike-
Monday, June 12, 2006
Job update
I haven't heard from Denver yet. The headhunter involved with that one knows Atlanta is my first pick.
It seems Atlanta really wants me, but is concerned about my lack of experience in the backend. So they want to hire me on a trail basis and if I meet expectations in 3 months, I'll go permanent.
We are still working out the details, but looks like I'll be going to Atlanta! I really hope it works out, I like this company very much. And Peachtree City was ranked the #8 place to live in the US by CNN!
I'm still flying to Minneapolis this Thursday to check out that company. Who knows? It might be even better?
-Mizike-
It seems Atlanta really wants me, but is concerned about my lack of experience in the backend. So they want to hire me on a trail basis and if I meet expectations in 3 months, I'll go permanent.
We are still working out the details, but looks like I'll be going to Atlanta! I really hope it works out, I like this company very much. And Peachtree City was ranked the #8 place to live in the US by CNN!
I'm still flying to Minneapolis this Thursday to check out that company. Who knows? It might be even better?
-Mizike-
Sorry =(
i want to apologize for the anemic posts lately. between the 11 to 12 hour work days, the job search, wedding plans, and now midterms and a paper due, i really haven't had time to compose any really thoughtful posts. instead i've been posting junk i've found during my daily internet breaks.
i don't see my schedule for at least the the next couple weeks. but i will try my best to give you guys something much better than boil water alerts.
as far as job hunts, i will find out today if the atlanta job will tender me an offer or pass. i hope to have the denver job's decision early this week also. i fly to minneapolis thursday night for the friday morning interview. skyprincess and i will spend time exploring cow pastures before heading back to our worksites on sunday night. right now, the minneapolis job is number 3 on my list, but that may change to number 2. i'm really hoping for the atlanta job.
i'll let you know when i know!
-mizike-
i don't see my schedule for at least the the next couple weeks. but i will try my best to give you guys something much better than boil water alerts.
as far as job hunts, i will find out today if the atlanta job will tender me an offer or pass. i hope to have the denver job's decision early this week also. i fly to minneapolis thursday night for the friday morning interview. skyprincess and i will spend time exploring cow pastures before heading back to our worksites on sunday night. right now, the minneapolis job is number 3 on my list, but that may change to number 2. i'm really hoping for the atlanta job.
i'll let you know when i know!
-mizike-
Wednesday, June 07, 2006
Typhoid Mizike
Just my luck, I'll get Typhoid.
----------------------------------------------------------------------------------

Boil Water Alert for Hinds County
Water system: City of Jackson
Effective date: 06/05/2006
-----------------------------------------------------------------------------------
The City of Jackson Water / Sewer Utilities Division has issued a precautionary boil water advisory until further notice for all customers on the City's surface water system.
An unexpected malfunction caused the O.B. Curtis Water Plant to shut down overnight, causing a temporary loss of pressure to many customers earlier today. The plant is back in operation, and pressure should begin to increase gradually throughout the afternoon and evening hours.
Until pressure is fully restored system-wide, all customers are being advised to use water for essential purposes only. Specifically, customers are asked to stop watering and sprinkling lawns for the next 48 hours. Conserving water during the next two days will enable the community to have water for health, sanitation and fire protection purposes.
The Jackson customers NOT AFFECTED by the Boil Water Notice are in the following areas:
West of Westhaven Boulevard, in addition to North Westhaven Drive, East Westhaven Drive, and South Westhaven Drive and Sunnybrook Drive; South of Interstate 20, West of Robinson Road Extension;
West of Robinson Road Extension / Suncrest Drive to Cooper Road; and
West and South of Forest Hill Road West of 1-55.
Crews will collect water samples to monitor the safety of the drinking water. It typically takes at least 24-48 hours to obtain the additional test results so it is important for customers in the affected area to continue to boil water until further notice.
When a distribution system loses pressure, contaminants can siphon back into the water. Public health officials consider any system that loses pressure contaminated until tests prove otherwise. Health officials strongly recommend that all water be boiled vigorously for one minute before it is consumed. Customers will be notified when tests show that the water is safe to drink.
Checklist for Safe Water Use
DO NOT
* Do not drink tap water while the water system is under a boil water advisory.
* Do not drink from water fountains in parks, public or private buildings that receive water from the affected system.
* Do not use ice made from water today. Freezing will not necessarily kill harmful bacteria.
* Do not use tap water to make drinks, juices, or fountain soft drinks.
DO
* Wash your dishes in boiled water, or use paper plates for the next few days.
* Wash your fruits and vegetables with boiled or bottled water since they may have been exposed to affected water from grocery store sprayers.
* Wash your hands and bathe as usual. Bathing is safe as long as no water is swallowed.
* Brush your teeth with boiled or bottled water.
* Cook with tap water if the food will be boiled for at least one minute.
AND REMEMBER:
* Properly chlorinated water in swimming pools is safe.
* Fish in aquariums are not affected.
* Bringing water to a rolling boil for one minute will inactivate all major types of harmful bacteria.
MDH Division of Water Supply: Melissa Parker, (601) 576-7518 (8am - 5pm)
Epidemiology hotline: (601) 576-7400 (24 hours)
Press Contact: Liz Sharlot or Kelly Shannon, (601) 576-7667 (8am - 5pm)
----------------------------------------------------------------------------------

Boil Water Alert for Hinds County
Water system: City of Jackson
Effective date: 06/05/2006
-----------------------------------------------------------------------------------
The City of Jackson Water / Sewer Utilities Division has issued a precautionary boil water advisory until further notice for all customers on the City's surface water system.
An unexpected malfunction caused the O.B. Curtis Water Plant to shut down overnight, causing a temporary loss of pressure to many customers earlier today. The plant is back in operation, and pressure should begin to increase gradually throughout the afternoon and evening hours.
Until pressure is fully restored system-wide, all customers are being advised to use water for essential purposes only. Specifically, customers are asked to stop watering and sprinkling lawns for the next 48 hours. Conserving water during the next two days will enable the community to have water for health, sanitation and fire protection purposes.
The Jackson customers NOT AFFECTED by the Boil Water Notice are in the following areas:
West of Westhaven Boulevard, in addition to North Westhaven Drive, East Westhaven Drive, and South Westhaven Drive and Sunnybrook Drive; South of Interstate 20, West of Robinson Road Extension;
West of Robinson Road Extension / Suncrest Drive to Cooper Road; and
West and South of Forest Hill Road West of 1-55.
Crews will collect water samples to monitor the safety of the drinking water. It typically takes at least 24-48 hours to obtain the additional test results so it is important for customers in the affected area to continue to boil water until further notice.
When a distribution system loses pressure, contaminants can siphon back into the water. Public health officials consider any system that loses pressure contaminated until tests prove otherwise. Health officials strongly recommend that all water be boiled vigorously for one minute before it is consumed. Customers will be notified when tests show that the water is safe to drink.
Checklist for Safe Water Use
DO NOT
* Do not drink tap water while the water system is under a boil water advisory.
* Do not drink from water fountains in parks, public or private buildings that receive water from the affected system.
* Do not use ice made from water today. Freezing will not necessarily kill harmful bacteria.
* Do not use tap water to make drinks, juices, or fountain soft drinks.
DO
* Wash your dishes in boiled water, or use paper plates for the next few days.
* Wash your fruits and vegetables with boiled or bottled water since they may have been exposed to affected water from grocery store sprayers.
* Wash your hands and bathe as usual. Bathing is safe as long as no water is swallowed.
* Brush your teeth with boiled or bottled water.
* Cook with tap water if the food will be boiled for at least one minute.
AND REMEMBER:
* Properly chlorinated water in swimming pools is safe.
* Fish in aquariums are not affected.
* Bringing water to a rolling boil for one minute will inactivate all major types of harmful bacteria.
MDH Division of Water Supply: Melissa Parker, (601) 576-7518 (8am - 5pm)
Epidemiology hotline: (601) 576-7400 (24 hours)
Press Contact: Liz Sharlot or Kelly Shannon, (601) 576-7667 (8am - 5pm)
Tuesday, June 06, 2006
I'm going to sue your arse!
Not that I get alot of comments on my blog, but at least this will bring peace of mind that I won't get sued over them.
Court Recognizes Site Owners Aren't Liable For Site Comments
-Mizike-
Court Recognizes Site Owners Aren't Liable For Site Comments
-Mizike-
Monday, June 05, 2006
I've been Wonkafied!
Ugh... I feel sick. I decided to buy a blueberry cobbler in the cafeteria today and ate just a few spoon fulls. It was extremely sugary and now I'm feeling sick. I don't process sugar very well. I'm starting to feel like Violet Beauregarde.
I'm not sure how my interview went on Friday. I can never judge these things. I think it went okay, but I could tell they were looking for particular answers to hypothetical situations. And I didn't give them exactly what they were looking for.
I have another on-site interview in Denver this Friday morning and am hoping to schedule the other on-site for Friday afternoon. If that works out, I'll need to catch a flight from Denver to Schofield, WI. There is a community airport I could possibly fly into. I'm awaiting word back to see if they will allow me the on-site or if they expect me to accept without visiting. If I can get the afternoon on-site in WI, Skyprincess will meet me there and we'll scope out the territory. Then drive to Minneapolis and check that area out on Saturday and Sunday.
I'm trying to schedule my other on-site for early Monday morning in Atlanta. Then fly back quickly to work. I can't afford to miss too many days, since I'm being paid by the hour.
Hopefully at least one of the four will make me an offer in the next couple weeks. It would be nice to get back to work in my chosen field.
For your enjoyment I will now give you a couple of links to click. Coming to you by way of my lunch break browsing!
The Nut Saver!
Periodic Table
Oh.. I guess that's all I saved. At least I'll post a pix of the Nut Saver in action!
-Mizike-
Gum chewing's fine when it's once in a while,
It stops you from smoking and brightens your smile
But it’s repulsive, revolting, and wrong
Chewing and chewing all day long
The way that a cow does.
I'm not sure how my interview went on Friday. I can never judge these things. I think it went okay, but I could tell they were looking for particular answers to hypothetical situations. And I didn't give them exactly what they were looking for.
I have another on-site interview in Denver this Friday morning and am hoping to schedule the other on-site for Friday afternoon. If that works out, I'll need to catch a flight from Denver to Schofield, WI. There is a community airport I could possibly fly into. I'm awaiting word back to see if they will allow me the on-site or if they expect me to accept without visiting. If I can get the afternoon on-site in WI, Skyprincess will meet me there and we'll scope out the territory. Then drive to Minneapolis and check that area out on Saturday and Sunday.
I'm trying to schedule my other on-site for early Monday morning in Atlanta. Then fly back quickly to work. I can't afford to miss too many days, since I'm being paid by the hour.
Hopefully at least one of the four will make me an offer in the next couple weeks. It would be nice to get back to work in my chosen field.
For your enjoyment I will now give you a couple of links to click. Coming to you by way of my lunch break browsing!
The Nut Saver!
Periodic Table
Oh.. I guess that's all I saved. At least I'll post a pix of the Nut Saver in action!
-Mizike-
Gum chewing's fine when it's once in a while,
It stops you from smoking and brightens your smile
But it’s repulsive, revolting, and wrong
Chewing and chewing all day long
The way that a cow does.
Thursday, June 01, 2006
Wish me luck!
I am catching a flight in a couple hours to Philly for an interview. I really hope it turns out well. Then next Friday I'll be in Denver for another interview. Of the 3 jobs pending, I would rather have either of the 2. The other place has me out in the middle of Wisconsin, 3 hours from a major airport. That will really not work out well for Skyprincess and I.
-Mizike-
-Mizike-



