Viewing profile — dkoston

Team building is pretty constant across all the “flavors” of agile. Building good communication patterns and trust isn’t coupled to the “how we execute” details

This is a standard agile exercise called “Rules of Engagement”. Should be run with any forming team. I’m always surprised that this knowledge isn’t more commonplace.

It depends on the day but not such a high percentage usually. Our design phases don’t last as long (software only). Virtual meeting fatigue is real because there aren’t as many nat…

Also using Miro and enjoy it. In addition to the software, make sure your team has good hardware. A screen large enough with high enough resolution is critical to see the whiteboar…

Thanks for putting this together. I’d recommend adding some indicator that the results load async. I thought you had zero restaurants in Austin and left the page after a second bec…

Sometimes it’s nice to have a list view. Google maps only provides geolocated results in a small list so you’d have to move around the city quite a bit to find the whole list. It c…

This was essentially the story of how we built a successful software company at cPanel. Our customers would describe things like “I want a button that does this” or “a script that …

Do you not have frequent one-on-ones and regular conversations with your remote employees? How do you learn about their motivations, goals, current situation, or changes? If you’re…

Avalara and Vertex both have options that integrate well with major billing systems.

I bought a VW GTI 20th anniversary (a numbered car) and the transmission broke on my third drive (wouldn’t shift out of third) which was a catastrophic failure. This was about 50 m…

Pretty nuts if this is reproducible. Would be similar to decades of progress in shrinking super computers down to pocket sized phones in a few years time.

That’s understandable. I’d imagine at some point you’ll need to decouple the monolith a bit in order to work effectively as you scale. Best of luck with the challenge.

I think I see where you are coming from. Being as we use different tools, we wouldn’t allow a pull to be merged if it wasn’t up-to-date with master which is similar but a different…

Good to hear, that’ll make change management less of a chore. I think the main thing that was missing for me is the rationale behind building this system rather than building a wor…

Interesting. Would you say this is more of a decision based around the constraints of using GitHub or more of the ideal process for Shopify’s needs? I’m curious because the article…

Thanks, I was hoping for more of this in the blog post. Since tools are just an expression of process/policy, it’s more interesting to here about the process and why than it is abo…

From what I gathered in the article, that’s the case now but before the queue required manual merges.

That’s what trying to get at in a “more polite” way. Many people use a “develop” branch to stage changes before master so they can run through CI. I’m curious as to why they used a…

Interesting. It seems like you have a very flexible process of how to launch code which could contribute to issues with visibility and rollbacks. I’m curious as to why you had a qu…

Rather than being pedantic about the definition, maybe you could share your experiences with why that’s superior to validating each branch? Being dogmatic about a definition rather…

Sorry if my comment was unclear. I consider the queue to be a “branch” as well. Many people use a “develop” branch instead of a queue in this instance. The queue appears designed t…

It would be useful in this article to hear about what content is acceptable in a merge request. For example: can these all go straight to queue because they use feature flags? Are …

In my experience, you don’t. With tons of IOPS you need EBS or crazy expensive instances. Instead you use a cloud like google cloud where you can add NVMe SSDs to whatever instance…

I've got about the same members and attendees. This will drive the cost up about 3x but honestly, that wasn't the part we were concerned about most. A couple of things: 1. At no po…