Blackcap Blog

Published at 10:22 on 9 September 2015

Despite my posted résumé containing a preface stating I am only interested in software development positions and explicitly ruling out systems administration positions, this clown spams me about a sysadmin job. To put the icing on the cake, the job isn’t local, either (that same preface mentions that I am unwilling to relocate).

Date: Wed, 09 Sep 2015 08:58:34 -0400 (EDT)
From: Srikanth Gampa <srikanth@net2source.com>
To: xxxxx@xxx.com
Subject: Need DevOps Engineer  at Salt Lake City, UT for Direct client

Good Morning

Greetings!

HI,
 
Hope you are doing great…

I have an Immediate requirement for the below location with the
required Skill set for one of our Direct client.

If you are comfortable revert back to the mail with updated
resume to discuss further

Mangled grammar and multiple salutations as per the original text I received. Given the name, he’s probably not even stateside.

Note I said “given the name,” not “given the name and grammar”. I’ve met plenty of Indians whose grammar in the English language is as good as any American or Brit. If you go to the All India Radio news site, you’ll find text and audio clips which are representative of how a well-educated Indian uses the English language.

But sleaze outfits like Net2Source are interested in cutting costs to the bone. Why cut costs a lot by hiring a well-educated workforce in India when you can cut them even more by hiring a poorly-educated one?

Published at 18:58 on 8 September 2015

Had another interview today, and the way it want (not badly, but not great either) makes it pretty certain I’m not going to get an offer. Which is OK, given the next point.

The biggest catch is that the guy who would be my boss, while very smart, has fallen victim to Respected Academics Syndrome. That’s when someone with lots of formal education and recognition to their name lets it all go to their head, to the point where they can’t take any constructive criticism, no matter how valid, from someone with less of either. They have the credentials, I don’t, so therefore there’s absolutely nothing they could ever learn from me. Period.

In this case, it was about SQL. The guy wanted to design a program that sent SQL to back-end databases that was both standards-confirming (so it would be database-independent) and efficient. You can’t do that: the SQL standard is surprisingly small. A lot of the SQL syntax that one takes for granted as basic stuff for writing efficient queries (such as the LIMIT clause) are actually nonstandard extensions. But no, I couldn’t make that point without being interrupted and having my concerns waved off (never with any actual evidence to the contrary, of course).

What’s sad is that it is at an organization with a very noble mission (cancer research). So this project is going to run into all sorts of unnecessary and easily foreseeable difficulties, wasting lots of money and effort, largely because the workplace is a hierarchical and authoritarian place. If the world wasn’t largely on such principles, personality faults like that wouldn’t do nearly so much damage: he’d still be respected for his past accomplishments but the moment he tried to bluster others into doing the impossible he’d get ignored and overruled by group consensus, because there would be no such thing as a “boss”. And because such academics could get easily called on their shit, they wouldn’t let their recognition go to their head in the first place.

And that is the biggest reason I am an anarchist: because life experiences keep on underscoring to me that authoritarian hierarchies just don’t work very well.

Published at 13:35 on 7 September 2015

The technology for camping on the playa has improved a great deal since I last seriously pondered going (and rejected the idea because I’m not a desert person and it was simply too expensive and impractical to get any comfort, i.e. shelter from the dust, extreme heat, and harsh sunlight).

Now, with hexayurts and solar swamp coolers, there are options which fall in the sweet spot between an RV, a generator, and lots of extra fuel (comfortable but expensive) and a mere tent (insufficient shelter in such a harsh environment).

But, I still think not. In between building and testing my shelter and its climate-control system, and implementing the theme I’d use, the job of preparing for the next festival would occupy most of my free time, like it does for most who attend Burning Man. It’s why it ends up being more a way of life than a mere week-long festival.

And I already have a life which I’ve chosen based on careful introspection into my priorities. I’m simply not willing to give up weekends spent hiking and botanizing in favor of weekends spent in town preparing for the next Burning Man.

So it looks like the answer is still “no” for me.

Published at 18:42 on 4 September 2015

My Internet résumé contains the following notice:

This résumé is being posted strictly for the purpose of soliciting responses related to employment opportunities in the field of software development. In particular, neither insurance sales nor systems administration are software development.

Today I received the following e-mail:

