Symptoms of a Certified Single/Taken

Got this from Istorya:

Symptoms of a CERTIFIED SINGLE:

• Mahilig kumain.

• Panalo ang social life. Alam lahat ng gimikan at mall sale.

• Hayok sa tulog.

• Gadget-addict.

• Sa cellphone, group message nang group message ng quotes.

• Ngumingiti kahit nag-iisa.

• Tumataba.

• Porma to the max.

• Mukhang happy kahit hindi naman talaga.

Symptoms of CERTIFIED TAKEN:

• Walang pera.

• Mukhang ngarag at laspag.

• Kuripot.

• Blooming, kasi, kailangan para hindi iwan.

• Walang social life kundi dyowa niya.

• Boring kausap.

ScribeFire; Rough Day

Well, I'm suppose to blog about this yesterday, but I was bombarded with multiple tasks so I wasn't able to browse any other links aside from my localhost, staging site of the project I'm currently doing, and the storefront manual. Having a chance today, I grab it quickly.

So what is ScribeFire? I'm actually trying it out right now. I'm using this Firefox addon to post this blog (well, later, since I'm still writing this entry. hehehe). ScribeFire Blog Editor is a Firefox addon that helps us update our blog easily. Well, that says it all. After installation, Firefox restarts, and open a new tab about instructions on getting started with this feature. Looks easy, so I'm trying it now. I wonder what will happen after I press Publish. hehehe

Anyway, so I have a rough day yesterday. As aforementioned, I was bombarded with multiple tasks. Added to that, a conference chat with a project. Well, it didn't end well. Our RSCO and my iBoss had a "misunderstanding". That's how our RSCO called that, a "misunderstanding". So I assume I also "misunderstood" their intentions. Anyway, so the ending was, we, the developers, were left dumbfounded and didn't know what to do next. In the other window, my colleague pm'ed me, asking "Unsa daw to???" (What was it, again?). I just replied, "Ambot ana nila." (I don't know about them). And aside from that ending, the conference ended up as if our RSCO is a little child who wasn't able to get what he wanted.

So there, I was so stressed out with just that. My mind was so filled up with that problem because they're going to hand the project over to me, and I don't know a thing. My mind was so occupied that I didn't realize I was already pushing myself to the limit of doing the tasks that was given to me at the beginning of the day. In the end, around 7pm, I was having an abdomenal pain (if that's what they call it). I mean, my uterus was already aching. So right after I uploaded my work for yesterday, I immediately turned off my pc, and went home.

I needed rest. And something to divert my attention from the stress in the office. I was thinking, if my son was just by my side, I won't have any problems diverting. Anyway, I had a hard time trying to sleep. I can't sleep because of anger. *sigh

FTP Upload in C# .NET

This is my first time to post a code. Well, I'm just so happy that if finally worked after a series of errors. So I want to share this code taken from a reference (ASP Alliance). We can find a lot of similar codes but I chose this reference because this was my starting point (recommended by my Project Manager).

private string ftpUsername; //username
private string ftpPassword; //password

private void UploadImage(string filename)
{
FileInfo fileInf = new FileInfo(filename);
string uri = "ftp://" + ftpAddress + "/" + fileInf.Name;
FtpWebRequest reqFTP;

reqFTP = (FtpWebRequest)FtpWebRequest.Create(new Uri("ftp://" + ftpAddress + "/" + fileInf.Name));
reqFTP.Credentials = new NetworkCredential(ftpUsername, ftpPassword);
reqFTP.Timeout = 1000000000; //set to very high value
reqFTP.KeepAlive = false;
reqFTP.ReadWriteTimeout = 1000000000; //set to very high value
reqFTP.Method = WebRequestMethods.Ftp.UploadFile;
reqFTP.UseBinary = true;
reqFTP.UsePassive = false; //my own addition
reqFTP.ContentLength = fileInf.Length;
int buffLength = 2048; //set to 2kb
byte[] buff = new byte[buffLength];
int contentLen;

FileStream fs = fileInf.OpenRead();

try
{
Stream strm = reqFTP.GetRequestStream();
contentLen = fs.Read(buff, 0, buffLength);
while (contentLen != 0)
{
strm.Write(buff, 0, contentLen);
contentLen = fs.Read(buff, 0, buffLength);
}
strm.Close();
fs.Close();
}
catch (Exception ex) {
throw new ApplicationException(ex.Message);
}
}

So there it is. I added some modifications like reqFTP.UsePassive = false; since I kept getting a "227" error. Found a forum that answers the same error, and suggested to include the said code. And after that, all worked perfectly. Kudos!

Codes in Post; It's July!!!

First off, I want to share this funny thing about cross-posting. I enabled my cross-posting in multiply, so that whenever I post a new entry here in blogger, it will automatically be added up in my multiply account. Well, it all went well until my prior post "Why do boys fall in love with girls".

I enclosed the article in a block quote here in blogger. The publish post, as usual. But later in the afternoon, my hubby pm'ed me, said that my post looks funny. I checked my post in blogger, but didn't see anything wrong. I assumed it would be the same with my multiply blog, since I've been blogging for a while now. Besides, I can't check my multiply blog since it's URL is blocked here in the office. So I asked my hubby, what's wrong with my post?

Then he replied, I included a series of codes after each item in the article. I asked again, where? Then he checked my blogger account, and said, the funny codes don't show here in blogger. I was curious so I checked my multiply account, and there it is, a series of codes, as he described them. hehehe...anyway, I didn't make any changes on the post anymore. It's for my readers to understand it's not part of the original post. hehehe

Second is, it's July! Weeeeeeeeee...my month. hehehe. It's still July 1, but I'm already excited about what will happen at the end of the month. For one, my hubby's coming home. And next, I'm turning 23. I'm getting older. But it doesn't matter, I still feel young. hehehe.

So my official countdown has started. I'm really really excited, I don't understand why. Anyway, I'm really looking forward for July 30. =P