3 ms·
These dicussions remind me of a quote I once read. My apologies for not remembering the source: "Anyone who calls themselves a 'Full Stack Developer' clearly d
by rubiquity 13y ago
These dicussions remind me of a quote I once read. My apologies for not remembering the source:
"Anyone who calls themselves a 'Full Stack Developer' clearly doesn't know how deep the stack really goes."
- a-priori 13y agoHow deep do you mean? I once did a project that involved: 1) a kernel module to do packet-level manipulation (intercept, hold, modify, inject packets) of TCP streams in real time 2) a user-space daemon to control the kernel module (Python) 3) a web service to control the daemon (Java) 4) a web front-end to administer it (PHP, HTML, CSS, etc.) I don't want to go into the details about what exactly this system did, but suffice it to say I worked in all parts of that stack. At another job I worked on DSP firmware code and in my spare time I've written simple OS kernels. There isn't much deeper unless you're soldering wires (spent a summer doing that once...) and flashing FPGAs (never done that). These days I work on web applications doing everything from diagnosing production issues ('why is the database doing that..?') and coding on a Java back-end, to working on iOS and HTML5 applications. You'd have a hard time saying I'm not a 'full stack developer' by any definition. But to be honest I don't like the term and don't call myself that. I just don't believe in pigeonholing myself into solving particular kinds of problems.