Saturday, April 24, 2010

Late Night Listening XXXVIII: In the Room Where Light does not Find Me

Tonight, I am immersed in the 80s. In lieu of the Groove Show on WTTS-FM, I am listening to the Saturday Night Safety Dance on Sirius/XM First Wave. They haven't played this song, but out-of-context snippets from this work certainly capture my spirit.



Work/life balance is way out of whack these days, and my desire to write for clarity has been almost nil. I have lost sight of a forward-looking narrative and have had a world of trouble regaining it or at least revising into a work that could revitalize me.

Pointing my browser back to the editor to write another post has been hampered by a false premise, that I must somehow have a grasp of what is going on before I can write about it. And as I have become mired in the fog of lessening awareness, I have been all the less moved to write on matters personal.

There is always an e-mail to answer, an IM conversation to have, a fire to fight, another coding task to wipe out. Somewhere in between there are parental tasks, bills to pay, and a whole host of other issues. Tonight I am writing because I forced myself to get the bulk of my coding tasks out of the way, and the kids are in bed.

The divorce papers were filed officially last week, one day after our 14th wedding anniversary. STBX had a recently-divorced friend complete the initial paperwork. If we complete the parenting class and get all of the settlement items worked out, our divorce will be final on the first full day of summer.

STBX has been super motivated to get the divorce moving forward because she wants to move out of her apartment when the lease is up in August and get moved into a house. I don't see how she thinks she will be able to handle the mortgage and upkeep, something she sought to get out of when she moved into the apartment, but it is her life.

The kids are doing well. My older daughter's grades have been really good thus far, but she has been having a rough patch in math with things like counting money. Her dance school has had two competitions so far, and she's been performing in two routines -- one with girls her age and a production number that runs the full gamut of ages. The production act won overall high points for their first competition.

The younger daughter has been enjoying the church-sponsored preschool co-op she changed to at the beginning of the year. They have a different instructional style from the co-op, but she seems to be really enjoying her homework. She seems to be having a harder time with not seeing me every day. There have been occasions where she calls me and cries saying she "really really misses" me. It tears my heart out to hear it.

Since STBX started her new job, I've started keeping the kids three days in a row on the weekends that I have them, which allows her to get ready to go to work on Friday mornings without having to wake up the kids.

A few embarrassing disclosures:

I haven't completed my Census form, but I did get my taxes paid on time. Federal refund was big. I owed the state money because STBX didn't do any state withholding for her unemployment benefits.

I haven't mowed the lawn at all this year, so the yard looks like a jungle. I wrote someone advertising on craigslist and got an estimate for a bunch of yardwork items that would greatly improve the situation, but he has been slow to get things going. He came over on Wednesday evening to scope out the property but then said that he wouldn't be able to get over to do the mowing until 8:30 am tomorrow, which is questionable now because we've gotten some rain. I got my first anonymous hate message in my mailbox on Friday, informing me that I would be reported to the county health department.

I haven't updated my direct deposit to reflect the child support recalculation based on STBX's child care bills. I have been writing supplemental checks to cover the difference and annotating the checks appropriately. It will be nice once this is all switched over to the state's payment system.

As for work, I'm finding myself increasingly burnt out, with some days going in wondering whether I'm going to have a job by the end of the day because I'm going to just throw up my hands and say that things are untenable and I'm quitting.

What has happened to make me so sour on my employer? The migration to management in August of last year moved me from a rather cloistered role where creation was of the greatest value to another which involved interacting with other parts of the company which have varying degrees of dysfunction.

The upper management knows something is wrong, but they haven't been able to develop the self-awareness to see how they contribute to the problem. Instead, they have sought out the corporate analog of religion, tea leaves which give them ways to explain away the problems with vague statements like "we don't communicate well enough".

Indeed the search for cosmic truth has led them to have a week-long training course on personality types back in August, another week long strategic planning session in January complete with a massive list of worksheets, an overwhelming list of followup tasks, and, most recently, a series of management meetings (two business days and counting!) based on a compulsory reading of a business book about management teams where we've allegedly figured out that no one has a clear idea of what the company is supposed to be about.

Since throwing the third VP of post-sales client relationship management off the ship back in February, the President of the company has taken on the role of managing that department. Her calendar is a wall-to-wall list of 1:1 and status meetings. She sent a company-wide e-mail a few weeks back enumerating all of the things they were doing to stem the churn of customers (which has been awful). They fell roughly into two categories -- giving away more free stuff to the customers who complain and smothering the others with tons of attention, including hand written notes.

Over in marketing, a department which has been amazingly free of accountability in the face of turmoil in sales and post-sales client relationship management, there has been an unearthing of some ugly statistics by the VP of Ops regarding just how much they skew the incentives so it's impossible for them to fall short of their targets. There is a dearth of automation, so things like lead distribution takes days. The department manager seems to think the only thing that will solve the problems is to throw more bodies at it.

A new EVP of Sales hired on at the beginning of February. I'm still trying to figure him out. One one hand he is very big on "collaborating" with other departments. He seems very hard nosed, which should bring some discipline to a department that has been adrift sans rudder since last fall. But there are some very big red flags.

For one thing, he is very resource intensive. He makes his home out on the East Coast and flies back and forth at the beginning and end of the week. For high profile leads, he will bring in three or four other people from other departments to sit in on calls or even make trips. He has brought on a large number of new reps, with more to come by mid-July. He shut down sales activity for the better part of a week in March to have sales training courses.

He is also very big on delegating tasks, which means he creates work for other departments, myself included. I've had to write more special documents for clients, and have prepared several hours of training materials for his team. He treats the Office Manager as his personal secretary, so a lot of his requests come to other people through her.

I also am not certain I can trust him. I know of anecdotes at his former employer where he had the habit of promising big ticket clients lots of custom work and then strong-arming the company into bending the roadmap to satisfy the client's whims. He has been chasing a major online travel website for three months now, sucking up lots of resources in landing them. This has included travel out to the Emerald City for him and the CEO to visit their HQ and for us to pay for three people from that company to come over and visit us on site so that they could have two full days of planning meetings with members of our team.

As for that travel site, the people we are dealing with are empire builders. They see social media as a gold mine for personal data, so they want to use a mix of e-mail and our application plus some custom development to collect all kinds of data about who drives the most revenue in their direction so that they can offer the deepest discounts. Their biggest competition, in their eyes, aren't other companies, but rather other departments within the same company.

One of the guys from the team, a meta manager with an overinflated sense of self, shared his enlightened visions of project management, his stint as a professional player of soccer overseas, his decade working for SauronSoft, and his pet dog of exquisite pedigree, traceable back to a champion. One of my coworkers, who had the horrible experience of sitting across from him at dinner during their visit, referred to him as a "douche wallow".

The CEO keeps expressing frustration that our team can't give his full wish list at full speed, going so far as to ask whether we needed to bring on contractors or offshore. So far, I have been able to hold my ground, refusing to compromise the department's history of high hiring standards. What we do develop gets done on time and with high quality. The new developer we took on in February has been doing well, taking on the bulk of server side software development for the last two sprints.

I've lost all respect for the President. At the beginning of the year, I found out that her father is among those on the company's board of advisors (translation: daddy bought me a job). She takes great pride that she majored in highly non-technical course of study -- writing of the creative sort. She's also in thick with the marketing manager cited above, with ties that date back to their hellenic affiliations in the college years. But these are small change compared to the things that really bug me.

Back when we did departmental budgets, I allocated enough money to pay raises to my team based on past payments, which are a sliding scale between 4 and 7 percent based on the quality of the effort. If you wind up on the 4 percent track, you get fired because it is a sign of zero growth. When the budgets were being reviewed, I was complimented on my restraint on spending, and I thought that would mean that my items would be honored.

I was worried at the January planning meeting when managers were told that the raise pool was 3 percent of the existing payroll. I figured that didn't apply to us, especially since we were the only department that had no form of bonus built into the compensation.

I recently had my annual review with my system engineer, who has done a great job moving our platform to the cloud, automating recovery of problems in production, and keeping costs so low that our cost of hosting the servers that serve our 400+ clients with more than three 9s of uptime is less than our company phone bill.

I recommended a nice increase, thinking that it would have a good chance of going through since I knew that both the President and CEO were worried about him leaving. In fact a couple months prior, they were so afraid that they asked me if a raise wasn't in order then.

