So late last night, I got an update from Wasmer, that they will no longer be continuing with my application. A bit sad, ngl, especially given friday wasnt by choice that I had to cancel the interview. But all the best to them.
So what now? I've been applying to more jobs and prepping my pitch deck, so I can look at funding UnitBuilds CC and V.E.L.O.C.I.T.Y. IDE! Which honestly would be amazing!
Right now, I'm taking a break though. Since I left my job, I've been non-stop busy and couldnt rest. So I decided I need a hiatus, rest and relax, then get back at it in a week or 2. In the meantime, I'm going to get back to my roots and relax, play some games (Tainted Grail has been REALLY fun!), went to the beach today, gunna do a BBQ now and go to bed, without the sound of 2 laptops and 2 computers running in the background.
Honestly, not very excited taking a break, but I think that's all the more reason to take 1. I wont stop developing during this time, infact, I think I'll be developing even more, but on the things that matter to me. IDE has gotten to a pretty solid place now, so it's minor refinements and testing. I DEFINITELY need to update my website (yeah, it's bad). Probably should release the health and fitness app, then beyond that, I'm not sure. Maybe refine pitch deck, set up cloud compute and model routing for the IDE, etc. That way it can live up to the dream I envisioned: "A lightweight IDE, that scales across all your available computers and if it has to, cloud". I kinda wanna refresh UnitBuilds itself (the original foundry) and open it up, I mean I have token plans to cover it, might as well open it up so people can test it.
Overall, I think I've gone too deep down the rabbit hole and I need some self-reflection time. Maybe finally read the Iliad and disconnect for a bit. But that's not quite me, I like software development way too much to quit cold turkey.
On other fronts, Doccit is doing well, I added regional support for practically most of the world, I wanna expand on it though. How many of you track your time and need time tracking apps like clockify to log your time. Imagine of the ide integrated with Doccit and automatically logged what you're busy with and where you spent that time... Optionally, with agent time tracking (not for billing, for production oversight), to see how much time the AI is doing the work and you're actually free to do whatever you like (lets face it, most of us either browse, or work on something else if we're invested).
So to finish up on this scatter brained spill of my mind. I have a question... If your IDE could do 1 thing, 1 magic thing, no matter how insane, what would it be? Genuinely, what is the thing you'd want most?
I had a few ideas, like a 'bottleneck detector' that highlights high traffic code that could be improved. Or a 'get it done' mode, where an AI team fully takes the product from 0 to 1, including comprehensive testing (not what passes for it by today's AI standards... Actual 24h+ usage to test it in real-world settings). Maybe a 'test suite' criteria checklist, where you state what you want tested and and what part of development, like E2E testing, integration testing and manual site traversal testing. I mean the IDE has full windows automation, so it could theoretically even use AutoCAD for you, if the model was smart enough to know what it's making. Or the core concept that UnitBuilds was founded on, 'prompt to binary', a true E2E production lifecycle in a single click, where your idea becomes a reality, no matter how many iterations it needs to go through to thoroughly complete and test it. Though as I experienced with the original foundry, sometimes, we're just a bit to vague on what we want and that leads to over or under engineering.
Top comments (2)
Sorry about the Wasmer outcome, a rejection after a forced reschedule stings more than a normal no. Taking a real break before the next round is a smart call, tired pitch decks and tired interviews both show. One thing that helps a lot when you come back: keep a short list of the questions that tripped you up and turn each into a small public writeup or demo in your IDE. When you restart, are you leaning toward funding UnitBuilds first or landing a role to give it runway?
iin1006h00
Personally, I'm leaning more towards funding UnitBuilds, I honestly dont like working for a company, the 8-5 is stupid, given that I'm most productive 4-11pm, so it's wake up early (I hate mornings) only to get most of the work done in the last hour of workday? So I'm mostly gunning for funding, unless a role is really attractive... Then I might consider working a day-job and keeping UnitBuilds as a side-project. But I mean most people who develop their own IDE start it as a company, mine is a fair bit more advanced than your basic Zed IDE, so probably should try focusing and getting it accelerated?