Design Pattern

[Emme Developer]

In these days in an italian community we are talking a lot about what the basics are for a developer. In the question "how much is important design pattern?" somebody answer:
"This question doesn't make sense. Writing code without following a pattern is really doing programming? These are the basics."

In these days I'm changing my approach to programming and my point of view on many things, so I would like to talk with you. I don't agree with previous answer. A lot of pattern require some "features" that in B4X we don't have (i dont want to discuss why, it's a RAD and for me is ok) such Abstract and Others OOP statement. So would this mean that we are not developers? I don't think.. Would this mean that we don't write good code? I don't think.. and anyway, what is a "good code"?
Sorry for the outburst, I hope we can start a constructive discussion

 

[Erel]

There isn't a single correct approach.

I've collected a few tips here: https://www.b4x.com/android/forum/threads/b4x-tips-for-b4x-developers.62121/#content
Not exactly about design patterns but might be related.

Classes are the most important feature of OOP paradigm and they are available.

and anyway, what is a "good code"?

- Works correctly.
- Maintainable.

If your code works correctly and can be further improved and fixed relatively easily then I consider it very good code.

 

[Emme Developer]

- Works correctly.
- Maintainable.

If your code works correctly and can be further improved and fixed relatively easily then I consider it very good code.

Yes, you're right, i think it too. In my country more and more people have too many prejudices:
Do you know Design Pattern? NO? So you're not a good developer.
Do you know Dijkstra's alghoritm? NO? So you're not a good developer.
Do you know bla bla bla bla bla bla bla? NO? You're not a good developer.
And if i think you're not a good developer, then you can't work with me.

Extend this concept with the fact that most employers or interviewers have these prejudices, and the result is that you have to leave the country.

 

[KMatle]

It's "good" if you see your owncode a year later and understand what you did. Today I do many things "better" than before. So to me it's a development, too

 

[Peter Simpson]

It's "good" if you see your owncode a year later and understand what you did. Today I do many things "better" than before. So to me it's a development, too

I completely agree @KMatle.

From time to time:
From time to time I look at my code from a few years ago and sometime I rewrite parts of it. I then ask myself, what was I drinking when I first wrote the code

I'm a better programmer:
I'm more than sure that I've learned more about coding using the B4X suite of tools in the last few years than I did using VS. VS gives you way too much room to mess up your code and your program still works and that could end up problematic in the future, it's unbelievable really. Whereas B4X especially B4R needs more skills in both coding and design for optimisation purposes. For example, in B4R because of the limitations of Arduinos, ESP8266s and ESP32s Microcontrollers, you really do have to code with little to no waste of memory and processing power, design wise it's absolutely essential, you can clearly see from my code snippets and tutorials in the B4R forum that everything is optimised to the best of my ability (at the time ). The B4X suite of tools really do help you to improve your general coding and design skills.

What a good coder needs:
A good coder needs to always be ready and willing to rewrite and improve their code after the fact, always willing to take constructive criticism with a pinch of salt and learn from it, and definitely willing to move with the times with coding techniques and solutions.

We are all learning every single day. You, me, Erel, et el, we never stop learning and improving.

Enjoy...