┌───────────────────────────────────────────────────────────────┐
│ │
│ THE INTERFACE IS ONLY THE SURFACE. │
│ I WORK ON WHAT HAPPENS UNDERNEATH IT. │
│ │
└───────────────────────────────────────────────────────────────┘
alias: CiSCO
handle: XCisCoX
role: Systems Programmer
environment: Windows / Linux
specialty: Native & Security Software
status: BuildingI build software close to the operating system—where processes, tokens, services, drivers, memory, IPC, tracing, security boundaries, and undefined behavior stop being abstract concepts. I do not collect programming languages. I use them as tools to interrogate the machine. |
C:\> whoami
XCisCoX\CiSCO
C:\> query specialization
Windows Systems Programming
Endpoint Security
Native Software Engineering
C:\> query current_state
[+] Learning
[+] Building
[+] Debugging
[+] Refusing to trust the happy path
C:\> echo %LIMIT%
LIMIT is not defined |
|
Native applications, Windows services, IPC, security software and low-level systems work. |
Automation, tooling, prototypes, bots and turning repetitive work into dead code. |
Reading beneath the compiler and understanding what the processor was actually told to do. |
Building native interfaces without forgetting that the real machinery lives behind them. |
◈ WINDOWS INTERNALS // PRIVILEGED ZONE
[+] Windows Services
[+] Process Creation & Management
[+] Access Tokens & Privileges
[+] SYSTEM / User Session Boundaries
[+] Native Windows APIs
[+] Event Tracing for Windows
[+] WinDbg & Crash Analysis
[+] Interprocess Communication
[+] RPC Client / Server Architecture
The GUI says what happened. The debugger tells you why.
◈ ENDPOINT SECURITY // DEFENSIVE SYSTEMS
[+] Endpoint Protection Architecture
[+] Scanner & Memory-Scanning Components
[+] Service Self-Protection
[+] Secure Process Communication
[+] Privilege-Boundary Design
[+] Cryptographic Signing & Verification
[+] Attack-Surface Reduction
[+] Failure-Resistant Native Software
My interest in security is not limited to finding a vulnerable input.
I want to understand the boundary, the assumptions protecting it, and what happens when every assumption fails at once.
◈ NATIVE ENGINEERING // MACHINE PROXIMITY
[+] C / C++
[+] Memory & Resource Management
[+] Multithreaded Systems
[+] Native Libraries
[+] Qt Applications
[+] CMake & Visual Studio
[+] Debugging Undefined Behavior
[+] Cross-Architecture Builds
I care about software that remains understandable when the logs are incomplete, the environment is hostile, and the bug only happens on someone else's machine.
◈ INFRASTRUCTURE // DEPLOYMENT LAYER
[+] Linux Administration
[+] Docker & Docker Compose
[+] PostgreSQL
[+] Git
[+] Reverse Proxies
[+] Network Troubleshooting
[+] Build Pipelines
[+] Production Debugging
Because a program that only works on the developer's machine is not software.
It is a local rumor.
|
|
class CiSCO final
{
public:
void solve(Problem& problem)
{
while (!problem.isUnderstood())
{
problem.observe();
problem.reproduce();
problem.breakApart();
}
problem.buildSolution({
.simple = true,
.observable = true,
.resilient = true,
.secure = true
});
}
private:
bool trustsTheHappyPath = false;
};Abstractions are useful—until they leak. Then somebody has to understand the machine.
|
Distortion, atmosphere, cinematic sound and the endless war against unwanted string noise. |
Questioning assumptions, systems, power, identity and the stories people mistake for reality. |
Building the kind of consistency that does not depend on motivation showing up. |
┌─[visitor@github]─[~/XCisCoX]
└──╼ $ connect
[*] Secure channel requested...
[+] Identity verified: CiSCO
[+] Interface ready.