cellio: (Default)

A (newer) coworker asked if he could pick my brain about a certain part of our product. Sure, I said -- and I asked some questions to figure out what he already knows (or doesn't). We chatted a bit, and then I said "Ok, I have some homework for you -- please read X and Y before we talk".

He responded with "pop quiz next Wednesday at 3".

So I scheduled the meeting. I mean, wouldn't you? :-)

cellio: (Default)

Working from home seems to be mostly going ok for my company. We have several standing "coffee break" video chats each week for the human connection and are using video more for other meetings. We have learned how to add custom background images to Microsoft Teams and this is a source of amusement. (I would like to find some from Babylon 5, particularly images from (a) Minbar and (b) inside the station, but have had no luck so far.) My team has a new person who started a few weeks ago, so he started in quarantine and hasn't yet been to the office. I'm his mentor, so I'm trying to make sure he's getting all the support and human connection he needs. The situation seems roughest on the people who live alone, though the ones with small children at home have challenges too. I'm fortunate to have Dani and the cat.

I have read a little more fiction than usual, some of it made available for free by authors because of the quarantine. Thank you! One that I just finished is Dragon of Glass by Zoe Chant, a delightful, lightweight novel about a transplant from another world and the woman who released him; watching him try to fit into our world is a lot of fun. Tor is making the Murderbot novellas available this week for free (leading up to a novel release next month); I'd read the first a while back but hadn't read the others yet, so this is good timing. I also have a gift waiting from a Kickstarter for a different book (while you're waiting and stuck at home, here...). I also just read (not free) The Body in the Building, a novella by a friend and fellow SE refugee. The point-of-view character is an architect who discovers problems with a major project, and then discovers that those problems were only the tip of an iceberg of bigger problems... I figured out the mystery before the reveal but also fell for some misdirection, so neither too easy nor too hard.

I have been spending more time in the kitchen. Yes I'm cooking all our meals at home aside from very occasional takeout from local restaurants, but also: with the food supply being sometimes erratic, I've upped the produce deliveries and am doing some low-key preserving. I've never canned and don't have the equipment, but I'm pickling things (to refrigerate, not shelf-stable). So far I've pickled eggs, beets, cauliflower, and jalapenos, and will do some carrots next. I also plan to dry some fruit, dried fruit not requiring refrigeration. (I'm trying to keep the fridge full.) I haven't been able to get bread flour since Pesach ended, so I guess I'll try making bread with all-purpose flour. (Also haven't been able to get rye flour.) I would like to get some more seedlings for container gardening, but I don't know if I want to go to Home Depot for them and nobody delivers. (Insert rant about how Home Depot gets to sell plants because they sell stuff for home repair, but local nurseries had to close.)

Someone I know indirectly from Mi Yodeya suggested a book and a series of videos on Reb Nachman that look very personally relevant. (I've read one chapter of the book and seen one of the videos so far; more soon.) I joined an online talmud class (by R' Ethan Tucker of Hadar). A friend pointed out to me that since we're all stuck at home anyway, synagogues in other cities are just as available to me as my local ones. There's one in DC that seems like a good fit for me. Closer to home, my synagogue's two rabbis and cantor each hold a weekly open chat on Zoom, so I'll get to see my rabbi that way tomorrow.

Our choir director sends out daily music selections with accompanying (short) history essays. I'm enjoying these.

I have barely watched any TV.

cellio: (Default)

Last week the director of engineering sent email announcing prizes for an "improve our tests" hackathon. He labelled one prize (about finding and fixing the most bugs) as "write yourself a minivan".

Later, in response to questions, he sent a copy of the 24-year-old Dilbert strip.

Over the weekend our CTO, in response to questions, sent email explaining what a minivan was.

I'll be over here, weeping into my prune juice and yelling at kids to get off my lawn.

cellio: (Default)

Yesterday, a delivery person came to our office door asking if so-and-so worked here -- he had a package that omitted the company name, so he wasn't sure where to deliver it. The package did have the suite number on it, which got him to the right floor, but he helpfully pointed out that none of the doors in our building actually have numbers posted on them. Huh! He's right!

After he left, I took a post-it note and a marker, wrote "suite #" on it (with our number), and stuck it to the wall next to the door at eye height. (The door itself has a company name at eye height.) That was a patch.

Today someone else printed a sign with a nice, large font and taped it to the door under the name, taping on all four edges to increase its durability. That was a fix.

If somebody else decides to make it pretty, with a splash of color and art, that will be marketing excess. :-)

cellio: (Default)

Last week I was at corporate HQ, where the rest of my group is, for a few days. Everything about the trip in on Monday was a model of efficiency -- the plane got in early, getting off the plane was faster than usual, Uber came right away, traffic was light -- so I got to the office about half an hour earlier than any of us expected me to.

Given that, I was a little surprised to be greeted with "oh thank heavens you're here!".

The previous weekend there'd been a catastrophic power failure and many of our servers came tumbling down. (I didn't hear the gory details. We have what I understand to be the usual precautions, and yet...) The small team responsible for that infrastructure was understandably frazzled. My teammates were happy to see me because the (internal) documentation servers are not managed by that team but by us. But their main custodian, G, was on vacation, and another person who knows relevant stuff, J, was on vacation, and that left me. I know some of the systems well but not others -- which put me ahead of anybody not on vacation. Okay.

