News for hackers. Stuff that matters.
Re:Managing Difficult Software Engineers by LeoNatan25 on Thursday August 17, 2023 @07:24AM (#37159967)
It’s all about perspective. In two companies now, I’ve been in teams that don’t really care about my tech stack. It was mutual, of course. You can blame the company for making these teams up (I did/do), but that how things are.
Re:Managing Difficult Software Engineers by ohyes on Thursday August 17, 2023 @08:40AM (#37160667)
Normally the technology stack refers to the languages and frameworks underpinning the project.

It is very weird to be in a situation where (for example) we’re working on a project in python and one person refuses to use python. Weird enough that I’ve never seen anyone with a personal tech stack, most people just try to adopt the local custom of the team they’re hired into.

Re:Managing Difficult Software Engineers by LeoNatan25 on Thursday August 17, 2023 @09:14AM (#37161065)
In my previous job, I was hired into a team of tech leads, each in their own field. In the current job, I was hired into a product team that was about a macOS app. After several reorgs, mergers and downsizing, the team is mostly web devs, backend devs (Go) and me, still developing the macOS app.

Why should I care about the teams’ other tech stacks (and vice versa)?

Re:Managing Difficult Software Engineers by flir on Thursday August 17, 2023 @12:11PM (#37163922)
I understand now. In my terms, you're a team of one who happens to be sitting next to another team, maybe under the same manager. That sucks, I feel for you.
Re:Managing Difficult Software Engineers by ohyes on Thursday August 17, 2023 @10:28PM (#37170817)
Do they not care about what happens if you decide you want more money, want to do something else, or just get frustrated and quit?
Re:Managing Difficult Software Engineers by diarrhea on Thursday August 17, 2023 @09:00AM (#37160902)
> teams that don’t really care about my tech stack

Relatable. I'd love to talk to them about my private Rust projects.

> You can blame the company for making these teams up (I did/do), but that how things are.

But... how did this work out in practice? There's a software project in language X, framework Y, domain Z, which everyone was familiar with, and you were brought in not knowing X and Y? That's like hiring for a Java position where the applicant couldn't care less for that the language. Strange.

Re:Managing Difficult Software Engineers by LeoNatan25 on Thursday August 17, 2023 @09:19AM (#37161125)
In my previous job, I was hired in a team of tech leads, each in a different domain. But the development at large in that company was web development, which I didn’t know how much I’d end up disliking. So I focused on my things within the company minimizing interaction with tech stacks I didn’t care about.

Current job, I was hired in a team of macOS devs for a macOS product. Several reorgs, mergers and downsizing, my old team is basically gone, and I find myself in a team of web devs and backend engineers.

I do miss having people around who can keep up a conversation in my tech niche.