Ro Ro Ro Your Boat

@_yoitsro

I once did a star jump on the Queen's lawn. CTO at .

Stockholm, Sweden
Vrijeme pridruživanja: listopad 2009.

Tweetovi

Blokirali ste korisnika/cu @_yoitsro

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

  1. Prikvačeni tweet
    8. sij

    We () are now for a Javascript Developer! Come and join us in changing the way the world works! 👉

    Poništi
  2. 23. sij

    We've recently had a few graduates apply for our developer role at , but we've not taken any of them forward. Kinda brutal, I know, but let me tell you why:

    Poništi
  3. 22. sij

    A few of the big reasons I chose to develop two native apps for rather than go down a "hybrid" route.

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

    Building stuff is hard. Ro (), our CTO, offers a behind-the-scenes glimpse into the world of a

    Poništi
  5. 9. sij

    Hiring is difficult. Make it easier for me? :)

    Prikaži ovu nit
    Poništi
  6. 9. sij

    Your product will pivot. That’s okay. Customers won’t come instantly. That’s okay. Trust your team. Stay positive, keep your head up and don’t be afraid of uncertainty ✌️

    Prikaži ovu nit
    Poništi
  7. 9. sij

    Don’t forget to appreciate those who have to put up with you day in, day out 🥰 They’re the ones who have to listen to your inane ramblings and deal with your grumpiness when things aren’t working!

    Prikaži ovu nit
    Poništi
  8. 9. sij

    Don’t neglect sleep. Without sleep, you can’t function, you can’t communicate, you can’t survive 💤

    Prikaži ovu nit
    Poništi
  9. 9. sij

    Don’t underestimate how long things out of your control will take i.e. App Store reviews. This almost caught us out meaning we’d have nothing for iOS users to use for National Coworking Day.

    Prikaži ovu nit
    Poništi
  10. 9. sij

    Just because you want to learn loads of new things doesn’t mean other people on your team will. You’re either going to have to do a lot of hand holding or you’ll have to explain concepts you yourself haven’t fully understood.

    Prikaži ovu nit
    Poništi
  11. 9. sij

    If you use Javascript, use . It plays well with . It also reduces the mental capacity required when working within a monorepo i.e. needing to know the parameters of particular function from a different package.

    Prikaži ovu nit
    Poništi
  12. 9. sij

    A better way to share common data access logic is to use something like a monorepo. We now use the concept of repo packages (for data access), service packages (for business logic) and API packages (for public consumption of our services).

    Prikaži ovu nit
    Poništi
  13. 9. sij

    Unless you have a small army of developers with lots of teams needing access to the same data in a normalised way, my concept of internal microservices is incredibly pointless 🙃

    Prikaži ovu nit
    Poništi
  14. 9. sij

    gRPC/Protocol Buffers are amazing! Since it generates the stubs for most common languages, if you change your definitions, as long as you ensure those definitions are consumed by the clients, simple errors can be caught at compile time 🎉

    Prikaži ovu nit
    Poništi
  15. 9. sij

    Microservices are fine, but they don’t necessarily provide resilience. An argument for using microservices is that if one service goes down, the rest of the app is still fine. Chances are, your databases will bail before your application code does, in which case, it’s game over.

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

    Integration tests are probably a better way to go. It’s the much more efficient equivalent of the old skool way of “testing”, where you change something, refresh the page and hope to see what you expect 🤷‍♂️

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

    Unit tests with 100% code coverage is excessive and restrictive. Test the bits of logic which you know are complex and which you know will cause you a potential headache in the future.

    Prikaži ovu nit
    Poništi
  18. 9. sij

    We’re now at a point where Kubernetes makes sense. It helps us scale as we need to and I actually know what I’m doing with it now...

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

    Kubernetes is incredibly powerful and has a lot of potential. With a basic setup, it’s almost definitely more powerful (and more costly) than you need it to be when running simple applications. If you don’t need it, use the likes of etc or a platform.

    Prikaži ovu nit
    Poništi
  20. 9. sij

    Start simple, start small. Kubernetes is not necessary. Microservices are not necessary. gRPC is not necessary. Self-hosted CI is not necessary. Self-hosted databases are not necessary. The requirement to scale does not occur overnight. These things can wait.

    Prikaži ovu nit
    Poništi
  21. 9. sij

    So, what have I learnt after building for 2 years?

    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:

    ·