This blog has been abandoned for a while. And even though every week I come up with a thousand new ideas to get it going again (from rebranding the whole “Aletec” concept, to moving it over to Medium or Substack, to handing it off to an automated agent I could just dump my thoughts into), I’ve decided that, for now, I’m going to use it as a repository for the things I’ve come across and found interesting.
Which is, I think, the pure essence of a topic blog. Those 2012 Blogspot pages where everyone shared their ideas with the 10 people who read them. Yes: the good old definition of a blog.
Today, to bring this back to life a little, I want to share two very interesting videos that stirred up a few concepts in my head while I was watching them.
Ecosystems, culture and architecture#
Software engineering at the tipping point breaks down the concept of ecosystems, and how a company’s internal culture massively shapes the architecture of its applications. Plenty to think about, honestly.
What does your company’s ecosystem look like? I don’t think that’s a simple question to answer, and I think it’s well worth sitting with it for a bit, along with whether we’re ready to face a world of more code, more vulnerable surface, far more context for agents, bigger binaries, faster pace… and brand-new bottlenecks.
I’m genuinely curious to see what the industry looks like in 5 or 10 years. And yes, in a way, I’m trusting that there will still be an industry in 5 or 10 years.
Raising tomorrow’s seniors properly#
In Should You Still Become a Software Engineer in 2026?, a GitHub (Microsoft) VP talks, in his own way, about how important it is to raise tomorrow’s seniors properly. About staying curious, about learning to write good prompts, about understanding the difference in complexity between saying “build me a Minecraft clone” and saying:
I need you to build a 3D video game based on cubes/voxels, where the main character has an inventory and can use the materials they collect to craft new things. For the first iteration we need procedural terrain generation, at least 3 ground materials, and character movement…
Understanding what we’re asking for and iterating on it is nowhere near the same thing as asking for a copy of something that already exists. One implies comprehension, depth, and a real ability to keep iterating on what we’re building. The other can look spectacular in a way, but it exposes a lot of limitations.
And beyond that: how important it is to learn to explain things, to communicate, to work in a team. And above all, to be a Software Engineer, not just a programmer.
Until the next one#
I hope to share more things here, and maybe even get around to making videos where I go deeper into what I’m thinking. But until then: thanks for reading, I hope everything goes great for you, and see you in the next post for a lot more tech content.