- People (co-workers AND management) may cynically use you for the tasks that are menial, messy and boring and doesn't lead anywhere. You become the tech equivalent of a janitor or secretary.
- People who see only one side of you think that that side is your only skill, not something you're able to in addition to your primary skillset.
In both cases, if you decide to assume the role of a generalist but want to avoid these risks, you have to spend some effort to position yourself.
These are the steps I would recommend:
1. When describing yourself, do emphasize the generalism. I tend to claim that I can do almost anything as long as it is technical, but I do some things quite slowly. In particular you need to communicate this with your manager.
2. Make sure you demonstrate the skills in the sides you have that you want to spend more time on. This means to volunteer for tasks of this type, and make sure to overperform on these tasks and market the result to decision-makers. This is perhaps the most crucial part, as it includes demonstrating an ability to show initiative and work independently.
3. Let people know that your time is valuable and costly. With managers you need to demonstrate that you can produce more value for them if they don't let you get stuck into something trivial.
4. With lazy/abusive co-workers, you may have to simply let them know that you're not the assistant they can hand over the boring part to. This may be more difficult than with the managers, especially if you're not good at marking your limits in a firm but polite manner.
However as long as management want you to work where you provide more value, you can simply tell your co-workers something like "I'd love to help you with <insert menial task they prefent not to be able to do>, AGAIN, but I'm afraid I don't have much free time until Thursday from 7am-8am two weeks from now....". Or you can simply say "I'd love to help you with <same as above>, but I've been ordered to focuson <insert more interesting task>, maybe you can explain your need to my manager and have him approve this". One approach is to make it inconvenient for them, the other is to force them to admit some deficiency to management before you help them.
I see so many resumes with massive lists of technology exposure. I assume the intention is to demonstrate the breadth of experience. But if you don’t want to work in that language or framework you used 10 years ago, take it off. Only list the stuff that is relevant and that you’re willing to work with.
The technical summary on my resume is just that, a summary, not a comprehensive list. It’s 1/3 of the tech I’ve actually used throughout my career because I’m not interested in a job doing Flash or Visual Basic and I don’t want to receive anymore recruiting inquires about Magento development because I used it briefly a decade ago.
But... I don't know Scala anymore, I don't LIKE scala, and I don't WANT to do scala.
So it's a bit of a trade-off; on the one end, you want your CV and linkedin profile to reflect how amazing you are, how many things you know, etc. But on the other, you want it to be an invitation for people to approach and hire you for something YOU want to be doing.
I've updated my linkedin to reflect what I'm fairly good at - web front-end - because that's job guarantee, and what I want to be doing - Go - for whoever wants to take a punt on it. And I'll keep tweaking it towards what I WANT to do. I'm sure I'll keep mentioning what I've worked with in the descriptors of different jobs and projects, but I will de-emphasize the list of technologies in the summary section.
When you are working in a company - if you don't want to have new responsibilities you don't touch it.
You touch WiFi router - well now it is your responsibility if WiFi stops working. You touched sendmail - well as you wrote quotes "expert".
But to be specialist on something it still requires quite in depth knowledge than "you were last one to touch it".
I consider myself full stack, but in my last role I presented myself as a frontend engineer, with some backend experience. Eventually this role just kinda expanded into both frontend and backend.
Now that I do contract work, I present myself as whatever they need, with my current contract, I was hired to do frontend, but just started looking at the backend when running into some problems or questions about the data. There's always a point where they ask you "oh, you can work on the backend too?".
Managers are excited about FS engineers simply because if they scoop up good ones, those who really know what they're doing -- masters of several areas of their stack -- they can rotate them effectively at a fraction of a cost, if not for free.
I fully disagree with that. Great software isn't just about what stack you have mastered, great software is build by people who can do whatever it takes to build great software, and that's not necessarily just about your stack.
And besides, where does your notion of "full stack" begin? Is it backend application code? Operating system libraries? Kernel code? Hardware drivers? I'd argue "full stack developer" is a misnomer anyway, since no developer can (or would want to) write both kernel drivers and html/css frontends.
You do realize this comment is going to pull the exceptions out of the woodwork?
I wrote all of the software for the first version of the Teledyne Lumenera Ethernet cameras. Everything from assembly codes in the bootloader to CSS in the on-camera web pages. Heck, I even had to review and debug the PCB design before I could start.
I don't think this is a particularly uncommon experience. Embedded development usually has very small teams, and very often the hardware has HTTP API's.
P.S. I'm available for work. Information in profile.
Yeah, it's probably my personal bias showing. I'm fine with most parts of the stack (like you, down to PCB design), but UI/GUI/WUI work is an area that I try very hard to avoid.
The main thing "wrong" with a specialist is that not every org needs a full time specialist, so specialists are more likely to need to work as consultants.
When I interview for jobs they always ask very specialized questions. Everyone wants a generalist but refuse to interview them or pay them like one.
You’ve probably heard of the 10,000 hour rule, it’s a hard and fast rule to say that it takes roughly 10,000 hours of doing something to fully master it.
Maybe not true in all cases; but consider the suite of tools you have to be practicing every day to do even a single role: VCS/DVCS, shell, OS fundamentals, build-systems, networking, DNS… now we have distributed computing concepts such as kubernetes and various DSLs, then there’s your programming language(s), their standard libraries, their extended contrib libraries.
Completely non-exhaustive list and we’re already closing in on 5 years working full time for each of those.
The sheer hubris of assuming you can throw together a few frameworks and understand 1 or 2 paradigms and then claim you know “the whole stack” is immature and exhausting; similar to the sysadmins of yore who could read QuickStarts and claim to know how to maintain software fully.
Delivering business value is definitely what we’re trying to do, but when it comes down to it: engineering is understanding; and nobody can claim to understand everything, not with a straight face.
Full Stack is either: the most senior you can be or the most surface level you can be.
If the former: we can’t afford you and I’m not sure how you managed to keep all your skills up to date.
If the latter then specialists will need to clean up after you anyway.
Second, splitting a general role ("backend engineering") in arbitrary atomic skills doesn't make sense because there's no end to it. Backend engineering -> OS fundamentals -> Driver programming -> Hardware design -> Boolean logic -> Set theory -> and so on...
Third, all engineering roles have cross-cutting concerns. You do need some network knowledge to be a "backend guy"... but also to be a sysadmin, devops, etc.. It's not like all these roles exist in a vacuum and you're starting from 0 if you switch between them.
Finally, most people that think of themselves as experts in some role, language or framework end up in the "1 year of experience repeated 10 times" trap. True experts are also somewhat generalists too, because you can't built a tall knowledge without growing the base too (pun intended).
[1] https://www.bbc.com/future/article/20121114-gladwells-10000-...
Not all subjects are equal, granted.
having overlap in knowledge between roles is also somewhat granted; being a complete master in backend gives a person a lot of knowledge towards being a sysadmin (maybe even 60-70% of the way to being a master in that direction!);
But, you've failed to convince me that any single human on earth can do "everything"; even if a person could literally master all technologies in use (not counting your strawman of driver programming) then there would still be a discipline mismatch.
Nevertheless, I have a solid understanding on all the things you mentioned and if you need help give me a holler because my rates are fair and I'm open to opportunities
Can they? My experience of people is that most of them can't master anything.
Specialists, I have less experience with working with them though so take these generalizations with a big and hopefully non-insulting grain of salt. On the one hand they will be experts in their field, know whatever they work on inside-out, and can squeeze every last grain of performance out of it - good DBA's are worth their weight in gold, they can solve a company's performance problems and save them millions depending on the scale.
On the other you have a group of people that sorta know one language, like Java, and will just coast along on it for their careers; their CVs will look impressive, their skills will be indistinguishable from someone who has one year of experience. I've literally seen code that was a copy / paste of the first google search result of "java sql query", buried ten indentation levels deep, in a critical core codebase.
It's hard for a full stack engineer to see or admit to this because of bias, it's much easier for someone outside of web development to see it, or a more well rounded engineer to realize it.
Full stack isn't even the correct term for these engineers. They usually aren't truly full stack. They just "front end" and "back end", of the web development stack. AN actual "Full" stack encompasses far more. OS development, embedded development, compiler development, database development, graphics programming, are all really hard things that are missing from someone who typically refers to themselves as "full stack".
To give some context here, yes, when people refer to full stack developers, they're usually referring to developers who are focused on web development, but that would also include API development, or even mobile development.
I don't think anyone thinks of full stack developers, as developers who know embedded development or compiler development, so I don't know anyone who looks down on them for not knowing these things.
> It's hard for a full stack engineer to see or admit to this because of bias, it's much easier for someone outside of web development to see it, or a more well rounded engineer to realize it.
Now obviously, the way that you put it, it's extremely difficult to say why you're wrong, because you've started by adding a bias to people who would defend it. So maybe, when you want to have a discussion about it, don't start by stating something that makes it extremely difficult to argue against it without being seen as having a bias.
Yes, I'm referring to technical people who are specialists outside of "web development".
>Now obviously, the way that you put it, it's extremely difficult to say why you're wrong, because you've started by adding a bias to people who would defend it. So maybe, when you want to have a discussion about it, don't start by stating something that makes it extremely difficult to argue against it without being seen as having a bias.
Why would i want to be told I'm wrong? People offer arguments in the belief that they are bullet proof so it's natural to say things that are harder to argue against.
If you're a full stack engineer this excludes you from answering because you may be biased. I can empathize with how you feel. I guess there's two things you can consider here. Consider that you are biased and that the statement is correct. Consider that I, the person who posed the statement, is biased and wait for a programmer outside of web development who has experience working with "full stack web engineers" to respond with his own opinion.
You would be biased not to consider the possibility that I am right, so strive to be unbiased.
30 years ago, every app developer was "full stack", and the concept didn't even exist. As apps moved to the web during the dot-com era, the added complexity made some companies split their teams of entry level developers into front-end, back-end and database. Still, at that time, this "stack" was simple enough at the time that a good dev could learn the basics front-end, back-and and basic db work within a few years. So, a few years after dotcom, the "full stack dev" became popular, but really what they were delivering was the same as the app devs of the early 90s.
But even within software, engineering is so much more than just making web apps or RESTful microservices behind the web apps, and the field is still grown rapidly. There is data engineering, machine learning engineering, infrastructure ("devops") engineering, operating system engineering, driver engineering, network engineering, real time system engineering, algorithm/library engineering, and I probably left most of the sub-fields out.
So my main issue with "full stack engineers" is that I've met a few with (in reality) a fairly limited skillset who are quite overconfident about other aspects of software and the infra around software, who assume that the principles they follow when buildings web apps apply to all domains of software, and show a significant amount of hubris [edit] but still often failing spectacularly when trying to use their particular skillset in a somewhat different domain.
I realize that this impresson of mine is based on a few bad apples. But I think there is something in this "full stack" concept that can contribute to some devs underestimating the the kinds of work that are normally not considered part of this stack.
I realized that I should have done so for a contract work that I wasn't hired for. They told me that they were looking for someone specialized. I knew exactly that they needed a generalist, mostly because they were an early stage startup. They never hired for the “specialized” position they contacted me for, because that position shortly became obsolete.
Best bet is to play to the crowd from my experience. Management class: tell them how much you've done. Engineering class: tell them how well you've done something.
Also think about it from the company side:
Would you rather hire someone that solves your "exact" problem, or the one-man Army that -could- do everything? Which matters to you?
I don't mind rebranding your LinkedIn to make it look like you're the Kubernetes DevOps guy, as long as that means you're totally fine with working the DevOps for my Kubernetes clusters for the foreseeable future.
In an ideal world we could shove around generalist developers to whatever is necessary at the moment, but the reality is each developer is a human with hopes and dreams and ambitions and not every role will fit those.
This sort of over reasoning is part of what bugs me about this industry.
Many devs change jobs at the drop of a hat, turnover is already high. Yet here you are, worried about job retention, trying to second guess what a dev knows about their own happiness.
I know you mean well, both for the org, and the person, but what makes you think you know, better than the dev, what will stress them out or not?
You aren't them, so just ask, and as long as it is clear they have thought of it, and want to move ahead, you should 100% drop the matter.
Frankly (as if I could be more frank, heh), likely there will be something entirely unrelated which will bug the dev. And all your concerns will be for naught.
Except, of course, you are throwing people's resumes in the trash bin, thus reducing your talent pool, due to unfounded concerns.
I'm not second guessing anything, in fact my comment says the exact opposite. If a developer reworks their LinkedIn to highlight some expertise they're interested in working on, then I fully trust them on that and will gladly hire them.
I'm not sure where your whole angle of not trusting developers to know their own happiness comes from. But let me be clear, if you're a generalist with relevant experience I will definitely ask you to come over for an interview. I'm not throwing valuable resumes in the trash. But during the interview I will be frank about what the job entails, and I'll gauge your response to figure out if you'll be content. Whether I'm effective or not I don't know, but I'm going to have to at least try to get the right person at the right position.
edit: BTW I'm not just saying this as a CTO at a small startup, I'm also saying this as a generalist with highly valuable frontend skills and I pray to god I don't have to get into another frontend job (either directly, or by being lured into it after applying as a generalist).
I think paragraph 1 and 3, sandwiched around 2, created an effect of negation.
So thanks for the clarification, and thanks for returning my goat.
I tend to contract to the guy who can solve my exact problem. Because if the problem can be solved I don't want to pay for headcount permanently. I tend to hire long-term the guy who can solve multiple problems, but less speedily.
Which, of course, is different if you mean "hire someone who solves a class of recurring problems I have with a specialized skillset" from "solve the exact problem"
I think the question is more who a generalist markets to. Some people have multiple resume's depending on what they apply for, they come in through one angle and then build some trust and take over more. Or it's a startup that needs help, but doesn't really know what they need help with.
The fundamental mistake is that people think that just because someone is specialized on a topic he's also good at it.
Many get the title "DevOps" who are basically Ops people with a new toolkit. One of the problems with the DevOps stack, though, as working in the infra-as-code needs a dev mentality to be done right. Many traditional ops people will "program" the infra-as-code using pretty bad quality code. (often using way too much cut&paste for stuff that could be generalized.)
On the other hand, when devs switch to "devops" they often fail to have the attention to detail and sense of responsibility found with many traditional ops people.
So finding good candidates for DevOps roles is really hard, and often those positions are staffed with people who are not really suited for the paradigm.
I -AM- a generalist and it's also a requirment for being actually any good in devops, but I position myself as Freelance Sr. Engineer with Kubernetes / DevOps / Golang Focus, because thats what I like doing and also what I am good at.
There is a whole longtail of skills that are required to do any of this, also quite a few that are not even tech related, like proper communication or empathy.
But yeah, if you require assitance, I am definitly the kubernetes-dude that you can call and it should be as simple as that.
Well . . . people always assume they have the answers, so they've designed an exact position to do what they think they need.
But if they need it and can't fulfill the need themselves, they probably don't know what they need.
The company, composed of vain people, is more likely to hire someone that solves their "exact" not-really-problem.
This is why I position myself as Consultant and Engineer, because you will know you have a problem with your cluster, and I should know how to solve it.
When you are at the point, where your question is: "I need someone to fix my internal ingress-controller because traefik binds all services to the public one", you might simply need to open an issue with the developers of traefik.
Yet if your problem is: "we would like to completly separate internal traffic from external traffic inside our own datacenter", you are looking for the kubernetes devops guy with the neccesairy experience.
I also hide my Excel skills extremely well, they are to be deployed only on emergencies.
My Ask HN post about it: https://news.ycombinator.com/item?id=32317514
These days it just means frontend and backend, in the same language, often the same framework.
The same term that was used to identify senior generalist engineers with extensive experience in the field, these days is used for any junior JS dev with a couple years of experience under their belt. Not their fault, it's the recruiters fault for appropriating the incorrect label instead of creating a new one.
I consider myself a "full stack employee". I've done backend, frontend, hosted live events, some sales, marketing, a dash of HR, pretty much everything.
Do I write that on my LinkedIn? Heck no. A year or so ago I looked at all the experience I had, saw I had a through-line story of how I've worked on video projects over the past 7ish years, and decided "I'm the frontend WebRTC guy." I identified the spots of knowledge I needed to read up on to be confident (just a few gaps here and there) interviewed at a job, and within 10 minutes into the interview my future (now current) boss said "You're the perfect fit!". Because I was. I'm the frontend WebRTC guy with some sales/marketing experience, and they needed a frontend WebRTC guy with some sales/marketing experience.
Before that, I was the Frontend DevOps guy. Before that, I was the Backbone.js guy. And before that, I was the Sharepoint guy (shhhhh don't tell anyone!)
If you're interested in AI, just go poke around and find something in AI. Don't sweat it. We all got plenty of time, and like you said, as long as we can center divs and set up click tracking on a Wordpress site we'll always be able to put food on the table! :)