My best team experience was using Extreme programming: pair programming, tdd, trunk based dev, ci / CD, baby steps, making vertical cuts and avoiding silos (no big division between fe and be), more mob programming and less pull requests or code review. We used Scrum, with an unofficial WIP of 3. I think the main point was collective ownership and the team was very small of 6 people.
That was the longest "NO" in the history... If you're bad at programming, please, for everybody's sake back away from the keyboard and do something else pls
@@Gytax0 definitely not dude, I didn't mean it in an amateur/hobbyist context at all. Hobbyist should be able to do anything they want, even juniors because that's how you learn. I'm talking about supposed pros who put other people in geopardy by their incompetence by posing/lying at interviews, blowing up their CV for extra pay kind of stuff.
My best team experience was using Extreme programming: pair programming, tdd, trunk based dev, ci / CD, baby steps, making vertical cuts and avoiding silos (no big division between fe and be), more mob programming and less pull requests or code review.
We used Scrum, with an unofficial WIP of 3. I think the main point was collective ownership and the team was very small of 6 people.
Your story towards the end, of the dev no one wanted to work with is eerily familiar 😅
That was the longest "NO" in the history... If you're bad at programming, please, for everybody's sake back away from the keyboard and do something else pls
This is pure wisdom right here.
Gatekeeping at its finest
@@Gytax0 I assume he meant as a professional programmer.
@@Gytax0 definitely not dude, I didn't mean it in an amateur/hobbyist context at all. Hobbyist should be able to do anything they want, even juniors because that's how you learn. I'm talking about supposed pros who put other people in geopardy by their incompetence by posing/lying at interviews, blowing up their CV for extra pay kind of stuff.