5

1. For my employer to invest in QA. Honestly, even if I'm 101% confident about my code, if nobody tests it other than me, I would advise against prod-ing(Is that a word?) it.

2. For recruiters so stop expecting a Full stack dev to be perfect in both ends (especially with an entry level salary. Stop taking advantage of them!!). Just stop using the term full stack entirely, please.

3. For API docs of other companies to be deserving of the title 'Documentation'. I'm so tired of figuring out other API parameters via trial and error. Just make your docs as clear as you can please, so we don't have to bother each other with so much email.

That's all for now. Thanks dev Genie.

Comments
  • 0
    @irene so... what do you call the dev that builds the servers, secures them, design and build the databases, the backend code, designs and prototypes the front end , builds it after management review, and launches all this into a production server(s)...

    Hi... from a {insert my new job title}
  • 0
    @irene I would but I have no issues with doing the design work. It allows for some non-code creativity.

    Plus all the designers I’ve worked with in the pass have done nothing but slow things down overall.
  • 0
    @irene I agree. It’s usually limited to front/backend code at best not the entire process and ecosystem.

    I need a new title... the whole stack dev.

    Doesn’t have the same buzz feeling.
Add Comment