10 ideas for your posts 💡
What to write when you have nothing to say.
We often stare at the blank page on LinkedIn and think: “I have nothing interesting to say. I just wrote code today.”
But staying silent is a missed opportunity. When you post, you aren’t just creating content; you are creating luck. You are telling the algorithm (and the people watching) that you are active, you are learning, and you are an expert in your field. This is how opportunities come to find you, instead of you chasing them.
I already talked about the importance of writing in a previous article where I explained why it matters.
Today, I want to help you with the what.
Here are 10 direct, practical ideas (with examples) you can use right now to fill that blank page.
1. Something new you learned
You solve problems every day. Did you discover a new library? Did you finally understand how a specific React hook works? Did you find a better way to write a SQL query?
Share it. You don’t need to write a huge tutorial.
The Format: “I was stuck on [Problem] for hours. I discovered [Solution]. Here is why it works better than what I was doing before.”
Why it works: It shows you are technically curious and constantly improving.
💡 Pro Tip: Don’t just share the solution. Share the pain you felt before finding it. People relate to the struggle.
2. A feature or project you launched
If you work in a product company or in consulting, you are building things. When a feature goes live or a project ends, talk about it.
Don’t just say “We launched.” Explain your specific contribution.
The Format: “We just shipped [Feature X]. My role was building the [Specific Part]. The biggest technical challenge was [Challenge], and we solved it by [Solution].”
Why it works: It proves you can deliver results in a real-world environment.
💡 Pro Tip: If you can, include a screenshot or a GIF of the feature in action. Visuals get much more engagement than text alone.
3. Your opinion on a current topic
The tech world moves fast. There is always a new version of a framework, a new AI tool, or a debate about remote work.
You don’t need to be a world-famous expert to have an opinion.
The Format: “I read about the new changes in Next.js. I really like feature A because it solves [Problem], but I’m not sure about feature B. Has anyone tried it in production yet?”
Why it works: It shows you stay up-to-date and it invites people to comment with their own views.
💡 Pro Tip: Keep it respectful. You can disagree with a trend without being toxic. Constructive criticism is a sign of seniority.
4. A productivity trick or tool
Developers love optimizing their workflow. If you use a specific VS Code extension, a terminal shortcut, or a time-management technique that saves you time, share it.
The Format: “I recently started using [Tool/Shortcut] and it saves me 10 minutes a day. It’s great for [Specific Task]. Highly recommend it.”
Why it works: It’s simple, helpful, and people often “save” these posts to reference them later, which boosts your reach significantly.
💡 Pro Tip: Ask your audience what they use. “What is the one VS Code extension you can’t live without?” is a guaranteed comment magnet.
5. A lesson on teamwork
Soft skills are just as important as code. Share something you observed about working in a team.
The Format: Share a code review process that works really well for your team, or how you handle meetings to keep them short. Or maybe give a shout-out to a colleague who helped you solve a bug.
Why it works: It shows you are a good team player who cares about the people, not just the computers. Recruiters love this.
💡 Pro Tip: Tag the colleagues you mention (if they are on LinkedIn). It spreads goodwill and expands the reach of your post to their network too.
6. Events and networking
If you go to a conference, a meetup, or even just a company team-building event, take a photo.
The Format: Post the photo and write 3 bullet points about what you learned or who you met. “Great time at [Event]. My biggest takeaway was [Insight]. Great to meet [Person]!”
Why it works: It shows you are active in the community and invested in your professional network.
💡 Pro Tip: Don’t just post a photo of the stage. Post a photo of you with people. It makes you look approachable and connected.
7. A mistake you made (and how you fixed it)
Nobody is perfect. Sharing a mistake makes you look confident and authentic.
The Format: “I broke production yesterday. Here is what happened, how we fixed it quickly, and the process we put in place to make sure it doesn’t happen again.”
Why it works: It shows maturity. Junior devs hide mistakes; senior devs learn from them publicly.
💡 Pro Tip: Focus 20% on the mistake and 80% on the fix and the lesson. You want to look like a problem solver, not a disaster.
8. Career growth and advice
You don’t need to be a CTO to give advice. You can give advice to the “you” of two years ago.
The Format: Share a tip on how to handle a job interview, how to negotiate a salary, or how to onboard in a new company. “I used to struggle with [Interview Question]. Here is how I answer it now.”
Why it works: It positions you as a mentor and someone who thinks about career strategy.
💡 Pro Tip: Be specific. General advice like “believe in yourself” is boring. Specific advice like “Always ask this question at the end of an interview” is valuable.
9. “Behind the scenes” of your company
People are curious about how other companies work. Without sharing confidential info, talk about your engineering culture.
The Format: Do you do pair programming? How do you handle technical debt? Do you have “hack days”? “At [Company], we do [Practice] every Friday. It really helps us to...”
Why it works: It makes your company look like a great place to work (your boss will like that) and shows you care about culture.
💡 Pro Tip: This is great content if you are looking to hire or grow your team. It attracts developers who like your culture.
10. A personal project or experiment
Are you building something on the weekend? Even if it’s just a “Hello World” in a new language like Rust or Go, share your progress.
The Format: Post a screenshot of the code or the running app. “Spending my Saturday playing with Rust. The compiler is strict, but I love the safety it provides.”
Why it works: It shows passion. It proves you code because you love it, not just because you are paid to do it.
💡 Pro Tip: “Build in public.” Don’t wait until it’s finished. Share the ugly “work in progress” shots. People love seeing things being built.
Start small
You don’t need to use all 10 ideas at once. That’s the fastest way to burn out.
Pick one from this list for your next post. Write 5-10 sentences. Add a photo or a link if you have one.
That’s it. You have a post. Do this once a week, and you’ll be miles ahead of the crowd.