I hadn’t expected to need to think about a fundamental business decision within hours of day one, but that’s the way things go.
My newly appointed office, based out of the local Wetherspoons, at £1.80 for unlimited hot drinks, is a good place to start the day when you don’t have an office. 🙂
Anyway, last three hours has been a solid meeting with someone I very much respect. It very much impacts what I am doing, and a high level analysis is:
- There is a prebuilt codebase available to me, that isn’t too far away from being a ready product in the AI sector.
- I can form a company with this person, and build that company beginning with this product.
The challenges are:
- The tech stack is something I am not 100% familiar with. I was very, very much wanting to go with Laravel + React/Vue + Python + Flutter. This is sort of similar but based on the https://www.graphile.org/news/graphile-starter/ start kit. Most notably I wanted to use Laravel for the backend ‘brain’ but this would negate that.
- I have been trying for a few weeks on and off, to get this working locally. We got it working on a Linux box last night, but to no avail on my MBP. So I haven’t really had the opportunity to really get to grips with it. This is the big blocker.
The opportunities are:
- The person in question is talented and experienced and would be a huge, huge force in going forward. He is, subject to caveats, happy to let me run with it as CEO.
- Of what I know of it, the system has working parts that are very much part of my roadmap.
For the moment that’s all I am going to write on the subject. I’m going to get on with other things today, and sleep on it. And figure out a way to get the product working locally where I can use it.
Back to Laravel
Laravel JetStream
The main problem I have is that the rest of the frontend I want to use is built with React components. I have way more access to React frontend components than Vue components. I can work with both, but since I already have some sort of dashboard ready to go built with React/Next … I have to think this through.
I’m choosing to build first with JetStream because that will implement the Laravel Fortify things that I need. I don’t want to put time into custom implementing my own auth structure right now, and JetStream will be a good starting point. I will be able to port things further down the line. Also Laravel Spark works well with JetStream so that’s a bonus.
Laravel Spark is really important because that’s how I envisage getting paid eventually, through a subscription access to the system.
I’ve got somewhere to be tonight, and didn’t expect a couple hour meeting (which is totally great), but still aiming to get something small up and running today as a small milestone.
Onwards.
Leave a Reply