Articles tagged 'Community'

We hosted the third Clojure Circle meet-up this year at the Funding Circle London HQ. We were joined by fifty of London’s finest for the presentations as well as the mandatory beers, pizza and socialising.

Starting at a new company is an intense period; one that, for most of us, goes by in a blur of introductions and meetings, interleaved with some moments of calm. Looking back at my first week all I can say is: it was intense, fun and well worth it...

Google I/O. That’s the developer conference Google holds every year in San Francisco to explore the latest and greatest in tech, including web, mobile and everything in between and beyond! In 2013, only 8% of attendees were women and in 2014, it rose to 20%. This year I was lucky enough to attend I/O and was a part of the record 23% in attendance!

I just got back from the Container Camp conference here San Francisco. It was
an informative conference with presentations covering a wide range of interesting topics in the
containerization ecosystem. There was a lot of discussion about the Docker application suite
since they are the dominant player, but there was also good coverage of alternative approaches
and presentations on the full spectrum of tooling required to use containers in production.

It’s been a year now since I joined Funding Circle as one of 8 CodeCrafters who spent three months being trained in website development and becoming a fully fledged software engineer. I was one of the three people who were hired by Funding Circle and here is a brief overview of my experience since.

Interviewing is difficult for both sides - the interviewee may have to recall small bits of esoterica while standing in front of a group who all know the answers to their questions, while the interviewer needs to find a way to evaluate a very important decision (whether she wants to work with the candidate or not, potentially for years), in a very short amount of time.

You might thing that delivering “value” is redundant in an article about values. But you are wrong!

This value is about making sure that the work that we do is valuable to our customers. When
deciding how to prioritize work, or whether we should even undertake a task should be decided based
on how it can make the experience of our users better.

When I look at code, the first thing that pops into my head is “Is this readable?” Can I quickly glance
at a class or a method and understand what it does? Is the interface clear, are side effects obvious,
and are there consistent patterns that tell other developers how to use the software?