this post was submitted on 24 Nov 2023
109 points (76.3% liked)
Technology
59322 readers
5106 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Programming is like 10% writing code and 90% managing client expectations in my small experience.
But a lot of the crap you have to do only exists because projects are large enough to require multiple separate teams, so you get all the overhead of communication between the teams, etc.
If the task gets simple enough that a single person can manage it, a lot of the coordination overhead will disappear too.
In the end though, people may find out that the entire product, that they are trying to develop using automation, is no longer relevant anyway.
Programming is 10% writing code, 80% being up at 3 in the morning wondering whY THE FUCKING CODE WON'T RUN CORRECTLY (it was a typo that you missed despite looking at it over 10 times), and 10% managing expectations
Typos in programming aren't really a thing, unless you're using the shittiest tools possible.
Typos are very much a problem in programming. Variables can be set to the wrong value without the programmer noticing, you can call the wrong method (example RotateZ instead of RotateX), and in more advanced programming such as Java/C# reflection the IDE can't correct you.