Which of these diagrams or approaches do you prefer as a developer?
(1 votes)
Loading...
(1 votes)Loading...
(1 votes)Loading...Similar Posts
Is Telegram actually anonymous, or only with a VPN?
Is Telegram actually anonymous, or only with a VPN? there are all sorts of illegal how to download film groups, porn, man can ordering cannabis via delivery etc., can something happen
Unity objects spawn when player is not looking?
ByGraviTeM
How can I spawn objects in Unity (at a predetermined position) whenever the player isn't looking there? I'm using the FirstPersonController from Unity's standard assets. Thanks for any help! 😀
Why can't I see my Steam games?
I downloaded several games from Steam, but I can't see them in the library… can anyone help me?
Why does ChatGPT say that my term paper was written by him?
As a test, I once ran parts of an old term paper through ChatGPT. I wrote the paper myself, citing almost 70 sources and writing it long before ChatGPT was created. So why does ChatGPT claim my intellectual property as its own? In retrospect, it doesn't matter to me, but if I have to write…
How long do policy violations count in the TikTok creativity program?
Hi, I have a question for the TikTok experts among you. I wanted to sign up for the program, but the guidelines state that you can't do it if you've recently violated the guidelines, which I actually haven't. I made my own videos, but TikTok still marked them as inauthentic. I wanted to ask if…
Sorry, but your survey is not really meaningful.
There is also a very important detail: the requirement.
I have never used structograms after training, and I do not see any advantage over code.
I usually use schedules for planning complex relationships.
I only rarely use pseudocode and is in the end only productive code where a few simple things have been omitted.
I only use comments if the code is not sufficiently understandable, for example to explain a method.
(comment) documentation I generally use NuGet packs with public content.
UML is not a chart, but rather defines many types of charts. Structograms and schedules are also UML.
It seems that the survey is not meaningful for you. Then why do you answer the individual points? It looks more like you are not particularly familiar with programming and try to hide your ignorance rather than respond in a targeted way.
It could be that you did not understand the core statement of my question. There is a demand function that you can use.
And the question was not that you should explain the individual diagrams!
Computer science would be so much more beautiful if everyone would be a bit more dear to each other and this lasting “want to be better” remains in a healthy setting.
The survey suggests that it is about when you use these procedures – I answered that. And I didn’t explain a single chart.
And if you already give me ignorance, please explain what I don’t understand about your survey?
You really don’t get far with this attitude. It’s disappointing to see how you’re looking for backup. I can only smile and take you to my ignorant list!
Computer science would be so much more pleasant if the information that someone gives were properly analyzed and understood. I had to make a thousand sentences here, only so that a self-appointed computer scientist could understand my simple question. Instead of reading my question correctly, it is unnecessarily written around…
What kind of “why”?
I wrote:
Do not place a survey, but write what you have before and ask for the preferred procedure, then you can also respond specifically.
How did you get to your “why”? How could I better formulate the question to find out the preferred procedures of individual developers? My goal is to find out what working methods others use. Is that so difficult to understand?
Depends on what.
Big code is to comment. It’s complicated to comment. Witness that cannot be taken from 1 to 1 so of the specification because “Insider knowledge” or “How do we not write this into the specification” must be commented. Otherwise no one knows that at some point and everyone has to find out what the 5 lines are good for.
Documentation of requirements (conversations, specifications,…) are worth gold. Documentation of implementations if you like to make people certain things by default (and not annoy) as well.
Pseudocode can be great if you are discussing how to build the common code with other developers, but it doesn’t make inventory code understandable and brings little into discussion with people who can’t program.
Schedules are great for larger processes to understand the overall picture, even in discussion with people who do not develop. For every small code, they would be a nightmare in care and implementation. An adjustment in the middle and that ding makes no sense anymore.
There is not the perfect means for everything.
The question is always:
Each has its own preferred style and approach when using instruments or methods. Personally, I prefer program schedules as they help me structure and disassemble my program more efficiently. What is your preferred method and why?
That’s what I wanted to do.
As shown above, situation and person dependent.
I’m not doing some kind of development. I have new development and pass code. I’ve only got modules for me and stuff that’s central and third.
I sometimes only develop for myself and sometimes with others.
Some stuff is 3 liners and some are 4 programs and hundreds of lines code.
I don’t have the one method I always use ode usually. I see what task is, who is involved and how complex/entire and then find what I think best fits.
Writing schedules when the specification comes in the field A instead of B is completely covered. There comes the comment with request blub changed from A to B and good isses.
But that’s not all.