3 ms·
I consider myself "full-stack" because my average work week nowadays seems to include a constant mix of four kinds of development: back-end performance-intensiv
by pavlov 8y ago
I consider myself "full-stack" because my average work week nowadays seems to include a constant mix of four kinds of development: back-end performance-intensive rendering services (C++ inner loop kind of stuff), back-end "devops light" service design work and glue scripts, back-end automation work (random shit like PHP/Hack scripts to wrangle data), and plain old front-end (SPA React nowadays).
The post author seems oddly upset that someone corrected his TypeScript design choices. If you want to do full stack, you can't take feedback personally. I regularly get code reviews where I've done something that's standard practice in one language but a no-no in another, and I just didn't remember. (PHP/Hack is like ground zero for these gotchas.) That's absolutely ok — that's why we do code reviews after all!
My real expertise is the C/C++ level stuff, but I write the other code because I'm basically the domain expert. The value of that code is that it's doing something useful and nobody else had to be assigned to write it; not that it's "ideal PHP" or "beautiful React" right off the bat. That can always be tweaked and refactored in code review.
Summary: in "full stack", you can't afford ego about your code, but you need conviction about the value of your contributions. That often means you need to spend time understanding stakeholders or user needs rather than e.g. reading TypeScript release notes.
- ptero 8y ago> I write the other code because I'm basically the domain expert I think this is a key point. In my experience there are two paths for engineers to senior level positions: (1) management, which is usually easier (more openings available, engineers may find it unattractive) but slowly moves one away from technology development, or (2) domain expertise which is technically harder to achieve (need to be recognized as expert) but often provides more freedom and allows staying science / technology focused. Each path requires some (different) soft skills which are more important than maintaining either a super broad or a super focused "stack". My 2c.