Alex is very much active on both tracks: 20 commits landed on the Mnemos repo across Sat 29 - Sun 30 Aug (FormField/FormCollectionField, DI registration, ViewModel migrations, then a run of renames and cleanups), and he is mid-conversation in the 1:1 today about how to decide when to take on technical debt. The substantive thread since 11 Aug is scope: he raised that his project isn't finishable in four months and asked to restructure around job-application guidance plus targeted proofs-of-concept, and coaches pushed back on 19 Aug that the time pressure comes from over-engineering rather than problem complexity. Two call attempts have now slipped - his meeting on Thu 27 Aug, then Florian's kids on Fri 28 Aug - and the open question he asked today (heuristics for which corners to cut) is still unanswered. Trello is effectively dark: current exercise unknown and the last time entry is 168 days old, so his own project is the only visible unit of work.
Edit freely, then copy. pokAI never sends anything — you paste it into WhatsApp yourself.
He asked directly for heuristics at 13:00 today and referenced Alexandros' compromise point. Answering with a usable rule, then aiming it at the actual open decision (interface per use case), engages his question seriously while pulling it toward the over-engineering feedback from 19 Aug.
Grounded in the 29-30 Aug commits and in the missed sessions on 27 and 28 Aug. Puts the scheduling burden on him with a concrete ask rather than another open-ended offer.
His own stated priority from 11 Aug never turned into visible activity, and all recent evidence (commits and 1:1 topics) is project-internal. Asking whether it's deliberate respects his judgement instead of assuming drift, and reopens the restructuring conversation he requested.
What the data does not answer.
Gathered 1 h ago, looking back to 10 Aug 2026.
CLIENT Alex de Kruijff Hi Florian, I have serious concerns about the feasibility of building my project within the remaining four months. It simply requires too much time to complete from scratch. It could easily take a year or longer. My absolute top priority for our remaining time is the job application guidance. Next to that, I want to tackle the expected technical hurdles, like server deployment, payments, and app store releases, through smaller, targeted proof-of-concepts instead of one massive application. I would like to schedule a call to discuss how we can restructure the remaining four months around this. Please let me know when you are available. Alex
CLIENT Alex de Kruijff We will talk after your vacation. Have a good one!
CLIENT Alex de Kruijff Let's end the discussion here and just agree to disagree.
Florian Rakete We can of course disagree - no problem with that. The important thing is that you get to learn different perspectives here. ..which pretty much falls in line with this message. In my opinion, you run out of time-scope not because of problem complexity, but because of over-engineering. And i truly understand your point / passion for intricate and elegant code, the love for interesting engineering challenges. But the harsh truth is: Good engineers get things done by weighing effort against result and finding the optimal balance. In an enterprise situation
We can of course disagree - no problem with that. The important thing is that you get to learn different perspectives here.
CLIENT Alex de Kruijff I'm currently held up in a meeting. I will join as soon as I can. If it's too late, I will try again next week.
CLIENT Alex de Kruijff I was thinking of debts as not writing documentation or tests. Hacking code because time to market vs writing maintainable code.
CLIENT Alex de Kruijff At the core of my question is: how do you make sure you aren't on the red line?
Florian Rakete Documentation imo has become much less of a hassle with current LLMs - I hand of a lot of the workload there - and updating adding missing docs is now a very light task. tests well - i'm a fan of big-unit unti tests generally. testing every tiny function brings rigidity that can slow thigns down a lot. on big teams it can be helpful, in getting an mvp off the ground the rigidity is not great in my opinon.
No time tracking inside the window. Last entry 168 days ago.