1. 2

    Trail running, climbing/scrambling, cooking, reading, and drinking.

    I had a lot more spare time before I became a parent, which has made me a lot more focused on the things I take on.

    1. 4

      Does anyone have suggestions for good resources to get started learning F#? I’ve been curious about it for a while, but I might dig into it seriously now.

      1. 2

        I actually really like Programming F# 3.0, Second Edition. It covers the language very well from top to bottom, while assuming relatively little familiarity with .NET. The only caveat is that it predates Xamarin Studio being good with F#, so there will be a bit of stuff you’ll need to glean off StackOverflow or other documentation—especially if you get serious about things and need tooling like NuGet. I think that’s an acceptable caveat, though.

      1. 1

        Massive piles of refactors at $WORK, par for the course.

        Learning O'Caml in my spare time and putting together a minimal website for making training schedules for a race (running), based on a given date.

        1. 3

          FYI, there’s no apostrophe in OCaml.

        1. 4

          Outside of day to day work, I’m tinkering on a paste-bin style service for time series graphs. It’s up and running on http://graphcake.com/ and I’m slowly adding new features as I find time.

          1. 1

            Hmm, cool. Any way to dump a bunch of data in as csv/etc? I know a bunch of people that track weight/lifting/etc as xls/csv. It’d be extra nice of you to allow exporting data as csv as well.

            1. 1

              I added bulk import and exporting data to the todo list. Data import kind of falls into the realm of the “time travel” feature (since it involves adding data points that aren’t right now). I’ll also need to figure out a good UI solution for the two input features.

          1. 5

            Finally got my company started, it takes a while, in Sweden at least. Have the homepage kind of complete at http://sayon.se/en/ now. Feedback is very welcome. This week will be spent with R&D, and a visit from an old friend.

            1. 1

              The design is nice, but it would be great if you had links to a portfolio to show off more of what you can do. As it is, you’re requiring potential customers to believe that you can deliver “big results”. Even better if you show them by example!

              1. 2

                Thank you, nice to hear someone else say it looks nice! Yes, a portfolio had been nice, but all I have for now is http://sayon.se/en/work/. It’s a bit of a catch 22, you need work to show off to get work and you need work to get work to show off. I have been employed for nearly nine years, but the things done for others isn’t something that I can show off. So my thought was to show off some of my open source work, to show some technical skill at least. But I know it’s quite the leap of faith to take as a customer, I’m working on getting a portfolio together. Thank you for the feedback!

              1. 2

                Pretty slick! It’d be nice if there was some audio that went along for the huge video on the page. It’s a bit hard to see what’s going on with the extension without squinting, as well.

                However, the extension itself looks pretty cool, and I’ll give it a shot. Thanks for sharing!

                1. 1

                  Thanks for checking it out. I’ll be sure to update the video with some sound.

              1. 2

                I live my development life in tmux and vim. I generally use Ubuntu, though I used to use debian, which was probably better . It doesn’t matter much what distro you pick for your workstation. Ubuntu’s not great, but it’s easy to set up.

                I’ve started using Google Docs, though I really preferred writing design docs in HTML (or markdown) and getting feedback over email instead.

                Almost all of my communication is over email, though I use irssi for IRC.

                1. [Comment removed by author]

                  1. 3

                    Heartbleed occurred after the release had been made - so the OpenSSL library included with 5.5 is vulnerable - so yes patching is required.

                    1. 4

                      I feel a bit dense asking, but how? The release date for OpenBSD 5.5 is May 1, well after heartbleed occurred. Are you saying the release was cut a while back, but only released to the public today?

                      1. 6

                        Yes. The release process basically goes:

                        • unlock tree from 5.4 release, become 5.4-current (occurred july 29, 2013)
                        • ~6 months of rapid development for work to become 5.5
                        • 5.4 is formally released from stuff up to july (occurred november 1, 2013)
                        • slow down, no big changes, abi/api lock, become 5.5-beta
                        • tree locks, hopefully no remaining changes (occurred feb 28, 2014)
                        • developers test final snapshots on all archs, discuss outstanding issues
                        • OPENBSD_5_5 is tagged, considered “5.5 release”
                        • CD images are created for 5.5 release, Theo works on getting artwork, giving CD images to pressing plant
                        • tree unlocks, becomes 5.5-current (occurred march 5, 2014), rapid development starts leading up to 5.6
                        • CDs for 5.5 release start shipping, ftp release happens may 1, 2014

                        So as you can see, 5.5 was created 2 months ago and already burned on CDs that shipped out. We can only backport fixes from -current to the OPENBSD_5_5 tree and issue errata during those 2 months between tagging 5.5 and formally releasing it.

                        1. 1

                          Although the OpenBSD release dates are 1 May and 1 November each year - there is a lot of work goes into ensuring that each release and associated packages are ready for manufacturing to create the CD’s so that they can be delivered on or before the release dates. So although each release happens on the 1 May and 1 November each the code that goes into each release is fixed about 1 to 2 months before the release date. This means that if you run current you start running some of the next release code - you can tell when this is happening as the ports tree is locked and ports are fixed ready for the release. hth :~) PS This is way the releases are such high quality every six months.

                      2. 2

                        Looks like M:tier is officially endorsed by Theo:

                        http://marc.info/?l=openbsd-tech&m=139896061602956&w=2

                        For those not in the know, M:tier provides the binary packages for stable releases:

                        https://twitter.com/jasper_la/status/461576068055707648

                        Does this imply that M:tier’s binary packages are now endorsed, too?

                        1. 1

                          I don’t read it that way; just that they donated money/hardware and their company functions and services are unrelated.

                          1. 2

                            True, but I think people will be much more comfortable with getting binaries from M:tier now that Theo has took the time to specifically thank them for providing some support for the release.

                            I mean, just look at the title of his email alone:

                            Subject: Thanks to M:tier for package signing infrastucture

                            I’d be surprised if they don’t see some spike in the business.

                        2. 2

                          Releasing with a known security flaw surprises me. Why wouldn’t they delay the release to get it fixed?

                          1. 3

                            I’m guessing because it was cut ahead of time and CDs had already gone out

                        1. 1

                          This was actually something I was wondering about for the last several days. I haven’t developed using OpenSSL or anything related to security or networks in the past. But is there no real alternative to OpenSSL? I would be genuinely surprised in this case given that almost every other library has multiple competing implementations.

                          1. 2

                            GnuTLS is the other open-source TLS implementation. It has its own set of security holes.

                            1. 1

                              A quick note: OpenSSL has a BSD license. GnuTLS is LGPL. You’re correct, I’m just noting the license differences.

                              NSS is also open source (Mozilla/GPL/LGPL licenses).

                              1. 1

                                I was going to mention the license differences, but I’m not sure how much of a role that plays in deciding to use one or the other. Most software depending on a TLS implementation dynamically link to the shared library, so LGPL shouldn’t be an issue.