Main public logs
Combined display of all available logs of Knowledge Base. You can narrow down the view by selecting a log type, the username (case-sensitive), or the affected page (also case-sensitive).
- 07:58, 21 January 2025 Chr1ss talk contribs created page File:End dev css.gif
- 07:58, 21 January 2025 Chr1ss talk contribs uploaded File:End dev css.gif
- 07:50, 21 January 2025 Chr1ss talk contribs created page Optimal Work Enviornment (Created page with "= Optimal Work Environment = thumb == Intro == What makes a good work environment for a backend developer in my mind involves several key factors: == Management == * Clear Project Requirements: ** Begin with well-defined project requirements: *** Specification of the system's functionality *** Performance expectations *** Architectural guidelines * Well-Defined Tasks: ** Clearly define tasks or user stories. Developers must have a solid...")
- 07:50, 21 January 2025 Chr1ss talk contribs created page File:Env emem solve.gif
- 07:50, 21 January 2025 Chr1ss talk contribs uploaded File:Env emem solve.gif
- 07:47, 21 January 2025 Chr1ss talk contribs created page File:Env work self.gif
- 07:47, 21 January 2025 Chr1ss talk contribs uploaded File:Env work self.gif
- 07:42, 21 January 2025 Chr1ss talk contribs created page File:Env colab.gif
- 07:42, 21 January 2025 Chr1ss talk contribs uploaded File:Env colab.gif
- 07:27, 21 January 2025 Chr1ss talk contribs created page File:Env backenddev.jpg
- 07:27, 21 January 2025 Chr1ss talk contribs uploaded File:Env backenddev.jpg
- 06:46, 21 January 2025 Chr1ss talk contribs deleted page File:Cc do donot2.jpg (content was: "meme formating code", and the only contributor was "Chr1ss" (talk))
- 06:46, 21 January 2025 Chr1ss talk contribs deleted page File:Cc do donot3.jpg (content was: "CleanCode Format Discussion", and the only contributor was "Chr1ss" (talk))
- 06:46, 21 January 2025 Chr1ss talk contribs created page File:Cc do donot4.jpg
- 06:46, 21 January 2025 Chr1ss talk contribs uploaded File:Cc do donot4.jpg
- 06:44, 21 January 2025 Chr1ss talk contribs created page File:Cc do donot3.jpg
- 06:44, 21 January 2025 Chr1ss talk contribs uploaded File:Cc do donot3.jpg
- 13:30, 20 January 2025 Chr1ss talk contribs created page File:CheckReqSynHig.png
- 13:30, 20 January 2025 Chr1ss talk contribs uploaded File:CheckReqSynHig.png
- 13:28, 20 January 2025 Chr1ss talk contribs created page Syntax Highlighting (Created page with "= SyntaxHighlighting in MediaWiki = First, I attempted to install the extension specifically designed for this purpose: [https://www.mediawiki.org/wiki/Extension:SyntaxHighlight MediaWiki Extension:SyntaxHighlight] To check if all requirements were met, I used this PHP test script provided by ChatGPT: == Description of the Script == The script tests the server environment for compatibility with the SyntaxHighlight extension. It checks for PHP functions, Python insta...")
- 10:43, 20 January 2025 Chr1ss talk contribs created page File:Cc do donot2.jpg
- 10:43, 20 January 2025 Chr1ss talk contribs uploaded File:Cc do donot2.jpg
- 10:41, 20 January 2025 Chr1ss talk contribs deleted page File:Cc do donot.jpg (content was: "Clean code curly braces new line", and the only contributor was "Chr1ss" (talk))
- 10:41, 20 January 2025 Chr1ss talk contribs created page File:Cc do donot.jpg
- 10:40, 20 January 2025 Chr1ss talk contribs uploaded File:Cc do donot.jpg
- 09:57, 20 January 2025 Chr1ss talk contribs created page File:Function currying.jpg
- 09:57, 20 January 2025 Chr1ss talk contribs uploaded File:Function currying.jpg
- 06:54, 20 January 2025 Chr1ss talk contribs created page Law of Demeter (Created page with "= Law of Demeter (Principle of Least Knowledge) = {{#mermaid: graph LR A["A"] -->|Friend| B["B"] B -->|Friend| C["C"] A -.-> C: "Messages from A to C are discouraged\n(*A friend of a friend is a stranger)" A -->|OK| B: "Messages from A to B" }} The Law of Demeter, also called the Principle of Least Knowledge, is a design guideline for developing software, particularly in object-oriented programming. It aims to reduce dependencies between components, enh...")
- 10:26, 19 January 2025 Chr1ss talk contribs moved page Imperative and Delclarative to Imperative and Declarative (Misspelled title)
- 22:49, 18 January 2025 Chr1ss talk contribs created page File:Codesmells see dead.jpg
- 22:49, 18 January 2025 Chr1ss talk contribs uploaded File:Codesmells see dead.jpg
- 22:25, 18 January 2025 Chr1ss talk contribs created page File:Codesmells comment meme.jpg
- 22:25, 18 January 2025 Chr1ss talk contribs uploaded File:Codesmells comment meme.jpg
- 20:11, 18 January 2025 Chr1ss talk contribs created page Coupling and Cohesion (Created page with "= Principle of High Cohesion and Low Coupling = In software architecture, '''cohesion''' refers to the degree to which the elements within a module or component are related to one another. High cohesion implies that the elements within a module are strongly related and focused on a single, well-defined purpose. '''Coupling''' refers to the degree of interdependence between software modules or components. Low coupling means minimizing the dependencies between modules, e...")
- 20:03, 18 January 2025 Chr1ss talk contribs created page Structural (Created page with "Here is the improved and well-structured version of the article using MediaWiki syntax and a C# example, with explanations added: = Structured Programming = Structured programming stands as a pivotal advancement in software development, offering a more organized and systematic approach to writing code. It promotes the use of well-defined control structures to enhance code clarity, maintainability, and reliability. This paradigm emerged as a response to the challenges p...")
- 19:58, 18 January 2025 Chr1ss talk contribs created page Procedural (Created page with "= Procedural Programming = Procedural programming represents a significant advancement within the imperative paradigm, offering developers a structured approach to organizing and managing code. Programs are constructed around procedures or routines, which encapsulate a set of instructions to perform a specific task. Unlike the unstructured nature of early imperative programming (e.g., assembly language or early versions of BASIC), procedural programming introduces modul...")
- 19:52, 18 January 2025 Chr1ss talk contribs created page Logic (Created page with "= Logic Programming = Logic programming focuses on describing the desired result or outcome rather than specifying the step-by-step procedure for achieving it. In this paradigm, programmers define a set of facts and rules, and the program's interpreter or engine deduces solutions based on logical inference. For example, in procedural or object-oriented languages, developers typically specify a sequence of instructions to manipulate data or perform calculations. In cont...")
- 11:58, 18 January 2025 Chr1ss talk contribs created page Specification (Created page with "= Specification Pattern = == Overview == The '''Specification Pattern''' is a software design pattern used to encapsulate business rules, logic, or criteria into a reusable, combinable, and testable format. It provides a clear and modular way to evaluate whether objects meet certain conditions. This pattern is particularly useful in domains with complex validation or filtering requirements. == Key Concepts == * '''Encapsulation of Criteria''': Encapsulates rules or con...")
- 10:06, 18 January 2025 Chr1ss talk contribs created page MediaWiki:Common.js (Created page with "importScriptURI('https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.6.0/highlight.min.js'); hljs.highlightAll();")
- 09:00, 18 January 2025 Chr1ss talk contribs created page Code Smells (Created page with "<syntaxhighlight lang="python"> def hello_world(): print("Hello, World!") </syntaxhighlight>")
- 18:06, 17 January 2025 Chr1ss talk contribs created page Working with XML (Created page with "# XML in CSharp __TOC__ In C# you can use the built-in System.Xml namespace to extract data from XML files and write XML files. There are two common approaches for working with XML in .NET: == Streaming approach (Using XmlReader and XmlWriter) == The streaming approach is more memory-efficient for large XML files, as it processes the XML sequentially without loading the entire document into memory. Here's an example: <pre> using System; using System.Xml; // Reading fro...")
- 17:53, 17 January 2025 Chr1ss talk contribs created page Exception Handling Best Practices (Created page with "= Exception Handling Best Practices MSDN = MSDN: [https://learn.microsoft.com/en-us/dotnet/standard/exceptions/best-practices-for-exceptions Best practices for exceptions] __TOC__ Exception handling is a critical aspect of software development, ensuring that applications can gracefully handle errors and prevent crashes. In this article, we'll delve into best practices for handling and creating exceptions to enhance the robustness and reliability of your applications. =...")
- 17:44, 17 January 2025 Chr1ss talk contribs created page Startup of ASP.NET Core Web App (Created page with "= Startup of a Web Application = __TOC__ The startup process of an ASP.NET Core web application is a crucial phase where the application is initialized, configured, and prepared to handle incoming HTTP requests. center|alt=Screenshot of Counter Strile stating My Config Settings == Initialize, configure and execute == The `Program` class contains the Main method and this is the starting point of the application. The Startup proces...")
- 17:36, 17 January 2025 Chr1ss talk contribs created page File:Startup webapp config pic.jpg
- 17:36, 17 January 2025 Chr1ss talk contribs uploaded File:Startup webapp config pic.jpg
- 17:34, 17 January 2025 Chr1ss talk contribs created page Storing Database Connection Strings (Created page with "= Storing Database Connection Strings = __TOC__ Nearly all Application interact with a database at some point. Therefore a database connection string is needed, that typically includes details such as the server or host name, database name, authentication credentials (such as username and password), and other parameters necessary for establishing a connection to the database. Properly configuring the connection string is crucial to ensure that the application can access...")
- 17:15, 17 January 2025 Chr1ss talk contribs created page Using Statement for Resource Management (Created page with "= using Statement for Ressource Management = __TOC__ == Basic Example and Overview == <pre> using (var resource = new SomeResource()) { // Use the resource } </pre> This idiom ensures that resources like file streams or database connections are properly disposed of when they are no longer needed, even if an exception occurs. The `using` statement in C# is primarily used for resource management, especially for objects that implement the `IDisposable` interface. The...")
- 17:14, 17 January 2025 Chr1ss talk contribs created page File:Using Statement idiom meme.jpg
- 17:14, 17 January 2025 Chr1ss talk contribs uploaded File:Using Statement idiom meme.jpg
- 17:11, 17 January 2025 Chr1ss talk contribs created page Record Type (Created page with "= Record Types in C# = __TOC__ == Overview == Record types, introduced in C# 9.0, provide a way to declare '''immutable''' data types. They are ideal for representing simple data containers or DTOs (Data Transfer Objects) where immutability, value-based equality, and a sensible string representation are desired. == Purpose == The purpose of record types is to simplify the declaration of immutable data types and reduce boilerplate code associated with defining classes...")