Posts

  • Note to Self

    Career advice I'd give my 20-year-old self.

  • Ecto.Multi and Sane Code

    Keeping code sane and reasonable for non-trivial business logic using Elixir and Phoenix.

  • Getting Answers while Data is Sparse Act 1: Promises and Baseball

    Wherein we set the stage for thinking about mixing subjective data with empirical data in graphical models.

  • Intuitive Boosting

    Take a minute to understand how boosting algorithms work and things to keep in mind when building models with them.

  • Github Pages Tutorial

  • The Paradox of Big Data

    Curious people find more questions to ask when the data is bigger. This is a review of pragmatic principles for data analysis.

  • But You Gotta Know It

    Career advice I gave to my son that I think also applies to junior developers as well as boot camp graduates.

  • If I Had to Bet...

    Thinking about the qualities I find the most and least effective in software development.

  • Where Are We Going?

    An effective leader gets their people to ask "Where are we going and how can I help?" These are lessons learned from effective and frustrating experiences delivering software systems for over 20 years in the business.

  • Quantified Baseline

    Some more thoughts on my progress increasing my intellectual abilities.

  • Quantified Self

    An approach to measuring my throughput as a software developer

  • Test Power to the People

    Getting comfortable with testing our code shouldn't be as hard as it is.

  • How Not to Be a Junior Developer

    I keep having this conversation about how to break into the development world. Some of these people have gone to developer boot camps or spent years learning new skills. A lot of the advice seems to be the same, stop being a junior developer and learn how to contribute to a team.

  • Gaussian IQ

    Instead of raging online, I thought I'd do a practical refresher on the normal distribution instead.

  • Random Walk

    MWRC, Mazes and Me, Oh My!

  • Saving Puppies

    Learning what makes software development important from the eyes of an 11-year-old girl.

  • Pairing Makes Progress

    So far, my pairing invitation has turned into some great learning opportunities. Here's some of what I've learned lately.

  • Pairing

    Pairing isn't extreme unless you make it extreme. Here's a detailed look at what I've learned from it. It's also an invitation if you want to reach out and build something together.

  • Six Months

    We can learn most technologies in six months. This is a guide for anyone learning a new technology.

  • Human Capacity

    Realizing how much capacity I have as a human being, I re-commit to learning and contributing. Where I focus I improve.

  • Getting Better

    A quick reminder to myself to keep working on things that are important and that I've been avoiding.

  • Plants vs Zombies

    Everything important I know about software can be expressed in Plants vs Zombies.

  • A Gaggle of React Components

    Spurred by student questions, I realize I should share how I progress through a problem. I take a concept from React.js and walk carefully from step to step.

  • Getting Out of the Mud

    New learners sometimes feel stupid when learning something new. It's not easy, but the problem isn't intelligence. It's often practice and familiarity. One way to get that quickly is SQ3R. Here's an introduction to the idea and how I applied it to my work.

  • Agile and Agility

    Striving to learn lessons from my experience at a large corporation, this article combines Dave Thomas' ideas on agility with my desire to do something worthwhile with my career.

  • Problem Solving

    Taking the advice of the JavaScript community, I'm blogging whenever I solve a problem. This helps me remember the lessons I've learned. It also helps me clarify my thoughts.

subscribe via RSS