5 ms·
"Boring" it's just another label, like "ninja" or "full-stack developer". Wouldn't it be better to avoid labels at all?
by viach 11y ago
"Boring" it's just another label, like "ninja" or "full-stack developer". Wouldn't it be better to avoid labels at all?
- fishnchips 11y agoAgree. Where I work we recently dropped all labels across the whole company - so no more juniors, seniors, frontend, backend, full-stack etc. Just software engineers. We still use 'CEO' and 'CTO' but only externally.
- takno 11y agoThen they're either not rewarding experience, or pretending to the juniors that they are getting paid the same and equally-valued.
- fishnchips 11y agoDo you really want labels as your reward?
- nickpsecurity 11y agoThat's a good point. Pay should be enough for most people.
- CuriouslyC 11y agoLabels aren't completely valueless. HR at some large corporations are actually anal enough to check that your official job title at a company matched the description you put on your resume, and will red-flag you if there is a significant discrepancy.
- fishnchips 11y agoPossibly, but that has nothing to do with rewarding folks for labels. Instead, you're rewarded with pay, respect and opportunities for your constant effort to perform, learn and teach.
- beeboop 11y agoI'm surprised you kept "engineers" as part of the title. Is a guy writing only CSS an engineer?
- fishnchips 11y agoWe don't have these.
- enjo 11y agoI'd imagine they'd be called a "Designer".
- jclulow 11y agoEngineering is rigour, understanding, accountability, the balance of competing concerns, communication and cowork with other people, the application of ethics, and continuous improvement. If your occupation strives to include these properties, and you strive to learn and improve your own skills and your field in general, I don't see why the particular language you use should prevent you from being an engineer.
- true_religion 11y agoBeing an engineer of X is like being a Doctor of X. It's a general descriptor about your experience, and the way you approach the work. Granted the state has stepped in and in someplaces you can't call yourself an engineer or doctor without certification, but the fact remains that the word has a meaning in common parlance.
- partycoder 11y ago"Full-stack" is very vague and very rarely means working on the full stack. Also, if someone cannot answer the question: "what happens when you type 'google.com' in your browser" then you are definitively NOT full stack.
- fishnchips 11y agoAh, the Google interview question. Should we start at keyboard interrupts? ;)
- V-2 11y agohttps://github.com/alex/what-happens-when#the-g-key-is-pressed https://github.com/alex/what-happens-when#the-g-key-is-press...
- partycoder 11y agoShould we start at the motor cortex?
- fishnchips 11y agoOnly if we're recruiting a neurosurgeon.
- beeboop 11y agoI think it depends on the context, and that context has shifted a lot over the past ten years. I can deploy an app to Heroku that scales tremendously well (if expensively) and have almost zero knowledge of configuring a web server or the tools it uses. I think it's probably more accurate to define "full stack" as being able to make and launch a web application on your own. Servers and databases are just tremendously easier than they used to be, so the bar has been lowered a lot. Knowing the steps of what happens after typing in "google.com" in your browser is only relevant to people working on projects of massive size, in which there is no need for a "full stack developer" in many cases, or you're doing something completely removed from just a web application.