Jim Carnicelli - Full-stack developer
What does that mean?
For starters, the "stack" here is essentially all the technologies required to deliver a complete application. For a basic web app that couple mean HTML, CSS, and JavaScript on the client side. And then ASP.NET and JSON-faced web services written in C# on the back end for feeding the client. And then T-SQL stored procedures (SPs) in a Sql Server database. And that's before we start talking about client-side JS and CSS libraries, .NET components, and other add-ons. Let alone all the satelite services and integration points to round out a larger enterprise system. And then there's the operating system and platform components undergirding the app. It's handy to think of this all as being like a stack of pancakes. Each typically communicates with pancakes above and below it. And the user communicates with the delicious pancake on top of it all.
Many business apps — especially at the enterprise level — are created by people with a variety of skill sets. You may have whole teams of specialists doing database design, middle tier construction, user experience (UX) design, JavaScript programmers and so forth on the pure engineering side.
A full-stack developer has the skills necessary to do all these development tasks.
A broader interpretation of "full-stack developer" could be synonymous with "software engineer" and imply that such a person can design, implement, and maintain entire projects. These people will be comfortable with roles of project manager, business analyst, technical designer, coder, tester, documenter, maintainer, database designer, database administrator, and so on.
That's me
I've served every basic role in the software development life-cycle. I describe myself as a software engineer, but also as a full-stack developer. I can take on all the essential roles and design and implement all the layers of a typical business application. I have worked on teams of all sizes for companies of all sizes. I have done entire enterprise systems by myself and with small teams assisting me. I have been project manager and chief architect for larger teams repeatedly.
I'm flexible. I like having control over how a project is engineered. I work well as a sole creator, as a team leader, or as a colleague in a larger team.