Tag Archives: Geek stuff

Touching yourself

That should bring the pr0n spammers around.

More accurately, the title of this post should be “NOT Touching Yourself”. Or “Wear gloves when working with chiles”. As in, don’t touch your face (or any other area) when you’re working with chiles and not wearing gloves, no matter where they fall on the Scoville scale.

In other news, we had almost an inch of ranch at the ranch this afternoon, with some giant cells moving over us. Huge thunderous roars came from the sky as it opened up on us and provided a light show.

I used Movavi* to do a couple of repeat clips at the end to show it in slow motion and then again in super slow motion. Very lucky to catch it, and it is awesome.

*No, Movavi does not pay me, and that is not an affiliate link. I have access to Adobe’s Premiere Pro, and that is a fine product, to be sure. But I don’t really have the time to spend figuring out everything in it when I can just slam some clips into Movavi, do a rough edit, and be done. I also have to redo all our tutorials on the “real” business side, as those are woefully out of date with the design they contain, even though the various functions operate mostly as they used to. Just another item on the todo list, which never goes away.

Until next time, peeps. Be well.


Plans, we got ’em

This weekend: probably more on this server thing, but thankfully that is coming to a close, at least as far as our involvement goes.

Other plans: pepper picking time! The cayennes and paprikas are nice and red  – I noticed while getting some mowing time in. That means harvesting, washing, splitting, and drying. It also means a house full of the smell of drying peppers, which is usually not that bad, although there are times when the smell – of that or any other food – is nauseating to me.

I’ll also be making broccoli cheese soup, because I am getting kind of tired of shakes and formula. If things (like my back) hold up, I might even make some cheesy potato soup (with crispy ham!) as well.

And another trip to the NOC, to set up a machine for someone who is upgrading his existing server to a big dog machine, so that is one ray of sunshine in an otherwise shitty and even more sleep deprived than usual week.

On a completely other note, meteorology really is one of the few jobs that you can be consistently wrong and still have a job. Today’s forecast: no rain, at all. Literally, a 0% forecast. Then a nice cell rolled right over us and brought about .2 inches of rain. Not a lot, and better than none.

Also on the menu for this weekend: taking stock of my sad, sad tomatoes, seeing what can be recovered, going through my seeds and finding some short maturity varieties to start another flat, and, of course, weeding. The weeds are not as bad in the frames where we’ve gotten the plastic or the weedblock down, but the edges are a nightmare because of the bowing of the frame edges (to be fixed in the fall, because that’s a heavy duty job). It’s also time to feed the bees again: the other day, I added additional brood boxes to two of them, so they are making progress.

Right now: more database wrangling, and then a brief stop for a nap before getting back up and doing more.

Until next time, peeps: be well.

It builds character

Stressful/rough times. Isn’t that what “they” say, whoever “they” are?

Day four of server recovery. Every single tool we generally use, whether main or fallback (and I’m talking about actual scripted code for processing) is hosed.  So, once again: no writing. Instead I will be manually creating a server’s worth of accounts on a new server, then manually creating archives of user content, database, mail, mailing lists, forwarders, and every single other thing that an account requires, porting those over to the new server, and manually unpacking everything.

Fortunately, a little bash know-how allows me to set off a series of commands to, say, crunch all the /home directories of the users without me having to babysit that or having to do them one by one myself. Ditto for databases. The most tedious part is going to be to recreate the database users to add them back to each user’s databases based on the config scripts I’ll have to manually track down within their site files.

It’s going to be a long day. And a day when I could be outside working, too – mowing, pulling weeds. We got about .3 inches of rain late yesterday afternoon, so that was good, but naturally it starting coming down when I’d already decided to water the gardens. Today through Saturday, it’s supposed to be clear, or at least partly cloudy. Guess I’ll try to get some outside time tomorrow and Friday, mainly for mowing. The chicken yard and the west yard desperately need a trim, as it’s now been three weeks. And then by the time I get those done, it will be time to start all over again in the front, which I mowed last Friday. The grass down here doesn’t need a ton of TLC to use any bit of rain plus the dew every morning to shoot up like a teenager going through puberty.

But I’m hoping to get some writing on those mornings while waiting for the grass to dry so it can be mowed. Cutting wet grass is really a no-no and shouldn’t be done unless there’s some urgent need to do it. Back to the point: this morning on my third natural wakeup call from my insomnia, I hauled myself out of bed. That was at 6:30 AM, within my target/plan of getting up anywhere from 4:30 to 6/6:30 or somewhere in there. That new habit forming routine is underway well, I think.