After she read the raise request, the President wrote back telling me that the 3 percent value applied to my team, too and that it would deplete the pay for others. I wrote back strongly encouraging reconsideration of the decision, citing the fixed compensation and the fact that the overall value was less than the traditional "you're fired" value. She said she would consider it, and that circumstances might change if we managed to get outside funding this year, but no concrete improvements.

When it comes down to an issue raised by a non-technical person either inside or outside of the company, I am seldom given the benefit of the doubt, so a lot of my discussions with her start off on the defensive. After recounting many of these things with my system engineer, he said that if he were a manager and put as little trust in my work as it appears she does in mine, he would have fired me.

Moreover, because she is non-technical and unwilling to pick up much of any new knowledge in that area. If there are ever issues with her computer or one of her friends within the company, you can be sure there will be hell to pay.

In late March, I took a couple days off to spend time with my daughters when they were on spring break, and she interrupted my time off to drag me in on drama involving my IT support guy. The main gripe was that a new phone auto answer greeting wasn't live yet, even though we had made no promise that it would be. We were still awaiting the delivery of the recording from the professional voice service, and they were still within their turnaround window.

And then again when we had the high profile visitors from the Emerald City a couple weeks ago, she pulled me out of another meeting so she could rail off about the unacceptable IT conditions with said IT employee present. The infraction? She couldn't get her wireless network or ethernet to work in the conference room. The wireless issue was caused by her leaving her ethernet connection turned on after disconnecting from her docking station, and the ethernet didn't work because she didn't have the cat 5 cable fully plugged in. Still that was somehow our problem.

She wanted me to agree with her that he needed to go right then and there. I sat there listening to her throw a fit about how time was money and she was so far behind in her work and that we had a people problem. I asked her what we could do to help make the situation better, but she continued to press for him to be gone.

I told her wearily that I wouldn't make a personnel decision in the heat of the moment, so she scheduled yet another meeting at 3 pm the same day so that she could complain more about it. I talked her down to a two week performance improvement plan where she wanted no problems with the networking or her ability to connect to anything. Moreover she was refusing to authorize any more spending on IT until all the "problems" were resolved.

I wanted to quit then and there. So did the system engineer, whom the IT support guy helps out, when he heard about the whole thing. Had we all been gone, that would have meant 60 percent of the engineering team would have disappeared in a single day. Moreover, there would be no one left to keep either the internal IT infrastructure or our production servers alive.

Moreover, since something like 60,000 lines of code of the application were written by me, there would have been a huge evisceration of knowledge. That's not the kind of thing you want to happen when you're burning money at a rate of where you might have four months of cash left to live on and you're in talks with VCs. I joked to my team that it would have be the $6 million hissy fit. Shortly after that eruption, I found a blog post written a little over a year ago that seems to sum up her personality.

The IT guy sees the writing on the wall, and he's been trying to line up a new job so he can get out of there. He's in a precarious situation because he's working on lining financing on a new house, and the last thing he needs to have happen is lose a job.

As for me, I've sketched out the revisions I want to make to my resume, and I'm contemplating putting it into circulation. My Aspergic mind keeps rerunning the calculation to see whether there is any hope for the company. The one bright point in management, the VP of Ops (who is a strong ally on many fronts), is making some traction, but probably not enough to make the needed difference. He is getting more and more stuff dumped on him by the President, and he gets pulled in to play Dad in more and more squabbles between other departments.

During a 1:1 with the President, where she asked me what might need to change to reduce the burden on me so that I had more time to recruit new employees, I mentioned that the lack of desire by some team members in sales and client relationship management was generating a lot of work for me and recommended that we start encouraging them to take more of an initiative to increase their tech savvy to handle customer requests without having to continually turn to more skilled team members.

She said that wasn't going to happen with her team. I told her then we needed to get rid of them and start over and raise the hiring bar. She came back with some handwaving mumbo jumbo about how marketing and sales people, because of their personality types, would not be inclined to learn the details. The thing is, our team doesn't even think twice about taking it upon themselves to learn more about marketing and other areas that concern the other departments, but the curiosity is not reciprocal.

I guess the bottom line is that there are few islands of doers which survive in a sea of people who fail to execute or just toss things over the wall to those who can get things done. Further complicating things are that some of the people who need to go most are closely tied to the founders, either by longstanding friendship or even blood relationship, so there are critically entrenched vestiges of unassailable incompetence. At some point, there has to be a sort of Atlas Shrugged moment with in such an arrangement where the skilled people leave the whole mess behind because working harder is just an exercise in futility.

There are several things that keep me from moving on... I have been accumulating options, and I'd hate to see them go to waste. I enjoy the company of my team, and the lunches I have with them provide very stimulating conversation. There are a couple members of the product support staff that I get along well with, whom I would miss dearly. I've learned a lot about the finance of startups from the VP of Ops, and I want to help him succeed at his goals. I don't know if I could earn as much somewhere else, which is important to keep in mind when child support is a recurring obligation. I like working in the city, which is a much shorter commute than the sterile office parks on the north side.

So that's where I stand... light at the end of the tunnel on the personal front... lots of uncertainty and ambivalence on the professional front. The good thing is that I find myself much better armed with skills and experience than I was three or four years ago.

Sunday, February 21, 2010

Damn, These Videos Have Great Production Quality

I apologize for the lack of post activity in this space. I've been underwater with work and home stuff. I'll be back soon. For now, enjoy this...


New Law Would Ban Marriages Between People Who Don't Love Each Other

Monday, January 18, 2010

Schnarch's Writings Applied to the Age of Social Networking

It's been a while since I've made mention of Schnarch in this space. I saw a post over at the New York Times blog Schott's Vocab that reminded me of his writings on two-choice dilemmas.

The term being discussed was e-ttenuation, which is attributed to Raymond Tallis. The post quotes an essay by Madeleine Bunting published in the Guardian:
... faced with such an abundance of interesting choices, there is a reluctance to commit and a provisionalism which promotes grazing, keeping options open. Above all, there is a paradigm of contractualism: relationships are measured by the question “what’s in it for me?”

When I read this, I heard echoes of Passionate Marriage (p.298):
None of us wants to face our dilemma(s) and choose one option over the other. Manic attempts to "do it all" maintain our secret fantasy that we can have it all -- and never have to face our anxiety. The 1960s free-love ethic that "it's unrealistic to expect one person to meet all your needs" subtly reassures us that we can have everything we want (all we have to do is spread our needs around several people). But decisions, commitments, friendship, and integrity only become meaningful in a world of finite options.

In Constructing the Sexual Crucible, Schnarch quotes Tristam Engelhardt:
(Friendship) is also a sacrifice. Since humans are not gods or goddesses, friendship entails the abandonment of other possibilities. Humans have limited resources of energy and time. The person who has a hundred friends has none, or is a god.

Perhaps once the craze over social networking websites has subsided, we will interpret it as a period where society was seduced by the connectivity of the web into believing that friendship could be as free as love was thought to be back in the 60s.

I sense that the seeds of disillusionment with social networking sites are beginning to take root.

In late December, the New York Times published an article about high schoolers making a pact to reduce Facebook dependency.

Then word broke out about a parody site called the Web 2.0 Suicide Machine. The virality of the site is a hint that there are good number people who are ready to unplug.

Finally, Bunting's own remarks point to another issue with social networking:
It is not technology per se at fault, but how it is used, and in particular how it combines with another equally powerful phenomenon – commercialisation; the assessment that everyone and everything has a price. It is the two combined which I would argue are so corrosive to our capabilities to create and sustain relationships of depth and durability.

It's not just person-to-person relationships that are commercialized. The site itself commercializes on a relationship of its own, just as Danah Boyd writes in her blog apophenia:
Let's take this scenario for a moment. Bob trust Alice. Bob tells Alice something that he doesn't want anyone else to know and he tells her not to tell anyone. Alice tells everyone at school because she believes she can gain social stature from it. Bob is hurt and embarrassed. His trust in Alice diminishes. Bob now has two choices. He can break up with Alice, tell the world that Alice is evil, and be perpetually horribly hurt. Or he can take what he learned and manipulate Alice. Next time something bugs him, he'll tell Alice precisely because he wants everyone to know. And if he wants to guarantee that it'll spread, he'll tell her not to tell anyone.

Facebook isn't in the business of protecting Bob. Facebook is in the business of becoming Alice. Facebook is perfectly content to break Bob's trust because it knows that Bob can't totally run away from it. They're still stuck in the same school together. But, more importantly, Facebook *WANTS* Bob to twist Facebook around and tell it stuff that it'll spread to everyone. And it's fine if Bob stops telling Facebook the most intimate stuff, as long as Bob keeps telling Facebook stuff that it can use to gain social stature.

