ChaniBlog











I’ve been doing a lot of Android dev lately. Which of course means even more swearing than usual (yep, that is possible). It’s actually been fun, in a bizarre why-am-I-enjoying-this-torture kind of way, but there’s been a steady stream of WTFs along the way, and a surprising number of them involve EditText.

god damn fucking edittext. It’s just a little widget to get some text from the user. how hard could that be, right? :P

I had problems right off the bat with my personal app I started over the holidays. That one was simple – I used the standard fragments+viewpager template, threw an edittext on my layout, and tried to get me some text. Nope. By default, EditText is multiline, so you have an enter key that inserts a newline instead of a submit button. I was okay with multiline in the sense that it should grow and wrap text if I type a lot, but I didn’t want actual newlines, I wanted a ‘done’ button. I could have added a separate button to my UI, but that’s no fun :P so I fought with getting that button to show on the keyboard. Turns out, you need not only android:imeOptions="actionDone" (or submit or next or whatever), but also a sensible value for android:inputType (which took ages of trial and error to figure out – autocorrect vs autocomplete was not clearly explained at all) which in my case was android:inputType="text|textCapSentences|textAutoCorrect" (I c&p that as the default for all my edittexts now).

Then there are the weird issues with focus when you leave fragments or click another edittext. mostly they just cause warnings, but on kitkat some of those warnings turn into crashes.

Oh, and another weird thing – clicking ‘done’ or ‘submit’ or whatever does not automagically dismiss the keyboard. nor does leaving the fragment (and the keyboard does not like it when it’s still open and its edittext has vanished). The code to manually hide it is so ugly that I was sure it must be a dangerous hack, and was reluctant to use it, but it appears to be the only way.

    static public void hideKeyboard(View focusView) {
        InputMethodManager imm = (InputMethodManager) focusView.getContext().getSystemService(Context.INPUT_METHOD_SERVICE);
        imm.hideSoftInputFromWindow(focusView.getWindowToken(), 0);
    }
    @Override
    public boolean onEditorAction(TextView v, int actionId, KeyEvent event) {
        //Log.e(TAG, String.format("onEditorAction %d", actionId));
        if (actionId == EditorInfo.IME_ACTION_DONE) {
            setAndSaveText(v.getText().toString());
            Helpers.hideKeyboard(v);
            return true;
        }
        return false;
    }
//I have to manually call this whenever I do a fragment transaction.
    private void onFragmentChange() {
        View focus = getCurrentFocus();
        if (focus != null) {
            //Log.e(TAG, "focus: " + focus.toString());
            //keyboard should go away when leaving a fragment. how is this not standard?!
            Helpers.hideKeyboard(focus);

            //fix focusout bug on api 15
            //notes: dispatchWindowFocusChanged does nothing.
            //clearFocus works on api 15, but also calls onfocusin,
            // and gives worrying error messages on kitkat (nexus 5).
            if (Build.VERSION.SDK_INT < Build.VERSION_CODES.JELLY_BEAN) {
                focus.clearFocus();
            }
        }
    }

Okay, that’s it for the problems encountered with a simple, common view. But then I started a more interesting project, where I needed to dynamically set up layouts at runtime. Yep, some of those layouts had edittexts in them, and that gets interesting. In a throw-your-computer-out-the-window kind of way. :P

The natural approach to a dynamic UI would be a ListView, right? It would just make sense, right? Wrong :P ListView and EditText do not get along. Period. Nothing’s stopping you from trying to put an EditText in a ListView, but if you do, spooky shit will start happening. Your keyboard will go crazy. Text will fail to appear, or focus will jump to the wrong place, or the cursor will show up in the wrong part of the screen… and on kitkat, it’ll just outright crash sometimes. After much googling and some rather depressing stackoverflow comments, I decided it was easier to just use a LinearLayout in a ScrollView. (luckily I won’t have enough rows for performance to matter.)

Everything seemed rosy again for a while, but here and there I was having issues with the text blanking out, or getting the text of a different EditText. Then I added a subscreen, and on returning to the screen with edittexts, poof, loads of text was disappearing. Oh, and radiobuttons were resetting too. Eventually I tracked it down to a really insidious side-effect of android’s helpful automatic view save/restore code. It was assuming that every view in the fragment has a completely unique ID, and since I’d instantiated multiple rows off the same layout, this was not the case.

