mijailr

I work at LittleHorse, though I'd been on the other side of this problem: owning services coordinating complex business flows that nobody could see end to end. We'd sometimes get questions like "why hasn't this account been activated yet?" and the honest answer was "give me a couple hours to track down and check the logs of each service involved."

The pitch that landed for me wasn't durability, it was the process itself becoming a first-class object: versioned, typed, and navigable. Something you can put in front of a non-engineer and they'll actually understand it. With Business-as-Code you can now see and own the entire process end to end.

I think that to have a good opportunity to get hired for a remote role you should have a very good personal brand, your code quality and your contributions to open source projects. Some times I receive job offers from people that looks at something that I made on GitHub.

So I can say: "My tactics is to love what I do, share knowledge with others and contribute to open source projects"

This is the first time I tried to make somthing with Golang, In fact I was never tried to learn Golang, so this is an exercise to learn the basics of Golang. Maybe is a very bad implementation, but feedback is welcome.