rado_stankov

3 ms·

1. 1.▲
   by rado_stankov 9mo ago

   https://rstankov.com/
2. 2.▲
   by rado_stankov 2y ago

   The top book imho is The Pragmatic Programer. Here some other recomendations - Designing Data-Intensive Applications - Tidy First?: A Personal Exercise in Empirical Software Design - A Philosophy of Software Design - Refactoring UI - The So
3. 3.▲
   My favourite Ruby on Rails engines(blog.rstankov.com)

   6 points by rado_stankov 4y ago|1 comments
4. 4.▲
   by rado_stankov 4y ago

   Ruby on Rails Engines is one of the most powerful and underestimated features. It distinguishes Rails from other web frameworks.
5. 5.▲
   by rado_stankov 4y ago

   Yes. Hiding errors leads to a lot of issues down the way. This is part of the process. If an issue requires deeper work, it moves a proper task in a sprint. We try to fix the easiest issues first so the deeper problems bubble up. How the pe
6. 6.▲
   by rado_stankov 4y ago

   Every sprint we have 1 person in rotation for bug duty. It works quite well. Overtime role takes some refactoring and tech depth as part of bug duty. I have a blog post on the subject a while back: https://blog.rstankov.com/
7. 7.▲
   Product Hunt Architecture(blog.rstankov.com)

   3 points by rado_stankov 5y ago|0 comments
8. 8.▲
   Techniques for Structuring Next.js Applications(blog.rstankov.com)

   3 points by rado_stankov 5y ago|0 comments