In your opinion, what are the things that a developer must to know to do his job?
-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
Things to know for a good developer
- Thread starter Emme Developer
- Start date
- Similar Threads Similar Threads
to be curious and innovative
I would say the hardest skills needed are:
Perseverance, not to drop an ongoing project just because it's difficult;
Patience, to endure those sometimes ridiculous suggestions clients make;
And broad thinking, vulgo "curiosity" or "think outside of the box"
Perseverance, not to drop an ongoing project just because it's difficult;
Patience, to endure those sometimes ridiculous suggestions clients make;
And broad thinking, vulgo "curiosity" or "think outside of the box"
Yeah guys, i agree with all. But i mean things that a developer must to know, not how a developer should be. For example, algorithm complexity, Computational complexity, OOP and Others 
In my opinion nothing mentioned here is required to become a developer. If, by chance, the developer has to take that in count, he could take a good documentation and learn in situation.
Having that in school is perfect because the guy will be prepared and a mass culture about the things but until he will be focused on one project only, he will have to learn by himself too.
Take the example of OOP : some languages did exist before OOP. And about the algorithms, I am bad at that always impressed when I see experts use them here in the forum. Do I care much in my today work ? I am not sure at that...
Of course, I am probably the worst developer in this world
That's secondary, I still stand by my comments, you can know all the algorithms in the world, all the complex equations and formulas but that WILL NOT make you a good/better developer, it will help, but it won't guarantee it.Yeah guys, i agree with all. But i mean things that a developer must to know, not how a developer should be. For example, algorithm complexity, Computational complexity, OOP and Others
Want proof? well, browse the forums, and you will see that some developers posted grandiose multi-page code to solve a problem, the next post by another developer with just a few lines solved the same problem.
There's no hard answer because it will depend on what kind of development you are into, but what will be common is: Imagination, practicality, efficiency and patience.
I never studied algorithm complexity. Few days ago, a my friend asked me how can i choose between list and hasmap without knowing their complexity and what is more expensive. I choose between maps and lists in relation on what i need to achieve, but in really i don't know what is faster. Is this an aswer? I don't know, but i am a junior developer and i'm trying to understand what is important and needed in our job
Last edited:
Faster doesn't mean better, if the code does its job efficiently then is the right code, the good thing with code is that you can always improve it (or damn it to hell) it's up to the developer.I never studied algorithm complexity. Few days ago, a my friend asked me how can i choose between list and hasmap without knowing their complexity and what is more expensive. I choose between maps and lists in relation on what i need to achieve, but in really i don't know what is faster. Is this an aswer? I don't know, but i am a junior developer and i'm trying to understand what is importand and needed in our job
And I would add that, if @Emme Developer makes his own researches and finds an answer, that could make a difference for his salary compared to his colleagues who don't already know
Honestly, that sometimes is the answer, while a "Senior" developer is quoting Einstein and Hawking and opening stargates, wormholes and what not, by the time he is done, some other dude already did the job, who would I hire?: The other dude.
Last edited:
I have not colleagues that are developers, so when i finds an answer there are more money for company
Technical skills wise, I guess knowing each control/language/technique payload helps, but unless you code F1 codes were every microsecond counts, it doesn't really matter.
I have no coding technical background, but if I'm to choose between 2 types of controls for a task, I take into account several things, most not technical, like, which one I feel more comfortable with
I have no coding technical background, but if I'm to choose between 2 types of controls for a task, I take into account several things, most not technical, like, which one I feel more comfortable with
An analogy I have used before in this forum to describe coding/programming is this...
I often say to colleagues and friends that programming is like handwriting; you can give several people a paragraph to copy, some people will choose to write in capitals, others may write joined-up (cursive), or some may chose to write it in their native language. Some will be neat and others barely legible, and some will undoubtedly contain spelling errors. But at the end of the day they will all say roughly the same thing.
That's why programming is like handwriting, we all have our own style and way of doing things. I agree that it is good to try and stick to certain standards and conventions to make it easier for others to follow your code, but at the end of the day, if it works and you're not expecting someone else to have to continue the project then its up to you how its done. And hopefully you'll have fun doing it
I think that useful traits to have when considering becoming a programmer is to be able to think things through logically. Programming is basically a sequence of steps from start to finish. Having a clear or reasonable idea of what steps are required to achieve a certain goal makes the programming easier. I also think that programmers are quite artistic and that this is a useful skill to have. Nearly all programs require user interaction and being able to create a visually appealing interface which is intuitive to use is a skill in itself.
Programmers are naturally inquisitive and I think like to learn.
I often say to colleagues and friends that programming is like handwriting; you can give several people a paragraph to copy, some people will choose to write in capitals, others may write joined-up (cursive), or some may chose to write it in their native language. Some will be neat and others barely legible, and some will undoubtedly contain spelling errors. But at the end of the day they will all say roughly the same thing.
That's why programming is like handwriting, we all have our own style and way of doing things. I agree that it is good to try and stick to certain standards and conventions to make it easier for others to follow your code, but at the end of the day, if it works and you're not expecting someone else to have to continue the project then its up to you how its done. And hopefully you'll have fun doing it
I think that useful traits to have when considering becoming a programmer is to be able to think things through logically. Programming is basically a sequence of steps from start to finish. Having a clear or reasonable idea of what steps are required to achieve a certain goal makes the programming easier. I also think that programmers are quite artistic and that this is a useful skill to have. Nearly all programs require user interaction and being able to create a visually appealing interface which is intuitive to use is a skill in itself.
Programmers are naturally inquisitive and I think like to learn.