From: Ron Nation <rnation2@farmersagentcareers.com>
Subject: Career Opportunity
To: Xxxxx <xxxxx@xxx.com>
Date: Fri, 04 Sep 2015 13:58:53 -0600

Hello Xxxxx,

My name is Ron Nation, District Manager for Farmers Insurance Group,
in the Seattle area. I came across your resume online, was impressed
with your background, and thought you may be a good fit for a
position I have available as a Sales Professional with our company.

[edited for brevity]

Welcome to my Hall of Shame, Ron. Congratulations, you’re the inaugural member!

Published at 15:49 on 30 August 2015

It’s not unusual for programming jobs to have programming tests as part of the interview process. What is strange is for a job that was advertised as being back-end coding having its biggest, toughest question being to code an AJAX web page.

After six slow hours, I’ve gotten the thing to satisfy two of the three requirements, and I think that’s about it for me on this one. Six hours with Javascript is about five hours too many for me, and if doing such things is really pertinent for that job, I don’t want it anyhow.

But really, if front-end stuff is that important to you as an employer, why not simply advertise the job that way? (Would an orchestra advertise for a tuba player if they really wanted a violinist?)

Published at 18:48 on 27 August 2015

A month after I got laid off in the midst of having some work done on my home, I finished the work today by completing the painting of my bedroom. Actually I spent under a month on finishing the work myself, because the first week post-layoff was spent taking a break and decompressing.

Now I’m ready for another break, of sorts: I’ve done very little hiking in the past month, because I’ve been preoccupied with playing home handyman. Right on cue, it looks like we’re heading into a rainy spell, which may well end up being the end of the summer dry season. Oh, well; so it goes. Hope the early rain makes for a good mushroom season (last time we had a lot of rain in early September, it was epic).

Published at 14:01 on 24 August 2015

1. Homax (the main brand aerosol texturing compound) is very touchy stuff. Changes in temperature or the pressure of the propellant in the can radically affect the texture you get. This means: a) always do a test coat on cardboard before using it; just because you got the nozzle adjusted properly yesterday doesn’t mean you will get the same texture on the same setting today; b) because of all the test coats you make, don’t expect to get anywhere near the patching coverage advertised on the can, c) you’ll have to throw out the can before it’s empty, because it will get to the stage where pressure is ramping down so fast that you can’t get consistent results even on a small patch.
2. All the above said, it’s still much cheaper to texture your own patches than to pay someone else to do it.
3. The water-based texturing compound is to be preferred. Not only does it stink far less, it dries slower. If you get a nasty surprise, it can be scraped off before it dries with relative ease.
4. Premixed mud is easier to use than trying to get all the lumps out of some powder you have to mix with water.
5. That said, there’s reasons to fiddle with the powder. For openers, quick-setting “hot mud” is only available in powder form. I just bought a bag of it to do the last two patches in my house. Reason: they’re high up, and I had to rent a large step ladder to reach them. Thus, the bother of mixing my own and the expense of buying another kind of mud (when I still have plenty of premixed left) pays for itself because I’ll be able to return the ladder far earlier.
6. Hot mud is quick-setting but not quick-drying. I.e. when it first sets it will still be damp, and you won’t be able to sand it without your sandpaper quickly clogging. It still takes 24 to 36 hours for hot mud to dry. The solution is to use a drywall knife or paint scraper to shave excess mud off. Save sanding for the final step, after it’s all dry.
7. Be sure the mud you buy has the words “lite,” “light,” or “easy sanding” in it, particularly if it’s hot mud (which is notorious for setting up as hard as a rock otherwise).
8. Hot mud comes in various set times, from 5 minutes up to 90 or more. I chose 45 as a compromise between being able to mix it and work with it without feeling rushed and rapid turnaround for the next stage.
9. To the best of my knowledge, hot mud is only available in ridiculously large batches. I had to buy 18 lbs of powder, of which I will use only a fraction. (But, to reiterate, that expense still paid for itself.)

Published at 10:35 on 20 August 2015

I’ve actually had pretty good luck doing my own drywall patching so far. I’ve learnt three significant secrets:

1. If you’re not a pro, you have the choice between doing a slow job or a bad job. Naturally, the former is by far the better choice. So expect it to take a while. Applying the mud isn’t easy and will take some time for each coat. Often, you’ll botch it right near the end and basically have to start over. That’s OK, you’re not a pro. Just try again. Moreover, don’t think you’ll get things finish-ready after feathering out three or four coats; expect several more touch-up stages. Expect to do a fair amount of sanding. It’s taken over a week for me to complete each patch (largely because I have to wait at least 24 hours for the mud to dry between each stage).
2. With practice, you can learn to remove mud and leave a decently-neat surface. By contrast, it’s virtually impossible to apply mud neatly. Even the pros don’t attempt that. If you watch a video of someone finishing a drywall patch on YouTube, you’ll see that what they do is apply significantly more mud than is needed at each stage, then carefully remove the excess to leave a neat surface.
3. One of the most difficult patches is an interior 45-degree corner. Unlike 90-degree corners, they tend to be gradual and not sharp. Not only are there no tools out there to directly form such corners, trying to form one freehand with a straight knife is (by contrast with a sharp corner, which is tricky but doable) virtually impossible. The solution is to make your own tool. I used a piece of thin, stiff polystyrene cut from a salad mix container lid. I took care to cut one edge as straight as possible, then curled the plastic as I held it, making a gradually-curved edge to use to smooth the mud and make it match the existing corner curvature.
4. It’s also exceedingly difficult to match texture. It’s noteworthy that many pros don’t really attempt to: their solution to patching a textured wall is to sand and retexture the entire wall. But I took it slow and blew a good chunk of my can of texturing compound just fine-tuning both the texture setting and my technique (I textured scrap cardboard cut from old boxes). While my two completed patches don’t match perfectly they do match closely enough that I basically have to know where the patch is and get a foot away from the wall to discern the difference. That’s good enough for me.

Published at 22:32 on 19 August 2015

In case you’ve been living under a rock the past week, it’s here. Basically, it’s nothing I don’t already know.

I actually applied for a few Amazon jobs once, and got phone-screened. It was clear from the phone screen it was basically the sort of place described in the article, and that was the end of my interest in working there.

Moreover, I live in Seattle and work in the high-tech field (when not between jobs, as presently). As such, I’ve had the chance to meet many ex-Amazon employees. They’ve all described it as basically the sort of place the NYT described.

There’s been some talk that like it or not, this makes Amazon the workplace of the future. Maybe. First, nothing is set in stone. Many people hate workplaces like that. It’s therefore likely that persisting in treating people that way will produce some sort of blowback.

Maybe it will be legal, via the political system (stricter overtime and leave laws). Maybe it will be via private actors legally exerting their pressure (e.g. worker choosing to organize a union). Maybe it will involve illegal but nonviolent actions, like sick-outs, blockades, or sabotage. Maybe it will be both violent and illegal (a workplace shooting or three). Maybe one or more of the above.

Second, the more it happens, and the more unstoppable it at first appears, the more it will radicalize people, because the more it will prove the old claim that capitalism cannot be reformed and naturally wants to revert to its sweatshop ways. I.e., the longer the blowback takes to appear, and the more frustrated it initially is, the more likely it is to become vigorous and militant.

Requiring people to give up their lives for a company that doesn’t much care about them and is set on mercilessly weeding them out is fundamentally inhuman and degrades the worth of the individual. It is at variance with centuries of post-Enlightenment progress in the other direction, towards greater valuation of individual worth.

Amazon should, in other words, expect resistance.

Published at 10:55 on 19 August 2015

I’m seriously pondering adding a new category and recurring feature for sleazy recruiters to this blog. It would be restricted to obviously sleazy recruiters. Even though my experience indicates it’s generally a sleazy crowd, an individual recruiter would have to demonstrate actual sleaze to be listed.

Examples would include:

• Misrepresenting a job to me (in the rare case where I follow up and am in a position to learn this),
• Misrepresenting me to an employer (again in the rare case when I follow up),
• Spamming me about a job that in no way relates to my experience,
• Spamming me about systems administration jobs in reference to résumés which explicitly rule such things out (as some of mine do).
• Spamming me about jobs that are not in the Seattle area, despite all of my résumés indicating I am not willing to relocate.

I’m still pondering it, but leaning towards actually doing it. I plan on naming names, both firms and the people at them who spam me. So long as I report accurately, this is not libel (which has to be both false and disparaging, mere disparagement does not count).

Because, if you don’t want people to make disparaging speech about your business, you shouldn’t act in ways which, if accurately reported, harm it.