Our doc infrastructure team has two newer members, an experienced writer who joined the company last fall and a recent grad who joined the company last month and the infrastructure team a couple weeks ago. The former has been focusing on git as my backup, and the latter is solidly in learning mode.

So first we did the usual dance of "this is not the right dock for my laptop / these are not the right monitor cables / why TF can't Windows see both of these monitors? / network, we have network right?". Once I could actually use my laptop, I settled down to investigate -- with the two newer team members watching everything I did and taking notes. It was kind of like pair programming, I think.

I think one of the most important technical skills one should have is debugging or diagnostic skills, so this is what I set out to teach my coworkers -- not explicitly, but by narrating the whys of what I was doing, I realized that this is what I was doing. There was plenty of backtracking, but they learned why I did the things I did even if they didn't turn out to be the right things. Like when I used ssh to connect to the server, got wonky display stuff, and realized I was talking to a Windows machine -- oops! And, err, our Windows server has sshd running on it? Today I learned. (Switched to remote desktop after that.)

The web server isn't responding -- well, is it running? The process list shows httpd; ok, where on this machine is the web server running? On Linux you can easily get the path for a process; on Windows I saw no way to do it, so off to Google and the right search terms, which took me to an answer on Stack Overflow (naturally), so that got me to the right directory and thus the server logs. At one point somebody said I must know a lot about web servers, but actually I don't -- not modern ones, anyway. But I know how to look for stuff, including response codes in the server logs. (Which told us that the server thought it was serving content just fine, even though the browser was getting errors -- even a local browser.)

There was a lot of this sort of digging. The web server was particularly mysterious because, it turned out, it was serving some content just fine but not most of it, and a chunk of our investigation revolved around unsuccessfully trying to find differences among those cases. We noted and otherwise ignored, for now, that builds were running slowly -- running is better than not running and, well, priorities. Eventually we split up and my teammates did some exploration and experiments on their own, coming to me with questions when needed. They had good instincts, yay.

We were not able to solve the problem with the web server that day. We were able to characterize some of it, but we bumped into the wall of specific missing knowledge. I wrote up what we knew and where we were blocked for the infrastructure list, and we decided that we could live with internal builds being down for a few days, we were not going to bother G on vacation, and we've identified some areas where we need to improve our internal documentation. (We do have internal documentation and we were consulting it. But there are some gaps, we learned. That happens.)

We had a team outing planned for Wednesday that G was going to be able to join us for, and everybody agreed not to say anything about this to him because we didn't want to ruin his vacation. But Tuesday night he checked email to confirm plans for the outing, saw the email thread on the infrastructure list, and fixed it.

