Roadmap and Architecture Design
E-mail me with any problem, big or small. I don’t have a problem with saying “I don’t know”. But I do have trouble resisting the urge to find the answer.
computer.linguist@gmail.com
Using existing, quality source code is always cost effective. If you are skeptical that code exists for your needs – what can you lose by sending me an e-mail? If I can’t improve upon your plan, I’ll tell you. I don’t charge unless I help.
If you are considering outsourcing a project, it is even more critical that you get a report to base your project requirements on. Many outsourced projects turn into nightmares, not due to lack of coder intelligence, but architectural experience and unclear communication. With a solid plan for your project, you are much better prepared to face the ordeal of using RentACoder, GetAFreeLancer, or any other outsourcing site.
Don’t reinvent the wheel. Send me an e-mail. And find out how little code you actually have to write to accomplish your goals.
And, best of all – the dogfood guarantee. If you run into trouble using a purchased design, I’ll support it at my normal hourly rate, no strings attached. I won’t suggest a plan I can’t code or troubleshoot.
I need to know
- What are your goals?
- What is your current plan?
- What is the state of the project now?
Once you have your goals set and ready to communicate themĀ - send me an e-mail at computer.linguist@gmail.com.
My reply
- A overview of what I can suggest (minus product/component names).
- A price quote and a payment link. I charge a flat $150 fee for all but the largest projects.
The report will include (depending upon project type)
- The simplest, most flexible architecture for your needs
- A sample roadmap for development
- A list and explanation of available frameworks, libraries, and components that will help minimize the amount of new code needed.
- Optimal tools for the project (such as development environments, version control systems, and unit testing)
- Best language(s) for the project. No language, tool, framework, library, or component is sutiable for every project.
- An explanation of the tradeoffs between the choices presented.
- Existing relevant or similar projects to draw from
- The licensing restrictions of the suggested components, if any.