Comments by "edgeeffect" (@edgeeffect) on "Developer Voices" channel.

  1. 14
  2. 10
  3. 6
  4. 5
  5. 5
  6. 4
  7. 4
  8. 4
  9. 3
  10. 3
  11. 2
  12. 2
  13. 1
  14. 1
  15. 1
  16. 1
  17. 1
  18. 1
  19. 1
  20. On the subject of Taylorism and Scientific management.. I think some of the best and most useful work I've done has been as a result of being Taylor's imagined very lazy employee... desperately trying to automate myself out of a job. ;) When Diana talks about how she loves and embraces complexity, it get's me thinking about how there's two kinds of complexity (and I forget the words that distinguish them right now). But, yes, there's the inescapable complexity that comes from the systems we are modelling. But there's also the totally unnecessary complexity that we, as developers, choose to add to our projects. Like unnecessarily generalised and overblown frameworks and our desires to try out unsuitable solutions that would look awfully nice on our CVs. This is the complexity that we desperately need to be rid of. When Diana's talking about the non-evolution of agile, I think she's put her finger on one of the huge problems we have in our industry in particular and probably in the world at large too. We can come up with an idea that helps to solve some of the problems we have NOW and if it does a really good job of helping to solve those problems, it becomes "the one true faith" (I'm really, really, thinking of SOLID as I say this). And the moment any idea becomes "the one true faith" it pretty-much instantly become a huge impediment to any kind of further progress to solving the problems that we have NOW (because that old "NOW" turned into "then" pretty quickly) but we cling to our old ideas because they were so great back when we first had them and why can't they still be great now. But time marches on. I made "If you're forcing regular expression on people, then there's an empathy problem" into a nice "quote-meme" to share on Slack at work. :)
    1
  21. 1
  22. 1