I knew ListView had to have been preventing this somehow, so I dug in (thank god most of android is still open-source) and found what it had done: blocking dispatchSaveInstanceState and dispatchRestoreInstanceState. I made my own subclass of LinearLayout that did the same blocking, and all my widgets were happy again. :)

public class FormContainer extends LinearLayout {
    public FormContainer(Context context) {
        super(context);
    }
    public FormContainer(Context context, AttributeSet attrs) {
        super(context, attrs);
    }
    public FormContainer(Context context, AttributeSet attrs, int defStyle) {
        super(context, attrs, defStyle);
    }

    //prevent save/restore of our children
    @Override
    protected void dispatchSaveInstanceState(SparseArray<Parcelable> container) {
        super.dispatchFreezeSelfOnly(container);
    }
    @Override
    protected void dispatchRestoreInstanceState(SparseArray<Parcelable> container) {
        super.dispatchThawSelfOnly(container);
    }
}

Well, there are still some warnings when I jump directly from one edittext to another. But I think this is as good as it gets :P



{January 9, 2014}   Why am I not blogging?

Goddamnit, I haven’t blogged in forever. I at least started a post on robotsconf, but never finished it. I’m damn well going to blog about *something* today, so, let’s talk about possible explanations for my not blogging.

This is going to be a rambling stream-of-consciousness post with no editing except to combat autocorrect. Because one of the things that makes it hard to blog is worrying about whether I could have phrased it better. The internet can be pretty mean, and if one little sentence is badly phrased then someone’s going to jump on it. :/

Which brings me to another issue: my blog is adrift on the internet at large, instead of being part of a community. When it was a part of planetkde, and I was contributing steadily, I always knew what I wanted to talk about and who was going to read it. Even when I didn’t have some cool feature to blog about, I knew my audience. I had a feel for how many off topic posts I should write to let people know about my hobbies without boring them too much.

Now, my hobbies are in chaos – I can’t seem to settle on one thing for more than a couple of sessions – my work isn’t something I can blog about much (and NIR would most people care) and I have no fucking clue who’s reading this.

I know that I’ve picked up some followers of my food posts (sorry, no time for that lately, Pete’s doing most of the cooking), I know some tiny subset of kde people still follow my blog, and I know some people read it via twitter now that I’m auto-tweeting my posts and actually using twitter. (Actually that last one scares me a bit, you never know who’s going to end up seeing it there…)

Twitter might be part of the problem too… The free time I do have is easily sucked up by reddit and twitter. And I don’t feel like twitter is a choice, because I’d miss out on stuff in various tech circles if I didn’t check it at least every couple of days. It keeps me feeling connected in these not-quite-communities around js, Vancouver tech, etc.

But, yeah, time is an issue. I started this post on the bus, and now I’m writing during lunch while the rest of the company chats. After work and dinner, I generally don’t want to do anything hard, and blogging is hard. It takes a good 2-4 hour block for me to do a good post, iirc, and if I’m interrupted I tend to lose interest. I have that time on the weekend but I have a million other hobbies and chores and social events competing for my attention then (and if it’s work-related I can take some work time but there aren’t many of those). Plus it’s hard to convince myself the post is worth writing if I don’t know who’s reading it.

Another thing that bugs me is this WordPress app.  For the most part it’s a good app, but it has a fatal flaw: it is way too easy to publish by accident. That makes me reluctant to use it the more complex my topic is. And with the small screen it’s hard to review a post – I don’t seem to have a preview at all here – so I always want to finish editing on a desktop and publish from there.

Oh well. This time I’m just going to hit send and damn the consequences :p



I’ve noticed a pattern at conferences and meetups lately. Some guy comes up to me, and the first words out of his mouth are something like “it’s so nice to see girls in programming” or “so how can we get more women in tech?” or something. It seems quite well-intentioned – I imagine he thinks it’s an easy way to break the ice, or wants to communicate that he’s not sexist, or at worst is trying to score brownie points – but it’s making me uncomfortable. It took me a while to figure out what I was feeling – the last couple of times I just sorta awkwardly ran away – so now that I’ve figured it out, I’m blogging it.

