Software Developer @Ingsoftware

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!

You hit the parameter limit because of UI filtering 🔴

Don’t worry - here is a 100% working solution 👇

In almost every case, you will do filtering with the Where and Contains LINQ methods.

And this is completely fine… until you hit the parameter limit.

So, what is the parameter limit?

What is the solution to this problem?

Is it optimized?

The answers to these questions are here:
↳ https://lnkd.in/d9nPSjhz


👉 Join to stay ahead with the latest .NET features:
↳ https://www.pavle.codes/

——

♻️ Repost to help others learn about optimized filtering in .NET!

➕ Follow me(Pavle Davitković) for more posts like this.

Pavle Davitković

I am a .NET software developer with a passion for creating efficient solutions. 

I have experience in:
- .NET
- Xamarin.Forms and MAUI
- Entity framework Core
- Relational databases

When I'm not coding, I enjoy posting content on LinkedIn.

If you find my content interesting, let's connect!

Clear, practical insights for modern developers | Microsoft MVP | Full-Stack .NET engineer

If you want a ready roadmap for a new project…

...then I have 3 required steps...and few more 👇 

A few days ago, I realized I hadn’t coded in my spare time for a while.

I wanted to build something useful for myself.

Before diving into what to develop, I wanted the technical foundation to be ready.

So I started by defining:

📌 Application type (Web API)
📌 Architecture (VSA)
📌 Database (PostgreSQL)

But then, a few more questions arise:

- Authorization and authentication❓ 
- Containerization❓
- Caching❓

Luckily, I found all answers in:

Real-World web development with .NET 10 by Mark Price.

This is not an entry-level book filled with toy examples.

It goes a step further and immerses you in building a real-world web application—the kind you’d actually ship.

The book covers topics like:

- ASP.NET Core MVC
- Frontend prototyping with Bootstrap
- Localization and security
- Data access with EF Core
- Building Web APIs with ASP.NET Core
- Integration testing
- UI testing with Playwright
- Web content management with Umbraco CMS

Get the best book here:
↳ https://lnkd.in/dwnFnt-8


👉 Join to stay ahead with the latest .NET features:
↳ https://www.pavle.codes/

——

♻️ Repost to help others learn about .NET and C# features!

➕ Follow me(Pavle Davitković) for more posts like this.

Roadmap for new projects by Pavle Davitkovic

Today I learned about this cool EF Core feature.

It turns out that...

AsNoTracking is redundant. Surprised? 

I was also. But here is the explanation:

Strongly typed entities are tracked in EF Core, and anonymous types are not.

So what happens when you write anonymous type query? 

- No entity instances returned
- No tracking occurs 
- Faster query execution
- Less memory usage

Simple, but yet effective feature.

👉 Join to stay ahead with the latest .NET features:
↳ https://www.pavle.codes/

♻️ Repost to help others learn more about anonymous types in EF Core.

➕ Follow me (Pavle Davitković) for more posts like this.

How to protect server from slow or stuck requests?

This small improvement will help you: 

Request timeouts define how long your application is willing to process an incoming HTTP request before giving up.

It's a timer when you’re waiting for something to happen.

When a request exceeds its timeout limit, the CancellationToken available through HttpContext.RequestAborted is triggered and its IsCancellationRequested property is set to true.

The request is not automatically aborted, which means the application can still return either a successful or failed response if it continues executing.

If the application does not handle the cancellation or produce a response, ASP.NET Core will return a 504 Gateway Timeout by default.

Without request timeouts:

- Your application can hang forever waiting for a request to complete
- Server resources like memory and threads stay occupied
- Slow requests can impact other users and reduce overall performance

So be sure to introduce them as soon as possible to avoid this type of problems.

👉 Join to stay ahead with the latest .NET features:
↳ https://www.pavle.codes/

——

♻️ Repost to help others learn about request timeouts in .NET!

➕ Follow me(Pavle Davitković) for more posts like this.

If you think that WFH is bread and butter...

...you are not far from truth. But you must know this:

I thought that working from home would mean:

- Pristine desk
- Perfectly brewed coffee
- Uninterrupted focus

But then realty hit. And bit by bit this "bad" habits are made:

📌 The "Instagram vs reality" split
↳ I wanted a minimalistic workspace. But instead I got desk with unfiled papers, notebooks, stick notes.

📌 The "Zoom Mullet" strategy
↳ If the camera cant' see my tracksuit or pajama under the desk, do they even exist?

📌 The commute calculation
↳ The commute is only 10 seconds, yet somehow the struggle is real. The danger of "five more minute" game nearly costed me a job at some point.

📌 Snack attack central
↳ The office kitchen had boundaries. Home does not. XY times my desk slowly transformed to graveyard of coffee mugs and takeout boxes.

📌 The "Sorry, I was on mute" lie
↳ "Meeting multitasking" is real. I was often caught lacking in meetings because of doing some other work that could wait.

