Podcasts about radoslav stankov

Interview with Radoslav Stankov, Head of Engineering at Product Hunt. He tells stories about him going from IC to Head of Engineering, the different stages he led through Product Hunt, the challenges he faces in product development, his leadership journal and much more. https://codingsans.com/engineering-management-newsletter?utm_source=Podcast&utm_medium=platforms (Sign up to the Level-up Engineering newsletter!) In this interview we're covering: The evolution of Product Hunt's structure Going from IC to leader Evaluating yourself as a leader The effects of the pandemic on remote work Leadership challenges in product development Learnings about product development And more! Excerpt from the interview: "I have a technique that I call my manager journal. I write a log of everything that happens every week. This includes the general things, like what I was doing or what core events happened to our system. I also use it to keep track of what I'm worried about that week. For example, there might have been an outage, or an argument in my team, or some of my points didn't go through. For example, my concern right now is the design system we're building. My main concern was balancing its flexibility with performance. I write these in my journal every week and check back every month to track how my concerns have changed and to see whether they'd been resolved." https://codingsans.com/blog/leadership-stories?utm_source=Podcast&utm_medium=platforms (Click here to read the full interview!)

Rado Stankov is the Head of Engineering at Product Hunt. He's based in Sofia Bulgaria. He walks us through learning Pascal and PHP and Flash. We then dive into Ruby and JavaScript and what he's working on now at Product Hunt. Host: Charles Max Wood Joined By Special Guest: Radoslav Stankov Sponsors G2i | Enjoy the luxuries of freelancing CacheFly ______________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ______________________________________ Links MRS 077: Radoslav Stankov RR 396: GrapQL at Product Hunt with Radoslav Stankov RRU 042: React at Product Hunt with Radoslav Stankov React Native at Product Hunt feat. Radoslav Stankov and Vlad Vladimirov Prototypejs jQuery Picks Radoslav Stankov: Dependency cruiser The Unicorn Project Charles Max Wood: The Name of the Wind LinkedIn Clean Coders Podcast Devchat.tv Workshops

Rado Stankov is the Head of Engineering at Product Hunt. He's based in Sofia Bulgaria. He walks us through learning Pascal and PHP and Flash. We then dive into Ruby and JavaScript and what he's working on now at Product Hunt. Host: Charles Max Wood Joined By Special Guest: Radoslav Stankov Sponsors G2i | Enjoy the luxuries of freelancing CacheFly ______________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ______________________________________ Links MRS 077: Radoslav Stankov RR 396: GrapQL at Product Hunt with Radoslav Stankov RRU 042: React at Product Hunt with Radoslav Stankov React Native at Product Hunt feat. Radoslav Stankov and Vlad Vladimirov Prototypejs jQuery Picks Radoslav Stankov: Dependency cruiser The Unicorn Project Charles Max Wood: The Name of the Wind LinkedIn Clean Coders Podcast Devchat.tv Workshops

Rado Stankov is the Head of Engineering at Product Hunt. He's based in Sofia Bulgaria. He walks us through learning Pascal and PHP and Flash. We then dive into Ruby and JavaScript and what he's working on now at Product Hunt. Host: Charles Max Wood Joined By Special Guest: Radoslav Stankov Sponsors G2i | Enjoy the luxuries of freelancing CacheFly ______________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ______________________________________ Links MRS 077: Radoslav Stankov RR 396: GrapQL at Product Hunt with Radoslav Stankov RRU 042: React at Product Hunt with Radoslav Stankov React Native at Product Hunt feat. Radoslav Stankov and Vlad Vladimirov Prototypejs jQuery Picks Radoslav Stankov: Dependency cruiser The Unicorn Project Charles Max Wood: The Name of the Wind LinkedIn Clean Coders Podcast Devchat.tv Workshops

Radoslav Stankov is the Head of Engineering at Product Hunt. He actually took over the post from our last guest, Andreas Klinger, and Andreas wanted us to follow up with Rado to learn about some of the changes he’s made. In this episode, we dive into the impact that “single-player mode” has on remote work and how Rado uses checklists and clear expectations to ensure his team gets onboarded effectively. For notes and a full transcription of the episode, visit woventeams.com/32. Special Guest: Radoslav Stankov.

