3 ms·
Ha, I had the exact same experience a bit over a decade ago! Only it came from a total misunderstanding of what agile teams were supposed to be, the idea that a
by crazygringo 4y ago
Ha, I had the exact same experience a bit over a decade ago! Only it came from a total misunderstanding of what agile teams were supposed to be, the idea that anybody on the team should pick up any story they wanted to.
So suddenly the graphic designer is writing HTML and CSS, the front-end developer starts writing SQL queries, and the product manager starts writing JavaScript.
The experiment lasted about a month with a lot of hurt feelings, because essentially all the code just had to be totally reverted.
The graphic designer knew how to write CSS for his browser and screen resolution, but didn't have the faintest idea how to deal with window resizing, browser quirks, unexpectedly long text, or how to integrate with our established frameworks at all. Just threw a lot of CSS straight into "style" fields instead of CSS files. The SQL queries fell apart in production because the front-end developer didn't know how indexes worked at all, or to aggregate values on the database server instead of client-side. While the PM's JavaScript was similarly just modifying the DOM directly instead of using the framework, leading to total spaghetti code (and global variables everywhere).
The worst part wasn't even the wasted time, but the damaged personal relationships. Because nobody had even the level of expertise to understand why their code had been reverted, so they blamed it on politics instead. The PM thought it was totally unreasonable to require usage of the framework, the front-end dev blamed the database architecture because indexes didn't seem like something anyone should have to deal with, and the graphic designer similarly could never be convinced of any good reason why CSS shouldn't be inlined into HTML. All of them wound up blaming the actual team member experts for getting jealous of their turf and trying to unjustly sabotage the new people's contributions.
Just a disaster all around.
Now obviously that was kind of a worst-case scenario. But nevertheless, ever since I've been extremely wary about people picking up development outside the area of expertise they were hired for, simply because people don't know what they don't know. In other words, they don't even ask to get assistance on how to do something properly, because they're totally unaware there's a proper way that's different from what they just naturally hack together.
- fifilura 4y agoThis sounds to me like your team did not think about what it means work together. Particularly now with so much technology support from remote working you can just keep an open channel. As soon as you get stuck or want to ask something, you just share your screen and ask for some help. Not much more difficult than that.
- crazygringo 4y agoWell the team obviously wasn't thinking about a lot of things. But it had nothing to do with an open channel. Everyone was literally sitting next to each other. But my point at the end was that it doesn't solve anything because nobody even thinks to ask in the first place.
- wellanyway 4y agoThis reads like nobody involved knows about code review and just commits straight to master. 'Hey this sql is fine but slap an index on name field' is not some shocking development if you just had three rounds of refactoring of a piece, let's say CSS. Or Java.