dkoston

11 ms·

1.
by dkoston 6y ago
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
2.
by dkoston 6y ago
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.
3.
by dkoston 6y ago
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 natural breaks. It is important to make sure that people know t
4.
by dkoston 6y ago
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 whiteboard. What’s also important is that video from meetings takes u
5.
by dkoston 7y ago
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 because there was no loading indicator. In fact, until I got to
6.
by dkoston 7y ago
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 can be useful to be remembered of places you like but haven’t
7.
by dkoston 7y ago
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 does that” and we had to make many assumptions about what th
8.
by dkoston 7y ago
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 trying to replace human interactions and relationships with
9.
by dkoston 7y ago
Avalara and Vertex both have options that integrate well with major billing systems.
10.
by dkoston 7y ago
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 miles deep. Took a few hours to get towed. VW said they would
11.
by dkoston 7y ago
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.
12.
Double eureka: Breakthroughs could lead to quantum ‘FM radio’ and end of noise(thenextweb.com)
1 points by dkoston 7y ago|1 comments
13.
by dkoston 7y ago
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.
14.
by dkoston 7y ago
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 approach. You’ll have to check at merge time because gettin
15.
by dkoston 7y ago
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 workflow in one of the existing CI/CD tools. Was there a t
16.
by dkoston 7y ago
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 doesn’t mention the core reasons that you chose to write yo
17.
by dkoston 7y ago
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 about building “yet another CD tool”. Appreciate the thoug
18.
by dkoston 7y ago
From what I gathered in the article, that’s the case now but before the queue required manual merges.
19.
by dkoston 7y ago
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 an untested queue instead. It seems like they wanted to cherr
20.
by dkoston 7y ago
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 queue instead of a develop branch before moving to CD? Was thi
21.
by dkoston 7y ago
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 than experimenting with works best in production at your bu
22.
by dkoston 7y ago
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 to allow arbitrary selection rather than merging in order (th
23.
by dkoston 7y ago
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 commits a "single piece of work", etc. Not to soun
24.
by dkoston 7y ago
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 type you need and configure custom RAM and CPU instead of p
25.
by dkoston 7y ago
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 point in this change did meetup suggest they were of
26.
by dkoston 7y ago
1Password allows you to add family members with access to specific values either read-only or read/write. The system for adding access is multi-step so unless you add someone to a vault they shouldn’t see, you have the flexibility to s
27.
by dkoston 7y ago
1Password has a Families plan for this.
28.
by dkoston 7y ago
I agree that this stuff is common place and I definitely understand that in today’s world of noise that you have to market yourself and your papers to get attention. I was glad to see them add the disclaimer as hopefully it’ll turn away peo
29.
by dkoston 7y ago
You can use a PRF for the domain to derive additional secrets. It simply depends on the scope of the project and who you think your users are. For example: if your user base is cryptocurrency wallet holders who have multiple secrets for eac
30.
by dkoston 7y ago
For #2, it seems unlikely that people would have a single secret. I’m not sure if the codebase is more just to prove the concept from the paper or to potentially get adoption. If you are looking for people to adopt the project, I’d suggest

More ›