More later, peeps. Be well.

Good morning campers

Our recovery of nameless guy’s server continues today, but I did implement part one of my overall plan to get some writing time.

See, the thing about owning a small business in the field I’m in is that not only is it very unpredictable, but sometimes it takes more than one day. It can take dayS, plural. We are in day three of this specific issue, and still going.

Fortunately, right now does not involve a ton of hands on for me while we wait, so I’ve been able to knock out a few other things that also need to be attended – payroll, for instance, since my employees don’t work for free, the bastards, and payroll taxes, because neither does the IRS or the country. Other “real” work things has filled the nooks and crannies, and I believe I am caught up in the routine, day to day things. Yay!

So maybe it’s time to type a few sentences into Scrivener and move that few footsteps closer to (one) goal. Progress is progress, after all.

More later, peeps. Be well.

The plan was

To write. Because it’s time to, as Neil Gaiman says, make good art.

I’d been moving sites around as we retire older servers, and finally got to bed this morning somewhere between 4 and 4:30. A few hours later, I get a notice to my phone about a customer server. Nothing is responding. I try to log in, get a login incorrect error. Huh, that’s weird, the client is unlikely to have changed the password without telling us. I try it again, same deal. Well, hell.

So by 7:30, I’m up and around and chatting to the client, and something very bad has happened – I won’t go into details except to say it is something so bad it makes your heart stop. The plans to write this morning and perhaps a second, smaller session this afternoon? Gone.

Off to the NOC to do some recovery on this client’s server. Spend a large number of hours reviewing the damage. Build a new machine because all his sites have to be transferred off the existing one. Deal with other client stuff throughout.

Finally, I’m shot at about 2-3 AM or somewhere in there. Crash out, wake up again at 7:30 (I am now typing this on Monday, the next day here), realize I have to go get blood drawn to check various things, drive out to the hospital (again) where I was in the ER back in February to get my records for that visit, as two previous requests to relay those records to Mayo resulted in the records not being sent because they didn’t have my fax although the transmission was good, then the records not being sent because the form I hand delivered to them, in person, wasn’t done (and a bonus: they lost my form and couldn’t find it when we called asking them where the records were), and then to Publix to pick up my meds.

Off I go right out the door, because the bloodwork has to be fasting. Do all of these things today, and I am back, in my chair, at my desk, at 10:50. That is not bad at all, and shows that focused work can be truly productive – and those tasks involved other people, as well. I wonder how much writing I could get done in three hours without people (real people, anyway) being involved in things I need to get done.

Sine we’re still dealing with this server, and some defacements of pages, and because I had to mow beeyard #1 as it hasn’t been mowed in three weeks, and because I needed to feed the bees and add a second brood box to one hive, and because work has been a steady drip, drip drip of things going wrong for people, no writing today. In fact, right now I am very sleepy, and if I didn’t have to transfer this guy’s sites off his server to the new box, I’d probably go hit the sack for a bit. I actually may not do that immediately, but run something that I won’t go into detail about, and then transfer the sites after that.

Now, I wait for something else to finish on that server, and I have titles popping in to my head, so I’m writing those down. Something productive in the writing arena after all! And the day has been productive otherwise, even if it seems like treading water.

Treading is better than sinking, though.

More later, peeps. Be well.

Moving day

No, not me. Late Saturday evenings are for the heavy lifting of maintenance, including server moves, which is what I’ve been doing for hours now. People who don’t work in tech don’t realize that probably a third of your time is spent waiting for something: waiting for a copy to finish, waiting for a compile to complete, waiting for a server to reboot after a new kernel is built, waiting for someone to reply to the question you’ve asked them.

A funny: a “webmaster of x years” (x = more than two decades) spent “two hours” trying to configure FTP, couldn’t connect after figuring out what to use like on ALL other systems he uses, which of course were MUCH easier to use, finally managed to get connected to find NO files listed when he KNEW there were files under the account, and WTF don’t we have the configuration information on the page for the FTP accounts, huh? I got to point out that clicking on the handily named “FTP configuration” link RIGHT NEXT TO the FTP account he created had the configuration information listed, that he had been unable to connect because he was using “user@domain.com@domain.com” according to the logs, and that he configured the FTP user incorrectly, assigning it to its own, restricted, directory, and not the directory with all the files in it. I didn’t bother to ask WTF he spent “two hours” trying to figure it out when he could have just opened a ticket and had a reply literally within minutes, as he did with his whiny list of trial and tribulations he was going through. As of right now, almost two days later, he has not responded to our last reply, nor has he corrected the incorrectly configured FTP user as per the instructions I laid out. And what’s absurdly remarkable about all this: he has the actual user’s master username and password. I wanted to ask him WTF he was bothering screwing around with a secondary FTP user when he could just log right in with the master username and password. Problem solved, in two minutes, not two hours of dumbassery.

