This commit is contained in:
4
.obsidian/types.json
vendored
4
.obsidian/types.json
vendored
@@ -5,6 +5,8 @@
|
||||
"tags": "tags",
|
||||
"work day": "checkbox",
|
||||
"pdf": "multitext",
|
||||
"date finished": "date"
|
||||
"date finished": "date",
|
||||
"done": "checkbox",
|
||||
"note type": "multitext"
|
||||
}
|
||||
}
|
||||
72
.obsidian/workspace.json
vendored
72
.obsidian/workspace.json
vendored
@@ -4,21 +4,21 @@
|
||||
"type": "split",
|
||||
"children": [
|
||||
{
|
||||
"id": "a02e12a961378868",
|
||||
"id": "df8f28bb5a4c5e3f",
|
||||
"type": "tabs",
|
||||
"children": [
|
||||
{
|
||||
"id": "032853642c3b53cd",
|
||||
"id": "92f81c142b14f9a8",
|
||||
"type": "leaf",
|
||||
"state": {
|
||||
"type": "markdown",
|
||||
"state": {
|
||||
"file": "Articles/Every Senior Engineer has read these books.md",
|
||||
"file": "Index.md",
|
||||
"mode": "source",
|
||||
"source": false
|
||||
},
|
||||
"icon": "lucide-file",
|
||||
"title": "Every Senior Engineer has read these books"
|
||||
"title": "Index"
|
||||
}
|
||||
}
|
||||
]
|
||||
@@ -187,63 +187,63 @@
|
||||
"graph:Open graph view": false,
|
||||
"canvas:Create new canvas": false,
|
||||
"daily-notes:Open today's daily note": false,
|
||||
"templates:Insert template": false,
|
||||
"command-palette:Open command palette": false,
|
||||
"bases:Create new base": false,
|
||||
"obsidian-excalidraw-plugin:New drawing": false,
|
||||
"pdf-plus:PDF++: Toggle auto-copy": false,
|
||||
"pdf-plus:PDF++: Toggle auto-focus": false,
|
||||
"pdf-plus:PDF++: Toggle auto-paste": false
|
||||
"pdf-plus:PDF++: Toggle auto-paste": false,
|
||||
"bases:Create new base": false,
|
||||
"templates:Insert template": false
|
||||
}
|
||||
},
|
||||
"active": "032853642c3b53cd",
|
||||
"active": "92f81c142b14f9a8",
|
||||
"lastOpenFiles": [
|
||||
"Career/Concepts.md",
|
||||
"Career/XOR.md",
|
||||
"Career/Windows Services.md",
|
||||
"Career/Test Driven Development.md",
|
||||
"Career/Database - SQL/SQL Joins.md",
|
||||
"Career/Solid Principles.md",
|
||||
"Career/Software Development Methodologies.md",
|
||||
"Career/Microlise/Session Stored XSS PENTEST.md",
|
||||
"Career/Security/Server-Side Request Forgery (SSRF).md",
|
||||
"Career/Microlise/Seb Search Improvements.md",
|
||||
"Career/ASP.NET Core Web API Fundamental Notes.md",
|
||||
"Career/API Architecture.md",
|
||||
"Career/Restful API.md",
|
||||
"Career/Microlise/Pre work prep.md",
|
||||
"Career/Powershell MOC.md",
|
||||
"Career/Database - SQL/Postgres.md",
|
||||
"Career/Security/OWASP Top 10.md",
|
||||
"Career/MVP + MVT.md",
|
||||
"Career/Microlise/Microlise Assessment.md",
|
||||
"Career/Microlise/Microlise MOC.md",
|
||||
"Career/Microlise/ESS ESP/Microlise - ESS.md",
|
||||
"Career/Design Patterns.md",
|
||||
"Career/Job applications.md",
|
||||
"Career/Java Portswrigger Test.md",
|
||||
"Career/Microlise/ESS ESP/ESS ESP Index.md",
|
||||
"Career/Microlise/ESS ESP/ESP Scripts.md",
|
||||
"pdfs/_articles/20-laws-software-engineering.pdf",
|
||||
"pdfs/_articles/I Thought I Knew System Design Until I Met a Google L7 Interviewer.pdf",
|
||||
"Articles/Attachments/2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium-01.png",
|
||||
"pdfs/_articles/Attachments/2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium-01.png",
|
||||
"Articles/Every Senior Engineer has read these books.md",
|
||||
"Articles/Attachments/2026-05-22-senior-books.png",
|
||||
"Articles/Articles MOC.md",
|
||||
"Articles/20 Software Engineering Laws.md",
|
||||
"pdfs/_articles/Attachments/2026-05-22-senior-books.png",
|
||||
"Articles/Software Quality.md",
|
||||
"Articles/Attachments/2026-05-22-software-quality.png",
|
||||
"Articles/I thought I knew system design.md",
|
||||
"pdfs/_articles/Attachments/2026-05-22-software-quality.png",
|
||||
"Articles/Substack Articles.md",
|
||||
"pdfs/_articles/software-quality.pdf",
|
||||
"Templates/articles template.md",
|
||||
"Templates/daily template.md",
|
||||
"Index.md",
|
||||
"Daily Notes.md",
|
||||
"pdfs/_articles/Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf",
|
||||
"Articles/Attachments/2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium-06.png",
|
||||
"Articles/Attachments/2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium-05.png",
|
||||
"Articles/Attachments/2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium-04.png",
|
||||
"Articles/Attachments/2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium-03.png",
|
||||
"Articles/Attachments/2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium-02.png",
|
||||
"Articles/Attachments",
|
||||
"pdfs/_articles/Attachments",
|
||||
"pdfs/blank.pdf",
|
||||
"pdfs/_urdu/Umrao-Jaan-Ada.pdf",
|
||||
"pdfs/_urdu/st_exupery_le_petit_prince.pdf",
|
||||
"pdfs/_urdu/Proficiency in Urdu through English.pdf",
|
||||
"pdfs/_urdu/Basic-Urdu-1670897891.pdf",
|
||||
"pdfs/_urdu",
|
||||
"Career/Security/OWASP Top 10.md",
|
||||
"Dailies/2026-06-03.md",
|
||||
"Dailies/2026-06-02.md",
|
||||
"Dailies/2026-04-30.md",
|
||||
"Templates/Daily.md.md",
|
||||
"Career/Security/Server-Side Request Forgery (SSRF).md",
|
||||
"Career/Security/Cross Site Scripting (XSS).md",
|
||||
"Career/Concepts.md",
|
||||
"_attachments/Drawing 2026-06-02 15.20.33.excalidraw.md",
|
||||
"Excalidraw/Drawing 2026-06-02 15.19.45.excalidraw.md",
|
||||
"Excalidraw/Drawing 2026-06-02 15.12.36.excalidraw.md",
|
||||
"Technical/Emacs/Org Roam.md",
|
||||
"Technical/Emacs/Org Publish.md",
|
||||
"Technical/Emacs/Org Noter.md",
|
||||
"Technical/Emacs/Magit.md",
|
||||
"Untitled.canvas"
|
||||
]
|
||||
}
|
||||
@@ -1 +1,10 @@
|
||||
---
|
||||
pdf:
|
||||
- "[[20-laws-software-engineering.pdf]]"
|
||||
date started: 2026-06-03
|
||||
date finished:
|
||||
type: pdf-notes
|
||||
done:
|
||||
---
|
||||
# Link: <https://substack.com/inbox/post/194605697>
|
||||
# 20 Software Engineering Laws: Notes
|
||||
@@ -0,0 +1,5 @@
|
||||
## Software Articles:
|
||||
|
||||
- [[I thought I knew system design]]
|
||||
- [[Every Senior Engineer has read these books]]
|
||||
- [[Software Quality]]
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
pdf:
|
||||
- "[[I Thought I Knew System Design Until I Met a Google L7 Interviewer.pdf]]"
|
||||
date started: 2026-06-03
|
||||
date finished: 2026-06-03
|
||||
type: pdf-notes
|
||||
---
|
||||
# AI summary:
|
||||
|
||||
- System design is not about memorising architecture patterns; it is about knowing why each component is needed.
|
||||
@@ -8,18 +15,15 @@
|
||||
|
||||
# Article Notes
|
||||
|
||||
## sharding or replication.
|
||||
> ([[I Thought I Knew System Design Until I Met a Google L7 Interviewer.pdf#page=2&annotation=341R|I Thought I Knew System Design Until I Met a Google L7 Interviewer, p.2]])
|
||||
> sharding or replication.
|
||||
|
||||
Sharding is the process of splitting a database into smaller, more manageable pieces called shards. Each shard is a separate database that contains a subset of the data. Replication, on the other hand, is the process of copying data from one database to another. This can be done for backup purposes or to improve performance by distributing read requests across multiple replicas.
|
||||
|
||||
## Notes for page 3
|
||||
|
||||
[[I Thought I Knew System Design Until I Met a Google L7 Interviewer.pdf#page=2|I Thought I Knew System Design Until I Met a Google L7 Interviewer, p.2]]
|
||||
> This is the part that changes everything. Every component has this envelope of conditions where it actually helps. Caching works
|
||||
> when reads dominate and access patterns cluster together. Sharding makes sense when write throughput matters way more than
|
||||
> transactional guarantees. Replication helps when read availability beats consistency.
|
||||
|
||||
## Notes for page 4
|
||||
|
||||
> Start with one database, one server, no cache. Only scale when some specific metric like latency or throughput or cost crosses a
|
||||
> threshold you can actually name. When you add a component, explain what new failure mode it introduces and how you’d even
|
||||
> detect it.
|
||||
> ([[I Thought I Knew System Design Until I Met a Google L7 Interviewer.pdf#page=4&annotation=345R|I Thought I Knew System Design Until I Met a Google L7 Interviewer, p.4]])
|
||||
> Start with one database, one server, no cache. Only scale when some specific metric like latency or throughput or cost crosses a threshold you can actually name. When you add a component, explain what new failure mode it introduces and how you’d even detect it.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
- api
|
||||
date: 2026-06-03
|
||||
done: false
|
||||
---
|
||||
**Z notes on API architecture - companion to [[APIM]]
|
||||
|
||||
# 1\. What is API Architecture?
|
||||
|
||||
@@ -1 +1,8 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
- api
|
||||
date: 2026-06-03
|
||||
done:
|
||||
---
|
||||
****Notes from [Pluralsight](https://app.pluralsight.com/ilx/video-courses/asp-dot-net-core-6-web-api-fundamentals/resources)****
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- theory
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Big (O) - Time and Space Complexity
|
||||
|
||||
## Intro
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
- <https://www.codurance.com/katas/bowling>
|
||||
|
||||
- <http://www.butunclebob.com/ArticleS.UncleBob.TheBowlingGameKata>
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
- devops
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
During the first wave in 2026, we planned to get the netcore version of site visits out to customers. There were a bunch of tasks relating to this, so I asked AI to conceptually explain them.
|
||||
|
||||
# Prompt:
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- devops
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Summary
|
||||
|
||||
CI/CD stands for Continuous Integration and Continuous Delivery/Deployment. It’s a development practice that automates building, testing, and delivering software so code changes can be released quickly and reliably.
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- moc
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
Here will lie articles, resources, notes and the like relating to my career. It differ with [this](https://www.zainezq.com/posts/career/career-list.html) page in the sense that this one will contain:
|
||||
|
||||
- Ideas
|
||||
|
||||
@@ -134,3 +134,13 @@ Some core programming concepts that are essential for software development. The
|
||||
- Turing machines
|
||||
- computability theory
|
||||
- MVPs and MVTs
|
||||
|
||||
# Data view query
|
||||
|
||||
All files that are not done:
|
||||
```dataview
|
||||
TABLE
|
||||
FROM "Career"
|
||||
WHERE done != true
|
||||
SORT file.name ASC
|
||||
```
|
||||
@@ -1 +1,7 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
A Dynamic Link Library (DLL) is a type of file that contains code and data that can be used by multiple programs simultaneously. It allows developers to modularise their applications, enabling code reuse and efficient memory usage. DLLs are commonly used in Windows operating systems, but they can also be found in other platforms.
|
||||
|
||||
@@ -1,3 +1,11 @@
|
||||
---
|
||||
note type:
|
||||
- database
|
||||
- note
|
||||
- ai
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
**TITLE: Introduction to AI for Work**
|
||||
|
||||
# Summary
|
||||
|
||||
@@ -1 +1,6 @@
|
||||
---
|
||||
note type: note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
A DAG (short for directed acyclic graphs) is a model that encapsulates everything needed to execute a workflow. [See this](https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/dags.html)
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
- database
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
A task in the context of airflow is the basic unit of execution. They are arranged into [[Airflow Dags]] and then have upstream and downstream dependencies set between them in order to express the order in which they should be run.
|
||||
|
||||
There are three kinds of tasks:
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
note type: database
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# xcom
|
||||
|
||||
XComs stands for cross-communications, and as the name suggests, it allows [[Airflow Tasks]] to talk to each other (because by default, tasks are entirely isolated and can run on seperate machines).
|
||||
|
||||
@@ -1,2 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- moc
|
||||
- database
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
- [[Postgres]]
|
||||
- [[Airflow]]
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- database
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Introduction
|
||||
|
||||
Database security is a crucial part of database administration. It ensures that only authorised users can access, modify, or manage data. Three core concepts used to control access are:
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- database
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
``` bash
|
||||
psql -h 82.18.104.48 -p 5432 -U zaine -d org_web
|
||||
```
|
||||
|
||||
@@ -1,10 +1,18 @@
|
||||
---
|
||||
note type:
|
||||
- database
|
||||
- theory
|
||||
date: 2026-06-03
|
||||
done:
|
||||
---
|
||||
|
||||
# The SQL JOIN Clause
|
||||
|
||||
The JOIN clause is used to combine rows from two or more tables, based on a related column between them.
|
||||
|
||||
Here are the different types of JOINs in SQL:
|
||||
|
||||
****(INNER) JOIN****: Returns only rows that have matching values in both tables
|
||||
****LEFT (OUTER) JOIN****: Returns all rows from the left table, and only the matched rows from the right table
|
||||
****RIGHT (OUTER) JOIN****: Returns all rows from the right table, and only the matched rows from the left table
|
||||
****FULL (OUTER) JOIN****: Returns all rows when there is a match in either the left or right table
|
||||
- (INNER) JOIN: Returns only rows that have matching values in both tables
|
||||
- LEFT (OUTER) JOIN: Returns all rows from the left table, and only the matched rows from the right table
|
||||
- RIGHT (OUTER) JOIN: Returns all rows from the right table, and only the matched rows from the left table
|
||||
- FULL (OUTER) JOIN: Returns all rows when there is a match in either the left or right table
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- theory
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done:
|
||||
---
|
||||
**WIP**
|
||||
|
||||
# Summary of the major patterns:
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- theory
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Java Concepts
|
||||
|
||||
### 1. Object-Oriented Programming Concepts
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Modules:
|
||||
|
||||
1st year
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# MVP and MVT
|
||||
|
||||
- An ****MVP**** is a ****minimal functional product**** built to validate what customers actually want by observing real usage.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
- api
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
**Z notes on API management so I don’t forget**
|
||||
|
||||
1. API stands for application programming interface. It allows systems to communicate with each other.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# What is ESP?
|
||||
|
||||
ESP is a software suite built by ESS and sold to customers. It is deployed on a **per-customer basis** — similar to TMC (another internal product) but with fewer applications in the suite.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
- ess
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# The ESP Database
|
||||
|
||||
ESP uses a single SQL Server database called **EspBroker**. This is deployed and upgraded as part of the overall ESP deployment process.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
The deployment is broken into **discrete stages** that can be run in any combination. This allows you to, for example, only run validation, or only run post-deploy checks, without triggering a full deployment.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
Reference glossary for all technical and project-specific terms used across the ESP deployment pipeline project. Alphabetically ordered.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
This file documents all known issues, risks, and blockers identified in the handover material. Understanding these early will help you avoid surprises.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# What Is the Manifest?
|
||||
|
||||
The manifest is a **configuration file** that describes a specific customer environment. The deployment scripts read the manifest to understand **what** to deploy, **where**, and **how**.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
These are items explicitly marked as TBC or not yet designed in the handover material. They represent real blockers or gaps that need to be resolved before the pipeline is complete. Use this file to track answers as they are determined.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# What is Azure DevOps (AzDO)?
|
||||
|
||||
Azure DevOps is Microsoft's platform for DevOps workflows. It covers:
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
The deployment scripts are structured in **three tiers**, loosely analogous to a presentation/domain/data layered architecture in software. This separation exists to:
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
The ESP Deployment Pipeline project is an effort to automate the deployment of the ESP application suite (built by ESS) into customer environments using Azure DevOps (AzDO) YAML pipelines and PowerShell scripts.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
Joined team Shackleton on \<2026-04-07 Tue\>, who are now overseeing the deployment process for ESS applications.
|
||||
|
||||
[[ESS ESP Index]]
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- microlise
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
1. What are you most proud of doing in the last 2 years?
|
||||
|
||||
2. What do you think you could have done better in the last two years?
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- microlise
|
||||
- moc
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# \<2026-05-27 Wed\>: XSS ROM Work
|
||||
|
||||
## [[Session Stored XSS PENTEST]]
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Clothing
|
||||
|
||||
# Bag(s)
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- microlise
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
DBAs are seeing high CPU and memory usage on SQL production servers due to SEB
|
||||
|
||||
@@ -1,3 +1,11 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
- microlise
|
||||
- security
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Links:
|
||||
|
||||
- [[Cross Site Scripting (XSS)]]
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- moc
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Articles/Resources:
|
||||
|
||||
- [On Synopsis and help syntax](https://gist.github.com/MyITGuy/18ea0f54d2accc0eb8e7ae1521952de0)
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- api
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# What is a RESTful API?
|
||||
|
||||
A **RESTful API** is a web service that follows the principles of **REST (Representational State Transfer)**. REST is an architectural style used for designing networked applications.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- security
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Definition:
|
||||
|
||||
- Cross Site Scripting (XSS) is a type of security vulnerability typically found in web applications. It allows attackers to inject malicious scripts into content from otherwise trusted websites.
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- theory
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
This stands for Open Web Application Security Project.
|
||||
|
||||
It is a non profit foundation which publishes the OWASP top 10, which is a standard document that identifies the most critical security risks to web applications.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- security
|
||||
- theory
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
This is a critical web security vulnerability where an attacker manipulates a server into making unauthorised HTTP requests to internal or external resources on the attacker's behalf.
|
||||
|
||||
## How SSRF Attacks Work
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- theory
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Software Development Methodologies
|
||||
|
||||
A software development methodology defines the *process, structure, and principles*
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- theory
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
The SOLID principles are a set of five design principles that help software developers create maintainable, scalable, and flexible software systems. The principles were introduced by Robert C. Martin (Uncle Bob) and are widely used in object-oriented programming.
|
||||
|
||||
The SOLID principles are:
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
Test-driven development is a way of writing code that involves writing an automated unit-level test case that fails, then writing just enough code to make the test pass, then refactoring both the test code and the production code, then repeating with another new test case. Alternative approaches to writing automated tests is to write all of the production code before starting on the test code or to write all of the test code before starting on the production code.
|
||||
|
||||
One example is [[Bowling Kata]]
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- theory
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Summary
|
||||
|
||||
Windows Services are essential components of the Windows operating system that run in the background to perform critical system functions. They operate without user interaction, starting automatically during system boot and continuing until shutdown. Managed by the Service Control Manager, they handle tasks such as network connectivity, hardware management, and system security. Administrators can manage services using tools like Services.msc, command-line utilities, and PowerShell for automation.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- theory
|
||||
- mathematics
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
XOR stands for exclusive or. It is a logical operation that outputs true only when the inputs differ (one is true, the other is false). If both inputs are the same (both true or both false), the output is false.
|
||||
|
||||
Here is the truth table for XOR:
|
||||
|
||||
@@ -3,5 +3,6 @@ pdf:
|
||||
date started: "{{date}}"
|
||||
date finished:
|
||||
type:
|
||||
done:
|
||||
---
|
||||
# {{title}}: Notes
|
||||
5
Templates/concept template.md
Normal file
5
Templates/concept template.md
Normal file
@@ -0,0 +1,5 @@
|
||||
---
|
||||
note type:
|
||||
date: "{{date}}"
|
||||
done:
|
||||
---
|
||||
Reference in New Issue
Block a user