"Microsoft Fullstack"
or
"Google Fullstack"
or
"Amazon Fullstack" (formerly "Apache Fullstack", now forked and rereleased)
21–30 of 41 posts
"Microsoft Fullstack"
or
"Google Fullstack"
or
"Amazon Fullstack" (formerly "Apache Fullstack", now forked and rereleased)
I interpret "Full Stack" to mean mostly web front-end. It generally doesn't mean mobile or desktop. It does also include back-end development but the trend is to use more off-the-shelf solutions and services so that there's less of it than there used to be. The reduction in back-end coding is taken up with the expectation that the "most commonly used functionality" is now in scope.
+ what other comments say where they want multiple specialists but are hiring one position for flexibility or cost.
All of the above: I interpret "Full Stack" to mean mostly web front-end. It generally doesn't mean mobile or desktop. It does also include back-end development but the trend is to use more off-the-shelf solutions and services so that there's less of it than there used to be. The reduction in back-end coding is taken up with the expectation that the "most commonly used functionality" is now in scope. + what other comm…
Full stack means they don't want to pay for specialists. So you will now be expected to do three people's jobs: Dev Ops - Backend - Frontend You'll also be implicitly on-call at all times despite that fact never being verbalized.
This is not at all fullstack to me. Imho; a fullstack developer is a person who can develop all pieces of an application (or game, or whatever) and put it in production, maintain it, improve it. I.e. design the database or other persistence, implement the layers that manages the data, the business logic and the user interface. It can be very different from different applications, of course, since some may not have an…
> You will rarely hear a full stack developer say "I'm unable to continue, because I have to wait for the (dba|integration team|ops team)". They will solve their problems and often has enough experience to do it well.
There are many of us like this who will never take a fullstack role because the reality is, we'd rather work at places that solve that problem by...
- properly sizing the integration/ops/db team for example?
- setting timelines up so that developers aren't blocked as often?
- account for downtime with things like codebase maintenance?
It's not like in theory a company can't have their ducks in a row and benefit from a "fullstack dev"...
The problem is if they're explicitly looking for full stack it tends to be a negative signal.
I'm surprised there's no product called: "Microsoft Fullstack" or "Google Fullstack" or "Amazon Fullstack" (formerly "Apache Fullstack", now forked and rereleased)
Underrated comment of the day here.
I made a joke on Facebook a few years back about true 'full stack' development. It was a post talking about some code I was writing to do some math computation on a simple OS I had written, running on a CPU I designed using my own custom instruction set, implemented in logic on a physical PCB I also designed and assembled. Of course even this is really only 'partial stack', since I didn't do the VLSI design of the 74…
Earlier quoted context omitted.
In what context would one realistically be able to debug TCP/IPv4/IPv6? Also in terms of network sockets and kernel implementation you're talking about apples and oranges.
_slightly_ tongue-in-cheek, because i'm annoyed by people calling the top 3% "full" stack But, an example is discovering from the DSACK responses that your network performance sucks because the intel TCP offload firmware is retransmitting entire jumbograms when any packet gets lost. Also discovering that you can't get near full network bandwidth because some moron attaches a 3-byte SNAP header. And if you don't have…
In my career (over 30 years now), full-stack in the context of web development has always referred to an engineer who could setup the tech stack and application from scratch. They can manage the servers, administer the network (as it relates to permissions for the various web-related processes), implement developer environments, code the back-end, code the front-end, some basic design skills, experience with developi…
All of the above: I interpret "Full Stack" to mean mostly web front-end. It generally doesn't mean mobile or desktop. It does also include back-end development but the trend is to use more off-the-shelf solutions and services so that there's less of it than there used to be. The reduction in back-end coding is taken up with the expectation that the "most commonly used functionality" is now in scope. + what other comm…
So HalfStack?