Tweetovi

Blokirali ste korisnika/cu @jamesmh_dev

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

  1. Prikvačeni tweet

    Building microservices is easy. What's hard: - Discovering proper boundaries - Integrating services (Messaging vs RPC) - Error handling (resiliency) - Sociotechno concerns (team boundaries, org changes) Can you think of any more?

    Poništi
  2. "If you can’t think of three things that might go wrong with your plans, then there’s something wrong with your thinking."

    Poništi
  3. "computer programmers are in the habit of gilding their mistakes by calling them bugs."

    Poništi
  4. proslijedio/la je Tweet
    22. sij

    Don't miss this meet up in Vancouver: Vancouver Event Driven Meetup Will be held at offices in Vancouver! You can join remotely. will join remotely!

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

    These 2 accounts are now the effort of more people than just me! for insights into understanding information systems. for up coming workshops, consulting help and other services including upcoming platforms and products. Please follow and RT!

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

    I read Refactoring Typescript by (the e-book) and liked it. I found it a nice refresher, a quick and easy read, and learned a few new ideas for refactoring, most notably CQRS. My slightly longer review:

    Poništi
  7. Would have to agree🙄: "Don’t use location as an excuse to pay developers less, unless you’re satisfied with average developer talent."

    Poništi
  8. This is SO true in software development. This is why code review, pair programming, automated testing, deep design, collaboration, etc. are so important. But to the un-seeing eye - these are "invisible, boring, seems too easy, feel unnecesseary" 😮

    Poništi
  9. Dev Tip: Got a singleton? Don't forget to make sure it's thread-safe!

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

    "What do you mean, this code is stupid? It looks EXACTLY like the architecture diagram you gave me!"

    Poništi
  11. I can see the typical arguments around "improper boundaries" coming up, but given a certain context I think something like this is a good "stepping-stone" or first step. Any thoughts?

    Prikaži ovu nit
    Poništi
  12. - Easier for devs to understand (helps with limited skillset / learning curve of splitting BCs) - No need to copy data to another BC (org restrictions / tech restrictions) - Less risk for teams new to (no SQL migrations needed at this point).

    Prikaži ovu nit
    Poništi
  13. That's in-memory communication. One might consider HTTP caching to be similar? Anyways... Some trade-offs / considerations:

    Prikaži ovu nit
    Poništi
  14. needs to display a user's name along with some other related info (on a UI), do you think something like this would have better trade-offs? user BC <- (user BC cache) <- BC X BC X will call the user BC directly but get cached data so it's not crazy DB hits all the time.

    Prikaži ovu nit
    Poništi
  15. For example, an application that clearly has a BC dealing with users in some fashion (let's say "employee management or whatev). When dealing with a user's (first+last) name, for example, instead of using an integration event to copy the name to another context that...

    Prikaži ovu nit
    Poništi
  16. Due to limited team skill-set, small # of devs, tech limits, etc. it might actually be a better move to create bounded contexts that don't integrate via events and copy data? Perhaps some BCs need to directly call one another as a first "splitting" attempt? (thread 👇)

    Prikaži ovu nit
    Poništi
  17. Took a look at "what is event modelling" again. Lots more content added around dealing with legacy systems, project management, etc.👍

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

    Hello world! When designing a fluent API, which method naming convention would you prefer (and why)! Please RT :-)

    Prikaži ovu nit
    Poništi
  19. proslijedio/la je Tweet

    Dev Tip 🔥: Always comment your pull-requests: - Why this change? - What could it affect? - Alternatives considered? - Code specific considerations? This will boost your reviews 🚀 and your reviewers will love you ❤

    Poništi
  20. Poništi
  21. proslijedio/la je Tweet
    21. sij
    Odgovor korisniku/ci
    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:

    ·