Skip to main content

On Wake Up Calls - Part I

I haven't written anything for so many months, that it's almost impossible to select a starting point for this entry, and unless you are bloggin reluctantly every second you can, an entry needs one.
I could start, perhaps, at the time of our move to New York, that would be a good one: 2005, middle of June; my contract with Goodyear is over, there is nothing more to expect from Cleveland, we need to do something, and that something, according to Evelyna, is nothing less than just moving to New York. The logic was impeccable: it doesn't matter, where not to have a job, but there we will be together.
To those, who tried to rent an apartment in any of the boroughs, good luck. To those, who tried to rent an apartment without having a job, my condolences. To those, who succeeded, hats off.
I had one week, before my "current" pay stub would start to look suspicious at least. That explains (sort of), why we ended up in Crown Heights, Brooklyn, and even that was not easy.
Knowing better now than I did back then, I would, probably, rather go for the neighborhood, where there's less than three hair/nail establishments per each block, and a bit more grass to walk the dogs, but, considering the circumstances, I think, I did well. And the place is big, which is a rare case for this city.
The neighborhood is OK, too; it only seemed hostile at first. I never thought of xenophobia as of something I had, but, apparently, there is a first time for everything. Mild case, but annoying nevertheless, although perfectly explainable - there are basically two kinds of species, inhabiting this neck of the woods: the ones, who go to those beauty shops, and the ones who own them. First kind is loud, cheerful and friendly; they like parties and loud music, they congregate for no apparent reasons around landmarks of any social significance, like phone booths, Laundromats, and staircases, where their kids play all the time up until bed time, which varies from 1 to 3 AM on a weekday. The second kind is serious and busy, they always walk fast, their men wear black hats, suites and coats, their women - long skirts, flat shoes and head scarves, and they all together make it impossible to find parking on Friday night, because they are not allowed to drive after dark, for it's already Saturday in their very old world.
Needless to say, that we don't blend in really well. May be, just OK, but not really well. On the other hand, it seems to be our way of doing things.

Popular posts from this blog

Who is running MacAddict forums?

I normally hate to complain, but, being a happy subscriber to the magazine for some time now, feel like I do need to express a concern about my recent experience with MacAddict forums section of the web site. Due to some server misbehavior, I had to re-register, my old profile disappeared, while I was updating it. My new profile was assign a label "n00b" (None Of Our Business, if I am not mistaken. This is some way to welcome a new member to the MacAddict community). It could've been cute, but it isn't. And I don't think, it was intended to be: from the post of "Scott": "...using tables for layout...is for lame-ass n00bs..." I have read several more posts in the "Web Design and Development" forum, which, for some reason, was for a couple of days named "George" (the name is back to normal now; but here is how forum moderator "Gipetto" reacted when he was asked about this oddity: "...poop, it blew me away tha...

{position:fixed} in iOS 6

I stumbled upon this oddity when upgrading to iOS 6 while working on a mobile advertising project, and it took me a better part of the day to figure out what is going on: all of a sudden an element {position:fixed} stopped working in a correct manner (which is staying put, while the page is scrolling), and started "sticking" to the scrolling page, moving out of the viewport, and then just "jumping" back to the correct location after the scrolling was finished.If you scroll this page , you will see it—hint: that's the one labeled "broken"—assuming that you have a correct device/browser combination. Mine was iPhone4 and iOS 6.0 (6.0.1-6.1.3 behaves just the same). On the original page, where I first encountered the problem, all of my elements were created dynamically using JavaScript, but at the end of the day (literally) it become clear, that the glitch is in the iOS 6 CSS implementation.Here is what happens: if you have an element {position:fixed} whic...

May 1st Reboot 2016

My main site gets a facelift (about half-a-decade overdue). Due to a chronic caching issues with iPage, I have to model everything on CodePen , and then FTP files to iPage, where, for some mysterious reason, html gets updated instantly, but CSS and Javascripts marinate somewhere for at least half an hour, before starting to render, which makes it impossible to model anything in real time. Annoying. Oh, well. At least I finally got to re-doing the site. I still do not have a concept for the galleries, though, and a main navigation menu is really primitive, but the new site is HTML5, CSS3 and what not, and I am not ashamed to refer people to it anymore. Yay. P.S. Resolved the cache issue with .htaccess file: FileETag None Header unset ETag Header set Cache-Control "max-age=0, no-cache, no-store, must-revalidate" Header set Pragma "no-cache" Header set Expires "Wed, 11 Jan 1984 05:00:00 GMT"  everything now works a lot livelier. P.P.S. Why is Blo...