This time I was talking with Radoslav Stankov. Radoslav is Head of Engineering at Product Hunt. He is a true source of knowledge. From organizing conferences to travelling around Europe and working remotely, you will hear a lot of interesting advices from Rado. If you want to meet him a person and learn more about React.js, you should definitely attend React Not a Conf he organizes every year in Sofia, Bulgaria. In this episode we talk about: Organizing conference Breaking into remote work Everyday habits Leading remote teams Optimizing remote work Notes and links: Product Hunt ReactNotAConf Vienna Andreas Klinger 2 Pizza Rule AngelList Feedback is underrated Routine Pomodoro Todoist Bear 1Password Audible Thinking Fast and Slow Antifragile The Pragmatic Programmer The Phoenix Project Refactoring to Patterns Radoslav Stankov Website Twitter Github Credits: Jan Jenko for header photo Gramatik for intro music

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Special Guest:  Radoslav Stankov Episode Summary In this episode of My Ruby Story, Charles hosts Radoslav Stankov, the head of the engineering team at Product Hunt. Listen to Radoslav  on the podcast Ruby Rogues on this episode. Radoslav was interested in technology from a young age, he was recruited by a company at a youth community center for IT support. He was interested in web development so he started to coding in PHP.  He then started learning Ruby on Rails and started working for a company which sells trucks where he built the Enterprise Resource Planning (ERP) system  in Rails. The user interface for this ERP system was very successful and Radoslav stresses any software that can’t be used by the client can not be considered very good. Radoslav then started working for a startup which failed but there he met the team  which eventually led him to the job at Product Hunt. Radoslav and Charles share stories where they were hired by people they had met at other projects. They point out that people like to keep hiring those they trust and admire. Radoslav then goes on to share projects he has been proud of throughout his career. Radoslav is currently at Product Hunt and one of the working to make the app work better and faster. Links Ruby Rogues: GraphQL at Product Hunt with Radoslav Stankov React Round Up: React at Product Hunt with Radoslav Stankov React Native Radio: React Native at Product Hunt feat. Radoslav Stankov and Vlad Vladimirov Radoslav’s Website Radoslav’s GitHub Radoslav’s Twitter https://devchat.tv/my-ruby-story/ https://www.facebook.com/DevChattv Picks Radoslav Stankov: The Ruby Toolbox formulaic Charles Max Wood: Skyward by Brandon Sanderson Writing Excuses Podcast  

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Special Guest:  Radoslav Stankov Episode Summary In this episode of My Ruby Story, Charles hosts Radoslav Stankov, the head of the engineering team at Product Hunt. Listen to Radoslav  on the podcast Ruby Rogues on this episode. Radoslav was interested in technology from a young age, he was recruited by a company at a youth community center for IT support. He was interested in web development so he started to coding in PHP.  He then started learning Ruby on Rails and started working for a company which sells trucks where he built the Enterprise Resource Planning (ERP) system  in Rails. The user interface for this ERP system was very successful and Radoslav stresses any software that can’t be used by the client can not be considered very good. Radoslav then started working for a startup which failed but there he met the team  which eventually led him to the job at Product Hunt. Radoslav and Charles share stories where they were hired by people they had met at other projects. They point out that people like to keep hiring those they trust and admire. Radoslav then goes on to share projects he has been proud of throughout his career. Radoslav is currently at Product Hunt and one of the working to make the app work better and faster. Links Ruby Rogues: GraphQL at Product Hunt with Radoslav Stankov React Round Up: React at Product Hunt with Radoslav Stankov React Native Radio: React Native at Product Hunt feat. Radoslav Stankov and Vlad Vladimirov Radoslav’s Website Radoslav’s GitHub Radoslav’s Twitter https://devchat.tv/my-ruby-story/ https://www.facebook.com/DevChattv Picks Radoslav Stankov: The Ruby Toolbox formulaic Charles Max Wood: Skyward by Brandon Sanderson Writing Excuses Podcast  

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Special Guest:  Radoslav Stankov Episode Summary In this episode of My Ruby Story, Charles hosts Radoslav Stankov, the head of the engineering team at Product Hunt. Listen to Radoslav  on the podcast Ruby Rogues on this episode. Radoslav was interested in technology from a young age, he was recruited by a company at a youth community center for IT support. He was interested in web development so he started to coding in PHP.  He then started learning Ruby on Rails and started working for a company which sells trucks where he built the Enterprise Resource Planning (ERP) system  in Rails. The user interface for this ERP system was very successful and Radoslav stresses any software that can’t be used by the client can not be considered very good. Radoslav then started working for a startup which failed but there he met the team  which eventually led him to the job at Product Hunt. Radoslav and Charles share stories where they were hired by people they had met at other projects. They point out that people like to keep hiring those they trust and admire. Radoslav then goes on to share projects he has been proud of throughout his career. Radoslav is currently at Product Hunt and one of the working to make the app work better and faster. Links Ruby Rogues: GraphQL at Product Hunt with Radoslav Stankov React Round Up: React at Product Hunt with Radoslav Stankov React Native Radio: React Native at Product Hunt feat. Radoslav Stankov and Vlad Vladimirov Radoslav’s Website Radoslav’s GitHub Radoslav’s Twitter https://devchat.tv/my-ruby-story/ https://www.facebook.com/DevChattv Picks Radoslav Stankov: The Ruby Toolbox formulaic Charles Max Wood: Skyward by Brandon Sanderson Writing Excuses Podcast  

