Ironically after getting more sleep last night I feel groggier this morning. Sunday night I couldn’t sleep re-hashing my 9-year old twins lost football (soccer) match (I’m the coach). Don’t want to be strung out thinking about it, but I am, pretty much every time they lose; although it’s particularly bad when I think the opposing coach is not setting a good example. Despite the lack of sleep on Sunday, yesterday was a solid day. I slept properly last night, but is this a cold coming on? Urgh. Been distracted this morning, but maybe by the right stuff? I’ve done a quick Slack/Email review and edited the AV Premium F2F offer page to include connecting to me on LinkedIn. I keep wondering what to do with the random folks connecting to me there - might as well be offering them a free hour of pairing on a charity project.
And now I want to just quickly follow through with Will’s advice on changes to the Premium Sponsorship form, and get the revised version out to a few folks:
Okay. This is only a side note, but I read this interesting article about names: http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ TLDR: have a single “name” field
Each question should have a reason. I want to know why you need to know what country I live in, for a premium membership.
The resume could be a lot of work. Shouldn’t the questions ask everything you want to know?
“If you’re working remotely, where is the company based? *” shouldn’t have an asterisk.
Edited-down mob programming videos might get more folks applying.
“Please upload a cover letter indicating how you think you would benefit from the Premium membership you are applying for” could become just “How do you think you would benefit from the Premium membership you are applying for?”
So now it’s much shorter:
But I must jump back to the APSoc membership database, and my new backup ritual which involves copying the previous day’s file in dropbox and relabelling it with the day I’m starting on. Giving LibreOffice Base an extra 2GB of Java memory does not appear to have helped with the lock up issues.
But let’s start with correctly populating the Local Group field in the membership form. I create and populate a new table, and in short order I have the Local Group dropdown as requested:
Now I duplicate the version and restart LibreOffice. And then I work on a new dropdown for pay method on the subscription payment form. I create the table, but then trying to set up the relation we get stuck again. I go make coffee, come back, still stuck. I kill the app, and re-start. I’m lucky - this time we’re able to recover the corrupted file:
But I’ve got no basis to diagnose the issue … I make a quick extra backup and continue, and I get it working:
There is no particular pattern - although I sense problems come when I double up on things, e.g. add a table in the SQL view by double clicking, but then also click the add button … okay, enough for today. I’m going to pass this version on to the client, as I said I would do that daily this week.