Published
August 26th, 2008I am very excited to announce that my second article has been published in “Coastal Christian Family”. The first one was about Podcasts and this one is about Blogs. It seems relevant to post on my blog that I wrote an article about … “blogs”.
RegEx Tester
August 20th, 2008I have been working with Regular Expressions lately and this site is SO handy for testing your expressions quickly.
Gotta love it.
Google Indexing
July 17th, 2008Love this blog entry:
googlewebmastercentral.blogspot.com/2008/06/improved-flash-indexing.html
It sort of feels like, “finally”. I have had to justify to clients why Flash is not going to get them the sort of search results they want, even though it will have aesthetics for those that are already there. And now, we can have both worlds. I still think text is going to work out better for menus and links because of its minimal bandwidth and accessibility options -but for those things that just serve us better as flash - its nice to know that they will be visible to the engines too. At least, one engine.
FTP Script and Bulk Uploads from the Command Line
June 1st, 2008Several years ago, this KB article would have been very handy. I needed it again today, so here it is:
Software Engineer Interviewing
May 6th, 2008I love this article…
http://www.joelonsoftware.com/articles/GuerrillaInterviewing3.html
the more you write, the more you get published
April 24th, 2008Not a very clever title. Certainly, to be published more I will need better hooks. But I’ll work up to that. For now, I am very excited that a local publication will be printing my articles about religion and websites/technology. I have felt for a long time that in order to market vertically, I needed to prove my expertise by being published. And, although the compilation of these writings may be book worthy some day, for now, the subject just doesn’t contain enough content to warrant a book. So monthly articles will certainly do. And we have so much success building church websites that we feel it is wise to exploit that fact and grow our name in that community. Just like Amy Grant and Reliant-K, we aren’t restricting ourselves to the Christian realm, that is not part of our business model. But we are certainly excited to market to that audience. And since we do not take on projects that are morally ambiguous, we are a solid vendor for those clients. We’ll see how it works out. And I’ll refer you to those articles as they come online.
postmasters, blacklists and commercial emailers
April 10th, 2008
Recently sent this to a client regarding email applications…
-
Blacklisted? Not sure? Check http://www.mxtoolbox.com/blacklists.aspx
and enter IP Address - Spamcop got you down? Not sure? Check http://www.spamcop.net/bl.shtml
and enter IP Address -
For gobs of information (and to signup to be in the feedback loop) -
visit http://postmaster.aol.com. The whole site has a lot of useful
information. Being in the feedback loop will allow them to notify you if
a user puts your email in the junk mail. This way you can unsubscribe the
customer, instead of risking being blacklisted. - Yahoo! wants to be your friend. How can you be their friend? Visit
http://help.yahoo.com/l/us/yahoo/mail/postmaster/postmaster-15.html -
Finally, here is a legal blurb about commercial email systems:
http://www.ftc.gov/bcp/conline/pubs/buspubs/canspam.shtm
doctype, a predictable problem
January 28th, 2008I don’t want to sound condescending, but it was something that was bound to come up. I ran into it working with the Tactical Sensor Model (also called the Common Sensor Model, and finally, Joint Sensor Model) working group. In that situation, the API needed to grow as the abilities and capabilities of the Sensors (and their Models) improved. And how do you progress an API (or in this case, specific Standards) and maintain backwards compatibility? Some people who are smarter than me are working on it which is good but I can tell you that we never came up with a solution that satisfied everyone. In this case, if I were developing a browser, I would NOT be interested in handling version cases for rendering a page. It means that the engine will grow and grow and grow and although there won’t be alot to maintain because each version will build on the last and once a version is released, its not going to get modified but what about NEW browsers? Really, they are going to test each version’s engine and move forward? So basically, if you are not in the browser market now, you will have a huge-uphill battle if this goes through. Ick, its a nightmare and its easy from the server side of the problem to sit back and go, “You, client-side people REALLY have your work cut out for you”. If that is the case, I hope the open-source community likes testing (as opposed to developing) because that is going to be where time gets spent.
The alternative isn’t pleasant either, what with all kinds of progress moving forward with standards AND browsers. It isn’t an easy puzzle to solve. Good luck. To everyone.
Leroy is a Zend PHP Certified Engineer from Crestview FL. He has been computing nearly two decades, drag-racing for 12 years and spent a year with a band as a guitarist
