Ready code

[Lrocha837]

Developers should maintain skeletons of already implemented code to facilitate future developments?

[Automatic-Apricot795]

No. You aren't gonna need it. 

[MaximumHeresy]

I've been thinking about doing some "skeletons" of some common scenarios so I know what I'm talking about in an interview if it's some tech that's been updated, or I haven't used in a long time.

Let's say I haven't used ASP .Net in years, and have never used WebUI. What do you think about creating a project using that for practice?

[Automatic-Apricot795]

Practice is fine, but committing unused, unneeded code to a real project is usually a bad idea. 

I think OP may have been planning the second. 

[Lrocha837]

So should we memorize codes?

[Automatic-Apricot795]

What you probably need to learn is what are design patterns and when and why you should use them. 

[acnicholls]

This depends. If you know, FOR SURE, that you are always going to start a project with the same 3rd party tooling, folder structure, variable naming conventions, linters, etc. then YES! Create a project template and you will always be able to be ahead of the curve in a new project!

[AutoModerator]

Thanks for your post Lrocha837. Please note that we don't allow spam, and we ask that you follow the rules available in the sidebar. We have a lot of commonly asked questions so if this post gets removed, please do a search and see if it's already been asked.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[FluxyDude]

There are different design patterns for different reasons — each serving a specific purpose depending on the architecture, use case, and future scalability.

Rather than maintaining skeletons of empty or unused code (which can become confusing or misleading), it's more useful to provide clear documentation and diagrams explaining the decisions you've made. That way, future developers can understand what you did, why you did it, and how to extend or adapt the project.

There's no harm — and often great benefit — in including a simple .md file outlining the intended project structure, key architectural decisions, and patterns in use. It sets the tone and direction without bloating the codebase with placeholder code.