He'll be back tomorrow and then I can ask him WTF is nginx. (I mean ok, I googled, but I have no real idea how it fits into anything on this server.)

cellio: (Default)

I visited our main office for a few days this past week. (Sorry to folks I didn't connect with.) I met our two new team members, one of whom is our new manager, and our intern for this coming summer, and I had lots of productive conversations. I also played one game of Caverna with coworkers.

I wondered what airport security was going to be like given the government shutdown. Monday morning in Pittsburgh the line was probably about 15-20 minutes long, but somebody came by to tell us the alternate checkpoint was open and had no line, so some of us went there. All of the agents I saw were polite, professional, and not acting disgruntled. I and several other passengers thanked them for being there despite the situation. Everybody there understood that the mess was not the fault of anybody there and taking out frustrations on the wrong people would be bad. Yay for people acting like adults!

Thursday night at Logan, the first checkpoint I found was closed but the second was staffed. It took me five minutes to get through. Again, people behaved themselves.

Wednesday afternoon our new writer and I took a walk through a park/wetlands area near the office. We saw lots of ducks and one heron. We later saw the heron catch a small mouse; I hadn't previously known that they ate mammals.

photos )

pick one

Jan. 12th, 2017 09:29 pm
cellio: (demons-of-stupidity)
A Glassdoor review of a former employer includes these two bits:
Pro: You can get lost in the masses with over 90,000 employees. Great for under-achievers.

Con: Lots of dead wood.

C'mon, pick a side. :-)
cellio: (avatar-face)
As I gather is increasingly common in larger US companies, my employer tries to entice people to actually get annual bloodwork by offering a discount on insurance to people who cough up some basic stats -- cholesterol, blood pressure, blood sugar, and a couple other things. (Assurances of confidentiality are made; cost-benefit analysis is left to the employee.) I had a physical recently, so I collected the data in case I want to use it later.

I noticed, after the call from my doctor's office, that he hadn't given me one of the required numbers, so I called back to get it. Oh no, he said, we don't routinely test blood sugar any more, because insurance companies don't cover it as part of preventative care. So he'd have had to charge me for that, and since I didn't present any relevant symptoms he didn't pursue it. I hadn't specifically asked about it up front, so I'm not faulting him for this.

But let me see if I understand this: my employer's health insurance will not pay for a test that my employer's benefits department wants me to obtain. Er, right.

I pointed out this gap to a coworker, who said that as these things go, this is one of the easiest problems to solve on your own: find a diabetic friend and ask to borrow a glucose meter. Yeah, I guess that could work. I can also (since I don't work at the main office) order a do-it-yourself test kit at no charge, but I begrudge the extra hassle (and needle-stick) when my physical was supposed to take care of this already.

But that's all assuming I'm willing to share this data. I haven't decided about that yet; it's a little creepy, and I might be willing to pay a slightly-higher price to retain that bit of privacy. Really, why do they need to know? Wouldn't a receipt from my doctor saying "yeah, saw her this year" be enough?

an outing

Oct. 7th, 2015 09:14 pm
cellio: (avatar-face)
Our director of engineering paid a visit to our local office today. The meetings were productive and didn't have too much growling and snarling.
photos )
cellio: (out-of-mind)
My employer provides free drinks, including soft drinks, but because ours is a small office we have to do our own buying. When supplies get low somebody goes to the store, which requires carrying cases of pop a couple blocks. Particularly during the winter this sometimes broke down, so that got us to look at options.

It feels wrong that it is cost-effective to buy our drinks from Amazon. That really shouldn't work. It can be less expensive to buy locally if there's a sale, but otherwise it's a wash -- and an Amazon box comes to our door.

Huh, weird.
cellio: (moon)
One day last week on my way out of the office, I encountered a pair of college-age women who looked a little lost. One politely asked if they could ask me something, so I said sure. (Cue ominous music.)

Her question: did I know where in the bible it says that God is female?