I do not like being reminded of my gender at tech events. Especially with the recent drama I’ve been seeing on twitter. I’d much rather forget that I’m different, and talk to you about how awesome node is, or bitch about android and ios, or hear about some cool project you’re working on. Please, just use the same damn ice-breakers you’d use if I was a guy.

Besides, I do not get magical feminist superpowers from my ovaries: I’m just as lost as most guys when it comes to all the women-in-tech issues (except t-shirts. I can go on about that one for ages). That’s part of the reason I don’t want to be asked about it, I suppose; thinking about it makes me feel lost and helpless and confused. And remembering that I’m a girl makes me feel a bit more self-conscious and awkward.

I might wander into conversations about it from time to time – more likely after several drinks – but please, don’t make it the first thing you say to me.



{November 20, 2013}   Accessibility surprises

So CascadiaJS was last week, and it was awesome. I did have one issue at the start, though, which surprised me enough to blog about.

First off, the issue was resolved quite well. I’m not writing this post to complain, but to educate. I might have been too shy to bring it up, but at the start of the conference they told us who to talk to if we had any problems, even ones that seem silly. :) I’m really glad of that.

So, the issue: for the first time, I had need of the accessible bathroom. But it was locked. When I first discovered this, the staff member with the keys happened to be nearby. After explaining why I needed it, he unlocked it, but insisted on locking it again afterwards so that nobody made it messy.

Two issues here: first, having to ask made me feel really bad. I look young and healthy, but I’m not. So I end up explaining my personal health situation to a stranger to beg permission to empty my bladder. It reminded me of being in grade school, having to put my hand up and ask instead of just quietly slipping out. I wasn’t looking forward to having to ask him again – even skipping the explanation, it still meant finding him, and interrupting whatever he was doing. And doing so again every time I needed to pee (which was about once an hour). And since I feel bad about imposing on him (and humiliated too), I felt pressured to keep my bathroom visits to the minimum too.

I now have a lot more understanding of how disabled people can seem like cranky assholes sometimes. If I stopped caring about the feelings of the guy with the keys, life would be much simpler.

And then I started worrying, what if I couldn’t find him when I did need the bathroom? Which brings us to issue two: the very next time I needed it, he wasn’t there. Some nice lady helped me down to the regular bathroom then – I’d delayed so long I couldn’t wait much longer. But after lunch, he was still gone. So that’s when I went to the awesome Angelina and got the problem fixed. Bathroom unlocked for the rest of the conference, apart from a few times when the damn door re-locked itself. :)

Oh, and nobody made a mess of the bathroom anyways. Yay for responsible adults!

What I learned from this is, accessibility isn’t necessarily intuitive. I could have just as easily been the one with the keys in this situation. He made a fairly reasonable assumption (that a guaranteed-clean bathroom was better than an unlocked bathroom) that just happened to be wrong. Now I’m wondering: what wrong assumptions about accessibility do we have in our code? (Assuming there is any accessibility in the first place :P ) Or in our other attempts to be helpful in general?

It can be hard to explain when something intended to be helpful is actually hurtful, or even to understand what happened. I just hope that if I end up on the other end, the person has the nerve to speak up and I have the patience to listen.



{October 6, 2013}   How to Not be a Rockstar

Lately I’ve been keeping up with twitter, and retweeting the best of what I see. And there’s a trend in that recently: articles encouraging humility. I like this, and I feel like saying a few words myself.

Most recently, @shanley wrote (or.. crowdsourced?) an article on how the “10x engineer” is a myth, and why it’s bad. Unfortunately it just sort of trails off at the end, and I’m left a bit confused, so I’ll try to sum it up: Long ago someone did a crappy study with way too few participants, made wild claims, and then it snowballed into this myth that encourages harmful behaviour like hero-worship, overworking, depression, etc.