Sponsors Sentry use the code "devchat" for $100 credit TripleByte Panel Dave Kimura Nate Hopkins Charles Max Wood Special Guest - Radoslav Stankov   In this episode, the panelists of Ruby Rogues speak with Radoslav Stankov about GraphQL and its implementation in depth. Radoslav is based out of Sofia, Bulgaria and is the head of the engineering team at Product Hunt. He is a full stack developer since 2002, working on JavaScript, Ruby on Rails, Elixir and GraphQL.   Show Notes: 0:00 – Charles introduces the panel and the special guest. 0:30 – Advertisement: Sentry - Use the code “devchat” to get two months free on Sentry’s small plan. 1:40   - Radoslav introduces himself and gives a short description about what he is working on. 2:20 - Charles asks him about the stack at Product Hunt and details about the company. Radoslav gives a brief historical background while explaining that they moved to GraphQL two years ago. He states that his team consists of about six full stack developers. He explains that GraphQL is their main API currently for communicating with the Rail backend and a React client in the front. He also mentions that they released a new iOS app recently. 5:12 - Charles asks if increasing number of websites are moving toward the mentioned model where Rails provides the backend API and rendering happens in the front. Radoslav agrees while saying Rails is faster but if the complexity increases, it starts becoming increasingly complex. He gives an example of views to explain his point. He interprets GraphQL as an update on REST API which is much cleaner and easier to work with.  7:08 - Dave agrees that GraphQL is interesting and compares it to SOAP interface while explaining the comparison in detail. He asks Radoslav the reason why GraphQL is used internally without a client facing API. Radoslav answers that he prefers GraphQL to be private and explains with an example using it internally is very flexible, hassle free and can be used for anything that the user wants to do in a simple manner.  11:30 - Dave asks does GraphQL handles versioning as the application matures. Radoslav elaborates on it by saying that versioning is similar to REST API and with GraphQL, the scheme is statically typed and it’s easy to identify information such as which field was requested frequently by the customer and which needs to be deprecated.  14:08 - Dave asks if GraphQL has a documentation API like Swagger. Radoslav talks about a tool called “graphical” which is an IDE for graphical queries that generates automatic documentation. 15:31 - Nate asks about the origin of the metric tracking in GraphQL. Radoslav says that it comes from certain tools, that all the libraries such JavaScript, Ruby, Elixir have instrumentation hooks and information is obtained by plugging into them.  16:22 - Nate then says that this is basically like hoisting SQL database to frontend layer and then goes on to ask how the database queries are optimized. Radoslav explains in detail that the optimization is done similar as normal Rails and explains the process of batching. He mentions that he has written two blog posts on the same topic - optimization for N+1 queries. 19:27 - Dave shares that GraphQL has a good feature where you can restrict the query based on what the user wants. Radoslav talks about the method of caching for optimization.  21:30 - Charles asks if building resolvers has gotten better than before. Radoslav answers in affirmative and talks about the usage of classes, methods and mutations that makes the procedure simple. He explains that one of his libraries has a GraphQL plugin where you have to define search queries and it exports those to GraphQL types and arguments that can be plugged into GraphQL schema. 24:20 - Nate asks about the implementation of GraphQL components. Radoslav says that it is separated into a single namespace, exposed to a controller, the GraphQL types are matched to REST serializers. The frontend has React component and the backend contains the controller, utility classes and the GraphQL logic. He then goes on to explain the structure in depth.   26:47 - Nate asks if this strategy has been blogged about to which Radoslav answers that he hasn’t but has given talks on it.   27:15 - Nate asks about the downsides of GraphQL. Radoslav shares his worries about making the API public as it should be made more bullet-proof as it could have performance issues on such a large scale and would involve much better monitoring. He says that authorization for resources would also be a problem. 29:17 - Nate mentions that in the end it is a tradeoff as it is with any software and asks at what point does it start to make sense to use GraphQL. Radoslav answers that it depends on the roadmap, the kind of the product is and gives some examples to elaborate further.   31:35 - Nate says that early planning could be needed for growing the team in a particular way. He also talks about the disadvantage of growing trends that break down solutions into smaller parts that it takes away the ability of small teams to build entire solutions. Radoslav says that while it is true, the developers in his team are full stack and capable of working with all kinds of tasks be it frontend or backend that come their way. 35:45 - Nate asks about the team’s hiring practices. Radoslav describes that they started with senior developers and later on hired interns and juniors as well. He states that interns and juniors ask better questions and work well with component driven design.   39:18 - Nate asks why Ruby is considered to be a good choice for GraphQL. Radoslav answers that the Ruby implementation of GraphQL is one of the best, used by big companies like Shopify, GitHub, Airbnb. It solves code scaling issues and integrates well with Rails.  42:45 - Dave says that it will be interesting to see what Facebook will come up next in the frontend framework. Radoslav agrees and says Facebook infrastructure team makes good tradeoffs and gives the example that each time there is React update, the team updates the whole codebase to the newest React version. 45:56 – Dave and Radoslav talk about the React team’s versioning being unusual. 46:23 – Advertisement - TripleByte - 1000$ signing bonus for listeners 47:20 – Picks! 54:50 – Radoslav mentions that he is available as rstankov on Twitter, GitHub and his website is www.rstankov.com. 55:25 – END – Advertisement – CacheFly!   Picks Dave Swing Cars - for kids Dewalt USB charger Nate Multipliers - How the Best Leaders Make Everyone Smarter Jimmy Buffet songs - A Pirate looks at Forty, Come Monday Charles For listeners - Tag devchat episodes on tv or github.com/cmaxw/devchat-eleventy. For every 5 episodes tagged (particularly Ruby, JavaScript, testing, new programmers, etc), one hour of coaching will be given. You can open an issue on GitHub for each episode you’re tagging so it does not get mixed up with other listeners. “How to Get a Job” - Book in progress. Radoslav Marc-Andre GraphQL Schema Design at GraphQL summit The Phoenix Project 