I said that no, it doesn't say that, or at least not the Hebrew Bible -- what any other books might claim is neither known nor interesting to me -- and that God doesn't have gender; grammar does. She then took a weird turn, talking about how the word "Elohim" (one of the words for God) is plural. I never did learn, during the conversation, where she was going with that. I told her that while the word has the appearance of being plural it is usually singular; for example, I said, in the very first verse of Genesis, we see that noun paired with a singular verb (and that continues through the rest of the creation narrative). I taught her as much Hebrew grammar as I could explain while standing on one foot.

She then said something like "but Genesis says 'male and female he created them, in his image, in his likeness' -- so God must be female too". I happen to know the Rashi on that and responded that God, master of the universe, is surely not limited by physical form, so "in his image" and "in his likeness" must mean something else, and gave Rashi's answer.

Soon after the conversation started to go in circles. She pulled out her phone to show me the verse in English (might have been King James; not sure); I pulled out my phone and said "let's look at that in the Hebrew, shall we?". The other person spoke for the first time around this point, saying something like "oh, are you Jewish? We have great respect for the Jews", which is usually a Christian lead-in for "but they've missed an important message", so I said that yes I am, sorry but I do have to get home, and good luck in their quest for knowledge and do check out the Rashi I mentioned.

I suspect that the one was tutoring the other in missionary work. It looks like they both need some more practice. Meanwhile, while I did a decent job in the counter-missionary role, I clearly didn't convince them that they were mistaken in the five minutes or so that I was willing to give this.

That was Wednesday, I think. Then tonight I came across this question on Mi Yodeya, which asks about the word "Elohim" being female, and that question links to a Christian video making an argument that uses these elements (arguing that there must be two gods, and the male one made Adam and the female one made Chava, err, Eve), so I see the connection they were failing to make now. It's still utter nonsense, but at least now I know the nature of the utter nonsense.

A comment on the Mi Yodeya post says the group behind this idea is actually a doomsday cult, but I'm not curious enough to actually research that.

I work in a usually-staid office building -- not a place I expect this kind of encounter.
cellio: (avatar-face)
Message from landlord: "In accordance with city ordinance blah blah, we will be conducting a mandatory evacuation drill on $date at 10AM."

Implied message from landlord: "Unless you particularly want to walk down 43 flights of stairs, that might be a good day to make other plans."

Unknown: whether the latter was intended -- fewer people in the building means fewer people who can mess up a compliance-check, after all. Though this would have been more plausible if they'd called it for 8AM rather than 10.

On a tangent, I wonder how people with mobility impairments get out of office buildings during alarms. There's no job-related reason I couldn't have a coworker in a wheelchair, after all, so somebody must have thought this through. (Please let somebody have thought that through...) Do they keep an elevator in service in that case (even though elevators are normally disabled during fire alarms), or is the floor warden responsible for rounding up people to carry the person downstairs, or what?
cellio: (tulips)
Two items seen in rapid succession today:
  • Here's why you're not hiring the best and brightest: (Jeff Atwood) talks about making telecommuting work so that you really can hire the best employees, as opposed to the best employees willing to live in a particular location. I once applied for a telecommuting position at a company that seems to get it as far as that's concerned, and a lot of the stuff they do is reflected in this article.
  • What do programmers care about? (20-minute video): Joel Spolsky (Stack Exchange, Fog Creek) talks to recruiters about how to recruit programmers. If you've read Joel On Software you already know a lot of what he has to say here, but I still found it interesting to watch.

Can you help? Somebody asked a question recently on Writers about guidelines and heuristics for when to use screen shots in technical documentation. The question isn't looking for opinions or what you, personally, do but, rather, formal guidelines along the lines of what GNOME does for its documentation. So far it's only attracting opinion answers. I, too, have opinions and practices that I follow, but I can't source them either and I'd like to see the question get a good answer.

Speaking of Writers, I wrote a little something about writing good API reference documentation (like Javadoc), based on advice I've given informally over and over again -- finally wrote some of it down in a public place. Feedback welcome.

