Code structure organisation
(this will be fast) My name is Marcelo Lebre, I'm co-founder and CTO at Remote. Twitter: @marcelo_lebre

For the past few years I've been experimenting with different ways to organize codebases. I started it to improve my own craft as a programmer and later realized many people/teams could benefit from these findings.

I want to publish my conclusions but would like to have a better understanding of its impact with data/metrics.

These questions focus on codebase structure, how to organize your files and the logic within them.

As thank you I will randomly offer a pair of rare remote socks (brand new ofc) :D
If your answer wins the rare remote socks how can I contact you? (optional)
Your answer
What's your main programming language?
How does your current codebase structure look like?
When you need to scale the current architecture what approach will you use?
Do you believe your current codebase structure could be improved?
Does your current codebase lean towards bigger files or more files?
Do you prefer bigger files (more LoC per file) or more files (less LoC per file)?
How often do you have to refactor code because of tightly coupled logic or poor code structure?
In your current project how much time do you spend refactoring, per development cycle, due to tightly coupled code or poor code structure?
Do you think your development cycles would improve significantly if you had a differently structured codebase?
Can you reuse most of your code as easily as you’d like to?
What’s your go-to strategy to keep your codebase sane?
Have you ever heard of cyclomatic complexity before?
Do you practice the single responsibility principle on your codebase?
If you could go back in time what's the one thing you'd fix in your codebase?
Why doesn't your codebase have better test coverage?
Where/how did you learn how to improve your code structure?
Submit
Never submit passwords through Google Forms.
This form was created inside of Remote. Report Abuse