Sponsors Sentry use the code "devchat" for $100 credit TripleByte Panel Dave Kimura Nate Hopkins Charles Max Wood Special Guest - Radoslav Stankov   In this episode, the panelists of Ruby Rogues speak with Radoslav Stankov about GraphQL and its implementation in depth. Radoslav is based out of Sofia, Bulgaria and is the head of the engineering team at Product Hunt. He is a full stack developer since 2002, working on JavaScript, Ruby on Rails, Elixir and GraphQL.   Show Notes: 0:00 – Charles introduces the panel and the special guest. 0:30 – Advertisement: Sentry - Use the code “devchat” to get two months free on Sentry’s small plan. 1:40   - Radoslav introduces himself and gives a short description about what he is working on. 2:20 - Charles asks him about the stack at Product Hunt and details about the company. Radoslav gives a brief historical background while explaining that they moved to GraphQL two years ago. He states that his team consists of about six full stack developers. He explains that GraphQL is their main API currently for communicating with the Rail backend and a React client in the front. He also mentions that they released a new iOS app recently. 5:12 - Charles asks if increasing number of websites are moving toward the mentioned model where Rails provides the backend API and rendering happens in the front. Radoslav agrees while saying Rails is faster but if the complexity increases, it starts becoming increasingly complex. He gives an example of views to explain his point. He interprets GraphQL as an update on REST API which is much cleaner and easier to work with.  7:08 - Dave agrees that GraphQL is interesting and compares it to SOAP interface while explaining the comparison in detail. He asks Radoslav the reason why GraphQL is used internally without a client facing API. Radoslav answers that he prefers GraphQL to be private and explains with an example using it internally is very flexible, hassle free and can be used for anything that the user wants to do in a simple manner.  11:30 - Dave asks does GraphQL handles versioning as the application matures. Radoslav elaborates on it by saying that versioning is similar to REST API and with GraphQL, the scheme is statically typed and it’s easy to identify information such as which field was requested frequently by the customer and which needs to be deprecated.  14:08 - Dave asks if GraphQL has a documentation API like Swagger. Radoslav talks about a tool called “graphical” which is an IDE for graphical queries that generates automatic documentation. 15:31 - Nate asks about the origin of the metric tracking in GraphQL. Radoslav says that it comes from certain tools, that all the libraries such JavaScript, Ruby, Elixir have instrumentation hooks and information is obtained by plugging into them.  16:22 - Nate then says that this is basically like hoisting SQL database to frontend layer and then goes on to ask how the database queries are optimized. Radoslav explains in detail that the optimization is done similar as normal Rails and explains the process of batching. He mentions that he has written two blog posts on the same topic - optimization for N+1 queries. 19:27 - Dave shares that GraphQL has a good feature where you can restrict the query based on what the user wants. Radoslav talks about the method of caching for optimization.  21:30 - Charles asks if building resolvers has gotten better than before. Radoslav answers in affirmative and talks about the usage of classes, methods and mutations that makes the procedure simple. He explains that one of his libraries has a GraphQL plugin where you have to define search queries and it exports those to GraphQL types and arguments that can be plugged into GraphQL schema. 24:20 - Nate asks about the implementation of GraphQL components. Radoslav says that it is separated into a single namespace, exposed to a controller, the GraphQL types are matched to REST serializers. The frontend has React component and the backend contains the controller, utility classes and the GraphQL logic. He then goes on to explain the structure in depth.   26:47 - Nate asks if this strategy has been blogged about to which Radoslav answers that he hasn’t but has given talks on it.   27:15 - Nate asks about the downsides of GraphQL. Radoslav shares his worries about making the API public as it should be made more bullet-proof as it could have performance issues on such a large scale and would involve much better monitoring. He says that authorization for resources would also be a problem. 29:17 - Nate mentions that in the end it is a tradeoff as it is with any software and asks at what point does it start to make sense to use GraphQL. Radoslav answers that it depends on the roadmap, the kind of the product is and gives some examples to elaborate further.   31:35 - Nate says that early planning could be needed for growing the team in a particular way. He also talks about the disadvantage of growing trends that break down solutions into smaller parts that it takes away the ability of small teams to build entire solutions. Radoslav says that while it is true, the developers in his team are full stack and capable of working with all kinds of tasks be it frontend or backend that come their way. 35:45 - Nate asks about the team’s hiring practices. Radoslav describes that they started with senior developers and later on hired interns and juniors as well. He states that interns and juniors ask better questions and work well with component driven design.   39:18 - Nate asks why Ruby is considered to be a good choice for GraphQL. Radoslav answers that the Ruby implementation of GraphQL is one of the best, used by big companies like Shopify, GitHub, Airbnb. It solves code scaling issues and integrates well with Rails.  42:45 - Dave says that it will be interesting to see what Facebook will come up next in the frontend framework. Radoslav agrees and says Facebook infrastructure team makes good tradeoffs and gives the example that each time there is React update, the team updates the whole codebase to the newest React version. 45:56 – Dave and Radoslav talk about the React team’s versioning being unusual. 46:23 – Advertisement - TripleByte - 1000$ signing bonus for listeners 47:20 – Picks! 54:50 – Radoslav mentions that he is available as rstankov on Twitter, GitHub and his website is www.rstankov.com. 55:25 – END – Advertisement – CacheFly!   Picks Dave Swing Cars - for kids Dewalt USB charger Nate Multipliers - How the Best Leaders Make Everyone Smarter Jimmy Buffet songs - A Pirate looks at Forty, Come Monday Charles For listeners - Tag devchat episodes on tv or github.com/cmaxw/devchat-eleventy. For every 5 episodes tagged (particularly Ruby, JavaScript, testing, new programmers, etc), one hour of coaching will be given. You can open an issue on GitHub for each episode you’re tagging so it does not get mixed up with other listeners. “How to Get a Job” - Book in progress. Radoslav Marc-Andre GraphQL Schema Design at GraphQL summit The Phoenix Project 

