| I don’t charge my clients. I’m retired and do this for the fun and to keep my brain active, so separate licences isn’t an option. There are definitely opportunities where I could merge files. My flight log v1 is ‘finished’ so I use that file for managing bugs. My v2 is nearing the end of development so has a couple of features I need to finish. My v3 is in requirements gathering so is pretty dynamic and gets exposed regularly to the client I am developing it with. I could put these in a single file but that risks exposing my bug list and my development list to a client who doesn’t need to know. Especially if I decide to move some of the functionality from v2 to v3. It does not pay to set expectations that you cannot achieve. While developing v2 I also developed an XCFramework for a PDF generator. That’s a generic library that is not specific to the flight log and that will be used in other apps. I put that into a separate file so I could focus on it without the distraction of the outstanding v2 and v3 work. While developing that, I also decided there were activities that I only did occasionally and that took too long. I wanted a tool for the Mac that could help me with these things, so I put that into a separate file because it’s an internal tool and for the Mac rather than a client tool for iOS. Having them in separate files allows me to narrow my focus to the task in hand. When you’re juggling a number of projects, focus is your best friend. Yes, I could put all of these into one file and have the top most level be the logical separation, but that makes it too easy to update the wrong project and to expose information I do not want to share with a client. It is absolutely vital that client facing information is kept separate from anything internal. The ‘one file’ concept may work for you and others. It doesn’t work for me. Extrapolating, I only need one Word document. Word supports sections in a document so every separate document could be a section in one file. I can edit one section at a time and can print a page range, so why would I want to create separate documents? It’s even better to have one document because I could ensure the same styles for everything I produce. Same argument for Excel as it has thousands of cells and multiple tabs. I could have one tab per project. Why would I want separate files. Apart from organisation, of course. Mind you, if I only had one Word and one Excel document their organisation would be easy. Pushing to extremes, I could have one SQL database and use schemas to separate dev, Q&A, uat and prod tables. It’s possible. What could possibly go wrong? Maybe I’m not using MLO correctly. I’m using it as a brain storming tool to flesh out a new release of a product or web site and then as a project management tool to deliver the new release. I’ve always designed and developed a new release starting with a new project. No professional project manager would go with a single project file for all releases, past and future. I could bang on for hours on the advantage of separate files. I suspect every argument I make could be refuted in favour of a single file. My past experience had led to separate files. Yours has led to a single file. That’s the nice thing about being human; we’re not all the same. Maybe you’re right. Maybe I should look for another tool. MLO have given me 30 files for now and that’s plenty for what I am doing. I suppose I could go back to Dynalist which gives me unlimited files for free. I prefer MLO though. I could go back to CarbonFin Outliner, but that’s iPad only and I had to write my own Windows application to read the files (I’m not yet competent enough to write a Mac client - but I’m getting there). I prefer MLO though as I can run Windows, iOS and Mac. I’ve written software in the past where I had a clear definition of how it was to be used and what could be achieved with it. Then customers got hold of it and did amazing things I had never contemplated. That’s the joy of writing software. Quite often I thought to myself that users were using it wrong… that’s not what I intended. But the fact that they could use it how they wanted to use it and not how I prescribed it should be used was so satisfying. MLO have done the same. They let me use it how I want to use it and, when I came up against an arbitrary limitation, they fixed the limit. All credit to them.
-- Steve Barnett On 5 Aug 2023, at 23:23, imajeff <[email protected]> wrote:
You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/F0C1BEFA-2A14-49D5-9D42-C13FCA4B09D9%40sabarnett.co.uk. |
- [MLO] Cloud sync limits Steven Barnett
- [MLO] Re: Cloud sync limits [email protected]
- [MLO] Re: Cloud sync limits Steven Barnett
- [MLO] Re: Cloud sync limits Andrey Tkachuk (MLO)
- Re: [MLO] Re: Cloud sync limits Steven Barnett
- Re: [MLO] Re: Cloud sync limits imajeff
- Re: [MLO] Re: Cloud sync li... Dwight
- Re: [MLO] Re: Cloud sync li... Steven Barnett
- Re: [MLO] Re: Cloud syn... Dwight
- Re: [MLO] Re: Cloud syn... Steve Barnett
- Re: [MLO] Re: Cloud syn... A. W.
- RE: [MLO] Re: Cloud syn... Steven Barnett
- Re: [MLO] Re: Cloud syn... imajeff
- Re: [MLO] Re: Cloud syn... imajeff
