Data all over the place? I plan, build and deploy platforms that bring it back under one roof.

Edinburgh UK
I'm currently offering vibe-friendly discovery packages from £300 half-day sessions for anyone with vibe-code, -ideas, -thoughts, -whatever who wants to take it up a notch and wrap a full, testable, scalable, deployable app around it. I mean let's face it, pretty much any simple idea is a handful of LLM prompts (and light expletives) away these days. But validating it - getting another human to add a layer of accountability, especially - that's something else. Like maybe you've put together a vibe coded prototype - dissecting it, you've probably got a mix of static content, dynamic views, some DB tables, some auth, and so on. What you don't have is a plan based around validated software engineering principles (and YES those still matter) - not just for the future scalability of your app but also for your Claude/Codex/Grok (if you insist) to build on. If you're vibe coding, you know very well how long and painful the road ahead looks with limited knowledge. I don't need to take you the whole way. Let's just get you swearing less at your computer. That's a good first step. DMs open.
1
7
1,063
This project's also fun for me because I'm using it as a way to challenge myself to build with AI without it having a hideous interface. And you can do so much more with it. Like contextually, how can you build more advanced UI that responds more intelligently to user input, based on e.g. selected mode, angle of view etc what does any given user need to see for any given action. I think this is a massively overlooked part of building with AI. They are atrocious at UI, and it's only adding to visual clutter and noise for people unfortunate enough to have to use the default stuff these things are building. So anyway, here's a little UI for my sunlight-hours visualiser, a way to easily edit a boundary fence - how to do that so it's not fiddly and so the user can very quickly grasp from current context how it works and how to use it.
1
167
I'm building out a tool right now for measuring sunlight hours, shadow impact for a property (useful for e.g. gardeners, people viewing homes to move) and I realised Opus 5.5 is REALLY good at trees.
1
7
211
"I one-shotted [GAME NAME HERE] in a weekend! Game dev is cooked" No it is not oh my goodness 1) Game studios are also going to be using these tools. You're competing with other people who understand their potential 2) If you can't see the absolute universe of complexity that's waiting for you beyond these interesting little tech demos you're producing, stop now
7
168
In a world where LLM coding was actually a game changer, users would notice. They'd say "wow, has anyone noticed how useful, reliable and fast things are these days? They'd aay it about websites, apps, windows, macOS... They do not. Ergo: the princess is in another castle.
I still can't get over the complete lack of impact agentic coding has had on software from a user's perspective. Our industry looks faintly ridiculous for waxing lyrical about the "agentic era" when it's had zero observable impact to the end user.
158
154
2,658
88,438
Robin retweeted
Oh come on. Quick look at colorshift (13x faster): HashMap in hot loop (unoptimized Rust vibeslop) is slower than indexed arrays (ASM). No shit. Numbers like 17x should raise eyebrows but reading the comments nobody is thinking anymore. This AI psychosis has fried people's brains
5
75
1,802
41,350
I still can't get over the complete lack of impact agentic coding has had on software from a user's perspective. Our industry looks faintly ridiculous for waxing lyrical about the "agentic era" when it's had zero observable impact to the end user.
313
129
3,235
318,153
A thought: The prediction is that everyone will have personalised software but what happens when there's enough personalised software to cover the majority of niches and AI just recommends what someone else has already built instead of doing it for you? Maybe there could be some revolutionary licensing model where the Source is Open and then the AI could get you to suggest contributions to it.
2
1
137
Robin retweeted
the moat is literally just caring about your work and being proud of your output and holy shit it does not seem to apply to 99% of people
110
516
7,508
358,426
Now is the time for calm minds who understand AI and are immune to the hype
I know this isn't a new observation but... The actual work of managing a software engineering team and leading a software development project in the age of AI is WILD. - You can prototype anything in minutes - The product, codebase, and system architecture are changing constantly and can look completely different in a matter of hours - No one reads the code or reviews PRs or even really understands how the system works - Agents are autonomously merging and deploying at all hours of the day - There's slop everywhere - not just in the codebase, but also in DMs, tickets, Figma, docs, etc. - Paradoxically, your backlog is somehow always getting longer despite code being "instantaneous and free" - Token spend is completely out of control - New technologies drop weekly that completely change everyone's assumptions and require you to re-think your architecture from scratch - Hackers have superweapons I could go on... WHAT A RIDE.
2
3
369
Ok, so Twitter has now become more unbearable than ever (quite an achievement) especially r.e. "software development is dead lol", and I think I'm going to stop engaging with it entirely. Summarising my thoughts on it, then I'm done - if you've got an opinion on it and are dunking on the profession for clout: 1) Shut the fk up, no one who matters cares 2) If you genuinely want to talk about it and engage in interesting discourse about it (because it IS fascinating, it's a massive paradigm shift and no-one really knows where this is going) seriously shoot me a DM or an email or whatever and I'd love to share some opinions But yeah this is not the subject to be seeking engagement bait on, it makes you look like a dumbass
117
Is all this “software is dead” “UX is dead” engagement noise considering that people won’t want their agents to do things for them. They’ll want to do things *with* them?
2
127
More backrooms dev. I chose this as a game project because I wanted a world I could sink a lot of time and effort into instead of jumping between ideas. Rule: if I have a new idea about something I (and Claude) want to build, it has to be embeddable within this world. From above, I want this environment to feel real and tangible. But as an overseer of a world, what do you see? I've build a "cutout" system so that all walls, when viewed from above and when "cutaway" (when player is behind them) show off their internal structure. Here, the "abandoned yellow hallways" architecture displays wooden joists and supports behind the plasterboard. Swapping to first-person view you can then see what that looks like up close. How does that play out as actual game mechanics? idk haha, I'm just vibing this right now. Does that sound like something conducive to a playable experience? No. It is not. Plan is eventually to make this more of a walking simulator, a maze to get lost in, an excuse to explore and examine.
1
126
The question isn't whether coding will disappear (yes, sadly) it's whether complexity will vanish too (no lol that's just getting worse)
109
Everyone's out there apparently one-shotting colourful interactive playgrounds with Claude Me: "more existential dread please claude. make the wallpaper greasier" I'm wandering the infinite isometric backrooms again today.
106
It really feels like none of these models are being tested against real, messy client work, stuff like that. Legacy codebases. Like yeah sure, vibe code a new maths solution or a Minecraft clone in a weekend. Run them against benchmarks full of neat little puzzles. But dealing with messy hands-in-the-mud codebase problems? AI slips up constantly.
2
4
143
The solution is, of course, to assume that all clients and normies are wrong and you can live the rest of your life building social media schedulers for everyone on Twitter
1
1
36
I'm considering branching out and focusing more on automation-infrastructure services in terms of what I offer professionaly vs traditional software development. Then I see services like Meta's Muse offering to provide on-demand integrations between systems, so is there much scope for this? I mean they've got all bases covered, from "help me read email plz" or "want book flights" to "help me read more emails please" So I think I'll be fine. Anyway. DMs open if you have a business-facing automation problem that's more complex than "help plz read emails"
1
97
Truths
Replying to @v0xium
The irony here is that nothing has changed. Management is still asking why everything takes so long. The reason that things take a long time has never changed, AI or not. Things take a long time because things are complicated. And if you rush head long into complicated problems with poorly thought through solutions, they will take longer and longer and longer to implement. All the old principles still apply. All the same consequences still accrue. The bigger the mess, the longer the time.
123
There's a major disconnect in the opinions vibe coders have about traditional software dev, and I don't think it's reflected in the discourse. It's easier than ever to spin up e.g. a Mario Kart clone in a weekend. But as soon as you want to try doing anything novel with that, as the complexity grows, so does the time taken to deliver changes. Context grows, requirements become more complex, smaller and smaller issues take more time to explore and diagnose. Even the super-smartest LLMs can churn for minutes or more on each iteration. Delivering what you (the human) actually wants remains, still, very challenging. So we're left in this mad scenario where two groups, equally capable of building "working software" in their minds are coming up with estimates anywhere between 2 hours and 2 months and everyone is correct in their own respective ways.
2
1
128
Saw someone saying they'd delivered an Elden Ring clone in a weekend and like no you bloody haven't mate, you've delivered "Man swings sword furiously in a three.js castle" "It's got 50 bosses" and they'll all be some variation of interactive polygon soup.
1
45
Also a significant amount of e.g. client work is getting the details right *because people want the details to be right* Of course you're going to be able to vibe code something in a day - because no-one actually cares about it. And ultimately if you're wanting to change the whole paradigm of software engineering you're going to have to change the fact that people sweat the small stuff. Whether you like that or not.
14