Sponsors Sentry use the code "devchat" for $100 credit TripleByte Panel Dave Kimura Nate Hopkins Charles Max Wood Special Guest - Radoslav Stankov   In this episode, the panelists of Ruby Rogues speak with Radoslav Stankov about GraphQL and its implementation in depth. Radoslav is based out of Sofia, Bulgaria and is the head of the engineering team at Product Hunt. He is a full stack developer since 2002, working on JavaScript, Ruby on Rails, Elixir and GraphQL.   Show Notes: 0:00 – Charles introduces the panel and the special guest. 0:30 – Advertisement: Sentry - Use the code “devchat” to get two months free on Sentry’s small plan. 1:40   - Radoslav introduces himself and gives a short description about what he is working on. 2:20 - Charles asks him about the stack at Product Hunt and details about the company. Radoslav gives a brief historical background while explaining that they moved to GraphQL two years ago. He states that his team consists of about six full stack developers. He explains that GraphQL is their main API currently for communicating with the Rail backend and a React client in the front. He also mentions that they released a new iOS app recently. 5:12 - Charles asks if increasing number of websites are moving toward the mentioned model where Rails provides the backend API and rendering happens in the front. Radoslav agrees while saying Rails is faster but if the complexity increases, it starts becoming increasingly complex. He gives an example of views to explain his point. He interprets GraphQL as an update on REST API which is much cleaner and easier to work with.  7:08 - Dave agrees that GraphQL is interesting and compares it to SOAP interface while explaining the comparison in detail. He asks Radoslav the reason why GraphQL is used internally without a client facing API. Radoslav answers that he prefers GraphQL to be private and explains with an example using it internally is very flexible, hassle free and can be used for anything that the user wants to do in a simple manner.  11:30 - Dave asks does GraphQL handles versioning as the application matures. Radoslav elaborates on it by saying that versioning is similar to REST API and with GraphQL, the scheme is statically typed and it’s easy to identify information such as which field was requested frequently by the customer and which needs to be deprecated.  14:08 - Dave asks if GraphQL has a documentation API like Swagger. Radoslav talks about a tool called “graphical” which is an IDE for graphical queries that generates automatic documentation. 15:31 - Nate asks about the origin of the metric tracking in GraphQL. Radoslav says that it comes from certain tools, that all the libraries such JavaScript, Ruby, Elixir have instrumentation hooks and information is obtained by plugging into them.  16:22 - Nate then says that this is basically like hoisting SQL database to frontend layer and then goes on to ask how the database queries are optimized. Radoslav explains in detail that the optimization is done similar as normal Rails and explains the process of batching. He mentions that he has written two blog posts on the same topic - optimization for N+1 queries. 19:27 - Dave shares that GraphQL has a good feature where you can restrict the query based on what the user wants. Radoslav talks about the method of caching for optimization.  21:30 - Charles asks if building resolvers has gotten better than before. Radoslav answers in affirmative and talks about the usage of classes, methods and mutations that makes the procedure simple. He explains that one of his libraries has a GraphQL plugin where you have to define search queries and it exports those to GraphQL types and arguments that can be plugged into GraphQL schema. 24:20 - Nate asks about the implementation of GraphQL components. Radoslav says that it is separated into a single namespace, exposed to a controller, the GraphQL types are matched to REST serializers. The frontend has React component and the backend contains the controller, utility classes and the GraphQL logic. He then goes on to explain the structure in depth.   26:47 - Nate asks if this strategy has been blogged about to which Radoslav answers that he hasn’t but has given talks on it.   27:15 - Nate asks about the downsides of GraphQL. Radoslav shares his worries about making the API public as it should be made more bullet-proof as it could have performance issues on such a large scale and would involve much better monitoring. He says that authorization for resources would also be a problem. 29:17 - Nate mentions that in the end it is a tradeoff as it is with any software and asks at what point does it start to make sense to use GraphQL. Radoslav answers that it depends on the roadmap, the kind of the product is and gives some examples to elaborate further.   31:35 - Nate says that early planning could be needed for growing the team in a particular way. He also talks about the disadvantage of growing trends that break down solutions into smaller parts that it takes away the ability of small teams to build entire solutions. Radoslav says that while it is true, the developers in his team are full stack and capable of working with all kinds of tasks be it frontend or backend that come their way. 35:45 - Nate asks about the team’s hiring practices. Radoslav describes that they started with senior developers and later on hired interns and juniors as well. He states that interns and juniors ask better questions and work well with component driven design.   39:18 - Nate asks why Ruby is considered to be a good choice for GraphQL. Radoslav answers that the Ruby implementation of GraphQL is one of the best, used by big companies like Shopify, GitHub, Airbnb. It solves code scaling issues and integrates well with Rails.  42:45 - Dave says that it will be interesting to see what Facebook will come up next in the frontend framework. Radoslav agrees and says Facebook infrastructure team makes good tradeoffs and gives the example that each time there is React update, the team updates the whole codebase to the newest React version. 45:56 – Dave and Radoslav talk about the React team’s versioning being unusual. 46:23 – Advertisement - TripleByte - 1000$ signing bonus for listeners 47:20 – Picks! 54:50 – Radoslav mentions that he is available as rstankov on Twitter, GitHub and his website is www.rstankov.com. 55:25 – END – Advertisement – CacheFly!   Picks Dave Swing Cars - for kids Dewalt USB charger Nate Multipliers - How the Best Leaders Make Everyone Smarter Jimmy Buffet songs - A Pirate looks at Forty, Come Monday Charles For listeners - Tag devchat episodes on tv or github.com/cmaxw/devchat-eleventy. For every 5 episodes tagged (particularly Ruby, JavaScript, testing, new programmers, etc), one hour of coaching will be given. You can open an issue on GitHub for each episode you’re tagging so it does not get mixed up with other listeners. “How to Get a Job” - Book in progress. Radoslav Marc-Andre GraphQL Schema Design at GraphQL summit The Phoenix Project 

