Tweetovi

Blokirali ste korisnika/cu @latebound

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

  1. proslijedio/la je Tweet
    2. sij

    the amazon was on fire for all of 2019. australia starts 2020 on fire. notre dame burned for 15 hours and people donated a billion dollars in one day.

    Poništi
  2. proslijedio/la je Tweet
    29. pro 2019.

    The queue is the pipeline that takes the idea in our heads and turns it into working software users can try for real. But over-emphasis on that queue tends to obscure that it's a *loop* feeding directly back into itself with *better* ideas

    Prikaži ovu nit
    Poništi
  3. 17. pro 2019.

    Good tests tell a story. Good stories don't follow a template. Pushing a bit harder on the notion of a test being a self-contained story that and talk about here:

    Poništi
  4. proslijedio/la je Tweet
    13. pro 2019.

    There is no “balance”, just as there is no balance between making art with a pencil and making art with Illustrator; no balance between interviewing a patient and using an MRI machine. We use tools if, when, and how they suit the task at hand. That’s not about “balance”.

    Poništi
  5. 12. pro 2019.

    Beck saying he'll at times print out tests and highlight relevant facts made me wonder - why don't our IDEs/editors support such arbitrary highlighting of bits of code to assist us in comprehending or explaining code? I'd find it useful if would support such a feature

    Poništi
  6. 12. pro 2019.

    It seems to me that one cannot succeed at the test && commit || revert workflow without the . If you're doing , you're probably following the , tacitly if not explicitly.

    Poništi
  7. 10. pro 2019.

    Such an amazing topic, I can hardly wait. When I listen to and , I learn about so much more than testing. I'm sure this'll be no exception and would be useful for programmers, too.

    Poništi
  8. 10. pro 2019.

    "When you take a tester away from testing and have them write automation, you likely lose a GOOD TESTER and gain a bad developer." I've said this for a long time, but not as well put as this.

    Poništi
  9. proslijedio/la je Tweet
    23. lis 2019.

    1) Current line of RST development for and me: testing begins with a bootstrapping process. You don’t know how to test something until you’ve tried to test it! So: survey what you’ve got; visit every important aspect of it; look for what is there to be tested. /

    Prikaži ovu nit
    Poništi
  10. proslijedio/la je Tweet
    8. pro 2019.
    Odgovor korisniku/ci

    My hope is that this, in combination with the concept that testers look for problems *where we don’t expect them* (where automation checks for success where we do expect it) helps the “automate all the testing” people adjust their mental models of testing. (3/3)

    Poništi
  11. proslijedio/la je Tweet

    Thanks also to for renewing my motivation to work on the project!

    Poništi
  12. proslijedio/la je Tweet
    29. lis 2019.

    Goodhart’s curse: Every metric that can be tracked gets incentivized and ultimately gamed Conway’s curse: Every decision-making dysfunction in your team reflects itself in your product Hofstadter’s curse: Every project takes longer than planned, no matter how great the plan

    Poništi
  13. proslijedio/la je Tweet
    23. lis 2019.

    Every day, someone proudly touts running a buhzillion automated checks “because neither we nor the developers have *any idea* where something might have been affected by a change.” Translation: the code is out of our mental control. Bad enough, but the checks probably are too.

    Prikaži ovu nit
    Poništi
  14. 12. lip 2019.

    If diversity is being invited to a party, inclusion is being glad you're there. -

    Poništi
  15. proslijedio/la je Tweet
    19. sij 2019.

    TDD Pro-Tip: Because the power of TDD is operational rather than artifactual, test-before provides several benefits over test-after.

    Prikaži ovu nit
    Poništi
  16. 29. lis 2018.

    1 of my 7 reframings so far: I can produce quality code when (focus on) code quality doesn't stand in the way of achieving OKRs -> Code quality that improves the likelihood of achieving OKRs lets me produce quality code

    Prikaži ovu nit
    Poništi
  17. 29. lis 2018.

    Trying to apply 's to: "Can't produce quality code 'coz incentive to achieve OKRs is more pressing than code quality". I'd love to hear from all you wise people your reframing of that objection as a goal.

    Prikaži ovu nit
    Poništi
  18. 21. lis 2018.

    Suggestion, - make 'em real pockets and leave it to the wearer to decide whether to leave 'em empty or stuff 'em. for every gender

    Poništi
  19. 17. lis 2018.

    . Here's a reference to the quote I shared with you at : Testers don’t break the software. They break illusions about the software. - . I hadn't realized then, but it's quoting his colleague.

    Poništi
  20. 4. ruj 2018.

    Use right as the facilitation tool it's meant to be, rather than just another test tool by emphasizing behavior over structure

    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:

    ·