1. 4

    Company: FreeAgent

    Company site: https://freeagent.com/


    • Product engineers, junior/mid/senior/principal - you’ll be working predominantly with Ruby on Rails but you don’t need to have direct experience of it - we’ll get you up to speed!

    • Platform engineers, mid/senior/principal - opportunities to work on our cloud migration (we’ve moving to AWS), CI/CD, developer tooling, data science, machine learning

    • Test Engineering - helping to build an even better testing culture into the product from creating an idea to monitoring once it is delivered

    • Engineering managers, team leads, product managers, product designers

    Location: Edinburgh, Scotland or remote in the UK for senior positions

    Description: At FreeAgent we help freelancers and small businesses be more successful by putting them in control of their company finances.

    We have built an award-winning banking and accounting app that offers full end-to-end compliance, from time tracking to tax return filing. We’re based in beautiful Edinburgh and we’re growing from strength to strength with over 90,000 paying customers and strong YoY growth. Our NPS is amazing (70!) - customers love what we do and our team get to make a real impact.

    That’s actually my favourite part of the job: seeing the positive impact that we’re having on small businesses with every release, allowing those people to get on with the thing they got into business for (hairdressing, dress making, web consultancy), rather than spending time worrying about their finances.

    We’re a growing team of over 200 people. 50% of our engineering team are distributed across the UK, the rest being based at our Edinburgh HQ.

    Contact: For applications, go via our hiring page: https://www.freeagent.com/careers. If you have questions, feel free to PM me here or send me an email: james [at] freeagent [dot] com

    1. 3

      This appears to be a podcast. It appears to have an rss feed which allows it to be consumed using a podcast client: https://newrustacean.com/feed.xml

      Why make it so hard / impossible to find any reference to the feed when browsing the website?

      1. 2

        That’s an interesting question from a discoverability point of view! I already subscribe to New Rustacean (I think I stumbled across Chris Krycho’s work via Twitter), so I was curious to see how easy it’d be to find it on the website.

        Like you, I couldn’t find an obvious link from the show notes to the whole podcast feed, but when I found the homepage (https://newrustacean.com/), I saw lots of ways to get to the podcast, including the RSS feed.

        If I remember right, the website is built using Rust’s standard documentation tooling. A neat hack, but a little twisted. I don’t know how easy it is to change the base templates to include the appropriate link(s). However,tThe lack of discoverability on the show notes might be useful feedback for him to receive.

        Some searching later

        Ah yes, here’s the repo: https://github.com/chriskrycho/newrustacean.com. You could raise an issue, or contact him directly via another mechanism?

        1. 1

          when I found the homepage (https://newrustacean.com/)

          I failed to find the homepage. I clicked on the big logo in the top left corner and assumed that that had taken me to the homepage, but in fact it took me to https://newrustacean.com/show_notes/index.html.

          You could raise an issue, or contact him directly via another mechanism?

          He appears to have authored this thread, so I assume he will see these comments…

          1. 2

            Oh! Certainly not an intended outcome—just a side effect of assuming (incorrectly!) that most people would end up seeing the home page. I’d not realized—literally until this post!—that the docs don’t have a way to link you back to the home page. If you have a GH account, I’d love it if you opened an issue, and I’ll figure out a way to get the RSS feed link into the show notes version of the page.

            Things like this are definitely the downside to a choice I made really early on because I thought it would be helpful for a bunch of things about the show (as indeed it has).

      1. 1

        We have a slack room where we post what we intend to to today and we post another message when leaving with what we achieved and what issues we encountered that kind of stuff. We’re still testing the process, it kinda works but I’m not really sure of the added value so far.

        1. 1

          This is sorta where we are with regards to experimenting more and extending the solution above, using a shared chatroom and individuals contributing. In effect, that’s what iDoneThis and StandUpMail (referenced above) also achieve, but this way the timeshifting is obvious.

          I’m trying to put together my thoughts on what’s working about that for us and what still isn’t. Like you, I wasn’t initially convinced of the benefits, I think it is a net positive. I’d like to explore why in a bit more detail.

        1. 2

          My team, despite being mostly local, uses a tool called iDoneThis. We have an in-person/virtual standup Monday morning to sync on work for the week and then use iDoneThis to stay in sync for the rest of the week. This is really helpful for when people are out and want to stay caught up on what everyone is working on. It also really helps look back and reflect on what you’ve worked on.

          1. 3

            We played with iDoneThis at FreeAgent many years ago, and someone also pointed me at: StandUpMail which from the look of things is fairly similar. I can definitely see those being useful for us, so we might have another explore of those tools.

            1. 1

              I looked at iDoneThis a few years back for a very small team I led. I loved the idea and was shocked there was no open source clone. Ended up not using it because of size, but if I ran a team that was either bigger or distributed, a similar tool would be very helpful.

              The question then becomes, when do you have the face to face between team members (managers will get their one to ones, of course). The options I see are:

              • adhoc, just through the course of working together
              • scheduled (I have heard of peer one to ones, which is an interesting idea)
              • weekly group video calls, as other comments have mentioned