Akineni | Websites That Work
Region: NG
Thursday 17 September 2026 18:11:56 GMT
5121
321
161
6
Music
Download
Comments
️Asilimia Mia :
You use inheritance. public ProjectB extends Project A { console.log("This is the smarter way"); }
2026-09-24 19:28:10
1
Cornelius Okodi :
I will create one project called Project M, which is the major project and make it as a package in python, then project A, project B, and other similar projects will just extend or inherit the major project. So I can even create even a million projects without rewriting the same codes. just by extending or inheriting the major project and just change the major values such as logos, app names, and other variables
2026-09-25 06:20:35
1
Felix Fleku :
That’s exactly what I did this week. It was similar project but some features were available on B to I just push the earlier A, push to GitHub and changed the logo and media files. The core functionality and logic remains unchanged
2026-09-25 15:26:20
0
Emmanuel Adekunle Peace :
I will write python script using python-docx
2026-09-25 17:38:33
0
Qudus Mustapha :
object oriented programming's inheritance of classes and polymorphism, while enforcing RBAC-role based access control
2026-09-25 10:35:30
0
alexadkinsbock :
Upload project A to GitHub and clone everything then adjust colors and logo names
2026-09-18 11:20:53
16
Eng.Waithaka :
write project A as a main project then create a new branch on the same repo and apply the changes for project B then deploy the two branches
2026-09-21 05:15:08
4
afrehsika :
what about code templating, just like how Tailwind and bootstraps have done to css
2026-09-23 20:03:52
1
Nick Frost ✪ :
Use a multi-tenant system Both project exist in the same code and repository, you will load all differences from a config file and apply it depending on which url is accessed. This make it easy to make changes that apply to both code making work easy
2026-09-20 11:53:53
2
VickyPaulKE :
use git repo with two branches
2026-09-19 11:14:28
3
ِ :
folks do be saying multi-tenancy but what are y'all doing about the additional module added to project B ? wouldn't that leak on to the project's A ? the best you can do is finish up with project A , push to git then clone it for project B and write your additional module and make neccesary changes[Pray] or also you can just have multiple branches on git. that approach works too but maintaining it might be confusing in the future if not careful
2026-09-21 01:09:23
3
TOX 😎😎 :
use docker and containerize the project then use GitHub to clone
2026-09-20 12:25:49
1
Sunday Etom :
mono repo
2026-09-18 12:28:46
2
Nara :
Modular design (React props) with Directus for CMS and backend (Shared). Directus stores and serves the assets.
2026-09-18 14:34:00
2
Mobility :
I will then make use of version control system (Git)
2026-09-21 20:26:44
1
PaalTech :
finish project A and fork to project B
2026-09-18 15:50:13
1
infotrix :
the main work will be done on GitHub with two branches project A and Project B in a single repository
2026-09-18 12:24:48
1
Magic :
Use a config file or .env file to activate or deactivate features, set app name, assets names, etc.
2026-09-21 20:34:26
1
🤷🏾 :
build reusable components and just use parameters or props for the differences and build out the extra modules for project b
2026-09-18 22:41:36
1
Blaze | Software Engineer :
Why not just make it a template? Build the common parts as a template project, install those two main projects, and then any future changes after the initial build can be managed through the template.
2026-09-17 18:24:14
1
i_am_chiaju :
I built an application that's currently being used by four different clients. A feature may exist in client one and not exist in others. As a backend dev, I have feature settings to turn on/off features. I wish there was a VN feature here. So an instance will be, an exommerce store, but client A doesn't want online payment and other clients want. Just add the configuration and turn on or off. Then we have configs for name, logo, client details. It's so mad but it's cool. So I just use one repository for all clients and nothing breaks
2026-09-18 05:56:19
2
C:/Users/mayor :
It mid level thing na bro. Use single multi-tenant architecture with feature flags and environment configuration. I do this all the time and I sell same app to multiple clients. Use environment variables or a central site configuration file to drive tenant-specific metadata (app name, logo URL, contact details, support emails). Feature Guard the two extra modules so they only render and execute when enabled for Project B.
2026-09-18 13:26:30
2
zagzy :
Work on project A firstly then upload to GitHub or bucket lab then make the changes for project b using project a and push you’re good to go If it requires database create double database one for project a and b after the project works successfully you’re good to go with that same code for project b then make you’re changes
2026-09-18 12:59:28
2
Teem :
Use version control
2026-09-21 19:06:23
1
Serious Boyfriend :
Toor. I learnt something while working on a project. Imagine both projects having Payment checkout. Create a service on the first one to handle the checkout. Then create a Config to handle the service. In the other project, just copy the service and the config easily.
2026-09-19 10:30:31
2
To see more videos from user @akineniwebdesign, please go to the Tikwm
homepage.
