The explosion of languages, frameworks and platforms in the software development world has created a bit of a double edged sword for those fancying themselves as technical generalists capable of doing just about anything. On the one hand it's created a world of ever more shiny new things offering a limitless supply of new toys to experiment with. On the other it's highlighted the stark difference between what I'll classify as coders and developers - making interactions with recruiters and other technical-interfacing leypersons increasingly more infuriating.
In my grossly generalized world the Coder can be identified by their battling cry: "That's a problem, I'm a developer". The Coder is characterized by his proficiency in a narrow range of chosen skills. The Coder will progresses and becomes better in his niche by sheer practice and repetition alone.
By contrast the Developer's single greatest skill is in being an applied learner. Quite simply the Developer has a knack for grokking new [languages|frameworks|platforms] and becoming proficient very quickly. There is no problem beyond their reach for they enjoy building at any level stack.
So, before you ask again ... NO I AM NOT A:
... back-end developer
... front-end developer
... java developer
... React developer
... developer...
for my fundamental understanding of the underlying principles and my willingness and propensity to learn whatever is asked of me means ...
I am JUST a Developer
This was originally posted on my own site back in January. A confluence of events this week has fueled the same rage that inspired that post so I share here again.
At some point in the future my job, responsibilities and technologies will be entirely different from today, and I'm excited for that future unknown. 😊
I dunno.
Are you a graphics programmer?
A gameplay programmer?
A machine vision programmer?
A networking programmer?
A game programmer?
I work in games. A games developer vs non-games developer are pretty different. Maybe "developer" is a good catch all within the context of games. But I'd say there are useful classifications beyond just "developer".
Also, I can't help but notice your website says "mobile and web developer". As opposed to just "developer". ;)
Reminds me of the Mason and the Bricklayer, a mason can tell you about the stone and mold it to whatever he needs it to be. He can do this because he has taken the time to really understand the medium and its limits and the techniques that are needed to build a solid structure. A bricklayer can tell you how long it will take, how many bricks are still in the pile and can replicate whatever wall you want. Each is needed, but the skill, expertise and price is the key difference.
I do get your point.
I wrote something similar a while ago.
Not sure if you'd like but I thought I'd share anyway.
medium.com/@juanp6/web-development...
You've drawn an artificial line in the sand. Are you also not a software engineer then? How about generic problem solver? Drawing such distinctions is silly.
Nowadays, the RH recruiting requests for developers sounds like:
Looking for:
Gynecologist with experience in lobotomy!
An oncologist with experience in root canal treatment!
An ophthalmologist with experience in wild animals toraxis surgery!