I recently saw an article with interesting-seeming observations and analysis of Modern Orthodox Judaism. I'm not all that tuned into the MO community and can't evaluate its credibility from inside, but I found it an interesting read. If any of y'all would care to tell me where on the spectrum from "yup" to "WTF?!" this is from your perspective, I'd be interested.

Finally, a little something for those who use the text editor vim (which I gather is related to vi?):

.

cellio: (mandelbrot-2)
I haven't really prepared a "year in review" post, but here are some random notes and thoughts.

On the job front there have been ups and downs but the year ended on an up. After thrashing about earlier in the year, being moved from one short-term or ill-defined task to another while people juggled charge codes and contracts, I finally got to settle into something (a) interesting and (b) that takes advantage of my particular specialty, and I rocked. I got a new manager mid-year (my first remote one, too; he's in AZ), which always carries some uncertainty, but he and I really click. He specifically appreciates what I do and wants to help me find more opportunities to do it. Excellent!

The cats have settled in well. I was only without cats for about 4.5 months, but they felt really empty. I mean, Dani's and my relationship is strong (no worries there!), but there was still something missing. That Erik, Embla, and Baldur all died within a span of 10 months (and the last on the day I returned from a frustrating trip to Israel) may have had something to do with that.

I continue to really enjoy my job as a moderator on Mi Yodeya, and last winter I was also appointed as a moderator on Writers (both Stack Exchange sites). On both sites I get to work with great teams on interesting content. I'm still trying to figure out how to increase the tech-writing content on Writers. I need to ask and perhaps self-answer some questions to nudge things along, I suspect.

2013 was a terrible year on another Stack Exchange site. What was supposed to be an academic-style biblical-studies site turned into a cesspool of Christian dogma. I know it's possible for people of different religions to have civilized, respectful discussions about the bible (and other religious matters); I've seen it. (I have thoughts on what makes it work when it works, but I'll save that for another time.) This site was supposed to be non-religious (though obviously most of its members are religious), like a secular university. But it didn't work out that way, and the evangelical moderators (there's no diversity on that team) either can't see or don't care about the damage being done. Everything I did to try to help get things back on course was thrown in my face -- with personal attacks, offensive (usually anti-Jewish) posts, and assorted misrepresentation. So I'm done with that; I have better things to do with my energy. There are a few good people there who are trying to turn some things around; I wish them much luck, but personally, I'm done.

I've had ups and downs religiously and congregationally. My rabbi is fantastic and I like my congregation, but there have been changes in how we approach services, and too many weeks I just don't go on Friday night because they're doing something kid-oriented or entitled (sisterhood service, Reform-style bar mitzvah, etc), and that's frustrating. The Shabbat morning minyan continues to be excellent and the spiritual high point of my week, so that's all good. I'm just trying to figure out Friday nights, and some of it is bound up in questions about whether the Reform movement is right for me at all (except I have this fantastic rabbi and he's worth staying for). It's just that sometimes, being rather more observant than those around me and caring about the halachic and other details that most shrug off, I feel like a mutant.

This year was the last Darkover Con, so On the Mark re-assembled to do a concert. That was fun, and it was nice to see friends I haven't seen in a while at the con.

I'm sure there's more, but this is what I've got right now. Happy 2014 all!

cellio: (don't panic)
Today at my software-development job I learned that if an active shooter in your building is throwing grenades you should hit the ground flat, but if he's shooting bullets you should instead crouch down, because grenade shrapnel goes up but bullets ricochet off the floor. Who knew? (Cover is also recommended if available, of course.)

No, nothing happened -- it's just a little farther afield than our usual mandatory training. I also took a refresher on time-reporting. That was much less interesting.
cellio: (avatar)
Today I attended a day-long class on web-service technologies. (Yeah, late to the party.) Being a programmer was not a prerequisite (though it helped), and most people there weren't. This wasn't so much about programming and software design as about getting from WSDLs (web-service specifications) to code and vice-versa, and about understanding all the pieces, the WS-* standards, etc.

I should also mention that at the beginning of the class the instructor asked us to introduce ourselves and say what we do. I mentioned API (programming interface) design, among other things.

One of the exercises was pretty straightforward: they gave us some Java code for a trivial web service, and we were to generate the WSDL from it and deploy the service. We were using Eclipse, which has built-in tools for this, so that's pretty straightforward. Some of my coworkers were asking questions about the Java code to better understand it (which is good, to be clear).

After this had been going on for a little while the instructor walked past me, saw me typing, and said something like "you're still working on this?". Well, not exactly on the assignment, I said; having finished that, I'd noticed a couple obvious omissions from the interface their service offered, so I was implementing them to make sure I understood how to wire it all up. He looked over my shoulder, said something like "that array might bring you pain; consider a Collection", I said I worried that that would be too Java-specific for a WSDL, and he pointed out that I was using a Java-specific tool and it would probably do something reasonable. And so it did.

After the class I apologized to him for being "that student" (I think I also asked more hard questions than everyone else put together), and he said no worries -- students like that keep him on his toes. :-) Me, I just wanted to make sure I got enough out of it to justify an 8AM start (ouch).

how I work

Oct. 7th, 2012 04:50 pm
cellio: (Monica)
LifeHacker is doing a series on how I work and one of my coworkers brought the concept to our wiki late last week. This is approximately what I posted. (I hadn't yet seen the LifeHacker posts, so the style doesn't exactly match.)

Read more... )

cellio: (avatar-face)
Time to code a work-around for a bug so a customer can give a better demo tomorrow and hopefully win a bid and give us money: one hour.

Time to deal with our own licensing system so we can just give them the one JAR file they need without making them re-install the product: three hours or so. (Or so I understand; I was not the one doing it.)

Something is not right here.
cellio: (don't panic)
[Originally locked, but I don't work there any more, so...]

Several weeks ago:

Tech lead: And we need to make a visualization to show X (which, from context, TL thinks is a big deal).
Me: Don't sweat it. I can code that in 10 minutes, once Y finishes the information architecture.
TL: I'm holding you to that.
Me: Project Manager doesn't go smaller than hours, so call it one hour.
TL: And we also need a chart that shows Z.
Me: That's harder -- put down two hours. For the pair.
Project Manager: I'll allocate a day to be safe.

Today:

TL: (angst) and you're going on vacation in August! What do you mean you haven't started?
Me: Y is finishing the information architecture this week.
TL: (angst angst angst)
Me: Ok, I'll talk to him and see if he can hurry it up.

Time elapses while I acquire a stable baseline. An hour and a half after that:

Me: See the two attached screen shots. By the way, you didn't specify A and B but they seemed like good ideas so I added them. I could add C and D tomorrow morning if you like.

I am vindicated. And I have learned something about how hard TL and PjM think certain tasks are, which I may someday need to use to my advantage. :-)
cellio: (don't panic)
Via [livejournal.com profile] tangerinpenguin: List thirteen things that are going well for you this Friday the 13th:

1. The customer who sounded like he wanted Big Complicated Things (In A Hurry) thought my first draft was about 80% while I was assuming 25%.

2. Two significant projects (and some lesser ones) at work want me and my manager will support whatever I want to do. Cool!

3. I read a letter on the eye chart this week that I don't usually get.

4. Some more e-books that I want to read are available as free downloads.

5. Good conversation with my rabbi last night.

6. Bought gas for $3.09/gallon (loyalty card) and it should hold me for a month.

7. Cirque du Soleil is coming to Pittsburgh and this time their web site allowed us to buy tickets. (Totem -- not interested in the Michael Jackson thingy.)

8. Waking up to a cat on my feet every morning still, even though the weather has gotten warm.

9. Baldur is eating better.

10. Mesura et Arte del Danzare -- lovely recording!

11. Neighbors taking care of things along the property line that they might have been able to get away with not doing.

12. The rain seems to have ended before I have to leave for Shabbat.

13. Dani makes me happy. (Why yes, that is redacted. :-) )

short takes

May. 1st, 2011 09:35 pm
cellio: (lj-procrastination)
I interrupt preparations for the class I'm teaching next week at the music and dance collegium (gosh, I hope I have this calibrated right...) to pass along some random short bits.

Dear Netflix: I appreciate the convenience of your recent change to treat an entire TV series as one unit in the streaming queue, instead of one season at a time like before. However, in doing so you have taken away the ability to rate individual seasons of shows, which is valuable data. It also makes me wonder, when you recommend things to me based on my ratings, if you are giving all ratings the same weight -- 200 hours of a long-running TV show should maybe count differently than a two-hour movie. Just sayin'.

These photos by Doug Welch are stunning. Link from [livejournal.com profile] thnidu.

How Pixar fosters collective creativity was an interesting read on fostering a good workplace. Link from [livejournal.com profile] nancylebov.

Speaking of the workplace, I enjoyed reading how to run your career like a gentlewoman and several other articles I found there by following links. Link from [livejournal.com profile] _subdivisions_.

Rube Goldberg meets J.S. Bach, from several people. Probably fake, but it amused me anyway. (This is a three-minute Japanese commercial. Do commercials that long run on TV, or would this have been theatrical, or what?)

Speaking of ads, in advance of our SCA group's election for a new baron and baroness today, the current baron sent around a pointer to this video about an upcoming British referendum on voting systems. Well-done! (Of course, I agree with both the system and the species they advocate. :-) ) I wish we had preference ballots in the US.

A while back a coworker pointed me to how to make a hamentashen Sierpinski triangle. Ok ok, some of my browser tabs have established roots; Purim was a while ago. But it's still funny, and I may have to make that next year.

Speaking of geeky Jewish food, a fellow congregant pointed me to The Kosher Guide to Imaginary Animals. which looks like fun. I've certainly found myself in that kind of conversation at times (e.g. is unicorn kosher? well, is it a goat (medieval) or a horse (Disney)?). Some of you have too, I know. :-)

[livejournal.com profile] dr_zrfq passed on this article about a dispute between a church and a bar. Nothing special about that, you say? In this case the church members prayed to block it, the bar was struck by lightning, the bar owner sued, and the church denied responsibility. I love the judge's comment on the case: “I don't know how I’m going to decide this, but as it appears from the paperwork, we have a bar owner who believes in the power of prayer, and an entire church congregation that does not.”

47 seconds of cuteness: elk calf playing in water, from [livejournal.com profile] shalmestere.

I don't remember where I found the link to these t-shirts, but there are some cute ones there.

cellio: (out-of-mind)
At work, two coworkers were standing near me discussing a problem of reconciling divergent data in a system I'm helping with. Coworker 2 said "draw me a picture". On a whiteboard, coworker 1 wrote "location 1" and drew a laptop symbol, then wrote "location 2" and drew another laptop, then drew a squiggly line between them, then drew something evocative of a bicycle.

Coworker 2 asked "what's that?". I replied: "the transport layer". (Yes, really. Customer has no network availability and multiple locations.) He was enlightened about the problem of potential data stale-ness, and did not ask me what protocol is used. :-) (BCP - bicycle communication protocol?)

cellio: (mandelbrot)
Neat visualization #1: the scale of the universe, showing how big (and small) things are. Link from [livejournal.com profile] filkerdave.

Ooh, pretty: when Planet Earth looks like art. Link from [livejournal.com profile] browngirl.

Overheard at work: "Every time a developer cries, a tester gets his horns".

Neat visualization #2, from a coworker: 200 counteries, 200 years, 4 minutes.

I had sometimes wondered what the point of bots was -- what does somebody get out of creating bogus LJ accounts just to add and remove friends? (At least when they post nonsense comments they might be testing security for when the spam comes later.) Bots on Livejournal explored helps answer that question. Link from [livejournal.com profile] alienor.

Graph paper on demand (other types too). Thanks, [livejournal.com profile] loosecanon; I can never find the right size graph paper lying around when I need it.

A handy tool: bandwidth meter, because the router reports theoretical, not actual, connection speed.

And a request for links (or other input): does anybody have midrash or torah commentary on the light of creation (meaning the light of that first day)? I have the couple passasges from B'reishit Rabbah quoted in Sefer Ha-Aggadah and I have the Rashi; any other biggies? I was asked to teach a segment of a class in a few days.

cellio: (lj-procrastination)
Via [livejournal.com profile] _subdivisions_:

1. What’s one thing that made you happy today?

After spending hours on porting item #1 to our new software version, item #2 took about 15 minutes. Yay for learning curves! (Ok, also bug fixes -- it's a pre-release version. :-) )

2. What’s one thing that drove you crazy today?

Having my Mac seize an audio CD and refuse to eject. 45 minutes and half a dozen reboots later it finally coughed up. Sheesh! For future reference, the trick is to hold down the left mouse button while booting, but it has to be a wired mouse. Um, what?

(Number 3 was redacted for complete irrelevance.)

4. Is there a TV show you never miss? What is it?

Historically, Babylon 5 and, later, LOST (the last 10 minutes of which does not exist in my world, thankyouverymuch). Of shows currently on the air, The Big Bang Theory. Though an important distinction: B5 always got watched on broadcast night; the others get/got watched within the week.

5. How do you get to work?

I drive via local roads (no parkway, yay).

6. Rake in the fall, or leave ‘em ‘til after the thaw?

Rake in the fall. I left them till spring once, thinking they would just turn into mulch and cease to be a problem. That didn't work so well.

7. What’s your favorite cheese?

I like rich, soft cheeses of the Brie/Camembert/etc family. I've had some excellent specimens that I can never find again (nor remember the names of) after the encounter. Oh well.

8. Who’s your favorite muppet?

I haven't watched any muppets since I was a kid, but I remember thinking that Oscar the Grouch got a bum rap and was clearly misunderstood. :-)

cellio: (avatar)
This week we have customers in for a big development-and-integration event, with the result that I'm expected to basically spend the week in a lab doing development (configuration, not Java code, but pretty complex configuration). The lab, for sound security reasons, is not on the corporate network nor on the internet.

Monday morning was spent setting up customers' servers, providing an overview of changes since the last release, and stuff like that. So I really only spent about half a day working on that lab machine, but it was still exhausting. The default Windows configuration is not one that works well for me visually, and the tools available to edit XML (and read server logs) were Notepad and Wordpad, and, well, that sucked. Oh, and while I'd managed to get another monitor (the standard setup had them bolted to the back of the table; it's our deployment configuration but that's too far for me to see), I realized late in the day that it was at the wrong height and that was part of why my neck hurt.

Ok, then. Yesterday morning I appropriated a thumb drive (after confirming I was allowed to connect it to my corporate machine), went upstairs to my desk, and grabbed a few tools I'd need: Windows display theme, emacs (with my configuration file), and KeyTweak to remap caps-lock to control like Jim [1] intended. (The Cygwin installer relies on an internet connection so no joy there, but I was mostly just repeating the same command lines over and over in the DOS shell, so ok. And no IntelliJ for licensing reasons.) And a ream of paper, for the monitor.

Ah, much better. I can get through the rest of this week now. If we could do something about the fluorescent lights it'd be even better, but at least they aren't directly overhead or in my line of sight.

[1] Jim Gosling. I used his emacs for a few years before I encountered Stallman's, which morphed into Gnu, which is what everyone uses now. And back in those days, the control key was just to the left of home row (VT100 terminal), easily accessible -- important for a program where almost all commands involve that key. I have never, ever adjusted to the PC (and Mac) putting that key down on the bottom row where I can't easily reach it without actually moving my left hand out of typing position.

Expand Cut Tags

No cut tags