Sponsored LinkedIn post
A dedicated post to introduce your brand to my audience.
Full Stack Engineer @ Skedda
Companies pay Pavle to write a post about their product on LinkedIn or X.
This page is where they book it. Below: Pavle's audience, recent posts and price. Naano, the platform behind this page, handles the brief, your approval of the post and the payment.
€188per X post, fixed price
or 3 posts for €375 · You approve the post before it goes live
1 collaboration on Naano, delivered on time
Looking for Pavle? View LinkedIn profileView X profileA creator yourself? Create your own page
Clear, practical insights for modern developers | Full-Stack software engineer
Hello there 👋 A few years into my software development career, I realized something surprising: you can write code every day and still feel like you’re not growing. Even with experience across .NET, mobile, and full-stack roles, I kept running into the same internal wall. I felt like an imposter - someone who should “already know more.” No matter how many projects I delivered, that voice kept telling me everyone else was ahead. It held me back from opportunities, from sharing what I knew, and from believing I belonged in this industry. Everything changed when I finally made a decision: Stop hiding. Start learning in public. I started posting on LinkedIn - not because I felt like an expert, but because I wanted to grow. Writing daily forced me to stay curious, up-to-date, and intentional about my learning. And slowly, something unexpected happened: the imposter syndrome got quieter. My posts helped people. I realized that growth isn’t about knowing everything - it’s about showing up consistently. Today, my mission is simple: Help developers stay current, grow with confidence, and realize they’re more capable than they think. Let's connect!
My most engaged audience
48% Senior IC · 85% Engineering / Data
From 483 people who reacted to or commented on my posts
LinkedIn export · Jul 28, 2026 – Oct 25, 2026 · Provided by the creator, not independently verified by Naano
X
Public X data · Captured Oct 27, 2026
Don't make you queries work more then they should. Here are 5 EF Core features that will make them more effectively 👇 ➡️Projection with Select ➡️ AsNoTracking ➡️ Filtered include ➡️ AsSplitQuery ➡️ Keyset pagination You don’t need to apply all five to every query. Choose the ones that fit the endpoint, inspect the generated SQL, and measure with realistic data. 📰 Subscribe to my newsletter at https://pavle.codes
What’s one of the most important things to get right in Vertical Slice Architecture without breaking it over time? Knowing how to organize your slices. A slice should represent one use case and keep everything required for that use case close together. That usually means things like: - endpoint and contracts - validation and authorization - handler / use-case logic - data access or integrations - tests and observability The important part is not that every slice must contain all of these. I wrote a complete guide here: https://lnkd.in/eW9AyYEV _______________________ 📰 Subscribe to my newsletter at https://pavle.codes
The only thing worse than a 90-minute debate on should we use a repository pattern? Having to write the summary for the rest of the team afterward. You absorb a massive amount of technical context during a deep-dive sync, but translating those raw details into a clean update feels like doing the work twice. Lately, I’ve been using Granola to handle this. Here is my 5 tips to make your notes meaningful: 1. Jot down the "Why", let Granola write the "What": Type only your core architectural decisions and let Granola automatically build the full context around your shorthand. 2. Seed your notes with structural tags: Drop quick tags like #content-idea during the call so you can easily pull insights for your technical newsletter later. 3. Lean on /WhatDidIMiss during complex pivots: Use this command to instantly catch up when you lose the thread during dense debates over API vs. SDK implementations. 4. Route Markdown directly into your knowledge vault: Push Granola's clean Markdown directly into Capacities so your meeting takeaways immediately connect to your active projects. 5. Keep the noise private, share only the signal: Share the concise AI summary with your team while keeping the messy, verbatim transcript completely locked down for your own reference. It’s the best way to keep everyone in the loop without buying extra seats or risking the exposure of sensitive discussions. (🔗 Link in the first comment 👇) Thanks to Granola for sponsoring this post!
Choose a format for your next LinkedIn collaboration.
A dedicated post to introduce your brand to my audience.
A series of posts to build visibility over time.
A series of posts to build visibility over time.
Choose a format for your next X collaboration.
A dedicated post to introduce your brand to my audience.
A series of posts to build visibility over time.
A series of posts to build visibility over time.
Your collaboration, managed on Naano
How does this price compare? B2B creator rates 2026
Based on 483 people who reacted to or commented on my posts. Percentages use the profiles that could be classified.
Based on 483 people who reacted to or commented on my posts. Percentages use the profiles that could be classified.
Based on 483 people who reacted to or commented on my posts. Percentages use the profiles that could be classified.
Based on 483 people who reacted to or commented on my posts. Percentages use the profiles that could be classified.
X
Attackers are using AI to move faster, which means our security tooling needs to keep up. CodeRabbit just launched CodeRabbit Secure to help you spot and fix security flaws right in your workflow before anyone can exploit them. Try it out now! https://t.co/NPOP8RLMK2
I’ve set up vertical slice architecture in 5+ greenfield projects. The biggest mistake I see? Treating a slice as just an endpoint + handler. Here’s what each slice should actually contain: - Database: Underlying database of choice - Persistence: Getting data in and out. Mostly EF Core logic or Dapper - Business rules and domain models: Core entities and invariants - Slice logic: All the necessary logic, validation and mapping required for single feature - Handlers: Often driven by CQRS patterns. - External integrations: Outside services specific to particular feature - UI: Entry point of the feature The biggest advantage? High cohesion and low coupling. In my opinion, feature organization is the future of software development. Here is how you can organize them: https://t.co/wEro52w7JP
This book helped me stay ahead of 90% of software engineers. Even before AI became the next big thing… Here is what I learned: 1️⃣Consistency: Ensure your environments are identical for predictable, reliable builds. This resolves dependency conflicts and the classic “it works on my machine” issue. 2️⃣Run anywhere: App can be built once and run anywhere, offering genuine cross-platform support. 3️⃣Resource efficiency: Containers start up in seconds, whereas traditional VMs are heavyweight. Additionally, multiple containers can share a single host kernel. 4️⃣Deployment and scaling: Deploying and scaling applications and microservices is as easy as executing a simple command. 5️⃣Faster development cycle: Docker speeds up CI/CD pipelines by providing faster feedback, rapid testing, and an effortless flow from code to production. 6️⃣Isolation and security: The isolation of an app improves the security of a system. Hope this helps! Subscribe to my newsletter: https://t.co/fvaagl7TJ2
You don’t want to become the engineer who ships 100% AI slop. Learn to question the code as quickly as you generate it. You still need to spot the query that slows down under load. The abstraction that hides unnecessary complexity. The test that passes without checking the requirement. Here’s where I’d invest my time: https://t.co/P4wRcJgtUs AI can help you move faster. Your engineering judgment determines where you end up.
If you want to grow as a software engineer in 2026… …these are the people to follow: 1. @mjovanovictech 2. @AntonMartyniuk 3. @TheCodeMan__ 4. @milan_milanovic 5. @kanaiyakatarmal 6. @dmokafa 7. @johncrickett 8. @DevLeaderCa 9. @NikkiSiapno 10. @systemdesignone 11. @pavle_dav 👉 Join to stay ahead with the latest .NET features: ↳ https://t.co/w6SKRai3Kn
I also have custom bundles to offer on https://pavle.codes/sponorships
Storefront by Naano · Create yours
Pavle Davitkovic is a B2B LinkedIn creator based in the United Kingdom with 76,756 followers, posting about Software, Productivity, and Developer Tools. On Naano, one sponsored LinkedIn post by Pavle Davitkovic costs €875, a fixed price per post. A sponsored X post costs €188.
The Naano team casts the creators, writes the briefs, reviews every draft with you and reports results per creator. You approve the shortlist and every draft.