Pushing a Feature On My First Day
One of my main reasons for joining Wealthfront was its engineering culture. After meeting the team as well as perusing the engineering blogs, I was excited to start working here. So how did the first day fare? Well I was setup with all of the major projects, finished work on a small feature for… Read more
Mocking Java enums with jMock is both trivial and impossible
I recently ran into a situation where I needed to test some code that used an enum to select between various strategies. As a toy example of this, we’ll use Accounts which have a list of investments and a Strategy which defines what investments are acceptable. View the code on Gist. Strategy is a Java… Read more
Building your street cred — A career forum for women in tech hosted by Wealthfront
You’re invited to join Wealthfront and Femgineer for an evening of professional connections, lessons on “street cred,” great presenters, and food. Lots of food. Wealthfront is proud to host October’s Femgineer forum on the topic of Street Cred on Tuesday, October 22nd at 6pm in Palo Alto, CA. Femgineer co-founder Karen Catlin will discuss “Street… Read more
Joining Wealthfront as a new college graduate
The First Day On my first day as a backend engineer at Wealthfront I received an overview of our architecture by one of our engineers. During the overview I realized I would be working with several technologies and flow patterns with which I was completely unfamiliar. Fortunately for me, Wealthfront was forward thinking in choosing… Read more
Marketside chats #1: market vs limit orders
This is the first in a series of articles about general market topics. They will be simple to follow and include the kind of knowledge and insights that are hard to get from publications. Some people consider market orders to be a much worse way to trade than limit orders, because you are paying the bid-ask spread. It’s not… Read more
Functional CSS (FCSS)
We’re big fans of functional programming at Wealthfront. Emphasizing immutability and functional style means fewer “surprises” because side-effects are limited or nonexistent. We can quickly build up large systems from discrete, focused components by way of composition. Applying such principles is straight forward in most languages, even if they’re not functional by definition, but the… Read more