This is why we use lots of quotes when someone claims to be a “webmaster” of x years, or a “developer”, or an “IT person”, or a “network engineer” – the latter are amusing when they insist there’s an issue with the network (because of course, they are a network engineer, far more skilled then we are even though they know nothing about us) because look at this trace and this ping from my computer and my cell phone can’t even pull up my site, so your whole network must be down, you suck! It’s fun to tell them they triggered the firewall because they tried to access the control panel on the wrong port, having transposed the last two numbers, and perhaps untethering their phone from their home wifi network would yield a different result if they in fact triggered the firewall in the future at some point, because then they would be able to check their site from a network unrelated to their home system.

Thus ends my mini rant about clueless people who proclaim themselves to be experts on something. I find that the louder those people speak about how many years they’ve been in x, or how they hold a high position of y in some random company, the less likely it is that they know what they’re talking about, and they will probably be among the rudest people we have to deal with in any given day.

Until next time, peeps. Be well.

Crawling out of timesinks

As I said yesterday, I made a massive shift that gave me time I could assign to something else.  What was that?

I shut down pretty much all social media.

Now, to be fair, I was most active on facebook and twitter, with a small dabbling in instagram from time to time, and those three are the biggies, name recognition-wise. But I got sick and tired of facebook, and deactivated my account there. As a result, I have quite a lot more time to pursue other things, because those “I’ll just spend ten minutes checking out facebook” is never really ten minutes. You look up, and suddenly you’e been checking it for an hour or longer, wasting time that could be better spent on other pursuits.

I still have a page on facebook, since publishers expect writers to have a “platform” (and let me tell  you how I want to launch that phrase into the heart of the sun). Before I deactivated my primary account used to create that page, I created a new account for myself that follows nothing and friends no one. I then passed administrative duties for the page from the account I used to this new account that I do not use except to manage that page: an object lesson in how to both have a presence and not have a presence on facebook.

That was followed next by twitter getting the heave-ho for the most part. I created another twitter account to use as my author account (for branding purposes, of course).   Under that umbrella, I can do the author update thing now and again without spending hours at a time on social media throughout the day.

So, while I know that it’s necessary for me (the artist) to have a presence on these outlets, it really is not necessary for me (the person) to have one, and now I basically don’t. And I’m ok with that.


No, not those kinds of hotties, you pervs – get your mind out of the gutter!

I’m referring to this sort:

This was just before 3 PM local time, with a temp of 93F and a heat index of 110F. You know that phrase “It isn’t the heat, it’s the humidity.”? This week has matched that phrase. This morning I popped out to the beeyard to check a few hives to see who needed a second brood box and to generally make sure there were a good number of bees and stores in those hives. At that time, about 9:30 AM, it was already 84F with a heat index of 92F. I was so soaked with sweat when I came in I had to change all my clothes. It was like wearing a swimsuit, and I had to peel all my clothes off my body, they were that soaked – including my socks.

But that’s ok. This is Florida, after all, and while some days are not all that pleasant, I expect this, and I chose to live here. Making it through the summers is my version of climbing Everest: how far can I push myself without keeling over?

I rolled out of bed at about 7:30 this morning, and this is what greeted me:

Foggy morning at the ranch, which turned into a burner of a day. It all burned off by the time I went out to the bees, and then Mother Nature did her thing by bringing the heat.

The gardens are still a work in progress, and there is still more work to be done. However, each year, I keep refining the processes out there, and I think next year will be even better because of the changes I have in mind. That refinement is what I’m trying to do in other areas of life as well, from outdoor work to the helpdesk where a new user accused us of selling his email address to spammers. He had registered a domain, and naturally, since WHOIS information is public, and the spammers watch new domain registrations, he started getting spammed. He also told us this was “very unprofessional”. I counted backwards from five, then pointed this fact out to him and offered to use our masking info for the domain, so that we would get the spam and the phone calls. He took up that offer. Problem solved, and for me, no being pissed off because of the rudeness some people shoot our way for no reason.