Been there, done that, got the t-shirt (and health issues nobody my age ought to have). And yet, it’s such a tempting trap that I keep having to drag myself away from it again. I mean, who doesn’t want to be a rockstar? Who doesn’t want to be the bestest programmer in the world, and have everyone think they’re awesome? My brain is good at avoiding substance addictions, but has a blind spot when it comes to people’s praise and approval. Besides, there’s so much in this world that I want to do, it’s hard to stop and rest when I need to the most.

Another post I retweeted was Presentation Skills Considered Harmful. It’s a very well-written post on how to reduce stage fright and be a better presenter at the same time – not “better” in the rockstar sense, but in the sense of actually being more useful to your audience. Last time I submitted a talk proposal, I had this nagging “I’m doing it wrong” feeling, and I think this post explains a lot of it – I was focused on how I could get my proposal accepted, how to make it sell and make me look like the sort of presenter everyone wants at their conference – not on how the talk could be useful to the audience. I mean, that was in there somewhere too, but it wasn’t the priority. In truth, even while writing it I didn’t really believe it was a useful talk. I just missed talking, and have yet to gain enough experience with javascript to have anything useful to say about it. :( Still, what I liked most about the article was that it gives me clear guidelines to follow when, one day, I do have something to say again. :)

Now, I find myself wondering: why is this rockstar thing so tempting? Why do I feel compelled to judge programmers, and persecute myself if I don’t appear to be the best? Why are people so eager to put someone on a pedestal and start a cult of personality? A part of my mind says, this is obvious, humans have always been that way. But I’ve found that questioning those “obvious” things can lead to interesting discoveries.

I can’t speak for other people, but for me…. it usually boils down to fear. Silly, irrational fears, which are the hardest to defeat. I fear that if I’m not the best programmer, I must be the worst programmer and I’ll end up with no job (despite having never been unemployed except by choice). I fear that if I’m not giving talks about awesome stuff, nobody will be interested in talking to me (despite all the good conversation and friends I made at WWDC, where I doubt any programmer knew less about apple tech than me). I fear that any imperfection in me could be used against my whole gender, even though the communities I hang out in wouldn’t put up with such behaviour, and the best thing I can do for other female geeks is to be myself as loud as I dare. :)

The worst part is, when I try to break away from this, I’m often overwhelmed by the fear that I somehow need these silly fears. They lie to me, and tell me that without them I’m nothing, that I’ll just lie on the couch and do nothing all day, and never accomplish anything. Yet when I’ve succeeded at putting aside those fears for a while, the opposite is true: on average, I get more motivation and energy, and accomplish more, and feel better about myself in general. Sure, sometimes I need a day or two of doing fuck-all first because I’m burnt out, but if I rest without beating myself up about it, I can’t seem to help doing something productive soon afterwards. And it’s a lot more fun when I wholeheartedly want to do it. :)

So, if you feel like your ego is hurting you… try putting it aside for a week or two. Focus on how you can help other people in your community, or at work. Try doing what’s right, even if you’re scared of getting punished for it. :) And put your health first, because you can’t help yourself or others if you work yourself to death. :P

Oh, and there’s another trap to avoid here: competitive humility isn’t real humility. If you’re putting down people for following their ego, you’re doing it wrong. And if you get angry at yourself for having an ego, you’re doing it wrong. I still want to be the bestest programmer ever. I still want oodles of money. There’s nothing intrinsically wrong with having such desires. I’m just taking them out of the driver’s seat for a while. Desires have a lot in common with two-year-olds; giving them what they want isn’t the best way to handle them, but beating them up isn’t right either. :)

Now that I think about it, fear and anger can be like two-year-olds too. Resist them directly, and they throw a wild tantrum and try their best to make you feel miserable. But give them some space and understanding, and hear them out, and they just might agree to try another way (forgive me if the metaphor is stretched; I don’t have much experience with actual two-year-olds).

Anyways, that’s enough for tonight. Maybe another time I’ll have a go at the hero-worship issue (note to self: The Speaker-vs-Audience Dichotomy is relevant reading). For now, I’ll leave you with an article that convinced me accepting tips is suboptimal, and a quote that changed how I think:

“Confidence doesn’t come from knowing you’re right – it comes from being okay with failing.” — Design is a Job



I’ve been meaning to blog about this for ages, but I seem to have writers’ block. Time to break through it!

