User Tools

Site Tools


work-stories

**This is an old revision of the document!**

Work Stories

  • You solved a customer pain point.
  • You solved a complex problem.
    • You raised the bar.

    ## IceCondor

  • Complex/Innovation: lmdb-based index, fit in ram constraints
  • Pain point/Challenge: access control, privacy fences
  • Raised the bar: Being early to market with a unique offering

Vault

  • Innovation: portfolio balancing algorithm from meetings with domain expert
  • Challenge: correctness, code tests, manual review
  • Raised the bar: included other developers, best practices

ChromaFund

  • Innovation: implementation from public whitepaper
  • Challenge: communicating with meteor daemon
  • Raised the bar: unique offering

More Questions

  • Tell me about a time when you gave a simple solution to a challenging problem.
    • Defining the architecture for the coinmanager part of Chromafund project. Specifically picking a language. The project to date was javascript. Not the best choice for numerical computations, but in the name of developer simplicity, javascript was the best choice for the coin manager piece as well.
  • Tell me about a time when you were working on an initiative and saw an opportunity to do something bigger or better than the initial focus.
    • Instead of outsourcing coinmanager, build in-house
  • Tell me about a time when you found there was a more efficient way to accomplish a task someone was working on. How did you convey it to them?
    • A coworker was tasked with implementing an internal site. They choose an obscure framework that was different than what we were using in-house. I told them what we are already using, and already have dev resources for.
  • Tell me about your most significant career failure and what you learned from it.
    • preference for startup environments, market fit and timing are hard to get right.
  • Give me an example of a time when you were 75% through a project, and had to pivot the strategy - how were you able to make that into a success story?
  • When did you take a risk, make a mistake, or fail? How did you respond, and how did you grow from that experience?
    • Replacing on-disk storage for icecondor from json to protobuf. The protobuf bits came along nicely, integrated with the build system without problem. Most of the updates to the codebase were comparmentalized and updated well. Then there was a hidden 30% of code debt that required a major refactor to finish this feature. A rewrite of the system was already on the schedule so that feature was halted and its goals added as a goal of the rewrite. learn: code coverage matters
  • How have you leveraged data to develop a strategy?
    • Icecondor keeps metrics of unique users accessing the site per day and total location data points ingested. This informs the performance monitoring.
work-stories.1658162739.txt.gz · Last modified: 2024/01/31 04:08 (external edit)