I’ve now posted to the blog here daily since the 24th. It’s a start, and helps me get into the groove of making writing a habit. It occurred to me that I wasn’t making writing one of my top priorities, being too busy with the business, doctor visits, and so on. I made the decision to make it a priority, just as the business, my gardens, and my bees are. I had started a web site as a hobby type of thing, tracking deaths in any given week, I realized that was a major timesink, since I had to pick from the lists, then go do research to build the short blurb I’d give to each. That one had to go, because it took away time I wanted to assign over to my writing instead.

There’s another major shift I made that freed up a ton of time. But that’s a story for tomorrow.

Be well, peeps, and I’ll blather more at you soon.

Updates, updates

I told myself to get back into updating ye olde blawg daily, to get me in the habit of writing something daily, which I tell myself will help with the actual writing I am supposed to be doing on anything real – any of the ideas I have rolling in my head for novels. Which, I should point out, I have actually gotten some  “here’s how the story goes, generally” notes down for, like this.

And right at this very moment, it all really sounds like total bullshit to me, probably because I let some asshole annoy me with his stupidity and then his panicky bullshit because he couldn’t be bothered to take ten seconds to think about something before completely freaking out. Likewise, his passive aggressive bullshit afterward didn’t do him any favors in my eyes.

I really wonder about someone who can’t quite get to the idea of choosing “settings” as the place to make a change in the app he’s using. It occurs to me that this is the kind of person who would gnash his teeth and rend his garments and wail about how he doesn’t understand anything about anything, and – in his own words, in not one, but two tickets – he’s now “fucked” and “screwed”, thereby ensuring that someone else will easily fix (because it was an easy fix) whatever it is he’s too stupid or too lazy to do in addition to him pissing off whoever has to deal with it.

So now that I’m typing this, guess who just found himself in a list of people in my head who will make appearances in the books I will write?

Since this guy is so terribly incompetent, he certainly can’t be the bad guy. You can’t really have an incompetent villain carry an entire book – well, I take that back, you can, but the book would not be very good.  I have read many books where the bad guy is so stupid, careless, and/or lazy that he should have been tripped up and strangled by his own shoelaces, yet the hero (male or female) is not able to figure it out for 300 pages.  That says something about that hero, too, but that’s something for another day.

No, this person will be a victim. Not someone that’s particularly going to be missed. Not someone who is a pillar of a community or an underthanked martyr, giving up their time for those less fortunate or privileged than they are. No. Not this guy. While I’ve been typing this, ruminating on the vagaries of dealing with people like this both in and out of the tech world, it came to me that I have the perfect spot for him. He’ll be a throwaway character with some very bad habits whose excuses have gotten old to those who have loaned him money and whose time has come to an end. It’s actually the first scene in one of those books up there. In my mind I had written that scene and the soon to be victim mans up, understanding his fate and resigning himself to it, but as I consider it now, I do believe that he will instead be a whiny, pathetic loser, paying for the problems he brought on himself – not paying in money, but with something far more dear: his life.

And now, having typed all that up there, I feel a bit better, and not like I despise the entire world because this one douchebag caught me up at a bad time.

By the way, those papers in the top image? Each one is a different story. This is how backlogged my brain is.  I have four different series characters, a fantasy trilogy, one standalone non-genre book, and one that I haven’t classified as yet, all hanging out in the idea lounge that is my brain, and all hanging out as a short description of what each of those books is about. I have to go update my author blog now, then post the same thing to my facebook author page, and then tweet the link to the blog – because authors these days need an “author platform”, a term that irks me almost to the same extent as “I know, right?”, “That’s what she said.”, a “You know” after every sentence, and “Because (something).”

Thus ends another blog post. See you tomorrow, peeps. Be well.


No problem, Mr. “Network Engineer”

You know what experienced techs think when you feel the need to insert “I’ve been a (something – in this case a “network engineer”) for 25 years.” after you’ve described how you “solved” a problem in a manner that shows you don’t know jack shit about what you’ve just described? Let’s just say there’s a reason we have compresses for excessive eye rolling and why we put quotation marks around things like “network engineer” or “developer” or “IT guy” or whatever else it is you think is going to impress us. It isn’t. We certainly hope whoever is paying you isn’t paying you much. But if that’s what helps you sleep at night, go right on ahead and demonstrate your vastly superior knowledge while at the same time showing that it literally took you all day to “fix” the (non) issue. Well done.