📌 The boundary collapses
↳ Sometime I can't work from my home. So my parents house is good. But there work/home boundaries are erased. The "No boundaries" life means reviewing code between dog walks and taking out the trash.

📌 The redemption
↳ But it's not all chaos. Small changes like cleaner desk actually do have a big impact on reclaiming your sanity.

Hope this will help you with your WTF habits!

And if you need to make a presentation for clients fast, then this is a right tool for you
↳ https://lnkd.in/dGts36C2

👉 Join to stay ahead with the latest .NET features:
↳ https://www.pavle.codes/

♻️ Repost to help others learn more how to level up WFH.

➕ Follow me (Pavle Davitković) for more posts like this.

Remote working habits by Pavle Davitkovic

I made a concise Web API few years ago.

This is how I've done it:

With the release of Minimal API, we in .NET ecosystem, learned new way to make APIs. 

No controllers, not ceremonial code from the start. None of that.

Just a clean endpoint with all required logic in body.

But then something even better came out: Fast Endpoints.

It's an open-source .NET library that streamlines Web API development by removing the need for controllers and routing attributes. 

Built on top of ASP.NET Core Minimal APIs, it retains all their performance advantages while offering a cleaner and more intuitive programming model.

FastEndpoints follows the REPR (Request–Endpoint–Response) design pattern and provides several benefits:

- Simplicity: Reduces complexity by modeling each endpoint as a dedicated class

- Performance: Optimized for speed, delivering high throughput and low latency

- Maintainability: A clean, structured codebase that’s easy to evolve and scale

One file. One endpoint. Nothing more.

And this is just a tip of the iceberg. There is a lot out-of-the box feature you can leverage like:

- Validation
- Dependency injection
- Event and Command bus
- Server sent events

Learn more here: https://lnkd.in/dQSh386H

👉 Join to stay ahead with the latest .NET features:
↳ https://www.pavle.codes/

♻️ Repost to help others learn more about Fast Endpoints.

➕ Follow me (Pavle Davitković) for more posts like this.

Have you worked with JSON in relational databases?

Well, today is your lucky day - because…

I have a simple challenge for you.

The idea is simple: extract objects.

The only hint I can give you is that the function starts with JSON.

The rest is up to you!
Good luck! 🚀

👉 Join to stay ahead with the latest .NET features:
↳ https://www.pavle.codes/

♻️ Repost to help others learn solve this challenge!

➕ Follow me (Pavle Davitković) for more posts like this.

Any problem can be solved.

Here are only two core principles you need:

- Think of the solution first
- Write the code second

If I were to break it down into percentages, it would look like this:

 -95% - thinking and structuring
- 5% - actually writing code

I also like to break big problems into smaller, more manageable ones. This makes the approach much more pragmatic.

And trust me—don’t try to reverse-engineer this process. You won’t get any benefit from doing so.

It usually just leads to wasted time and the inevitable question: "Why didn't I think first"?

So, grab pen and paper, or your favorite note taking app, split the problem into pieces and solve them one at the time.

A little bit goes a long way. 

👉 Join to stay ahead with the latest .NET features:
↳ https://www.pavle.codes/

——

♻️ Repost to help others learn about 95/5 principle.

➕ Follow me(Pavle Davitković) for more posts like this.

These tools are often faster than Microsoft’s own.

And chances are you’ve never even heard of them.

Built in Devart’s engineering kitchen, they tackle the most common bottlenecks in modern data engineering:

📌 High-speed .NET data providers

dotConnect delivers high-performance direct access to major database systems Oracle, MySQL, PostgreSQL, SQLite, and services like Salesforce, QuickBooks, Zoho, etc. It is a complete solution that helps develop data-related .NET applications and web sites. 

📌Data Modeling & Design

Entity Developer: A powerful visual ORM designer that keeps EF Core models clean and maintainable. Model complex database structures visually, reduce bugs, and ship features faster.

For more than 20 years, these tools have helped companies like Apple, Walmart, and many others keep their data foundations rock solid.

Recently, Devart shipped a major update with dotConnect 2025.1.

The feature list is long - but let’s focus on my favorite part: performance.

📌Massive performance gains:
 
- Visual Studio 2026 and .NET 10 support
- Modern SSH encryption and key exchange support for dotConnect for Oracle (in Direct mode), dotConnect for MySQL, and dotConnect for PostgreSQL
- OAuth integration for cloud services
- Batch updates for enhanced performance
- Added support for PostgreSQL 18 in dotConnect for PostgreSQL
- Added support for MariaDB 12 in dotConnect for MySQL

You can find the full breakdown here:
https://lnkd.in/ddkGkGZj

I’m confident you’ll enjoy exploring it.

Out of curiosity-which tool would fit best in your project?

👉 Join to stay ahead with the latest .NET features:
↳ https://www.pavle.codes/

——

♻️ Repost to help others learn about request timeouts in .NET!

➕ Follow me(Pavle Davitković) for more posts like this.

taplio

Pavle Davitković's Linkedin Analytics