After over a decade in the tech space, I'm finally doing what I've always said I would do: I'm writing about it.
This won't be just about the technical stuff, there'll be plenty of that. This will cover the real stuff. The human side of tech work. The contracts that seemed fine until they weren't. The tools that promised everything and delivered half. Clients and employers who taught me what professionalism should look like and the ones who taught me what it doesn't. Red flags I missed, and the ones I learned to spot.
Why Now?
Honestly, two reasons. There's a lot to talk about, which is funny, because I'm not someone who talks much. And second, I'm currently in a situation that made it very clear to me: if I don't share what I've learned, someone else is going to learn these lessons the hard way. That's a waste
What to expect
I'll be writing about tech tools and architecture decisions: what worked, what didn't and why. About working across borders and cultures in remote-first environments. About the human side of this industry: the contracts, clients, red flags and stuff that didn't make it into job descriptions. And when the time is right, there's a story I'm going to tell that I think a lot of people in this space need to hear.
If you've been in tech for a while and have stories and lessons you think will benefit others, do reach out. Who knows, we could collaborate. If you're early in your career and have questions about navigating this space, feel free to ask. Let's make this useful.
I'm making this public so I actually follow through. You know, accountability, right?
Let's see where this goes
Top comments (0)