Panel: Lucas Reis Nader Dabit Special Guest: Radoslav Stankov In this episode, the panelists talk with today’s guest, Radoslav Stankov, who is a senior developer at Product Hunt. The panel and the guest talk about React, jQuery, Backbone, and much more! Check it out! Show Topics: 0:00 – Kendo UI 0:31 – Nader: Hello! Our guest today is Radoslav. 4:02 – Nader: What is your role and what are your main responsibilities? 4:10 – Guest answers. 4:39 – Panel: Can you tell us the story of how you started to use React? 4:55 – Guest: We started 4 years ago. The guest answers the question and mentions jQuery and Backbone. 9:01 – Panel: That’s nice – so you are trying to use a simpler application but the React server still need to be separated right? 9:14 – Guest: Yes, we tried to keep it as simple as possible. 10:38 – Panel: How was the adoption of React and how painful was it? You mentioned that you were used Flux and others, so was it messy and complicated for you? Or was it easy for you? 11:15 – Guest: It had its moments. 16:03 – Nader: So what are some of the reasons why you would be messing around with service-side rendering? 16:20 – The guest lists the reasons why they use it. 18:07 – Nader: Interesting. It helps for mobile clients? What do you mean – is it for the people with slower connections? 18:22 – Guest: Yes. The mobile plan can see the page. It can actually see how it’s rendered. 19:53 – Panel: How do you detect that it’s a mobile request from the server? 20:00 – Guest. 31:04 – Panel: We wanted to make it much faster and started using Node and streaming the library. Instead of creating a big string and then sending back to the user we were using the function...It’s super cool. We started using 30% less resources once we’ve deployed. (Wow!) Yeah I know! When you stream then the Node can be smarter and streaming at the same time. 32:03 – Guest. 33:21 – Panel: Interesting thing about the streaming is that we were fetching data after it started. After it was streaming HTML it was already... 38:21 – Nader: We talked about the WEB but you are all using REACT with mobile, too. Can you talk about how your company is using REACT? I know you’ve made things natively, too. 38:40 – Guest: I bit of history first then I will answer the question. 41:29 – Nader: Do you think the changes will happen in the right time to help with your fruition or no? 41:45 – Guest answers. 43:33 – How does the team manage working with all of these technologies? Does everyone have his or her own role? 43:54 – Guest answers. 48:03 – Panel: What are the drawbacks to that? 48:10 – Guest answers. 50:52 – Nader: Anything else? 51:00 – Guest: I think we covered a lot of great topics! Ads: FreshBooks! Get A Coder Job! Cache Fly! Links: Ruby on Rails Angular JavaScript Elm Phoenix GitHub Get A Coder Job React Round Up Guest’s LinkedIn Guest’s GitHubGist Introducing Hooks Idle Until Urgent Nader’s Tweet Sponsors: Get a Coder Job Cache Fly Fresh Books Kendo UI   Picks: Radoslav Getting to know React DOM’s event handling system inside and out React Fiber Architecture React Hooks React.NotAConf Lucas Idle Until Urgent Introducing Hooks Nader Writing Custom React Hooks for GraphQL React Native Hooks

