Every tech career is really two journeys happening at once !
The first is technical, the bugs that eat your afternoon, the systems that fail in ways no documentation predicted, the new tools you keep meaning to try. The second is professional: the skills you choose to build, the decisions that shape your path, the lessons nobody puts in a job description.
Most blogs pick one, This one covers both, because in practice, they were never separate. The way you troubleshoot a problem says a lot about how you'll grow, and the way you grow changes what problems you get to solve.
So here's what you'll find on Troubleshoot & Climb:
- Technical deep-dives. Real troubleshooting stories, told honestly, what broke, what I tried, what actually worked, and what I'd do differently. Not polished tutorials that pretend everything worked on the first attempt.
- Career moves. Practical lessons about growing in tech, the decisions, the skills, and the moments that turn out to matter more than you expected.
- New PoCs to try. When I experiment with a new tool or technology, I'll write up the proof-of-concept so you can try it yourself, setup, gotchas, and whether it's worth your time.
My promise is simple everything here comes from real experience. If a post doesn't help you fix something, learn something, or decide something, it doesn't get published.
The first deep-dive is already in the works. If any of this sounds useful, subscribe or check back soon, and if there's a topic you'd like covered, the Contact page is open.
Let's climb...
— Razan
