Programming

17418 readers

224 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Programming As a Career Isn’t Right for Me (medium.com)

submitted 1 year ago by Aboel3z@programming.dev to c/programming@programming.dev

18 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] zero_spelled_with_an_ecks@programming.dev 9 points 1 year ago (1 children)

Now my day-to-day is filled with process. We must break our deliverables into 2-week chunks so that the stakeholders can see our progress and know that we’ll deliver on time. But it’s not on time. Everything must be tested. But it still has bugs. Everything must have thorough documentation. But it quickly gets out of date and we never read it.

[–] onlinepersona@programming.dev 5 points 1 year ago

Most stakeholders don't understand software-development, development cycles, or even SCRUM (the most known collaboration framework for software development). It always amazes me how managers and even seasoned developers do not understand these things. They don't understand estimates, roadmaps, task division, the value of software architecture nor exploration, nor just how complex it is to write software.

This also leads to them not understanding the tools used to manage the process, the developers, the software, nor the outcomes.

Everyone just wings it.