Going from desktop kde/qt programming to mobile and web development has been quite a change. Some of the lessons I’ve learned along the way, I wish I could have read about instead of walking into. So, I’m writing about them now to save the next person from that. :)

Let’s start with node.js. I love node.js, it’s a lot of fun to work with. A shame there’s always web browsers at the other end. ;P But, node is a place where you are guaranteed to run into one of javascript’s biggest annoyances:

Callback hell

Now, for KDE programmers, callbacks might not sound so bad. Signals and slots are technically callbacks, right? And they’re easy and fun to work with. But when you strip away all that nice abstraction, you get a lot of ugliness. Ugliness like this:

doAsyncThingOne(data, function(error, result) {
    if (error) {
        ohshit();
    } else {
        doAsyncThingTwo(data, function(error, result) {
        if (error) {
            ohshit();
        } else {
            doAsyncThingThree(data, function(error, result) {
                if (error) {
                    ohshit();

…and so on. (sorry about the ugliness of the code formatting, that’s what you get on a free wordpress account.)

And that’s assuming that all your async methods use the “data, callback” pattern. it’s a popular one, but there’s another popular pattern, “data, successCallback, errorCallback” – and sometimes “data, {success:callback, error:callback}”. And then there’s the question of what pattern they expect for those callbacks you’re passing in – is it “error, results”? “results, error”? Something Completely Different?

It can get to be quite a headache quite quickly when the libraries you’re working with don’t all use the same pattern, and you always have to remember which one expects which. and there’s no compiler to warn you, either – you just get things breaking horribly or, just as often, silently dropping bits on the floor.

Cleaning it up

Fortunately the majority of libraries I’ve worked with follow the pattern in my example – including async, a library purely for reducing the pain of callback hell. Async can get that awful example down to something more manageable:

async.waterfall([
    function thingOne(next) {
        doAsyncThingOne(data, next);
    },
    doAsyncThingTwo,
    function thingThree(dataFromTwo, next) {
        doAsyncThingThree(dataFromTwo, function (error, result) {
            if (result.isCool()) {
                next(null, result);
            } else {
                next("not cool!");
            }
        });
    },
], function finalize(error, dataFromThree) {
    if (error) {
        ohshit();
    } else {
        yay(dataFromThree);
    }
});

note that since thingTwo fit async's callback expectations perfectly, we didn't even have to wrap it. :)

However, this is still pretty inflexible – what if a particular result from thingOne means that you can skip things 2 and 3 but still need 5? I've heard that Promises are more flexible in this regard, and I plan to try them out sooner or later, but I'm not sure what to do about all the libraries that don't offer a promises api. We shall see.

The ‘dummies’ part

Now, I actually got way off topic there. There’s a different problem with callbacks that inspired this blog post. I felt really goddamn stupid when I noticed I’d done it, but then I realised… everyone else working on the project had also done it somewhere.

See… the thing about callbacks, is that when you take one, you're promising to call it once, and exactly once. Not twice, not zero (excepting that thou then proceed to one ;). What we had was some callbacks that might never be called, and some that were always called twice. Or more.

Oops.

So, yeah, don't do that. It’s bad.

And… that’s it, really. I keep feeling like I should have more to say about it (One shall be the number of the counting, and the number of the counting shall be one?) but it’s just a matter of checking your code. And hopefully keeping the methods simple enough that checking the callback call doesn’t require a state diagram. :)

If you want more information, just google “callback hell”. There are plenty of other blogs about it. :) (ooh, Elm sounds interesting…)



{August 30, 2013}   UIWebView css theming

For one of our apps at SteamClock, We’re switching from a dark to a light theme for iOS 7. We’re still keeping the dark theme for iOS 6, though. This has been a bit of a pain, and today I had the “fun” of figuring out how to theme our about page, written in html. :P It took about three stackoverflow answers and a blog post for me to piece together working code, so I’m adding Yet Another blog with a solution that’s more robust (so long as your theme doesn’t change while you’re displaying it).

The gist of it is, we use external css files (something the internet was unclear on too) and then edit the html string so that it loads the correct css file for the theme.

Here’s the line of html that loads the css:

   <link rel='stylesheet' href='about-THEME.css' />

Note the lack of a leading slash in the href. It broke when I added one. Oh, and of course I’m confident that ‘THEME’ will never appear elsewhere in my html.

Now, the ios code…

First, we load the html from our resource:

        NSString *htmlPath = [[NSBundle mainBundle] pathForResource:@"about" ofType:@"html"];
        NSData *htmlData = [NSData dataWithContentsOfFile:htmlPath];
        NSString *htmlString = [[NSString alloc] initWithData:htmlData encoding:NSUTF8StringEncoding];

Pretty straightforward.

Then, we swap out the ‘THEME’ placeholder for the right name:

        NSString *themeName = IS_IOS7 ? @"light" : @"dark";
        htmlString = [htmlString stringByReplacingOccurrencesOfString:@"THEME" withString: themeName];

That IS_IOS7 macro boils down to:
([[[UIDevice currentDevice] systemVersion] compare:@"7.0" options:NSNumericSearch] != NSOrderedAscending)

Now we need a base url so that it looks for the css file in the right place:

        NSURL *baseURL = [NSURL fileURLWithPath:[[NSBundle mainBundle] bundlePath]];

Finally, we load the page:

        [self.webView loadHTMLString:htmlString baseURL:baseURL];

And that’s it! (well… almost. you may want to set the backgroundColor of the webView to match your css background, so that it looks nice while scrolling and such.)

Now our about page automagically fits the theme, and as an added benefit, all our translations share the same css instead of having it c&p’d into the html files. :)



{June 17, 2013}   WWDC 2013

This week was… quite an experience. :)

My company got me a ticket to WWDC – the big apple conference that sold out in less than two minutes. I’ve been in two minds about it ever since getting the ticket. On the one hand: holy crap it’s awesome, I get to go to a cool exclusive conference and meet lots of smart people involved in iOS and other mac stuff. And party, of course. On the other hand… it’s exclusive, which isn’t nice. The culture is different, what with all the proprietary-ness and stuff. And at the same time, it’s huge – over 5000 people in one conference, and more who didn’t get a ticket but came down anyways. I was worried I might not feel welcome there. In the end, there was a bit of both sides, but mostly good, and it all worked out well in the end.

I’d say the atmosphere there was… positive, but.. detached. Instead of a community of developers, it was a million little groups. Most of them were welcoming groups, though, especially since many had only met at the conference in the first place. I only remember one guy in the whole conference who made snide comments about free software (or any competing tech), and since it was such a big conference I never saw him again anyways. In the end, I made some great new friends over the week, and already have plans to meet some of them again. :) I also got to chat with Bill Atkinson, who I’m told is a Big Deal ;) He seemed like a nice man to me, I wish we hadn’t been kicked out of the park so soon.

Most of the conference was like that – lots of new people and never enough time to talk with them. There were multiple parties every night, labs and sessions during the day… I’m going to have to download a ton of sessions I missed, now, and watch some on the flight home. Unfortunately I’m not allowed to talk about them – apple and their secrecy. :/ oh well. The labs were great, though – getting to talk directly to apple engineers about problems we’d been having and API we’d like added. I just hope they’re able to follow through on the suggestions they agreed with, and don’t get stuck in red tape or anything.

I can talk about the keynote, though. That was.. interesting. It was like a little window into apple’s view of themselves and the world. In both the keynote and the rest of the conference, I discovered that they really do see themselves as designers, as people who care about quality and making good UI that’s easy to use. I like that. But, it was a little hard to take it seriously sitting there in my XL men’s conference jacket. I mean, maybe there’s a reason (I can’t think of any) that they couldn’t ask us our size when we bought our ticket like every other conference ever. The jackets were first come first serve, so the people who showed up a full day in advance got to have a small jacket. But they never even made any ladies’ jackets AT ALL. Only men’s. What the fuck, Apple.

image

The ladies’ lunch managed to fail at shirts too. of all places you’d expect to find attention to that little detail… nope. I got a medium ladies’ shirt (used it as a nightgown last night) and an XS that fit over top of it. It wasn’t until tuesday night at one of the parties (Stir, I think?) that I got a conference shirt I’ll actually wear. Ah well – I bought a hoodie that fits (although the zipper keeps confusing me, it’s on the opposite side because it’s a guy’s shirt) and the free food and alcohol kept me happy ;) I’d heard bad things about apple’s boxed lunches, but I took the beef option twice and it was really good. simple and healthy.

The official wwdc party was good too, but short. I think the band was only on for half an hour. It was Vampire Weekend – I loved the drums. Might have to get some of their music, but my cheap speakers wouldn’t do it justice. I tried to get some dancing going, and there were some people moving a little, but mostly ended up dancing by myself. it was fun, though. :) There might be some photos of that popping up somewhere…

