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

WordPress: How to add custom fonts to a twenty seventeen child theme.

Quick help to those who have tried to find some help and failed (as I have so I have to write the code myself). Assuming that you have your virgin child theme configured and activated: here is a function which goes into the functions.php file (of your configured and activated child theme): function childtheme_twentyseventeen_fonts_url() { $replace_original_font = true; // unless you really like Libre Franklin if ($replace_original_font !== true) { $hyph = '-custom-'; } else { $hyph = '-'; }; $font_families = array( //add your Google fonts and weights (400 and 700 are defaults for normal and bold) here: 'Oswald:200,400,700', 'Lato:200,400,700', ); $query_args = array( 'family' => urlencode( implode( '|', $font_families ) ), 'subset' => urlencode( 'latin,latin-ext' ), ); $fonts_url = add_query_arg( $query_args, 'https://fonts.googleapis.com/css' ); wp_enqueue_style( 'twentyseventeen' ....

{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...

Have to do something about something

I recently realized, that I haven't been doing any 3D work for month now. I also noticed, that the last movie I made, wasn't all that exciting of a project. For some reason my interests shifted - again - to another area, which is, in turn, split between standard-based web design, and making music with GarageBand. May be, I should concentrate on something; just may be. May be, I will achieve some sort of recognizable and reputable state in that area, whatever that area would be. May be, people will refer to me as an authority on some obscure subject, like cross-browser implementation of unordered lists, or making Apple-compatible loops, I will become famous, and will receive an incredible job offer (this last statement is about as realistic, as me winning a lottery, considering that I never play). Somebody just sent an email to my wife, asking if she still gives art lessons. I couldn't help noticing custom domain name in the email address, so I checked it out: very decent ...