Jonathan Maltz

I have kept a weekly (or bi-weekly) Confluence blog at Stripe for the better part of 4 years now.

I oftentimes talk about projects existing in three phases: meetings phase (defining the scope), building phase (building it) and shipping phase (converging and flipping the thing on).

This is a little flashcard game I made to help my wife prep for the USCIS citizenship test.

When teams shifted to remote + hybrid work, they also needed to adopt a much greater emphasis on having a written culture.

As projects grow it can be difficult to keep track of all of the documentation associated with them.

During my career I've had the chance to work on teams of a lot of different sizes.

One of the challeging things about being a technical leader is knowing how much time to spend on big-picture vision setting vs. writing code and solving the problems of today.

A while back a friend gave me some important, but hard to hear feedback.

Recently I had a shower-thought about the concept of "organizational neutral".

Spend enough time working with domain experts on a problem and someone is bound to say "we should build a rules engine to solve this problem."

Recently I've found myself in situations where there's no right answer.

Sometimes engineering teams find themselves in a situation where they're tackling a cross-functional problem with no clear path forward.

As you move from owning individual problems to owning projects, you'll often find yourself in a position where you're surfacing risks to your manager or other senior folks.

Estimation is something that I've done for a long time, but I've never really felt like I've done it well.

Teams often find themselves in a position where they need to figure out how much work they can commit to, most commonly in quarterly planning.

One of my challenges at Nuna has been setting up team-level communications structures in the face of uncertainty.

A while ago I was struggling with the question of "how do I get a project prioritized."

Over the past few months, a few people have asked me about my experience speaking and blogging, specifically through the lens of what type of opportunities it has opened up for me.

I had lunch with a friend yesterday, and he shared an interesting story.

Over the years at Nuna, our data platforms have grown from small pipelines which served simple analytics, to large, polyglot pipelines which can help patients receive personalized doctor recommendations.

Back in university I worked in a media office, and it seemed like all the creatives had two jobs in their life: their real job, and the thing they did on the side.

When building APIs, it’s common to run into a problem which is basically a form of “We want an API that will support a list of something.”.

Continuing to grow as a software engineer can become increasingly hard as you become more experienced.

Feature flagging is a great way to reduce risk by allowing features to be turned off remotely, but only if it's done correctly.

I recently had a chance to give a talk at Android Makers about how to work with cross-functional stakeholders to create change.

I recently had the chance to speak at Droidcon Boston about one of my favorite topics: code review.

One of the first questions I got after giving my talk about mentoring new hires was (paraphrasing) "how do you deal with effectively mentoring people who are 1+ year into their time on the team?".

Currently at Yelp I'm working on building out our next generation experimentation infrastructure, a large part of which involves writing a Java wrapping library around a Rust library which does most of the heavy lifting of our experimentation.

I recently had a chance to talk about A/B testing at Droidcon SF as part of a talk called "A/B Testing From The Ground Up".

I recently presented a new and improved version of my talk on "Multiplying Your Impact Through Mentoring" presentation, this time at Droidcon London.

One of the more unintuitive things in professional software development is the idea that you should break your code up into small, fully functioning chunks, rather than shipping it all as one big change.

Every month, a group of engineers at Yelp get together for something we call the "technical roundtable", which is basically a big discussion group on technical topics that are challenging the company.

Whenever I hangout with mobile developers at meetups, I hear a bunch of misconceptions tossed around, but one of the most pernicious is the belief that designers are head-in-the-clouds artists, throwing pixels around without concern for what it will mean…

I recently presented an updated version of my "Multiplying Your Impact Through Mentoring" presentation at Chicago Roboto.

This weekend I had the pleasure of getting to attend the AI In Action Spring 2017 hackathon at Claflin University in Orangeburg South Carolina.

Software engineers always talk about how code reviews are the single biggest thing to improve your code quality, but we often forget that putting your hard-written code up for review can be scary.

I gave my first big boy conference presentation today at DevFest Minnesota!

We’ve all been there before: you’re chugging away on a technical problem and suddenly you hit a brick wall you just can’t seem to get over.

Over the past weekend I had the pleasure of mentoring at Hack The North in Waterloo, where I gave an updated presentation on how to have an awesome internship/co-op.

Today I had the pleasure of giving a presentation to students at stanford about how they can have a succesful summer internship.

Every developer has their own little kit of productivity tools which they constantly expand over time.

Last week I gave a talk at Rutgers about how to make the most out of your summer internship.

have You ever read an english essay so riddled with errors its tough to read. i'm not talking your normal run of the mill errors; I'm talking about really systematic misunderstanding of how to use punctation!

Back when I first declared my CS major at Rutgers three years ago, the community was a far cry from the vibrant and passionate one that characterizes Rutgers today.

It’s no secret that over the past three years hackathons have exploded across the country, bringing with them the opportunity for thousands of students to grow their coding skills and build a community of developers at their university.