The conference ended friday, but a few of us spent saturday down in Santa Cruz at a ren fair. It turns out there’s a guy at apple who is also a magician, and he invited us down to see his show. It was pretty awesome. :) I figured out a few little tricks, but a lot of it still seems like, well, magic. :)

image

The rest of the festival was good too – I don’t think any of us had ever been, so we didn’t know what to expect. There were lots of booths selling jewellery, leather bags, and so on, plus some music, food, and mead. Good mead, too, imho. I may bring a bottle of it home. :) I ended up getting sunburn on my hands and feet (yeah, it is possible to burn hands) but it was totally worth it. :)

Now it’s sunday, and I’ve picked up a conference bug. No surprise there. It seems to be a mild one so far, though. I’ve got a couple of days left to rest and see friends in oakland, so hopefully I’ll have recovered a little by the time I go home…



{May 25, 2013}   Polyglot!

Whoops, I haven’t blogged for a while. I had two different posts I wanted to write a couple of weeks ago, but got hit by a week-long headache instead. Anyways, I’ll try and write a general update tomorrow. Today, I’m busy at the polyglot conference!

Despite the name, it’s not about human languages. It’s about programming languages. It’s also an unconference, so the schedule was voted on this morning… while I was asleep.  :-P I tried to do a bit too much this week, and something had to give. Anyways,  with a schedule covering everything from mobile development to zsh to salary negotiation, there’s something for everyone here. Picking which session to go to is tough.  :-)

