Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

And devs are in the perfect position to take on this responsibility. They usually have sufficient domain knowledge and know what it takes to build stuff in this context.


sort by: page size:

They’re doing all the roles that allow developers like us to have a job.

Depending on the definition of "dev", they can be the ones who define the requirements and API.

I agree. Function of devs that have deploy power.

I think that's a great point, but I'd argue that one of the reasons that works well is that the developers are (typically) also the product owners, project managers, etc.

That or they get developers who know exactly what they’re doing…

I think the point of the article is that if developers were required to do this, they could do it.

To be fair, developers seems to be very good at doing this themselves as well.

Developers tend to be intelligent.

What's tricky is that in a different context, those people would be excellent contributors. Like in a mature product, who wouldn't love a developer who works on documentation, builds out a staging environment, and makes the codebase more scalable? But it just doesn't make sense when you haven't shipped anything yet.

Good developers are good developers.

Why not also be the developer if you can do that much already?

Why developers? In most cases I know this is responsibility of product people who explicitly want that.

They needed this developer to help them understand what they needed. Every project I’ve worked on (even personal projects) has a fair amount of this.

Good point. The issue is easily solved by making developera part of the program by choosing whcig projcts they would like to work on the most and why

Exactly, I'm a dev myself.

Developers thrive when they know what to do and can make the right decisions.

Developers can develop for what they want.

Lots of developers do this.

Yes! Developers are people too..
next

Legal | privacy