The days roll on.
Today was a day of calls.
Today taught me one thing and that was that the act of posting everyday actually has better consequences than just post engagements on LinkedIn.
I was doing a few interviews today – graduates from TechEducators software development bootcamp … and a few of them had read through my posts on this site and LinkedIn. It was interesting to hear that they had done that, since I pretty much just write for myself at the moment.
But I realise that the story that you make when starting something is actually important because, if they choose to, people can gain context on what you are doing. It’s not just about flawlessly sanitized marketing … founders can benefit from just being genuine and not being afraid of not being seen as being perfect. You just have to not care about that aspect.
Anyway, it’s been challenging to do a post on an almost daily basis, but along the way you realise that it’s having unintended positive consequences. Which is great.
Improvements to my story marketing
I’m going to need to scale up with a bit of automation into other social networks; and do more videos. I want to focus first on the core original content that I create; and then look at what I can use AI to supplement that. But I need to scale into video content focused more on AI value, and also founders story.
IT Projects
I’m working on another project which will remain nameless. It’s a tricky one since it’s a great project with great potential; but it suffers from the very common IT project pitfalls – most of which I have fallen into in my career:
- At the beginning of the project, it’s OK to do some R&D prototyping to see what’s possible; and it’s OK to use agile … but sometimes you do actually need to plan through what the end product MUST do. When you are replacing a system or starting a non-trivial one from scratch … you can’t just wing it. You must be specific about what you’re building and more importantly HOW you are going to get there. Make the decisions AHEAD of time. This is a massive skill and vibe coding people will never do this… we will see how it turns out over the long term.
- During the project you need to communicate; as soon as that starts breaking down, things slow down. And the communication needs to be kept in places other than emails or messaging. Find what works for your team.
- When things start getting a bit tricky, bring in specialist help. I can’t emphasise this enough. Whether that is a talented project manager developer, or a developer with better skills at your tech stack… don’t hesitate. You need someone sooner than you think.
- DOCUMENT! When projects are several years down the road; onboarding new developers is slow since they have to figure it all out from scratch.
Leave a Reply