The distaste is for complexity. I think that principle I've heard before called "1, 2, 3, abstract"; as in, wait until you see it at least three times before considering extraction. If you're struggling with managing your infrastructure, then maybe you need someone with a DevOps or Systems Administrator mindset. Many bootcamp graduates take a month or two before the job search to develop their expertise. You can't learn that sort of judgement when to use vs when not to use from a book. There are simple techniques to keep view logic and application logic decoupled, for example by introducing a separate data structures prepared and optimized for view components to consume.
The Eight Levels of Programmers
If it doesn't make an impression, 9 out of 10 times we'll walk away. Are you a developer and you sometimes have to interview candidates? People you know and trust are good, but they can think they are giving you a good deal because it is more effort for them then someone who specializes in your project. When we compose systems, we are looking for fewest dependencies and stable dependencies. We are not speaking here of personal grooming, though in one case a programmer actually smelled so bad that nobody could sit next to him long enough to look at his listings.
How to Avoid Hiring Bad Programmers
Of course there are different kinds of dependencies. Anchor on Feb 5, I think the right approach is not to avoid dependencies, but to manage them. If good dependency management is cheap , programmers will use it, and even if some dependencies are volatile, side-effects can be bounded by the dependency graph. Stressed candidates don't perform at their best. Such people, if they had presented themselves for jobs as programmers in great numbers, might have failed in great numbers, making us feel a need to measure intelligence of programmer applicants. Some of these are easier than others, you can also follow up and ask if it is custom coded or are they using libraries and plugins. Test parts of their other code
A programmer's job is to get things done, and getting things done sometimes requires moving around obstacles, jumping over them, or simply knocking them down. There's a few ways in which state vs coupling can play out. So even effort is hard to guage, since a programmer can easily claim effort, and will claim effort, for another project that helps this one go quicker. If you pitch the salary too high, then you'll naturally spend more than you should. An amateur programmer loves to code, and it shows: they might be a promising student or intern, or perhaps they're contributing to open source projects, or building interesting "just for fun" applications or websites in their spare time.