News for hackers. Stuff that matters.
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?