Panel: Lucas Reis Nader Dabit Special Guest: Radoslav Stankov In this episode, the panelists talk with today’s guest, Radoslav Stankov, who is a senior developer at Product Hunt. The panel and the guest talk about React, jQuery, Backbone, and much more! Check it out! Show Topics: 0:00 – Kendo UI 0:31 – Nader: Hello! Our guest today is Radoslav. 4:02 – Nader: What is your role and what are your main responsibilities? 4:10 – Guest answers. 4:39 – Panel: Can you tell us the story of how you started to use React? 4:55 – Guest: We started 4 years ago. The guest answers the question and mentions jQuery and Backbone. 9:01 – Panel: That’s nice – so you are trying to use a simpler application but the React server still need to be separated right? 9:14 – Guest: Yes, we tried to keep it as simple as possible. 10:38 – Panel: How was the adoption of React and how painful was it? You mentioned that you were used Flux and others, so was it messy and complicated for you? Or was it easy for you? 11:15 – Guest: It had its moments. 16:03 – Nader: So what are some of the reasons why you would be messing around with service-side rendering? 16:20 – The guest lists the reasons why they use it. 18:07 – Nader: Interesting. It helps for mobile clients? What do you mean – is it for the people with slower connections? 18:22 – Guest: Yes. The mobile plan can see the page. It can actually see how it’s rendered. 19:53 – Panel: How do you detect that it’s a mobile request from the server? 20:00 – Guest. 31:04 – Panel: We wanted to make it much faster and started using Node and streaming the library. Instead of creating a big string and then sending back to the user we were using the function...It’s super cool. We started using 30% less resources once we’ve deployed. (Wow!) Yeah I know! When you stream then the Node can be smarter and streaming at the same time. 32:03 – Guest. 33:21 – Panel: Interesting thing about the streaming is that we were fetching data after it started. After it was streaming HTML it was already... 38:21 – Nader: We talked about the WEB but you are all using REACT with mobile, too. Can you talk about how your company is using REACT? I know you’ve made things natively, too. 38:40 – Guest: I bit of history first then I will answer the question. 41:29 – Nader: Do you think the changes will happen in the right time to help with your fruition or no? 41:45 – Guest answers. 43:33 – How does the team manage working with all of these technologies? Does everyone have his or her own role? 43:54 – Guest answers. 48:03 – Panel: What are the drawbacks to that? 48:10 – Guest answers. 50:52 – Nader: Anything else? 51:00 – Guest: I think we covered a lot of great topics! Ads: FreshBooks! Get A Coder Job! Cache Fly! Links: Ruby on Rails Angular JavaScript Elm Phoenix GitHub Get A Coder Job React Round Up Guest’s LinkedIn Guest’s GitHubGist Introducing Hooks Idle Until Urgent Nader’s Tweet Sponsors: Get a Coder Job Cache Fly Fresh Books Kendo UI   Picks: Radoslav Getting to know React DOM’s event handling system inside and out React Fiber Architecture React Hooks React.NotAConf Lucas Idle Until Urgent Introducing Hooks Nader Writing Custom React Hooks for GraphQL React Native Hooks

