3 ms·
I built my own framework that I've used for a dozen or so apps since 2005. It started in SQL/PHP/HTML/JS/Air and slowly migrated project by project, class by cl
by noduerme 5y ago
I built my own framework that I've used for a dozen or so apps since 2005. It started in SQL/PHP/HTML/JS/Air and slowly migrated project by project, class by class, to SQL/Node/Typescript. Some of the utility classes are still almost exact transcriptions. Every project introduces new challenges and use cases the framework wasn't designed for. I try to add the ones to the core that I think will be helpful down the road, and keep a repository of other elements I can look up just in case.
Whenever I take a project, I often find myself building in "what if" scenarios - e.g. what if the client asks for some further functionality down the road. I view my job as a programmer as trying to think of these things the client might not yet have conceived of, and leaving room for them in future iterations. I'll bring them up to the client and if they don't need them, I'll often write them in anyway. From the POV of putting out a concise, open-source package, I wouldn't do that. There's no need to expose half-baked functionality. But for myself, for my own work, I'll at least make a code stub and some notes every time I think of one of those things where an extra argument could be added, or extra functionality could branch off. At least half the time, clients come back years later asking for some functionality I stubbed, and I at least know where to look for it. If it seems useful enough, I merge it into the core.
So I don't think it's a bad impulse to try to think of every edge case. That's a great impulse. You just don't have to write the code for each one right now unless you think they'll impact daily operations. But if you were to lose the urge to do it, I'd argue you'd be a lesser programmer.
- midrus 5y agoI'm sorry for anyone that has ended up having to maintain any project made with any of these custom frameworks.
- noduerme 5y agoI certainly understand that from a team / larger organization perspective. But since I'm the de facto maintainer of these apps for the rest of my life, it's quite nice to have written everything myself and know the strengths and weaknesses intimately, from the UI to the database. And it wouldn't be so bad for someone to take over. I maintain contingency "if I get hit by a bus" documents for each active app, accessible to the client and containing keys, links to source code, and helpful pointers. The framework has evolved to be readable, relatively simple in practice, and well documented. For what I charge, it's been a good deal for both me and the clients - mostly smaller businesses with custom needs that can be iterated over time. When Salesforce reps come knocking, trying to scare them about the dangers of technical debt or future migration costs for custom platforms, it's pretty much like, "we'll switch eventually if we have to, but why would we pay you guys three times more to migrate and manage it, when we can already request new features whenever we want?" The truth is, no one will ever have to maintain them, because when I'm gone they'll just rebuild from scratch; they've already gotten their money's worth over the years of operation.