Alessandro Diaferia

@alediaferia

Building product . When I'm not coding at my laptop I'm most likely eating or travelling with and Hiro 🐶

Joined January 2010

Tweets

You blocked @alediaferia

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @alediaferia

  1. 21 hours ago

    Hiro has been out partying for Yesterday and is now hungover.

    Undo
  2. Aug 25

    Do you keep your stories implementation-language free? Avoiding implementation details will help you focus on the problem. You'll be amazed at how many more effective solutions you'll be able to explore

    Undo
  3. Aug 24

    Documenting is not only useful for your readers but it also helps validate your ideas. Use it as an opportunity to improve instead of considering it plain overhead.

    Undo
  4. Aug 24
    Undo
  5. Aug 24

    Keep an eye on this. Very important exercise in order to understand how to decouple your code dependencies and move towards bounded contexts.

    Undo
  6. Aug 23

    Empower your engineering teams to continuously strangle your technical debt.

    Undo
  7. Aug 22

    Product engineering is the practice of guaranteeing that the software craft supports the product vision

    Undo
  8. Aug 21

    Bringing too many implementation details into the discussions anchors your thinking to the status quo, potentially preventing you from identifying the right value for the users of your product.

    Undo
  9. Aug 17

    Keeping the implementation details of your as secret as possible will help you stay when reacting to changes

    Undo
  10. Aug 15

    Great summary on the principles that drive our engineering hiring process at by . Check it out!

    Undo
  11. Aug 14

    If your Pull Request checklist has become a manual on how to code at your company, have you considered replacing your engineers with a neural network?

    Undo
  12. Aug 12

    Great insights on how to do code review. When was the last time you checked out a Pull Request and tried running it locally? Do that before asking the PR author for clarifications: you'll learn much more about the changes and you'll keep bias away.

    Undo
  13. Aug 12
    Undo
  14. Aug 11

    Totally agree with this statement from . Isolation is vital to reach clarity. TDD is one way of helping reaching it at an implementation level. But don't forget that TDD alone does not architect systems.

    Undo
  15. Jul 24

    Every line of code you write is a liability. Write very little code.

    Undo
  16. Aug 7

    A quick reminder that nobody in software has any idea how long anything is going to take. Set an optimistic goal, limit the hell out of the scope, and get going. And forgive yourselves when targets slip. Send this tweet to your manager.

    Undo
  17. Aug 8

    If your technology is better but potential customers are too set in their ways to switch, use it yourself and compete with them.

    Undo
  18. Aug 7

    I guess the purpose of a screaming architecture is not to make the next unlucky engineer scream in pain when trying to debug an issue, right?

    Undo
  19. Aug 7

    Stop lying to yourself: your code is not self explanatory. Document it!

    Undo
  20. Aug 2
    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·