@arnan Proper devs nitpick things I don't get?
I'm genuinely intrigued what you've got against "stacks"! It just seems kinda appropriate term, for anyone lucky enough to have anything close to a well-layered architecture.
Top-level
@arnan Proper devs nitpick things I don't get? I'm genuinely intrigued what you've got against "stacks"! It just seems kinda appropriate term, for anyone lucky enough to have anything close to a well-layered architecture. 4 comments
@arnan You appear to be arguing against a definition of "stack" which is clearly not the one being used in the original post. "Stack" is not being used as a synonym for "set of languages a person knows". I think it's probably a stretch to think that it's being used as a synonym for "set of languages a system is written in" rather than "the system". @arnan Maybe, but I don't think it's the usage in the post you're replying to, which is what I think's relevant here. "Will rewrite said [choice of technologies] 2x as fast, and half as buggy if you let them." just doesn't make much sense to me. Removing bugs from code, yes, technology choices, not so much. "First thing we need to do is switch technologies" is way more junior dev than senior. |
@sgf we don't need a 'well layered architecture' for summing up what programming languages someone knows. Especially not if full stack can mean literally any combination of it. It's a meaningless term.