May 17, 2023
This is an idea for JumboCode (What is JumboCode?) that is not a particularly good idea, and JumboCode should probably not do it, but I thought itâs interesting nonetheless.
JumboCode builds these free apps for non-profits each school year, but then the club doesnât maintain them. If clients want improvements or bug-fixes, we donât do them. It feels like there might be an idea here, but Iâll explain at the end why itâs probably not worth exploring right now.
If you want the organization to keep using the app you built for them, maintenance is super important.
As soon as bugs start cropping up, or they notice features that are missing, it feels like a ticking time bomb: why keep using this software that wonât get improved?
My âJumboCode+â idea is that we create an organization to do the maintenance, hiring already-skilled developers, but we charge the clients for our work.
These developers will be experienced in web development; most JumboCode developers are learning web development for the semi-first time (which is fantastic!), but these developers will need to be more experienced since:
The money that JumboCode+ earns could be split between the developers and JumboCode, as a way of funding the club. (The club is also providing the service of finding clients, which justifies its cut.)
And more club funding is always great!
Personally, I see JumboCodeâs mission as two things:
Money is nice, but this JumboCode+ idea doesnât contribute to either of these. Itâs something that would take a large amount of effort, and it seems misguided to expend effort here rather than furthering the core mission.