Posted December 23, 2021
low rated
It is great Magnitus & dtgreene that you have unwrapped all the entanglement Sw development entails.
You have moved from the oversimplified "programmer vs CPU time trade-off" to grab the bull by the horns.
I am afraid I will not reply every piece of your posts: It would require a significant time and typing effort that this holidays do not allow me. Besides, is not the place to have this deep discussion.
Instead, I'll try to write a short post then.
After finally bringing the meat to the table, I declare Magnitus the winner of the tiger raffle (In case your/my posts were a winner/loser competition or it alleviates somehow my 2 provoking posts).
I am afraid I won't tell you my expertise areas. Instead for a change, I propose we brag how many times we have been the villain/,,loser,, pushing back projects by the topic on the table.
Don't you think would be more purposeful? :)
Anyway, in pursue of shortening, I quote key phrases from both of you:
Magnitus: "If you never had to deal with deadlines. I envy you. You must be very privileged (but also kind of out of touch with the reality most developers face).
I won't pretend that the software industry doesn't suffer from a wild west problem"
Magnitus: "A well designed piece of software is full of tradeoffs leading to a well designed solution for the problem the software is trying to solve.
Universally good software, irrespective of problem domains, doesn't exist. Its always contextual."
Magnitus: "bloated complexity ... I bailed out of that some years ago"
dtgreene: "the code is running on a system not owned by the developers"
dtgreene: "aren't suitable in embedded situations. In this case, CPU power and RAM are not as cheap or abundant as they are on more conventional machines"
dtgreene: "launching shuttles into space [considerations]"
Magnitus: "Context matters"
Magnitus: "When taking advantage of fine-grained lower level optimization, it is assumed to be performed by someone who is proefficient and knows how to optimize thing"
Magnitus: "conservative with technology at heart. I don't use a tool until I've understood it well (I don't need to read all the code for dependencies that are very large, though I do expect at the very least to get a lot of wisdom from people with a great deal of experience in the tool, usually indirectly via a book). It does create a hard limit on what I can use which I find healthy. It forces you to prioritize on what truly matters and it causes fewer failures in production"
dtgreene: "test out snippets of code to see how they actually work while you are learning"
Magnitus & dtgreene: [Several specific cases]
I agree with both of you. Magnitus, if you like, you could compare this quotes to my 1st post keywords list. Any way or other, we are talking about the same: A long list of things to consider.
Then, if we agree: Why both of you used the infamous oversimplified "programmer vs CPU time trade-off"? (Rhetorical question)
I invite both to more frequently be the villain/,,loser,, raising the voice against unrealistic deadlines, bore to death the decision makers with all the intricacies Sw Eng entails (Go find and use puppetry and 5 years old explanations if needed), push back the deadlines and the scope creep with the ultimate goal to deliver quality Software. Let's get some scars to be proud of and let's create a safety_net/union (open to proposals) to give support to each other into a business crushing the human talent causing us stress, anxiety, nonsense, and a lot of sh*tware. Again, someone will need to clean up all the mess and very probably will be ourselves.
Please, we must defend the respect Sw Eng deserves.
I hope someday to meet both in person to have this fascinating discussion.
There, I will not need provoking/profanity tactics. I promise.
Enjoy the holidays and read you both later.
You have moved from the oversimplified "programmer vs CPU time trade-off" to grab the bull by the horns.
I am afraid I will not reply every piece of your posts: It would require a significant time and typing effort that this holidays do not allow me. Besides, is not the place to have this deep discussion.
Instead, I'll try to write a short post then.
After finally bringing the meat to the table, I declare Magnitus the winner of the tiger raffle (In case your/my posts were a winner/loser competition or it alleviates somehow my 2 provoking posts).
I am afraid I won't tell you my expertise areas. Instead for a change, I propose we brag how many times we have been the villain/,,loser,, pushing back projects by the topic on the table.
Don't you think would be more purposeful? :)
Anyway, in pursue of shortening, I quote key phrases from both of you:
Magnitus: "If you never had to deal with deadlines. I envy you. You must be very privileged (but also kind of out of touch with the reality most developers face).
I won't pretend that the software industry doesn't suffer from a wild west problem"
Magnitus: "A well designed piece of software is full of tradeoffs leading to a well designed solution for the problem the software is trying to solve.
Universally good software, irrespective of problem domains, doesn't exist. Its always contextual."
Magnitus: "bloated complexity ... I bailed out of that some years ago"
dtgreene: "the code is running on a system not owned by the developers"
dtgreene: "aren't suitable in embedded situations. In this case, CPU power and RAM are not as cheap or abundant as they are on more conventional machines"
dtgreene: "launching shuttles into space [considerations]"
Magnitus: "Context matters"
Magnitus: "When taking advantage of fine-grained lower level optimization, it is assumed to be performed by someone who is proefficient and knows how to optimize thing"
Magnitus: "conservative with technology at heart. I don't use a tool until I've understood it well (I don't need to read all the code for dependencies that are very large, though I do expect at the very least to get a lot of wisdom from people with a great deal of experience in the tool, usually indirectly via a book). It does create a hard limit on what I can use which I find healthy. It forces you to prioritize on what truly matters and it causes fewer failures in production"
dtgreene: "test out snippets of code to see how they actually work while you are learning"
Magnitus & dtgreene: [Several specific cases]
I agree with both of you. Magnitus, if you like, you could compare this quotes to my 1st post keywords list. Any way or other, we are talking about the same: A long list of things to consider.
Then, if we agree: Why both of you used the infamous oversimplified "programmer vs CPU time trade-off"? (Rhetorical question)
I invite both to more frequently be the villain/,,loser,, raising the voice against unrealistic deadlines, bore to death the decision makers with all the intricacies Sw Eng entails (Go find and use puppetry and 5 years old explanations if needed), push back the deadlines and the scope creep with the ultimate goal to deliver quality Software. Let's get some scars to be proud of and let's create a safety_net/union (open to proposals) to give support to each other into a business crushing the human talent causing us stress, anxiety, nonsense, and a lot of sh*tware. Again, someone will need to clean up all the mess and very probably will be ourselves.
Please, we must defend the respect Sw Eng deserves.
I hope someday to meet both in person to have this fascinating discussion.
There, I will not need provoking/profanity tactics. I promise.
Enjoy the holidays and read you both later.