The Dev-X Project is a series of features with industry leaders sharing their developer experience insights. In each “episode”, we ask an industry leader 10 interesting questions about DX, collect their responses and insights and share them with you.
Tal cares deeply about developer experience. In building Torii he says he is “building the company I’d like to work for. Best people, best technology, happiest customers.”
We really appreciate Tal taking the time to share some of his DX insights with the community.
When did you decide to become a developer?:
[Tal Bereznitskey]: At the age of ~6 I learned that my Atari console can run Basic and I got a programming book and starting building games. Having the ability to imagine something and create it with a short feedback loop was amazing. From that point I pretty much knew that’s what I’ll always want to do.
What are the key ingredients to a really good engineering culture?:
[T.B.]: A good culture starts from trust between the team members, holding each other to high-standards, being curious and always striving to improve.
Let’s say you’re building something from scratch. What does your ideal stack look like?:
Tell us about an epic engineering fail you’ve experienced in your career. What did you learn from it?
[T.B.]: I once worked on a large C/C++ project and noticed an existing function that returned no value, although the caller expected one. It was widely used. So I fixed the function to return the value and that crashed the entire system. I learned that you should respect the past, be curious and use git blame/annotate to figure out why weird thing in the code exist before you change them.
How important is “Developer Experience”? Do you see this as a trend that will evolve into dedicated teams/functions for mainstream tech companies?
[T.B.]: For a developer, DX is everything. As someone who enjoys programming, I can feel the love poured into tools that just work amazingly well and sees the developer who is going to use them. I believe every team from a certain size will benefit from having dedicated people working on internal tools, or optimizing the DX for the rest of the team.
Let’s take the mono-repo question once and for all - should you ‘go mono’?
[T.B.]: I do not have enough experience with mono-repos, but they are definitely here to stay.
What will be the hottest dev trend/adopted technology in 2022?
[T.B.]: I hope to see Svelte gain more traction and becoming mainstream.
Some claim that front-end developers will become irrelevant in the future of no-code tools. Do you see this happening? If so, how soon?
[T.B.]: I believe they will not become irrelevant but they can start working on more higher level issues than before. I do hope to see front-end developers working less on aligning items, and more on providing a great user experience for their users.
Share some tips to help remote teams collaborate better:
[T.B.]: Get on a “face to face” call when Slack messaging isn’t progressing the conversation well enough. Seeing people (even on video) helps team members to work together and understand each other better.
Do you want to share anything else? Please share anything you think would be of value to the broader developer community:
[T.B.]: I created a browser extension to scratch my own itch and it seems others had the same problem, now used by 20K+ daily active developers. It’s called “Better Pull Request for GitHub” and helps with code reviews on GitHub. You can check it out here.