Three metrics you pointed out:
1. Linter
2. Cyclomatic/halstead complexity
3. identifier naming convention testing
Are those really things that candidates can get a negative ding for? Those are things that can/should be handled automatically by libraries or your CI/CD (ex: Rubocop)
More importantly, how do you get more details/nuance over things like naming or cyclomatic complexity.
Tinkergarten is on a mission to elevate childhood. We’re growing a technology-enabled network of leaders that bring families together in a natural place in their community for classes where kids learn through play. [ early childhood education ]
We're looking for a software engineer with at least 2 years professional experience. Our stack: Ruby/Rails, ReactJS, Mysql, AWS
Tinkergarten is on a mission to elevate childhood. We’re growing a technology-enabled network of leaders that bring families together in a natural place in their community for classes where kids learn through play.
We're looking for a software engineer with at least 2 years professional experience.
Our stack: Ruby/Rails, ReactJS, Mysql, AWS
To me this is the primary challenge of outsourcing your client side tracking -- you risk a wholesale block of your analytics if the Segment file gets blacklisted.
I think their value over the long term is similar to tripadvisor/yelp - while anyone can come in a create a repository of home sharing they wouldn't have the reviews/reputation data as AirBnB has. Going into someone's home / letting someone in your home, just like hotel reviews or restaurant, reviews/ratings can matter in the decision making process.
Are those really things that candidates can get a negative ding for? Those are things that can/should be handled automatically by libraries or your CI/CD (ex: Rubocop)
More importantly, how do you get more details/nuance over things like naming or cyclomatic complexity.