Why? No one makes money off of creating private communities in an era of "free." It's in Facebook's economic interest to force people into being public, even if a few people break up with Facebook in the process.

Perhaps this exploitation of relationships will be what drags the collective consciousness into the crucible.

The shrinking number of active bloggers that once were counted among my unspoken social graph is also evidence of this fatigue. It's hard at times for me to imagine just how many posts I read and wrote during 2006 and 2007. Now I can go for days and weeks without corresponding with these erstwhile net friends, perhaps validating just how easily friendships can dissolve online.

Still, I don't think the friends I made writing here could be discarded purely as shallow. Indeed, the conversations we had online were deeper than what is usually found on a Facebook wall. We were struggling with big questions on our relationships, perhaps things that we weren't ready to share with friends in our real lives. As for me, it was more of a testament about the lack of depth in my real-life friendships, which I let subside horribly during the deterioration of my marriage.

What matters now is that I continue to work on building real life friendships where I can be my authentic self, finally accepting that by living in the real, I must let go of the promise of many for the rewards of deeper, and fewer, friendships.

Sunday, January 10, 2010

Late Night Listening XXXVII: Darker Days

One of the things I love about my Friday and Saturday night radio shows is that they introduce me to so many new things. I heard this gem from Widespread Panic on WTTS-FM's Groove Show.

This song does a good job of capturing the mood I've been in since I went back to work. Somber, drained, yet hopeful that lighter days will return.

Dark day program – pen to page
Nothing’s broken – show our age
Feed the flame – tears enrage
Wait till morning to face the day

Now we’re toiling over
Thoughts and mixed emotions
Hard to really see
What’s lying underneath
Like a roller coaster
Up and down just floating
Touch the grass and leaves
Faces in the trees

Kick ‘em over – the darkened days
Tip ‘em over – the darkened days
Door is open – light the way

So what's got me in this funk? I think it's a culmination of many things, some of it is valid concern, part of it is just the pain of going through changes.

The snow and bitter cold has been a drain on my energy, and that's just the start.

In the wee hours of Sunday, Jan 3, we had an outage caused by a runaway process on a key server, which caused a cascade of server failures. My systems engineer, support engineer, and I spent two and a half hours on IM and phone trying to untangle the mess.

I started of the week by working at home. I had my daughters over the weekend, and as Sunday was drawing to a close, my older daughter was starting to look tired and droopy. By the time they got into the tub for bath, she said, "I don't know if I'm going to puke," which is her way of saying, "Get met to the toilet. STAT!" She got sick two or three times before the night was over.

STBX's first day at her new job was on Monday, and she had no place for the kids to stay with the older daughter being sick, so upon learning the the older daughter had gotten sick, she asked me whether I would be able to work from home. Since the meetings I had on my plate could be done by phone, I agreed to do so. The girls stayed an extra night, and they enjoyed having an extra dash of daddy time before they went back to school.

STBX's schedule is going to be variable these first couple of weeks because she's still in training, but once things settle down, she will be working three days a week with 12-shifts. One of those days will be on the weekend, which will coincide with when I will have the girls.

I came back to work having to deal with the president in a tizzy similar to that meltdown back in November. She was bent out of shape by problems that were being encountered by the three biggest customers, and she had a list of things in mind that she wanted fixed.

She tried to blunt the criticism that this was falling back into the trap of wasting development resources to mollify complaints of a few customers by making the hand-waving argument that if these customers are running into it, then other customers are, which isn't really the case.

There was a meeting of with members of the client services on these issues. Prior to the meeting, I asked for the raw data upon which the complaints had been based along with some narratives on the genesis of the problems. What emerged was a picture of scattered data points and bad analysis.

