"Your Job Is Not To Write Code"

[Darren Dirt]

https://medium.com/@lauraklein/your-job-is-not-to-write-code-d002609b117a

...come for the frustration reading the article, STAY for the brutality of the responses**!


found via http://hexatlas.com/entries/5 "You can smell "Product Manager" miles before the signature line of the article." lol





** like, such as

If the PM did not ensure that there is proper QA, it is that PM that is responsible for the @%&#ty code in production. If the product doesn't do what the customer expects, it?s the PM that did not write proper use cases and proper specifications and operational parameters, and it would be the PM that did not ensure that the QM had created the necessary test cases and functional specifications.

My skill is not customer management. My skill is not necessarily to know the business that the client is in. My skill is to transform various degrees of incomplete specifications into something that resembles what the customer wants, within reasonable time, and with a reasonably high quality.

...If the CEO doesn't understand or care about these roles and allot the necessary time and/or resource ? that company will be fighting fires, playing blame games, and losing clients.

Sincerely,
Your Developer.

Dear Product Managers:

Your job is not to sketch ideas.

Your job is to define the product for our users so it can actually be built and deployed. If you want to get technical about it, your job is to provide detailed specifications that include both product improvements and the technical environments users live.

https://medium.com/@nathanst/your-job-is-not-to-write-click-bait-articles-that-actually-say-nothing-6962fa1a25e4

You have Coders putting code directly into Production.

:-D

[Darren Dirt]

found via http://hexatlas.com/entries/5 "You can smell "Product Manager" miles before the signature line of the article." lol

That ended on a rather passionate note. In a good way, tbh, it kinda inspires me:

Your job is to write the best code you can, as quickly as you can, within budget, meeting all of the expected features, in a maintainable way, and a million other things, and still make the users happy.

And yes, all of your goals conflict with each other, and you will make mistakes, and you will fail, and you will learn, and you will get better, and you will succeed.

Your job is to tell someone when you make a mistake.

Your job is to work together with your testers and with operations and with product and finance and, yes, even the other engineers.

Your job is to figure out what product will ask for before they ask for it, and build the code so that if and when they do, adding the feature is easy because the code wasn't written in a way that requires a year-long refactoring project to do it in a way that wouldn't make Cthulhu literally gleeful at the thought of it.