3 ms·

Indeed! Our "architect" (cough) stuck us with mass microservices even though we are too small a group to need them. Bloatville. He kept quoting "separation of c

by tabtab 8y ago

Indeed! Our "architect" (cough) stuck us with mass microservices even though we are too small a group to need them. Bloatville. He kept quoting "separation of concerns" and other "magic Legos" abstraction/reuse/modularity BS memes. Plain ol' OOP classes do all the same. I've been fighting to debunk it, but so far losing. It's more a case of momentum and if-aint-broke-dont-fix than logic so far. Nobody seems to want productivity enough yet to care, so if they pay me to mow the lawn with tweezers, I'll tweeze away...

madeuptempacct 8y ago
Oh hey, I had the same issue. Except micro-services eventually lost. Having class libraries in NuGet did work well for us (we are open source). Next trend to die soon: TDD / "Unit tests" that mock half the app
maxxxxx 8y ago
People with "architect" in the title generally are a problem especially if they don't code anymore. I think architecture should done by the senior engineers who work on the codebase. If necessary they still can coordinate with other teams.
phakding 8y ago
In ideal world, your technical argument would be enough for higher-ups to take your concerns seriously. In real world, it's mostly how much they like and trust you. If they don't, then validity of your argument will be of no value.
- maxxxxx 8y ago
  In the real world you can't evaluate every argument. It just takes too long. I definitely filter by people who I know usually have good ideas vs. others whose ideas never make sense.
konschubert 8y ago
The way to fight bullshit is not by trying to refute it, which would be futile due to the bullshit asymmetry principle. The way to go is to offer a compelling alternative. Of course, this applies only if the bullshit has been confirmed as such and if the person promoting it has shown to be uninterested in a sincere and fair argumentative discussion.

by tabtab 8y ago

madeuptempacct 8y ago

Oh hey, I had the same issue. Except micro-services eventually lost. Having class libraries in NuGet did work well for us (we are open source). Next trend to die soon: TDD / "Unit tests" that mock half the app

maxxxxx 8y ago

People with "architect" in the title generally are a problem especially if they don't code anymore. I think architecture should done by the senior engineers who work on the codebase. If necessary they still can coordinate with other teams.

phakding 8y ago

In ideal world, your technical argument would be enough for higher-ups to take your concerns seriously. In real world, it's mostly how much they like and trust you. If they don't, then validity of your argument will be of no value.

maxxxxx 8y ago
In the real world you can't evaluate every argument. It just takes too long. I definitely filter by people who I know usually have good ideas vs. others whose ideas never make sense.

konschubert 8y ago

The way to fight bullshit is not by trying to refute it, which would be futile due to the bullshit asymmetry principle. The way to go is to offer a compelling alternative. Of course, this applies only if the bullshit has been confirmed as such and if the person promoting it has shown to be uninterested in a sincere and fair argumentative discussion.