Dinis Cruz

@DinisCruz

CISO and SVP Engineering at Glasswall, Transformation agent, project leader of OWASP SBot and O2 Platform projects Personal account, options are my own

London
Vrijeme pridruživanja: rujan 2008.

Tweetovi

Blokirali ste korisnika/cu @DinisCruz

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

  1. Prikvačeni tweet
    2. stu 2018.

    My Generation Z Developer is now published on Amazon :)

    Poništi
  2. prije 3 sata

    It's only 11am and in our meetings this morning there has already been more than 10 mentions of PST (Pioneers, Settlers and Town Planners) Common language is staring to be occur :)

    Poništi
  3. prije 15 sati

    Just upgraded the GW_Bot to use a much more recent version of Chromium Screenshot was taken from the lambda function (note: it is out of date by 0.0.0.123 versions :) ) I'm using the binary from project

    Poništi
  4. prije 17 sati

    Hi the Version 69.0.3494.0 (Developer Build) (64-bit) is crashing when trying to login to cloud have you seen this behaviour? I hit this when using puppeteer/pyppeteer

    Poništi
  5. proslijedio/la je Tweet
    prije 17 sati
    Odgovor korisnicima i sljedećem broju korisnika:

    Well , scanners don't understand the application's logic (which REST is part of it) Amazing how event after all these years, APIs testing is not a solved problem somebody should pick up the since key part of the solution is already there

    Poništi
  6. prije 20 sati

    Amazing how I missed the environment it is such a great way to interact with data, debug issues, and capture coding workflows

    Poništi
  7. prije 20 sati

    Hi is there a way to see the current status of the Ngrok server performance? I'm using it for a project where we are seeing some latency in opening up some pages, and I'm thinking that it could be NGrok

    Poništi
  8. 2. velj

    As we grow and evolve, it is very important to capture the past, so that we can learn from it in the future

    Prikaži ovu nit
    Poništi
  9. 2. velj

    Here is blog post just published by Hewitt that makes me really proud of the change of culture that has happened at Glasswall in the last 3 months (driven by my ideas on openness and collaboration)

    Prikaži ovu nit
    Poništi
  10. 2. velj

    and Task-11 being updated to NOT contain the link to the (now deleted) TASK-36

    Prikaži ovu nit
    Poništi
  11. 2. velj

    the issue being deleted from

    Prikaži ovu nit
    Poništi
  12. 2. velj

    which is captured in two new events

    Prikaži ovu nit
    Poništi
  13. 2. velj

    Final step is to delete Task-36

    Prikaži ovu nit
    Poništi
  14. 2. velj

    Task-11 has also been updated to include a link to Task-36

    Prikaži ovu nit
    Poništi
  15. 2. velj

    Here is the data that is stored for Task-36

    Prikaži ovu nit
    Poništi
  16. 2. velj

    and the dashboard shows the new issue too (it was picked up because the new issue has a link to 'Task-11')

    Prikaži ovu nit
    Poništi
  17. 2. velj

    First view in shows the two events we received from

    Prikaži ovu nit
    Poništi
  18. 2. velj

    This is what the newly created 'Task-36' looks like

    Prikaži ovu nit
    Poništi
  19. 2. velj

    and link it to 'Task-11'

    Prikaži ovu nit
    Poništi
  20. 2. velj

    To trigger the use case, first step is to create a new Issue

    Prikaži ovu nit
    Poništi
  21. 2. velj

    2nd view is a dashboard which is doing a search for particular issue value (this will allow use to see the contents of the data stored in to confirm that all that has been changed in Jira has been changed in Elastic) Note the 'Task-11' filter on the top right

    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:

    ·