hard to compete against sunshine

I'm using Sunshine and Moonlight to stream my PC to my TV too

Seeing the thread has come to an end;

You argued very well!

Personally, I would like to see LINQ query syntax and LINQ method syntax separated too. Because I find method syntax very useful (for simple or linear-spread-cascading queries), but I find query syntax hard to read and reason. Even worse so when it introduces variables. I don't want to see it anywhere in my projects. But method syntax has clear reasoning borders and I enjoy using it (up to a certain query complexity).

Depends on what I want or need to "understand".

I've worked for many years on a project (it's a whole project ecosystem tbh with multiple projects; desktop winforms app, server app, SQL server, asp.net MVC app, asp.net blazor app, mobile wpf app, sync service app). On the main project (client + server) I haven't visited one major area, and another I confidently know that it's not understandable to me without specific deep effort.

I recently had to work on the latter. I take a localized approach. Explore what I have to do, without opening the full scoped understanding that'd lead me to architecture refacs. I write out the method call stacks to get an overview of who calls what when. To then know what I have to inspect and analyze further.

I take notes where necessary, or improve and comment code where appropriate for better understanding and obviousness.

I create documentation - about concepts and architecture as appropriate and necessary.

Code should be obvious and intuitive. Concept docs should document the broader concepts.

When those concept docs exist, those are what you look at to understand app intention and behavior. And it should give you an introduction to architecture. From there, exploring the code should be self-explanatory (but may require specific, repeated, and iterative analysis). And I take notes about what's relevant and I need for understanding or task.

Afterwards, those notes should have, or should then integrate into the code base or docs, or be determined irrelevant for that. If I had to write them out and down, it's more likely they should be part of something than not.

Do you mean it does not summarize the video well? Or its content alone?

This description is so foreign to me. I guess you're talking about big [software] companies?

Nobody in my company, a software development company, measures by lines of code. We bring value through the software we develop and the collaborations we do.

When I miss them I create them. Then they're there.

It didn't kill GitHub Stars. And they know it.

By looking at commit velocity, issue counts, pull requests, and forks alongside stars, we can better understand a project's adoption and overall value.

I worked on some existing personal dotnet projects, updating targets to net8, upgrading dependencies, and integrating and improving GitHub actions.

I made code improvements to a data-fetcher fetching speedrun.com data - although I did not get far enough to give it fully clear structure and trigger a full data update after I initially set it up two years ago (and ran it through multiple partial downloads). I want to include cache headers, because the API supports it, so the next data update includes them and future fetches will be able to make use of them.

I added some more content to my website, and noticed one page was referenced but missing. Turns out the 100 MB request size limit was reached (because of a few video clips). After updating my CI-deployment-accepting service and the Nginx configuration my website updates on push again (hugo-generated static website).

I've also thought about creating a GitHub dotnet template repository so I can more easily generate repos and projects from them. But it looks like that's not possible for private repos. I ended up creating one with the appropriate git, editorconfig, and dir props files. I will be using them next time I create a project.

Another thing I want to do is continue on or finish a web game written in Blazor. Some game rule restrictions are not enforced yet, and legal moves are not visually obvious yet.

I also want to try out GoDot.

On my Japanese/Hiragana practice tool, I almost want to give up because it's such a hassle and more significant effort to implement.

I've also been contributing to Wikipedia again.

After a long time of very little work holiday, I finally have three weeks. Two more weeks. We will see what I will focus on and be able to do or complete. :)

It doesn't have to "error" if the result case is offered and handled.

You don't need to escape any content for storing in a DB field.

Use the correct database interface and you're good.

I'd be more concerned about intention and intentional design. Arbitrary characters can be misleading or problematic for users. Using an allow list for accepted username characters is a good approach if you can't depend on good intentions of users.

Not to invalidate your job hunting experience, but did you get a four year degree not to learn but only to get a job?