Radoslav Stankov and Vlad Vladimirov join the show to talk about their transition from Native to React Native at Product Hunt

Radoslav Stankov and Vlad Vladimirov join the show to talk about their transition from Native to React Native at Product Hunt

Radoslav Stankov has been doing software development since 2002, starting as PHP programer, but quickly moved around the tech stack. Rodoslav considers himself to be a full stack developer. Currently he's working at ProductHunt, where he does iOS development in Objective-C / Swift, backend in Node and Rails and frontend in React / Redux. He believes that frontend and backend are equally important and a lot of problems can be avoided by working in collaboration. Show notes at http://hellotechpros.com/radoslav-stankov-technology/ Key Takeaways ProductHunt started as small mail list, hottest thing in tech today. Place to discover your next favorite thing - podcast, text, books. Not a single person knows everything, ask for help if you don't know, there is no shame, but there is shame in not having respect for others. Estimating projects can be off by far if you don't understand the other tech stacks. Strive to be equal partners with clients, they can explain why something not needed or need to be added, have weekly goals. Everything that can be automated should be automated, just focus on what the code should be doing. graphQL from Facebook is alternative to REST services + JSON and every client gets the same response graphQL you pass in a template and get back the data you want mobile app and chrome extensions use public API; website uses private API where things change contantly defined like a database schema People should not label themselves as a frontend or backend developer, they should be someone who solves problems on a team. Resources Mentioned ProductHunt graphQL Sponsors Levant Technologies - Voted Oklahoma's #1 website design and development company.