The more I work with the president, the more I am reminded of Master Shake from Aqua Teen Hunger Force, who had the unique capacity for drawing the least reasonable conclusions given a set of facts (c.f. Master Shake's analytical capabilities in Bus of the Undead).

My team wasn't happy because the technical solutions were being formulated and presented to us without our input, which was different from what we had done in the past, where we were given a description of what problems we were trying to solve, and then our team determined the technology to address the needs.

During the meeting, I worked to point out in places where the customer's complaints were caused by the inability to properly set up and manage customer expectations. When we brought on these larger customers, there was no agreement with the clients on what metrics would be used to determine success, and so we had fallen into a trap where our good standing with the client was imperiled by whatever measure they chose to focus on for the moment, an that was definitely happening in each case.

We managed to eliminate many of the proposed solutions, but the president was adamant that we didn't have enough time to do an analytic approach, modifying individual parameters and waiting to see if they had the expected effect. She wanted to make all the changes and right away. My counterargument to that was that by making all of the changes, we stood to gain little knowledge regardless of success or failure. She refused to budge. We have a project planning meeting Monday afternoon where we're supposed to start drawing up the to-do list for the next few weeks. I suspect this will be a doozy as well.

If there is any hope in all of this, it's that the VP we hired at the beginning of December has been gathering hard data and is starting to see the processes, or lack thereof, that wind up hurting us. Our department has been very open to providing him with cost data on our production environment and advocating areas where we saw opportunities for improvement through automation. From his preliminary findings, it looks like he could succeed in making the president aware of the true costs of perpetual fire fighting.

Some other things that have been going on... Been working my way through another round of resumes submitted via online ads and a posting the CEO put on a business networking site. We've also got a big management strategic planning meeting coming up that will take up the time of all department heads for two full days.

Changes on the personal front with respect to STBX's new job include me getting up really early one day a week to get the daughters ready for the school bus and preschool. My nights out remain unchanged, but on Wednesdays I have to pick up the kids from SBTX's friend, whom we're paying to watch the kids. The cost of that has been something of a stressor for me, but STBX's insurance is much cheaper than mine, so she will be putting the kids on her plan. All in all, I suspect it will balance itself out, but there's a part of me that's worried about making all the ends meet.

Friday, January 01, 2010

2am... Back from Fountain Square

Made it home from the music venue safe and sound. Last alcohol was consumed at 10 pm, so I was not even so much as buzzing after the Born Again Floozies finished up their last number.

All in all, it was quite a night. For a mere $15 + small convenience fee, I saw four local acts made up of some of the city's most talented and creative musicians. I wound up buying some CDs from the merchandise table. I'm glad I pushed myself into going, and I think this will motivate me to get out and see some other local music performances in the year to come.

My only regrets... First was showing up at 8:30ish. I figured that there wouldn't be many people there, but many of the good tables were taken. I wound up sitting towards the back. Second, although I had a great time with the music, the New Year celebration was hard going alone. I felt like the grade school playground again, where I was the odd kid out who didn't really relate to others.

Loneliness anxiety is painful for me. Very painful. I need to dig up my readings on this topic because I am far from transcendence in this area.

Thursday, December 31, 2009

Late Night Listening XXXVI: I Went out Tonight Edition

The year, and arguably a decade, now come to a close. Three and a half years have passed since the events leading to this blog took place. I can't see myself ever wanting to return to that life. Yet, the last year or so has felt like a wandering in the wilderness, a time to shake out the remains of an life before moving on to Canaan.

I have visions of what a life after marriage looks like, but I have struggled with the inertia of making it a reality. Maybe there is a part of me that feels guilty for wanting these things. Or perhaps it is fear that some unexpected negative karmatic event will visit itself upon my life, making it impossible to get where I hope to go.

Indeed I have seen shades of such things in the past year or so. STBX's extended unemployment. The major breakdown of her van. My dad's hospitalization and his further deterioration of health.

I have not come to terms with Loss. This is an awareness that I have gained in recent days. I reflect on past experiences... unreliable parents, untimely deaths of relatives during times of celebration. I think the message I have submliminally garnered from these things is that there is no joy in life that could be so utterly destroyed by an indifferent, or even sadistic, divinity.

I keep the feelings of hurt buried well, but sometimes they come back to haunt me. Sometimes it is late at night when I am alone. Sometimes it happens when I see narratives of others' losses, even in cartoons like Up and The Pricess and the Frog. My daughters must think I'm nuts for bursting out in tears.

It's during these dark moments when I realize that my attachment to this world is tenuous, driven not by love for this world, but rather the sobering awareness that I have commitments to fulfill before my time here is through.

And so I bide my time here, ensuring that my children do not do without a father in their lives. Getting lost in the Flow of work helps me to escape this sorrow temporarily. Indeed the lost self awareness is the closest I can come to resolving the Absurdist Dilemma.

I cannot work through this stagnation alone. I need to reconnect with a greater community, someplace I can feel welcome. I don't know where that is, but I know that I cannot find it by staying at home. I need to accept that Loss will come again, and that the avoiding the pain by avoiding life will mean that I have no life.

To this end, I am forcing myself to go out tonight to a music venue I have never been to. To the best of my knowledge, I will know no one. The self consciousness has been weighing on me. Can I be happy in being alone in a crowd of many? Can I open myself to the possibility of meeting someone new, without indifference to the possibility of rejection? Can I be brave enough to be who I am regardless? It is a raw test of differentiation, self soothing in the face of projected exclusion.

I will go, and I will be.

Monday, December 21, 2009

Late Night Listening XXXV: First Day of Winter Edition

I don't think there has been a time in my life where this song has been more relevant than now.



The past month has been rough for me. Shorter days and colder weather usually don't help my spirits, but this year I couldn't even bring myself to listen to anything remotely Christmas themed until today, when I finally tuned in to the XM Pops channel to listen to chorales.

I don't think I'm turning into a Scrooge. I make a distinction between that spirit which is pure and good and rightly represents the season and the commercialism and the compulsion that drives peoples to misery in the quest of doing things that are believed to keep others happy.

I was generous with gifts to my employees, and I took them out for lunch on the day of the final release. I have been active in selecting and purchasing gifts for the kids. I have donated freely to charities, and I've even tried to set a good example for my daughters, teaching them to put money in the bell ringers' kettles.

I know that workaholism has been a recurring theme in posts here, but my funk isn't really a work/life balance problem. It's more like an everything else/me balance issue. I've been spending way too much time handling requests from others that I've neglected to tend to my own needs.

The condition of my house had deteriorated into an embarrassing mess over the past month. The family room had been cluttered with the girls' toys and art supplies. My kitchen table once again reached critical mass with bills and junk mail. I was behind on laundry, and nary a dish was clean. I hit rock bottom this past weekend and finally rolled up my sleeves, getting the house straightened up. The bathroom could use some work, and I still have an unruly pile of note pads from work, but the day-to-day stuff is caught up once again.

On the work front, we had a development cycle that ran between Thanksgiving and the middle of last week. As sometimes happens, some items required way more work than what was anticipated. There were even a couple of things that we hadn't anticipated working on. There was a lot of client side work, too, so I had to step up and code some JavaScript. There were even a couple of Bozo items that came up from some of our high maintenance clients.

The last two releases involved going into overtime with test completion times in the late evening. Just about four hours before the first release, our hosting provider had a power issue that wound up taking out 3/8 of our server capacity for a couple hours. The other release had to be delayed by a day to make sure that must have features were implemented.

On top of this, I was busy trying to find a new developer. After revisiting the resume pile, I picked out five candidates for consideration. One of the interviews lasted a mere six minutes because they weren't aware we were a Linux shop and they had no desire to learn that. The other four made it to the point where they got the mini project assignment. One of them didn't submit a response. The other three had problems serious enough that I sent them rejection letters.

On the personal front, my daughters and I attended the wedding and reception for my cousin whose mother is the aunt with whom I've had issues in the past. I really didn't want to go because it was back in my hometown, and I feared that I'd have to face and talk to people about my situation. In a small town like that, there isn't much respect for boundaries. Fortunately, most of the people there I didn't know, so I was able to remain in obscurity.

STBX asked me to work from home on the 11th because our younger daughter had a fever, so she couldn't go to her sitter. STBX had a full calendar that day, complete with a test for the secretary training course she had been taking and driving her mother up to a clinic to see a doctor. The doctor's visit ran way over, and her mom got sick on some medicine that she had taken, so I wound up staying late with the kids, missing the company Christmas party.

Then on the 16th, she asked me to take the day off to take the younger daughter to the pre-school co-op for her last day of school there. After about a month of elevated drama, STBX decided she couldn't take it anymore. The school's finances are a mess, and the executive director has been trying to pin the blame on STBX's close friend, who served as the co-op president the previous year and as treasurer the year before. They submitted complaints to the county prosecutor, who looked at the claims and decided there wasn't enough evidence to file charges.

When STBX found out what all had been going on, she was livid, so much so that she stopped taking our younger daughter to class. On some days, the younger daughter didn't go at all. On others, she was taken by the sitter.

It suffices to say that my day at the co-op was awkward. One of the mothers asked me whether there was anything they could do to change our minds. I said that I wasn't sure about the circumstances of the withdrawal and that I only wrote the tuition checks. My younger daughter volunteered during circle time that she was going to a different school after this.

The irony of all of this is that the co-op had been a social underpinning for STBX. For the past four years, she had been on the board, chaired fund raising efforts, had served as president, and had baked countless items. One of the things that had weighed on my reluctance to push forward with the divorce was that I didn't want her to have to pull the younger daughter out of school because she would have a full-time job. But now, it is a moot point.

I am still struggling with isolation. There's a part of me that wants to get out and connect with others, yet there is inertia. There are feelings of guilt that I can't quite explain other than I feel like it's wrong for me to have fun before I'm fully divorced, so I am stuck in limbo.

I have been listening to some local programs that promote local music acts, and I caught word of a parody lounge act that was going to be backed by a big band orchestra for a Christmas show at a popular jazz venue. I wanted to go badly, but I couldn't bring myself to go alone.

I ran a "strictly platonic" ad on CL a week prior to the show to see if anyone wanted to go along. I got one reply from a woman from the northern part of the state whose life I would find was rife with drama and lacking in reliable transportation. Another was from someone who planned to go to the show and said I should go alone regardless. On Friday, when I had resigned myself to going alone, I found that all seats were sold out for both shows.

If there is any consolation from this experience, it is that I will get another chance to see the lounge act, sans big band, on New Year's Eve at a great place on my side of town. So I've committed to that night by purchasing a ticket up front. At least I can take comfort in knowing that I won't be spending my New Year's Eve in isolation.

Three years ago, I used the phoenix as a metaphor for the self dissolution that I was undergoing in the big job search of 2006-7 and the collapse of my marriage. The phoenix certainly rose from the ashes on the career front, but my social life still lies dormant. The hiatus is taking a toll on my spirit, and I fear that if I don't take decisive action to break through this year, I may not be able to recover. My gut is that I'm going to have to build a social graph from scratch.

Just as a Scrabble player whose current set of tiles allows no useful word combination, I must cast them back and draw anew if I am to make progress.

Thursday, November 26, 2009

Thoughts on Thanksgiving 2009

Saw this e-card in referenced in an e-mail newsletter today. I couldn't help but laugh and share the sentiment.

This Thanksgiving, cherish the time spent with your family as a reminder of why you moved very far away from your family

Before I descend into the navel gazing stuff, I want to offer up a list of things for which I am thankful this year:

  • My older daughter has had a good transition to grade school and finds joy in learning from a teacher she loves.

  • Both of my daughters find so much joy in being creative.

  • My dog of eight years is still as healthy and happy as ever.

  • I received a promotion that has given me a chance to grow and provide better for my daughters.

  • My department has continued to do so well in getting projects done on time with high quality code.

  • I have public transportation nearby that can get me to work.

  • The DJs of WTTS-FM have helped me keep my sanity, especially Todd Berryman and Brad Holtz.

  • Amazon MP3, for making it so easy to locate and purchase music that I hear on my satellite radio.

  • The Mozilla Foundation, Yahoo, and Google, for providing tools that make web development fun.

  • Web comics like Basic Instructions, xkcd, and Dinosaur Comics, for giving me reasons to smile.

  • For a number of friends, who shall remain anonymous, who have helped put smiles on my face.


As I did last year, I took a trip up to the north burbs to visit with my brother and his family. I wasn't all that enthusiastic about going.

I can't seem to get past this mental energy barrier that makes the thought of any family gathering extremely painful. It's not that I dislike my relatives, but there are some things about their behavior patterns that make interaction as grating as it is predictable, especially my mother and my aunt. Add to that the continuing cloud of my marital breakdown, and there's not a lot to get excited about.

Fortunately, so much of the conversation centered around my cousin's wedding next weekend that some of the old patterns were disrupted for this year. My aunt didn't seem to be as ready to rehash the old stories about my behavior as a two year-old for the umpteenth time. My mom wasn't ranting about how biased the Peacock Network's commentators are against the collegiate football team of Universitas Dominae Nostrae a Lacu and whether they should fire the coach.

Still, after everyone had left, my sister-in-law tried to get me to talk about the divorce, wondering where things stood. I gave some basic information... we were still technically married... we'd be filing in the new year... STBX is taking a unit secretary class... we were still civil.

She asked me if I had done any dating and whether anyone had tried to fix me up with someone. I told her that I hadn't and that I had intentionally stayed off of the social networks because I am not ready to reconnect with old acquaintances. I'm pretty sure that if I did have a profile, it would show my status as "It's Complicated". Moreover, I don't think I would respond well to one of those retrosexual, "You know, I had a thing for you way back when... but I never said anything about it."

I think she's still very curious about why the marriage broke down. I have been very quiet on the events leading up to it. Last year she told me that my mother had speculated about the sexual orientation of STBX, so I can only imagine what sorts of narratives that they have constructed since then.

My daughters are staying with me tonight because I have the day off tomorrow, and STBX has to get up early for her class. I'm not sure what we'll do. I've thought about taking them to the light ceremony show downtown tomorrow evening, but it's supposed to be cold and yucky, and for the most part they would be cooped up in my office until it was time for the lights to be switched on, so we might have a movie night instead. Once they are a bit bigger, I'd love to take them to see that show.

There has been less tension with my team than there was a few weeks ago. We managed to get commitments worked out for the "clean up" development cycle, and out of that came the fulfillment of all but the dumbest requests. Still, there are times when my employees express concern about where the company is headed. One thing that left the team rankled was that in lieu of our standard company meeting, where there is a recap of goals and how we met them, the President decided to make it a form of a quiz show, with questions created by managers based on things that their departments did for the month of October.

My boss has assured me that we as a company will dig deeper into that question at the beginning of the year when we do a strategic planning session. The CEO is very interested in opening up the architecture so that third parties can develop widgets and apps that integrate with the application. The President is fixated on totally revamping the system that is used to adjust the look and feel of content pages.

Nov. 17 was an awful day for the systems engineer and I as we had the worst outage that we've ever seen in our collective experiences. He was careless with the management of directories checked out under revision control. Instead of using the appropriate deletion command and committing the change, he used a standard file system command to delete the files. When he updated with the repository, the obsolete files were restored and pushed into production, causing a failure in our caching and bringing the application to a cascading failure. After getting things fixed, we had a long post mortem and worked on some systems and code level changes to keep that component from being a single point of failure.

The past couple of weeks have included budgeting meetings, and I have seen some tension between the CEO and the President there as well. The CEO, noting that we are getting a total of a million in funding from a state-sponsored fund, said we should aim for the fences and try to grow aggressively. The President is fixated on the goal of being in the black, which was a goal that we missed in November. I don't know all the details of why we missed that, but I suspect that it was because we hired on some new people in the customer service end of things.

At this time, my department will likely get everything I requested, which included big increases for professional development and reference materials. But I've also heard that some departments will get much less than what they requested because they asked for some pretty ungodly increases in their budgets.

The President floated an idea suggested by the company's advisory board -- eliminating salary increases for the entire year, replacing it with a company wide collective bonus based on whether the company met its targets, to be awarded at the end of the year. Given that none of the other departments meet their targets, or do so in a way that is laden with asterisks, I wasn't about to buy into this. I told them that moving the goalposts out from under my team when they have been working under a different compensation reward system would most likely motivate them to look for employment elsewhere.

On the recruiting front, we interviewed someone on site a couple weeks ago, and decided that there were enough red flags to not extend him an offer. I phone interviewed a couple of others who have proved to be promising, but one of them gave up on the sample code exercise when he couldn't get the software working on his computer. The other submitted a good result, so we will probably bring him in either next week or the week thereafter.

Another amusing item from the marketing end of things... Our marketing team decided it wanted to revive dead leads for whom we had offered a price quote. The package essentially offered twice the amount of priced units for the original price quote. All I could think of was some annoying informercial guy screaming, "Check this out! Well give you more of what you didn't want at the price you weren't willing to pay!"

Word came to me late last week that upper management was in the process of putting together an offer to a guy for a VP of Ops. According to the President, he was working for another start up in town that was crumbling because of a bad funding plan, and they saw a real opportunity by "scooping him up."

Never mind that they bypassed the rest of the company's managers in vetting him through a formal interview process. My guess is that this guy is connected in some sense and had the job handed to him. As someone who had to interview and earn jobs without the convenience of connections, I can't imagine just getting a job handed to me, much less feeling good about getting a job like that. Since this role currently doesn't exist within our organization, it's not clear what the org chart will look like this. I did some Google stalking and found out he was not technical, so I hope he won't have jurisdiction over our department.

On a completely unrelated note, I got a promotion from my cell phone carrier for an early upgrade, and being a fan of Do-No-Evil, I am falling prey to the siren song of getting a Droid.

Saturday, November 07, 2009

Late Night Listening XXXIV: Of Boiling Points and Breakdowns

Before I do the big information dump, let's pull out something out of the ordinary. I heard this unlikely cover on WTTS-FM's Over Easy a month or so ago. I was reminded of it last week while listening to a WICR-FM's Have You Heard?, where they had Sean Baker, a local jazz musician talking about vocal groups, and he brought up his soft spot for the Andrews Sisters.



Yeah, I'm a sucker for those harmonies, too. :-)

The last few weeks haven't been very easy on me.

On the work front, my team and I spent most of October working furiously on the last phase of a larger project that has consumed most of our development time since I took over the helm of my department.

It all started last summer when one of our sales reps got in touch with the purveyor of aftermarket vehicle accessories. This guy had a vision for using our application in ways we hadn't envisioned, and scale of some of the usage requirements would tax both the user interface and the back end so heavily that it would surely break both.

The development roadmap was rapidly shifted toward meeting these goals. What we envisioned at the beginning wound up being much of what we implemented, save for one administrative interface and one standard user interface item. We swapped those out for a couple of additional changes requested by the customer, so things balanced out.

The good news is that we met the letter of our commitments to upper management, so we were able to collect on a bonus funded out of money that had been budgeted originally for the employee we let go in early Sept. That money will be coming our way later this month.

The bad news is that one of the changes we made removed a feature that we warned management would go away, and it was explicitly listed in our work items, but the client management person who is the point person with our demanding customer didn't communicate this to him, so he wasn't happy.

Moreover, despite my advice to the President that she needed to communicate this change to Sales in advance, she chose not to follow through with this, so the sales team continued to plug this feature in their demos right up through the day of its removal.

Pile on top of that various observations and complaints for customers to a dysfunctional client management team that doesn't know how to manage such situations effectively, and all of the sudden our department was under pressure from upper management to restore the old feature.

It suffices to say that my team was not happy with this. I pushed back and negotiated a compromise. The old feature would remain dead, but we would extend an existing feature, currently available only to administrator roles, to regular roles but limited to viewing things rather than having the ability to make changes that administrators could.

Of itself, that exchange wasn't awful, but a number of other events started to strain my relationship with the President. We have a standing brief 1:1 status meeting in the afternoon. Normally it's small administrative items that can be taken care of in short order. A new pattern started to emerge last week, where she started to ask me about changes to the application and whether we could fit them in before taking on the next big project.

For about a year and a half, our department has used a project management style that has proven to be very effective. We let management set strategic priorities from an ongoing wish list, and we gradually work down that list developing concrete lists of work items and time commitments. We also have a shorter term planning process that lets us respond to tactical issues, like bugs.

For the most part, we hit our targets, and the execution is the envy of other departments in the organization. Some of the departments have established "cargo cult" style practices that emulate what we're doing but they lack some key ingredients -- one is they don't make actionable commitments, and the second is that there is no accountability for failure to meet them.

Anyway, the nature of the requests from the President started to look like ways to circumvent that process because they asked for specific things rather than asking us to solve classes of problems. Almost all of the requests were specific to either a single customer or a small group of customers. At least two of them were driven either by personal connections between the President and the client. She also seemed to be pushing for commitments to resolve them without me discussing the details with my team.

After about five days of this, my team was starting to wonder what the deal was with upper management. Were they abandoning longer term roadmap items for revenue chasing one-offs? Two of my three charges were seriously concerned about the future of the company because they had seen similar patterns in prior jobs and weren't happy about it.

On Wednesday this past week, I met with the President and had a long talk about what I was seeing, offering a willingness to work with her to meet company goals but needing a better sense that these smaller items were going to be addressed through our usual procedures, which ensure accountability on both sides. It was a useful discussion, and I got in writing a concrete plan for dealing with both the short term issues that had been occupying her as well as the need for longer term vision.

The week ended with a timetable for getting these things straightened out, which left both my team and I in a better emotional state.

Another recurring battle I have been dealing with is the influence of consultants who claim to know how to get search engine rankings. This is field that is rife with poseurs, hacks, and quacks. Advice is dispensed with handwaving and minimal statistical backing, sometimes justified by claims that they got high rankings for their clients. Most of these people have no background in computer science, let alone understanding of network protocols and indexing algorithms.

My employer has been very concerned with how consultants view our application, be it as something that is of no use to them or as a direct competitor. Nonetheless, local and national consultants both have weighed in and given bad advice with authoritative voices. As a result, I've spent more time than what I would have liked researching claims and determining their credibility.

It's gotten to the point where I think we need to invest resources on our own independent research using controlled experiments. Much of the more exotic advice we have received would require major application modifications, and if the techniques were later ruled as disreputable by the search engines, all that work would have been for naught.

I've also decided that my next dream job would be to go work for the spam detection folks at Do No Evil and work to ferret out the shady tactics these guys ply and destroy them, but that's just my Aspiness showing through.

Job applications have started to come in over the past month, and I've been doing phone interviews. The quality of developers around here is really hit-and-miss. Out of four candidates, there has been only one which has been worth bringing in on site. (side note to Drunken Housewife: I suspect that I might be just as picky as Sober Husband about screening, which could make this painful)

STBX started a six-week Unit Secretary training class with a local hospital a couple weeks ago. The hope is that this will help her get hired on there, but there is no guarantee of employment, and the cost of the training is being paid entirely by her.

On the kids front, our older daughter is doing well in school. Some days she has problems with some homework items if the task is unfamiliar, but once she gets familiar she does really well. She is really into writing. This weekend, she has been working a composition about what Thanksgiving foods she likes.

I took off early on the Friday before Halloween to attend both kids' Halloween parties. Their trick-or-treat choices for the older and younger daughter were Batgirl and Daphne from Scooby Doo respectively.

This morning, I took the girls up to a dinner theater on the northwest side of town for a children's performance of Jack and the Beanstalk. One of the preschool moms works at the theater and arranged for a good discount on admission. They both loved the watching the show, and they got to get the cast's autographs afterward.

Had a bit of a scare earlier this past week with my car. I drove out on Monday evening to get something from the grocery, and my car started running really rough, so badly I feared that I wouldn't make it home. I took it to the mechanic, and it turned out to be ignition issues. I needed a new coil and new plugs. I also had them fix a slow coolant leak I had been deferring for several months. It turned out to be a bad hose. Set me back about $480, but the car is really running well now.

To speak to Anais' recurring question on my sex life. I'm still keeping a low profile on such things until we get the divorce taken care of, modulo a few encounters of the type described by ChelseaGirl, which happened back in early February (blushes).

I've been dealing the lack of touch by getting massages, which have become much more affordable with my increased income. That's been especially helpful in dealing with the stress, but it doesn't entirely address the loneliness anxiety that crops up from time to time.

I also wanted to thank everyone who commented on my post about the "I would be honored to be your first" woman. It was good to get some other perspectives and finally get that whole story out there. It's a secret I had carried around in my mind for some time. Bonus points go to Desmond for pointing out that the song is a cover.

Speaking of secrets, I was amused by a post from Tech Crunch a few weeks back. There is now a microblogging site for people to post about their relationships. The site's tag line pretty much sums up the nature of the Diggersphere -- "It stays between us (and the web)." :-)

Saturday, October 17, 2009

Late Night Listening XXXIII: I Should Have Forgotten by Now, but I Haven't

I'm going to indulge in some self-absorption tonight, sort of a Post Secret confessional, extended dance mix version.

Let's set the mood by pulling out a copy of a forgotten 90s hit...



... my mind goes back to 18 years ago...


October 1991
Su Mo Tu We Th Fr Sa
1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31


... a Thursday night, just before the midterm break at Universitas Dominae Nostrae a Lacu... a gathering at my apartment. A couple days before, I had disclosed to you and another classmate that I had not yet had my "first time"... While we were alone on the balcony, you spoke to me with an admiring voice and riveting eye contact. You took my hands, holding a glass of wine, into yours and told me that you'd be honored to be my first. We never found the time or place to give you a chance to live up to those words, but we did dance to this song at the senior bar later that night.

I will never know the motivations behind that conversation. By your own admission in a conversation a couple weeks later, I would learn that the statements were just "mental gymnastics". The time in between, I experienced feelings of confusion and euphoria... things a man at the age of 22 should not have felt. For the first time in my life, I thought someone had found me to be truly desirable. I thought, spoke, and wrote things that were truly foolish. Indeed, I was your fool for a night.

If I could set the time machine and find myself on 10/16/1991, I would slap myself silly and say, "Don't go on that balcony tomorrow night. Go out, drink, try to have fun, get a cab. Just stay away from her."

(recovers composure)

I hate that this specter lurks in the reaches of my memory. It's a petty grudge, certainly not worth carrying for all of these years. Most people get past these things and wind up forgetting they ever happened.

Over our time up there, she went on to shack up with another classmate for a couple of years. I know from Google that after earning her doctorate she married another grad student who would earn his pay writing about politics, sociology, and food. I think she's since divorced and remarried, living out in the Mountain timezone. I doubt if she remembers me at all.

At the core, it really isn't about her. It's about a set of beliefs about myself that I have struggled so hard to bury, but they keep resurfacing, like a band of tireless zombies. I am not good looking... I am uninteresting... I lack some unnamed essence that makes women crave men... I cannot satisfy a woman...

To my credit the list used to be much longer, laden with lots of negatives about my potential as a professional. My latest job has taken me past those feelings. I am a much more productive and skilled person as a result.

I sometimes buy myself respite with mental affirmations or rationalizations... I'm unique... I don't think like most, so I won't be compatible with most... I need to live somewhere else... I need to be at peace with myself before I can relate to others. I need time to heal from the changes I've been through... There so many suffering so much worse... Other times, the loneliness overwhelms me, and I wallow in self pity.

So tonight, I fess up to this intermittent replay of insecurity and resentment, hoping that by committing it to text, giving it form, it will be exorcised from my soul and imprisoned in these paragraphs. Rather than seeking to remind myself of past injustices visited upon me, I should live in the here-and-now, doing my part to be loving and just to others.

Sunday, September 20, 2009

Sunday Morning Sing-a-Long VII: Triphoppin'

As I mentioned in the Twittersphere last night, the local good radio station played the Nightmares on Wax song "70s 80s":



I can't get that guitar loop out of my head.

The week was busy. It was stressful, but in the end it was all for the good. Last week, I blogged about the Big Switchover in the code base at work. This week is the week that code made its way into production.

A release candidate was cut and put on the test environment on Tuesday. I felt bad for the systems engineer and user interface engineer who had to code review and test the changes because there was a lot of code going into this release. Between my ex-boss and I, there was something on the order of 1,600 new lines of code. To aid them in their efforts, I wrote up a detailed test plan of things for them to do to flex different parts of the code.

Late in the afternoon, there was a false alarm bug that was really system configuration issue. The new code relies on asynchronous execution of tasks, and the queue that was dispatching the requests was not up and running.

After I got home that evening, I found a bug in my own code for something I had not taken into account in the testing. I worked with the system engineer to get the fix merged into the release candidate.

The push to production on Wednesday morning had issues.

It turned out that code I had written for doing synchronous population of a data store had not been tested for multiple sites. I had a stray line of code that was breaking the execution of a loop, so we had to fix that.

Then once the code went live, we started getting alerts about fatal errors. A fatal error happens when a script cannot execute to completion. It was being caused by some validation code that I had written as part of this release. I was checking the value of a variable using the wrong name.

Within an hour, I had coded the fix, got the system engineer to test it, and then got it pushed into production. Lucky for us, the bug was exercised only when an "about us" type of page was requested. According to the logs, most of the hits were being generated by search engine crawlers rather than real humans.

On Thursday, another issue was detected. A database query had been written without adequate entity constraints, so there were situations where if you requested a post by its permalink URL, and there was another post in the database with an identical title, you would wind up with another person's content. Fortunately, it was a two-line fix, and the issue was resolved within a couple hours of detection.

I've also been busy with some external development stuff. We have another company who wishes to integrate with our application. Since we have ways for third parties to use our services programmatically, this is pretty easy to do.

In fact, we have one company who did just this thing this past summer, and their development team was really happy with the design. This other company isn't quite as web services savvy, so educating them on ways to get what they want done quickly has been a challenge.

To make their work much easier, I will need to make one change to our application that gives them much more flexibility. I took the lead on implementing that over the weekend. It won't be a breaking change, thankfully, but it will need to be vetted before we push it into production, so I will be using our group code review time to put it under peer scrutiny.

We also made plans this week for the development week the next couple of weeks. We will be adding a user interface for adding accounts that doesn't require a call to our support team. When I announced this at our company mini-meeting on Friday, I got cheers from the support team, which made me feel good.

To finish off the week, the President and CEO took my team and I to lunch at a brew pub downtown. It was one of my favorite restaurants, and luckily it has enough breadth to keep the diversity of my teams tastes happy. One is a vegetarian, another is a teetotaler, and another is on a high protein diet.

I think the meeting was good because we got the ear of upper management, and they got to know us better. We have a good reputation within our company because we consistently get stuff done, usually on time or pretty close. The CEO said that at the last startup he was at, software releases involved nail biting and stress. He said he doesn't worry about that stuff with us. I told him, "We worry, so you don't have to."

Despite having one less team member, I feel good about where we are headed. I gave a new job description to the President on Friday, and it's a major rewrite of what my ex-boss used. After 1 3/4 years on this job, I've got a good sense of what the good hires and not-so-great hires are like, and I've got a better sense of the soft criteria that discerns the two. The description takes that into account.

With the quarter coming to a close, I will be sitting down with my team members to set goals for their own personal development for the next quarter. While it is important for us to get the releases done on time, I know it's also important for our team to grow in our expertise and skill.

On the home front, STBX started one of her part-time jobs last week. She has to be at the workplace at 5 pm on Wednesdays, so I have to take off work early. That's not such a big deal because I go in early on Wednesdays because of releases. Since my older daughter has to be in bed earlier these days, that gives me more time to spend with the kids.

My older got her first progress report this week, and she got good marks. She's really enjoying school, and it's so neat to see her grow in her abilities. The younger daughter is in preschool three days of the week now. The other part-time job that STBX has is working as a substitute in the school cafeteria. Since that has the possibility of conflicting with getting the younger daughter to and from school, she has arranged for the preschool teacher's mom to be a sitter. The rate isn't too awful, and I'm picking up 75 % of the tab for that.

In a few hours, I'll be picking up the girls to take them up to the north burbs. My mom is house sitting for my brother, so she's invited us up there for a cookout. That's about all that's news here.

Monday, September 14, 2009

An xkcd Comic that Hits too Close to Home

Be sure to mouse over the image to get the tooltip that makes yet another analogy.

Brontosaurus

Saturday, September 12, 2009

Late Night Listening XXXII: Tetering on the Edge of the Known Edition

(picks self up off of pavement after being hit by what felt like the bus I ride to and from work)

Tonight we set the wayback machine for the mid 70s and find the nearest arena to rock out to Kansas' "Point of Know Return".



I always loved the cover art for the album on which this track appears, and it is of symbolic significance this week because on late Friday afternoon, I got the OK to push through a significant change way that our application works.

This project has been a long time coming. Both my ex-boss and I had long eyed the possibility of replacing a naive algorithm for content sorting with something more industrial grade. A business development opportunity which threatened to push the existing code past it limits created a the motivation to push forward with it.

Changing the algorithm wasn't without risks. The end result of this sorting algorithm is user-visible, and a major shift in the sort profiles threatened to hurt the search engine cred for some of our customers. To protect against damage, I ran extensive comparison tests for almost 20,000 different content aggregations, identifying which ones might be hurt most.

Fortunately over half of the aggregations remained unchanged. About 30 percent shrank, and the remainder increased. After some additional number crunching by other departments, and adding a bunch of subjective measures, they came back with a list of adjustments that they thought would be needed.

A couple of product support workers got the task of refining the sorting criteria, running into issues along the way. It seemed as if no matter what they did to loosen up the criteria, they still wound up with bad results. Fortunately our team was able to tune the sorting system to get better results.

There was a lot of tension along the way, with upper management at the point where they were wanting to delay the switchover to the new algorithm even later than what we had done already. In the end, I managed to persuade them that some of the shifts they were worried about would lead to better results in the long run because the sorting would mean something.

So all of that was enough to keep me busy this week, but there was more, and it put me through a wringer.

First, I had to deliver the "break up" message to the problem employee. Thankfully he took things well, and wasn't totally blindsided by the announcement. It probably helped that upper management had authorized a week's extra severance as part of the package. Still, the experience was emotionally draining, and afterward, I jokingly told the remaining workers, "Please don't make me do that again."

Still the newly ousted employee had some chutzpah. The next day, he e-mailed my boss to say that he had done some thinking about the agreement and said that he wanted one month's pay instead. Keep in mind, he had been with us only three months. My bosses did not budge, thankfully.

But there was more. On the afternoon of testing day, I found a couple of bugs in a major user interface feature for the week. They were show stoppers, and to ship with the bugs would have been insane. Since we were already doing the release on Thursday, instead of Wednesday, due to the short work week, to postpone the release would mean no release for the week at all since we don't do releases on Fridays as a rule.

So I worked late with the UI engineer to debug one of the issues. It was a tricky bug caused by a lingering subscription to a change event that fires when an asynchronous HTTP request is finished. It turned out that the developer of the user interface was using the web service code in way that it was never envisioned. We made changes that wound up making the problem just go away. By the time the UI engineer fixed the other bug, it was 2:30 am on Thursday, and both of us had to be in the office by 7:30 am for the push to production. It was a looong day.

On top of all of this, I was working with another manager to finish up the draft proposal for our outage emergency policy, attending management meetings where there was debate over the values and mission statement of the company, and preparing presentation materials for the company meeting that was supposed to be on Friday, but got moved to next week.

Which brings us back to the code switchover. This sorting change was a big effort. It was started by my ex boss, who did the foundation work and some prototyping. I had to refine it and handle a lot of edge case nastiness. None of these items, let along testing, could get done in a week's time. So we had to commit changes to a branch that lasted over a month.

At two points over the past month and a half, I was able to merge subsets of this code into trunk to handle new functionality, but the merge I did early this morning marked , for all practical purposes, a crossing of the Rubicon. Although there were some pieces in place to roll back after the switch, the reversion would be a risky operation that would only be employed in the event of an emergency. So in essence, we have now crossed that point of no return.

Indeed, when I committed the merged changes back into trunk, I included a lyrical reference to tonight's song. The sad thing is that I think not one person on my dev team was born when this song was big.

On the personal front, I didn't make it out for the testing today. My mom had to work, so the kids were all mine all the day. We went out for lunch and then went out for a couple hours later to go to the library and do some shopping.

I've been taking it easy this weekend. With my nerves as raw as they were on Friday afternoon, I need the downtime to recharge.

Monday, September 07, 2009

Late Night Listening XXXI: For the Love of Labor

Tonight's selection is an obscurity... Thompson Twins' "You Take Me Up".



This track is not my absolute favorite from this group, but since it touches on the theme of labor, I thought it appropos for a posting on this holiday.

Within the depth of this Aspergic mind of mine, there is a region that obsesses over the reinterpretation of songs in different styles, much like what Jack White did with the Racontuers' "Old Enough", by getting Ricky Skaggs and Ashley Monroe to sing a bluegrass version. I could see a rearrangement of "You Take Me Up" sung in a more traditional gospel/bluegrass style, and having it work pretty well.

On a superficial level, Jack White creeps me out. Yet, the Skaggs/Monroe recording and his work with Loretta Lynn (c.f. "Portland, Oregon") hints at a musical transcendence that bespeaks creative genius. I'll drink a slow gin fizz to that any time.

Getting back to Thompson Twins... my favorite song from their canon is "Lay Your Hands on Me", which has a refrain that has a religious revival feel to it. (looks away wistfully) I... miss touch... badly.

So where are things with me? Overall pretty good. House is a disaster area, mostly toy scatterage. I'm starting to catch up on laundry. Bills are paid, and the bank account balance has been slowly and steadily rising.

STBX has a couple of very part time jobs lined up that should allow her to keep our younger daughter in the preschool cooperative for her last year. First, she got on as a substitute cafeteria worker where our older daughter goes to school, and she's going to be working a couple of days a week for a frozen custard chain, doing detail on their cakes.

I didn't do too much over the weekend. Wrapped up some odds-and-ends tasks, and I'm code complete for the Tuesday end-of-business cutoff, save for some fill-in-the blank things I'm waiting to get from a coworker. That's a good thing because I have 4 1/2 hours of meetings scheduled on my calendar for Tuesday, which leaves very little for coding tasks.

I wasn't supposed to have the girls this weekend, but I got some Daddy time in. They went down to my dad and stepmom's on Friday, and I went down to pick them up yesterday afternoon. STBX had to go to training for her cake detailing job today, so I came over and got them. We took a bus trip to downtown, which is something they have been wanting to do ever since I started riding what they refer to as "the work bus". We met my mom for lunch at the big mall (those of you at the blogger gathering last October would know where this is). We also stopped at a chocolate shop for some ice cream. Here is a picture of them ogling the deserts...



... the moment that picture caught was one of those warm-and-fuzzy times that makes being a dad so much fun. Just watching them off by themselves... in a state of wonder... enjoying life.

Let's pay a visit to the office now...

Getting used to the management role has been fairly smooth. I am now at a point where I have an idea of where our department is and how the other departments are doing, and I've been able to keep up my coding commitments.

The feedback I have gotten from my boss, the President, is that I am doing really well. She also added that if I needed flexibility in my schedule for family stuff, she's give me leeway since she knew that I had put in a lot of extra hours through all of this. Their main concern is that they don't overwork me to the point that the "break 2am".

One sign of confidence from upper management... Back when I took on this role, I was promoted at a "Director" level, not the "Vice President" level that my boss held. They envisioned getting someone who was more into doing business development work for that role, and that was fine by me. I've been able to keep things going well enough that they've decided that they could postpone hiring for that VP role, with them reconsidering reopening that search on a month-to-month basis.

We've made good progress on the big project that we started at the beginning of August. My ex-boss chipped in some trailblazing work, and I was able to use that as a starting point, and refine it to handle all of the edge cases. What emerged from that is a really good system that should make our customers happier than the old system. However, our customer service team is nervous and needed more in-depth data over the impact of the change, so its release has been delayed by a week. I have been more than transparent, giving them solid and complete before/after data sets.

The one thorn in my side is the guy we hired on back in mid-June. He has been something of a slacker since day one... coming in late morning, cutting out some afternoons early, missing deadlines, writing shoddy code. Before he left, I know that my ex-boss had a talk with him about his performance.

And when I took on the director role, I had another talk with him. I had learned that he had gone to the President with his complaints... including our rapid development pace and the fact that our developers also had to do testing. He thought we needed to hire on a full-time QA person. I tried to address his complaints and explained how our system had some benefits for him as well.

When we started this new project, I gave him more leeway than usual to work on the design for a new user interface component. He spent way too much time on it, and again, deadlines crept out and out. This was starting to really annoy the other UI developer, too. We reached a point where I told him that we needed to move from the prototype to a full version. We mapped out a day-to-day schedule to ensure he understood that we needed to see this into production this past week.

Still, he dragged his feet. My boss was concerned about his progress, and she could tell he was starting be a real problem for me. We talked about what we could do, and agreed we would try to keep him on board until we wrapped up this project and then look seriously about getting rid of him.

On Tuesday afternoon last week, just before the code-complete deadline. We realized that there would be more time needed to get things done, so I agreed to have the first release candidate cut on Wednesday morning. I didn't see the slacker online when I signed on at 9 pm that night. The diligent UI guy was online, too, and was miffed that the slacker had not been available to help with some code integration work, so he started working on the slacker's code to fix the issues.

The slacker signed on after 11 pm, irritated that the other developer had worked on his code, and then he IMed me saying he wanted to speak with me the next day about his future with the company. I told him that I would be willing to speak with him, but not on testing day, when things are super hectic. I opted for a meeting after lunch on Thursday.

During the meeting, he rattled off what was bugging him about the job... his ideas weren't taken seriously, he didn't like our frequent release schedule, we put too much time into engineering things, he felt like he was being micromanaged. Everything was everybody else's fault.

His solution? Move him out of the department to be a "product manager", so that he could concentrate on less time sensitive things that required creativity, like prototyping. I asked him whom he thought he would report to. He said he thought that he should report directly to the President, my boss. He also said that if this move wasn't possible, he might have to start looking elsewhere.

The sense of entitlement was completely annoying. This was basically a shoot-from-the-hip whiz kid in his 20s who was being paid way more than what he had given us in output, and at no point had he ever owned up to mistakes he had made along the way, many of which resulted in either bug reports or emergency fixes.

I spoke with the President after that meeting, communicating what he had told me. We both agreed that he needed to go. Keeping him on while he was looking made no sense because he had never put in full effort at this job. The checkout would have made him complete deadweight. Since he had already scheduled to be out of the office on Friday, I arranged for the axe to fall on Tuesday (tomorrow), at a meeting with the Presdient, him, and me late in the afternoon.

So with two months of experience in this role, I've managed one of the largest development projects the company has had, and I've had to fire someone along the way.

On other matters...

The system engineer who overslept a few weeks back took a much deserved vacation the last week of August, half of it spent at Hilton Head, and the other half at Sin City. I went out of my way to make sure that I did not interrupt his vacation for anything, and fortunately we did not encounter any issues that would have required his help.

Also, Anais has recommended that I get involved with the local Mensa group to build some new friendships. It turns out they have admissions testing this coming Saturday. If I can get my mom to watch the girls for a few hours then, I will head out to do that. If I can't make it then, there is a larger testing event in town in mid-October.

Saturday, August 22, 2009

More on the Vanilla Sex Magazine Article

Anais writes in a comment:

I want to know why a magazine has to "sell" vanilla sex to anyone. I'd be interested in reading the article just because I can't imagine what it says that could possibly interest me in participating in more vanilla sex and less kinky sex. I mean, yes, vanilla sex can be VERY hot -- but I would never voluntarily damp down the kinkiness factor in my sex life and I doubt any article will convince me to try it.

(Actually, I know a little about magazine titles, and of course this is just one more way to get the word "sex" on the cover, to make people want to buy the magazine.)


I think the question she raises at the beginning of her comment expresses what I was thinking when I first saw the cover. To me, the line "Vanilla Sex: Why It's So Great" register as "Settle for less. It's more than you think." Try recasting that statement in terms of something other than sex, and you can easily create statements of profound absurdity.

I did check the magazine's website to see if I could find the article in question. The only thing on their carousel about sex was this article:

Better Sex Now

but it's more about spicing things up in a moderately non-threatening way. I also Googled the headline as a quoted phrase and turned up another article for a Canadian magazine of a similar title that is cited as having been published in Oct. 2008.

Vanilla sex: The best you've ever had?

I wondered if the magazines might have a common publisher. If you look at the "favicon" (that little image that appears adjacent to the site's address on most browsers), you'll see the silhouette of Pegasus, which is a trademark held by the publishers of Reader's Digest[1].

If you click on the Subscribe link on the Canadian magazine, you'll find that it takes you to a server hosted on the readersdigest.ca domain. I think this gives us good reason to believe that the article is being repurposed in a sister publication in the US.

I read through the article and have mixed opinions. On one hand, he is right about the overemphasis on techniques when it comes to advice. Sexuality has mental and spiritual dimensions that make it more satisfying. But on the other hand, the article has a subtext that good sex requires the abolition of the unusual or the anxiety provoking. Indeed, it sounds as if he is cheerleading for Scharff's notion of "good enough sex".

Then there is this passage toward the end:

Now that I’m married, sex has assumed its proper place in my life. It generally happens at a preordained time. Sometimes circumstances prevent it; other times there’s a bonus. It’s pretty basic, stripped of all its bells and whistles. Afterwards, one of us might casually say, “That was fun.” Then we roll over and fall into a delicious sleep. Or we might get up and go about the rest of our business, of which—with three boys and two careers —there’s plenty.


He seems so... contentedly suburban, which is anything but what I am. Maybe that's why I found it so irksome?

For an alternative perspective, refer to "White Collar Holler", recorded originally by Stan Rogers and covered here by the Rambling Sailors.



I remember hearing Rogers' version of this for the first time on an episode of Dr. Dimento way back in 1984 and laughing my @$$ off.

[1] -- One of my casual Aspie interests is being able to recognize trademarks and know the formal names of companies.