I think the best one I’ve been in so far is the “how to be a better developer” one. It was basically a brainstorming session on all the things that help us keep improving. I taught some students about gsoc, got a list of books to read, and considered joining a programmers’ book club.

And now- Holy crap, the last session is starting soon. It’s really a shame that the conference is only one day. I didn’t go to the paid tutorials Friday (two of them were done by my co-workers anyways) and I haven’t signed up for the Sunday hacking thing (half of it requires Microsoft tools, and anyways I need rest) so this day went by way too fast.

Oh well, at least there’s still the after party!  :-)



{April 28, 2013}   Linuxfest Northwest 2013

So I’m at Linuxfest Northwest this weekend. It’s been great so far, despite a soggy start.  Sitting in the border line in the rain for an hour proved that our motorcycle gear isn’t quite as waterproof as we thought.  :-P

Anyways, we still arrived in time for the lightning talks, and those were really good. I learnt a new xor trick, and there’s something to do with circuits and html5 that I didn’t quite understand but hope to learn more about.

Here’s a random photo from one lightning talk I liked:

image

The swag here has been cool too; I have a nice USB key / bottle opener from openshift, and I think I got signed up for some free web app thing I need to check out. I got new light-up bsd horns too (but I have my own EL wire version at home I ought to fix up).

The conference party was good, although dinner made us a bit late. Totally worth it, though – I never thought pork chops could be that delicious.  :-) I just wish I’d spent some time looking at exhibits or trying the various board games instead of getting sucked into cards against humanity for so long  ;-)

Now it’s Sunday, and there are lots of talks I’d like to be in at the same time. I saw the delegation one before lunch, which was quite good, but mostly reminded me that I knew all this stuff because KDE was doing it right (or trying hard at it) with the code of conduct and having junior-jobs and such.

Next up is a Javascript talk, which I’m hoping will be good and not just a list of words to google.

PS: the save button in the WordPress app actually means “publish”. Oops :-)



et cetera
Follow

Get every new post delivered to your Inbox.

Join 353 other followers