Now is the time for me to start projects to get the hang of ASP.NET (Razor Pages then MVC), although it doesn’t seem like there’s a whole lot I need to worry about but I fucking feel like I’m messing it up already. I’m just worried about how I’m going to work up to sumn I would do at a job and remembering everything I have to do in the project and why

It's not particularly important. It's a broken paradigm to start with.

@SortOfTested could you explain what you mean, I’m lost lol

@Bubbles
Rendering HTML on the server as a glorified string concatenation and transmitting it downstream is an excellent way to pay for something a user's browser is more capable of doing for free.

@SortOfTested oh, true. Idk if this is a common opinion and I was thinking about making a post about it, but from what I’ve messed with so far backend doesn’t seem nearly as complex as I’ve made it out to be. It seems like it’s just handling requests, processing data in whatever way that data needs to be processed in (like encrypting/decrypting it or sumn), inserted into a database OR taking data from the database and apply it to the frontend of the user, using it to send an email to the user, etc

Am I right or ignorant, because if I’m wrong I want to be told before I make a bigger fool of myself.

Don't worry about it, if you already know C# and HTML(or any other web language/framework/thing) it shouldn't be thst complicated, chill out, and don't worry about fucking up, because that's what you learn the most from

@Bubbles
"Backend" can be as complex as you want to make it. Personally, I feel that your server-side code is making the best use of its resources when you're handling transactional data, event-based faas, etc. The business logic bits of the equation.

The issues I tend to see with server MVC frameworks is they try to be both cart and horse, without regard to what is paradigmatically appropriate. You will inevtiably see server-state, and in many cases unnecessary data that is serialized into the payloads to commute pieces of that state. This is overcomplication.

The payloads are also rarely optimized (take a look at your mvc output). There really isn't a canonical way to "minify" any of your payloads, so responses carry unnecessary weight in the form of scripts, "pretty html," injected styles, etc. It always hits a bottleneck at modest user counts, and the solution is always more ram and static html caching. It gets real expensive, real quick.

@SoldierOfCode it’s my first backend framework in general

@SortOfTested yeah you gotta point

The worst i have seen so far were a TempData storing a string of the view name i was coming from. This was later used to redirect the user after a post.
The horrible feeling while seeing js(jquery) in a script tag on each view just to make a specific thing work.
Parsing a c# array into a string and then parsing it back to js in the script tag of the page 🤣. Omg the Html was infested with a gigantic array.

As long as it's .Net, Corporate will take the 10s+ page load.

@Benutzername that sounds fuckin messy dude

@Bubbles That will be your future too if you keep pursuing the .net stack 🤣

@Benutzername honestly don’t plan to for long