3 ms·

your comment describes an interdisciplinarian with basic communication skills, which is exactly the type of engineer most teams should be looking to hire, even

your comment describes an interdisciplinarian with basic communication skills, which is exactly the type of engineer most teams should be looking to hire, even if only to strengthen collaboration between dedicated design, engineering, and product functions > they should also do frontend, backend, dev ops, security, and on-call this is exactly what a full stack in a small- to mid-sized team does. all things dev + on-call rotations. > why dont we throw in project management and product management while we're at it this has been a collaborative effort on most of the teams i've been on, even with a dedicated PM > it's not like those UI/UX people do much either, so let's just make the devs do that too in my experience design output from an engineer with junior-to-mid design experience is more successful than that from most mid-to-senior designers without engineering backgrounds > we'll have like 5 mandatory meetings a week to check in on them you're bothered by your job checking in once a day during the work week?

jackblemming 4y ago
From the sound of your post, you seem to enjoy the ever increasing set of responsibilities tacked onto the "fullstack" title. Many do not. Especially because pay does not seem to increase at the rate new responsibilities are added. But if you enjoy making your boss richer for no increased pay, have at it. It may surprise you, but I do all the things I described for my own company and I keep all the money I make from it. I would never expect someone I hired as a developer to do everything I do, for likely peanuts compared to what I make. But I guess this is how some devs want to be treated. More responsibility isn't always a good thing.
- replygirl 4y ago
  a broader set of responsibilities doesn't necessarily equate to more work. in my experience there's no correlation at all between the scope, intensity, and exploitativeness of work i agree entirely with the substance of your post and don't understand how it conflicts with the substance of mine. i hold to the same standards i laid out whether i'm working for a boss or working with a co-op or other worker-self-directed group

jackblemming 4y ago

From the sound of your post, you seem to enjoy the ever increasing set of responsibilities tacked onto the "fullstack" title. Many do not. Especially because pay does not seem to increase at the rate new responsibilities are added. But if you enjoy making your boss richer for no increased pay, have at it. It may surprise you, but I do all the things I described for my own company and I keep all the money I make from it. I would never expect someone I hired as a developer to do everything I do, for likely peanuts compared to what I make. But I guess this is how some devs want to be treated. More responsibility isn't always a good thing.

replygirl 4y ago
a broader set of responsibilities doesn't necessarily equate to more work. in my experience there's no correlation at all between the scope, intensity, and exploitativeness of work i agree entirely with the substance of your post and don't understand how it conflicts with the substance of mine. i hold to the same standards i laid out whether i'm working for a boss or working with a co-op or other worker-self-directed group