Sergii Shymko

@SergiiShymko

Director of Engineering, Magento Architect, Magento 2 Co-founder

Los Angeles, CA
Vrijeme pridruživanja: ožujak 2015.

Tweetovi

Blokirali ste korisnika/cu @SergiiShymko

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

  1. proslijedio/la je Tweet
    29. sij

    Hey peeps, when it comes to pipeline deployment to production, what do you prefer?

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

    Google's Chrome browser is scheduled to change how it handles SameSite Cookies in 4 days. Is your Magento site ready? We've put together an article to help users understand the change and access helpful resources for this time-sensitive issue.

    Poništi
  3. proslijedio/la je Tweet

    This image has floated around for ever but I've never seen a credit - who made it?

    Poništi
  4. proslijedio/la je Tweet
    prije 6 sati

    A clever art installation reminding us that "data is not objective and [...] can be hacked and manipulated"

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

    Truly inspiring piece on engineering greatness: immerse yourself in the low level problems to get insights on how to build systems at scale; change the direction of own career to pursue things which you believe in

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

    I was ready to roll my eyes for just another SOLID video. Gave it a chance. Was surprised. It *actually* mentions single responsibility does not mean single task. It also gives you method how to detect when code is split too much. Separate mapping files anyone? Ha

    Poništi
  7. 1. velj

    Admitting mistakes in front of colleagues/management is necessary. I have no problem owning my mistakes, although it's unpleasant (thus striving to minimize them). Reaction is more interesting: people are shocked to hear somebody directly taking responsibility for their errors.

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

    Handy graph from NYT. TLDR: don’t panic

    Poništi
  9. 31. sij

    Modern debugging tools track down problematic code rather quickly provided the issue is reproducible. Most difficulty is in evaluating alternative fixes. Ideal fix should improve code maintainability (simplify, reduce dependencies, etc.) not just patch the test case.

    Poništi
  10. proslijedio/la je Tweet

    Do you know somebody who fits this profile: • Owns a profitable internet business doing $500k-$10MM in annual profit • Wants to sell and have the freedom to leave, in a quick 30 day process We are paying $25,000+ referral fees. All you have to do is intro us 😊💕😊

    Poništi
  11. 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
  12. proslijedio/la je Tweet
    29. sij
    Prikaži ovu nit
    Poništi
  13. 30. sij

    Inventory tracking is always problematic in implementations. Nobody's happy with their inventory sync up across channels/systems. Accuracy, latency, performance are always an issue.

    Poništi
  14. 30. sij

    Has anybody experienced generating empty merged CSS files? Seems to be related to concurrent writes to file system. Any known solution/workaround?

    Poništi
  15. 30. sij

    The issue of broken page scrolling somehow passed testing (likely because of dependence on cookies) and resulted in total inability to browse the sites on mobile for many months before the issue was finally noticed.

    Prikaži ovu nit
    Poništi
  16. 29. sij

    Dev 1 who implemented the CSS media query hack is the author of 175-lines added to 15 files instead of 1-line fix! Would you keep such a person if they’re doing the same thing times and times again regardless of all the coaching?

    Prikaži ovu nit
    Poništi
  17. 29. sij

    Let me tell you how codebases turn into trash. Small changes like that seem harmless: few lines here or there, what a big deal? Now imagine every task, no matter how simple it is, being done with such quality and attitude. Few months and codebase is unmaintainable!

    Poništi
  18. 29. sij

    Imagine JS popup displayed via () on 2nd page visit tracked via cookies. Business wants no popup on mobile. Dev 1 hides popup via CSS media query breaking scrolling. Dev 2 adds screen size checks to show() method. For God's sake, call show() conditionally!

    Prikaži ovu nit
    Poništi
  19. 29. sij

    What's your best practice for storing secrets, such as payment gateway API Keys, in projects? I advocate to commit encrypted values to repo in config.xml files. Encryption key is NOT in the repository. Deployment inserts the key from env variables to app/etc/env.php.

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

    Yesterday alongside 2.3.4 we released our official Page Builder PWA Studio integration, this enables any new PWA Studio store to utilize Page Builder within CMS Pages 🎉🎉🎉

    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:

    ·