Reverendender

I used green lentils instead of red, because that's what I felt like.

Original post with recipe

Image is from Boston Harbor, MA, courtesy of my mother, the tour guide.

Signature Plastics (Black Friday Doorbusters - Hell Yeah!)

SA-P Tequila Sunrise (Alphas + 60% Modifiers Gorton + 80% TKL Add-on)

G20 Semiotic (80% TKL Set)

DCS Nova White (Alphas + 60% Modifiers + 80% TKL Modifiers)

G20 Stealth (Alphas Night + TKL Night)

The bank shut down a discussion on an internal website about a five-day return to office policy after dozens of employees criticized the move

Original link: https://www.wsj.com/business/jpmorgan-chase-disables-employee-comments-after-return-to-office-backlash-19199a4a

Signature Plastics SA Geoma Keycaps RK Gaming S98 board

I’m a business analyst, and a big part of my job involves working with engineers and product managers to gather detailed, in-depth information. For reasons I don’t fully understand (though I have my theories), I often find that engineers, in particular, seem oddly reluctant to share the information I need. This makes the process more challenging than I’d like. Does anyone have tips or tricks for building trust with engineers to encourage them to share information more willingly and quickly?

EDIT: Here's a summary with more details for those who requested more info: I’m working on optimizing processes related to our in-house file ingestion system, which we’ve been piecing together over time to handle tasks it wasn’t originally designed for. The system works well enough now, but it’s still very much a MacGyver setup—duct tape and dental floss holding things together. We got through crunch time with it, but now the goal is to refine and smooth everything out into a process that’s efficient, clear, and easy for everyone to follow.

Part of this involves getting all the disparate systems and communication silos talking to each other in a unified way—JIRA is going to be the hub for that. My job is to make sure that the entire pipeline—from ticket creation, to file ingestion, to processing and output—is documented thoroughly (but not pedantically) and that all teams involved understand what’s required of them and why.

Where I’m running into challenges is in gathering the nitty-gritty technical details from engineers. I need to understand how their processes work today, how they’ve solved past issues, and what they think would make things better in an ideal world. But I think there’s some hesitation because they’re worried about “incriminating” themselves or having mistakes come back to haunt them.

I’ve tried to make it clear that I’m not interested in punishing anyone for past decisions or mistakes—on the contrary, I want to learn from them to create a better process moving forward. My goal is to collaborate and make their jobs easier, not harder, but I think building trust and comfort will take more time.

If anyone has strategies for improving communication with engineers—especially around getting them to open up about technical details without fear—I am all ears.