The longer pieces. How developer careers actually work: being known, being trusted, and the parts nobody explains.
6 articles
You don't post on LinkedIn to become a content creator. You post so that when someone asks 'do you know a developer who can handle this?', somebody thinks of you. It's a long game, and it beats the resume line.
NDA, clearance, or a company that won't let you talk about the product? You don't need to. Every project is full of decisions that aren't the project, and how you made them is what a senior dev or hiring manager actually wants to see.
The most common thing developers tell me is they don't know what to post on LinkedIn. You fixed something this week, made a tradeoff, screwed something up. That's the post. Write five sentences and hit publish.
Developers are upset about the job market, but hiring managers are drowning in hundreds of AI-written resumes and would rather interview someone they already know. Become known before the job opens.
If an interview comes down to how many LeetCode problems you ground through beforehand, it's testing the wrong thing. I want to see how you tackle a problem, and the questions you ask are the answer.
Most developers define themselves by their tech stack, and that's incomplete. Six questions (what you build, who for, with what, what you're known for, your philosophy, where you're going) give you a position and a direction.