HackerTrans
トップ新着トレンドコメント過去質問紹介求人

padseeker

no profile record

投稿

Making your code base better will make your code coverage worse

stackoverflow.blog
7 ポイント·投稿者 padseeker·10 か月前·1 コメント

コメント

padseeker
·9 か月前·議論
this ^^^

I've used turbo/stimulus/hotwire. It's best suited for STATELESS interactions withe the browser/web page. The problem is not all desired user experiences and use cases are stateless. And the ecosystem for hotwire is a minuscule fraction of all the other popular js frameworks.

If you're searching for inventory available its perfect. However if you want to update one thing based on the most recently touched input it becomes more complicated and in all honesty more trouble that it's worth.

Honestly if you're a solo Rails dev, use whatever you want. However the React ecosystem, and really all of the other popular JS ecosystems (vue, ), are very strong and you have so many available options. Stimulus is 2 steps back from jQuery, it inverted the Event delegation pattern. No one else outside of the rails community is using it.
padseeker
·7 年前·議論
THIS - my experience with interviewing with startups has been very poor. Generally startups are staffed by younger people.

Sometimes those people conducting the interviews are on their first or second job, and generally those younger coders have a tendency to emphasize things like obscure syntax for whatever programming language and the latest programming paradigms. It is overly language centric rather than dealing with how to solve problems. That is a terrible metric for the issue at hand "will this person be an effective at their job".