![]() ![]() People who believe they multitask well turn out to be the very worst at it, and full-stack engineering is just a gold lamé wrapper around chronic context switching. Our minds do not multithreadįor all our many talents, human brains do not scale exponentially, and we’re terrible at parallel processing under heavy cognitive loads. But in most cases, full-stack can be a choice to settle for less optimal solutions while setting up engineers to fail.ĭoes full-stack engineering deliver one-third the value? One-fourth? Whatever the math, the conclusion is clear: You’ll get much more value from a high-performing and experienced team of specialized engineers. (I’ll say more about these below.) And full-stack expertise can reasonably be an end game for very senior engineers with many years of experience. There are some exceptions: specific tools in specific use cases where full-stack engineers can deliver perfectly functional code. The supposed upfront savings will cost you in malformed databases, a bucket of technical debt, and/or unnavigable user journeys. If you’re hiring developers, don’t ask exclusively for full-stack engineers. ![]() ![]() You’ll be expected to do two jobs for one salary, each in half the time. If you’re a developer just getting started in your career, be wary of any job posting looking for a full-stack engineer. Full-stack engineering is an attractive legend, but in many cases it’s a misguided compromise that can produce a lower-quality product in exchange for making one individual more stressed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |