Andy Zaidman

@azaidman

Full professor . All about software engineering . Software tester. Software evolutionist. Researcher. Teacher, dir. of studies. Storyteller.

Delft, The Netherlands
Vrijeme pridruživanja: srpanj 2009.

Tweetovi

Blokirali ste korisnika/cu @azaidman

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

  1. proslijedio/la je Tweet
    2. velj

    Good news! Our paper "How Bugs Are Born: A Model to Identify How Bugs Are Introduced in Software Components" co-authored by yt Daniel German is accepted for presentation at Journal First track.

    Poništi
  2. proslijedio/la je Tweet
    2. velj

    One of the ironies (tragedies?) of programming is that making something complex is so easy.

    Poništi
  3. proslijedio/la je Tweet
    1. velj

    Don't like maintaining library dependencies? Don't miss 's talk on , a project working towards intelligent and sustainable dependency management!

    Prikaži ovu nit
    Poništi
  4. proslijedio/la je Tweet
    1. velj

    Fascinating debate on bill of materials and compliance at the legal and policy devroom. To be continued this afternoon at the dependency management room: including talks by debaters , and yt

    Poništi
  5. proslijedio/la je Tweet
    31. sij

    That is what is all about: James: British 🇬🇧, Vito, Jasper: Dutch 🇳🇱, Carlo: Italian 🇮🇹, me: Polish 🇵🇱 We are all scientists. Despite our different backgrounds We will miss you UK: You are, and always will be, part of European family 🇪🇺

    Poništi
  6. proslijedio/la je Tweet
    31. sij

    Great keynote by chief architect Jan van Zoest. Conformance to reference architecture is CEO-level KPI.

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

    Key take-aways from Jan van Zoest, chief architect at Philips. Good summary to use in a software architecture intro slideset. See Conway 's law?

    Poništi
  8. proslijedio/la je Tweet
    31. sij

    Philips' Chief Architect Jan van Zoest discusses his company's health platform HealthSuite. In a way, Philips has evolved towards being a software developer.

    Poništi
  9. proslijedio/la je Tweet
    31. sij

    Are you personally using a Linux distribution? Consider responding to this 5-minute survey on package outdatedness in Linux distributions:

    Poništi
  10. proslijedio/la je Tweet
    31. sij

    If you do research in talk to Philips. Seems like software architecture Valhalla

    Poništi
  11. proslijedio/la je Tweet
    31. sij

    The people we admire the most are not those who never fail. The people we admire the most are those who have the courage to try things that might not work and the resilience to keep going when things don’t go as planned.

    Poništi
  12. proslijedio/la je Tweet
    31. sij

    R&D at Philips: 11,500 employees, 60% in software.

    Poništi
  13. proslijedio/la je Tweet
    31. sij

    60% of Philips R&D is software. Yup, software is eating the world even more.

    Poništi
  14. proslijedio/la je Tweet
    31. sij

    Five of the fathers of Dutch Software Engineering are awarded and become honorary members of Gentlemen you have our eternal gratitude

    Poništi
  15. proslijedio/la je Tweet
    31. sij

    Great initiative by ! Honorary fellows in (Dutch) Software Engineering: Jan Bergstra, Hans van Vliet Doaitse Swierstra, Mehmet Aksit, Rinus Plasmeijer, Roel Wieringa, Fahrad Arbab, Paul Klint

    Poništi
  16. proslijedio/la je Tweet
    30. sij

    Dear software practitioners, if you have ever annotated your design and implementation choices while coding, we would appreciate it if you could help us participating in this short survey: Thanks a lot, and feel free to RT.

    Poništi
  17. proslijedio/la je Tweet
    30. sij

    Build Automation and Programming Languages (BAPL 2020) ... to explore the interaction of build automation and programming languages in systems for incremental analysis, building, testing, packaging, and deployment of software. At PLDI 2020 Contribute!

    Poništi
  18. proslijedio/la je Tweet
    30. sij

    In my team at GitHub, we'd like to study examples of "nefarious commits" in open source, which introduce a bug on purpose. Can you point me at such commits? Could it have been detected by analysing the committer's behaviour as well as the code change itself?

    Poništi
  19. proslijedio/la je Tweet
    30. sij

    The are conducting a user study to evaluate the impact of collaborative features on database-related tasks. Participants will be entered into a raffle for $20 Amazon gift cards. All levels of experience are welcome! Retweets appreciated!

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

    Hi, I'm studying how project maintainers perceive the effects of code review bot adoption on pull requests. It takes no more than 10 minutes. It’s voluntary and confidential, with no commercial objective! Thanks!

    Prikaži ovu nit
    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:

    ·