User:Prd: Difference between revisions

← Older edit Newer edit →

VisualWikitext

Revision as of 18:07, 14 May 2025

Holder of the skeleton key.
Upgraded to level 8

The Decider

Figure it out mentality.

From signal to server, understand everything!

Socials

Discord - prd1847

Prdandsuch on Reddit

KenshiDBdotWiki@gmail.com

Right on time.

Woohoo!

Understand(ing mission critical systems, why they must not fail and why mission creep invalidates intentional design, i.e. process failure): https://forums.debian.net/viewtopic.php?t=120652
Merely because something has been embraced does not mean it qualifies as anything other than a stopgap to an unsolved problem. If the levies are built to break then you have all the evidence you need once the flood waters clear and beg the questions "how" and "why"? Because, you trusted someone who never deserved it. Perhaps you were desparate. Maybe the path of least resistance is the most sensible. Which is why we have resistors (read: process controls and guardrails). Stop allowing the flow to dictate the direction - it does not and never has cared which path it follows. Systemd is proof that incompetency is the norm in software engineering and its creator should be ashamed. No apologies for wanton neglect.

Scalar severity

Non-Critical Applications
Short Product Life Expectancy / Non-Critical Applications
Product Accessible to Field Repair
Application Critical
Refurbished or Reclaimed Parts
Reporting Source Alert on Items
Field Work or Repair Impossibility (i.e., Satellites, etc.)
Mission Critical
Safety Critical
Life Dependent Applications

@@ Line 19: / Line 19: @@
 ;Understand(ing mission critical systems, why they must not fail and why mission creep invalidates intentional design, i.e. process failure)
 :https://forums.debian.net/viewtopic.php?t=120652
-;Merely because something has been embraced does not mean it qualifies as anything other than a stopgap to an unsolved problem. If the levies are built to break then you have all the evidence you need once the flood waters clear and beg the questions "how" and "why"? Because, you trusted someone who never deserved it. Perhaps you were desparate. Maybe the path of least resistance is the most sensible. Which is why we have resistors. Stop allowing the flow to dictate the direction - it does not and never has cared. Systemd is proof that incompetency is the norm in software engineering and its creator should be ashamed.
+;Merely because something has been embraced does not mean it qualifies as anything other than a stopgap to an unsolved problem. If the levies are built to break then you have all the evidence you need once the flood waters clear and beg the questions "how" and "why"? Because, you trusted someone who never deserved it. Perhaps you were desparate. Maybe the path of least resistance is the most sensible. Which is why we have resistors (read: process controls and guardrails). Stop allowing the flow to dictate the direction - it does not and never has cared which path it follows. Systemd is proof that incompetency is the norm in software engineering and its creator should be ashamed. No apologies for wanton neglect.
 :Scalar severity