29 ms·
> Java might be verbose, but it's well-understood, and it's not actually what slows development. I think you're onto something. Maybe some Java-by-default work
by hitekker 3y ago
> Java might be verbose, but it's well-understood, and it's not actually what slows development.
I think you're onto something. Maybe some Java-by-default workplaces lack technically interesting problems that engineers want to solve, so those engineers instead overfocus on the frictions of the parts they can control. Maybe those engineers desire expressiveness in their working programming language to compensate for the restrictions on the rest of their work.
Just a hunch though.
- deleted 3y ago[deleted]
- throwaway13623 3y agoI think you may have a point. At mature companies, they have largely solved the product market fit and uses a stable stack that just works. I have worked worked for such companies, and developers jumped at the chance to use the latest (untested) technologies for greenfield projects if they had the chance. In my startup we also use a "boring" stack, but the problems we solve are innovative and motivation in itself. The developers work closely with customers and can see the impact that the product has. They are no longer working in a Jira-factory and while they are still interested in technology they also find motivation in the product itself.