Michael Feathers

@mfeathers

Director, R7K Research & Conveyance. Author of Working Effectively with Legacy Code.

Miami, FL
Vrijeme pridruživanja: ožujak 2008.

Tweetovi

Blokirali ste korisnika/cu @mfeathers

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @mfeathers

  1. Prikvačeni tweet
    25. pro 2016.

    Once you start looking for confirmation bias you see it everywhere.

    Poništi
  2. proslijedio/la je Tweet
    4. lis 2018.

    Most problems in software development are problems of incentive. It's funny that we don't seem to approach them at that level.

    Poništi
  3. proslijedio/la je Tweet
    8. kol 2019.

    Fred Brooks said that software is best when it looks like it was designed by one mind. Mob programming is an attempt to create one mind of many. Quality goes down as the number of people touching code independently goes up. Interesting constraint problem.

    Poništi
  4. 27. sij

    Unison - a content-addressable programming language

    Poništi
  5. proslijedio/la je Tweet
    22. sij
    Odgovor korisniku/ci

    The trick is to organize applications so that exceptions (if they are used) are thrown from the shallow edges rather than the depths.

    Poništi
  6. 22. sij

    d3 is sort of a mirror image of git. The pretty model is outside rather than inside, but you still have know the inside.

    Poništi
  7. proslijedio/la je Tweet
    20. sij

    A significant driver for recommending better-defined teams and interactions in 👇

    Poništi
  8. 20. sij
    Prikaži ovu nit
    Poništi
  9. 20. sij

    Now more than ever, teams exist in the mind, and orgs may not have any accurate picture of them.

    Prikaži ovu nit
    Poništi
  10. 20. sij

    Cognitive load: “how many people do I need to collaborate with to do this?” is a big deal.

    Prikaži ovu nit
    Poništi
  11. 20. sij

    Sense of team identity and purpose affect how often people stay inside or step outside these nebulous bounds of collaboration.

    Prikaži ovu nit
    Poništi
  12. 20. sij

    Social distance now is less spatial. The metric is more: do these people talk at all, and if they do, how frequently? Do they see themselves as coordinating collaborators?

    Prikaži ovu nit
    Poništi
  13. 20. sij

    Two people can sit next to each other and each interact more with different people on the opposite side of the building (or world). In what sense, then, are they part of the same team?

    Prikaži ovu nit
    Poništi
  14. 20. sij

    Conway’s Law is about how social grouping affects design. My sense is that “grouping” is far more nebulous than we realize due to our increased reliance on communications technology in teams.

    Prikaži ovu nit
    Poništi
  15. proslijedio/la je Tweet
    20. sij

    BTW I got the idea for this technique from 's Working Effectively with Legacy Code, one of the most useful programming books I've ever read.

    Poništi
  16. proslijedio/la je Tweet
    11. velj 2018.
    Poništi
  17. 19. sij

    Well reasoned but I’d love to see discussions of typing move from what is and isn’t possible to ergonomics: what is easy and hard over the lifecycle. Static and dynamic have different affordances and make different trade offs. It’s a contextual choice.

    Prikaži ovu nit
    Poništi
  18. 17. sij

    Languages are tools. There can be many communities.

    Prikaži ovu nit
    Poništi
  19. 17. sij

    It’s hard for me to read this and remember issues in Scala without having the thought that it might be overreach to consider programming language and community the same. It certainly seems to lead to more strife than necessary.

    Prikaži ovu nit
    Poništi
  20. 14. sij

    The math of organization scaling.

    Poništi
  21. 14. sij
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·