3 ms·

I'd love to have only the problem of Junior developers to pass experience to. I currently have to deal with "senior" developers and architects who desperately w

by sidlls 9y ago

I'd love to have only the problem of Junior developers to pass experience to. I currently have to deal with "senior" developers and architects who desperately want to put some "Big Data" stuff on their resumes and constantly chase after things like Kafka even when it's not justified.

cookiecaper 9y ago
As in everything else, the portion of actually useful and competent decision-makers in tech is vanishingly small. There are plenty of fine worker bees, but they're all too easy for marketers to divert. Ironically, such diversion is normally done with promises that deploying NEW_TECH_Z (which is almost always OLD_TECH_Y dressed up in a different outfit) will instantly make users useful and competent.
closeparen 9y ago
Compared to what? I've often heard wisdom like "it's irresponsible to use Kafka when you could just use RabbitMQ" but why does that statement not work equally well in the opposite direction? It seems like some "you don't need this fad technology" sentiments don't provide a whole lot of justification for sticking with the unfashionable choice. Does it all come down to "the devil you know?" What if you aren't that experienced with either choice?
- sidlls 9y ago
  > I've often heard wisdom like "it's irresponsible to use Kafka when you could just use RabbitMQ" but why does that statement not work equally well in the opposite direction? It could, in some circumstances. Generally, though, the two have only a very small overlap with respect to messaging use cases. One was designed to be general purpose and solve a variety of MQ use cases and serve even "dumb" clients. One was designed very specifically to impose a high burden of state tracking on clients for a very specific paradigm. > It seems like some "you don't need this fad technology" sentiments don't provide a whole lot of justification for sticking with the unfashionable choice. The "unfashionable choice" that works doesn't need justification. The new shiny one does.
  - closeparen 9y ago
    >The "unfashionable choice" that works doesn't need justification Why? That's what I'm asking.
    - suchire 9y ago
      The older choice usually by default has: - More people who know how to operate it - A greater portion of its failure modes that are known, with workarounds - Mature tooling and libraries New technologies need a compelling reason that their pros will outweigh the above incumbent benefits.

by sidlls 9y ago

cookiecaper 9y ago

As in everything else, the portion of actually useful and competent decision-makers in tech is vanishingly small. There are plenty of fine worker bees, but they're all too easy for marketers to divert. Ironically, such diversion is normally done with promises that deploying NEW_TECH_Z (which is almost always OLD_TECH_Y dressed up in a different outfit) will instantly make users useful and competent.

closeparen 9y ago

Compared to what? I've often heard wisdom like "it's irresponsible to use Kafka when you could just use RabbitMQ" but why does that statement not work equally well in the opposite direction? It seems like some "you don't need this fad technology" sentiments don't provide a whole lot of justification for sticking with the unfashionable choice. Does it all come down to "the devil you know?" What if you aren't that experienced with either choice?

sidlls 9y ago
> I've often heard wisdom like "it's irresponsible to use Kafka when you could just use RabbitMQ" but why does that statement not work equally well in the opposite direction? It could, in some circumstances. Generally, though, the two have only a very small overlap with respect to messaging use cases. One was designed to be general purpose and solve a variety of MQ use cases and serve even "dumb" clients. One was designed very specifically to impose a high burden of state tracking on clients for a very specific paradigm. > It seems like some "you don't need this fad technology" sentiments don't provide a whole lot of justification for sticking with the unfashionable choice. The "unfashionable choice" that works doesn't need justification. The new shiny one does.
- closeparen 9y ago
  >The "unfashionable choice" that works doesn't need justification Why? That's what I'm asking.
  - suchire 9y ago
    The older choice usually by default has: - More people who know how to operate it - A greater portion of its failure modes that are known, with workarounds - Mature tooling and libraries New technologies need a compelling reason that their pros will outweigh the above incumbent benefits.