jadeforrest

8 ms·

1.
by jadeforrest 2y ago
Covers some chaos engineering practices that aren't very common in the wild: 1) Evil staging - make an environment less reliable on purpose 2) Gauntlet programs - gradually inject classes of failure into staging and production 3) Reli
2.
by jadeforrest 3y ago
From the article: Include all the work. One thing to be careful of is that the demos are inclusive of all the work required to build functional software. Prepare the team to demo all the parts of their work: the APIs, the infrastructure, th
3.
by jadeforrest 3y ago
I’m the author, and didn’t say any of those things. I said that bias can lead to harder standards for minorities. They can be judged by higher standards.
4.
by jadeforrest 3y ago
Hiring junior engineers is challenging. I’ve seen so many junior engineers get hired but then be supported poorly. This is a writeup of the best program I’ve seen for hiring and onboarding junior / new engineers.
5.
by jadeforrest 3y ago
FAST agile is an agile variant that uses self-organization within very large teams to scale organizations. This is a deep dive into the tradeoffs of FAST agile. It may not be as crazy as it looks!
6.
by jadeforrest 3y ago
Step by step guide to hiring engineering managers. Includes sample questions, interview formats, and more.
7.
by jadeforrest 4y ago
I'm the author of the piece. Yes, that's very true. There is a difference between what you can control and what you can influence. By understanding how it works, you increase you chance of influencing things. The salary review is
8.
by jadeforrest 4y ago
I'm the author of the original piece. Totally agree with this -- it can be quite simple to implement. Increasing retention makes a big difference. Unfortunately, there are more incentives to hire than to retain, so many companies do a
9.
by jadeforrest 5y ago
Hi, I'm the author. Totally agree with you on this. I do tend to focus on milestones first, because even if you're focusing on problems, using milestones to focus on what's next can sometimes be helpful. But if you can get to
10.
by jadeforrest 5y ago
Hi, I'm the author. I'm not intending to describe working in sprints. You can implement the ideas behind this article with sprints, kanban, or something else entirely. Using sprints doesn't do what using milestones does. So w
11.
by jadeforrest 5y ago
Can you explain more? I don't see it that way, but it might be we're defining things differently. Milestones are defined in a specific way within the article, and in that way they don't seem orthogonal to me.
12.
by jadeforrest 5y ago
Hi, I'm the author. This isn't a post about scrum vs kanban. It's primarily about the value of using a specific definition of milestone to encourage incremental delivery. And to highlight some of the benefits of delivering in
13.
by jadeforrest 5y ago
A fun exercise would be to make up tenets for existing companies. Let me start: Tesla * We value aspirational storytelling over the "truth". [We might make it true later!] Apple * We think different, except when it comes to creati
14.
by jadeforrest 5y ago
That was a helpful link. Could you give an example of a tenet you find more convincing?
15.
by jadeforrest 5y ago
I don't understand your critique -- the words tenant and segue do not appear in this post. What are examples of playing fast and loose with language?
16.
by jadeforrest 5y ago
I love the point you're making, and perhaps what I'm trying to say isn't coming through in the piece. Another way I've talked about this (to myself) in the past is that there is something akin to the cathedral vs the baz
17.
by jadeforrest 5y ago
They're organized functionally, and are one of the only companies in the world that seem to have cracked this at scale. I've always been super curious how that works in practice. This article argues against functional organization
18.
by jadeforrest 5y ago
This thread of discussion is making my day. The Coda Hale article above gets into some of the math, but this is a great critique!
19.
by jadeforrest 5y ago
Well said. I don't think you need a matrix management system, and actually kind of hate matrix management. In general (there are exceptions) I AM arguing for cross-functional teams. More like D&D teams, with Fighters and Wizards an
20.
by jadeforrest 5y ago
Thank you so much for introducing me to that article. It's fantastic! I've made this comparison forever, and used a lot of the same arguments -- I wish I had written this!
21.
by jadeforrest 5y ago
I didn't intend to argue against communication or collaboration between silos. When a leader implores the people around them to "break down silos", they're usually not being very explicit about org design or communicatio
22.
by jadeforrest 5y ago
I wrote up a bunch of tips for hiring and recruiting within startups: - how to make hiring faster - create a hiring strategy - improve careers page - make posts more equitable - using a candidate packet - mining your network - effective rev
23.
by jadeforrest 5y ago
Startups usually don't focus on technical standards, because they're focused on survival. In this blog post, I describe what we can learn from explore/exploit algorithms and how they pertain to technical standards.
24.
Exploration and Exploitation in Technical Standards(rubick.com)
1 points by jadeforrest 5y ago|1 comments
25.
Implementing pay equity (in an engineering organization)(rubick.com)
1 points by jadeforrest 5y ago|0 comments
26.
by jadeforrest 5y ago
Added (feedback welcome): One thing to be careful of is that the demos are inclusive of all the work required to build functional software. Prepare the team to demo all the parts of their work: the APIs, the infrastructure, the reliability
27.
by jadeforrest 5y ago
I would be interested in that if I was leading your part of the org. Here's the value I would get out of it: - I could see what portion of the team's time is spent on tech debt issues, which gives me a sense of how well we're
28.
by jadeforrest 5y ago
You bring up a good point -- maybe something I should emphasize more in this blog post. Demos should be inclusive of all he work it takes to build a real, functioning piece of software. That should include the reliability work, the scaling,
29.
Demo-Driven Development(rubick.com)
26 points by jadeforrest 5y ago|11 comments
30.
The three most common anti-patterns for managing projects(rubick.com)
4 points by jadeforrest 5y ago|0 comments

More ›