marcos ferreira mracos

Expert-Aligned Engineer System Prompt

You are an expert systems engineer with a production-first mindset. Your responses must align with these core principles:

1. Production-First Systems Engineering

Every design decision assumes production deployment from day one
POCs are production-capable systems that do less, not prototypes to be rewritten
Include observability, health checks, and graceful shutdown from the start
Container-native by default (Podman/Docker with proper multi-stage builds)

Development Guidelines

Philosophy

Core Beliefs

Incremental progress over big bangs - Small changes that compile and pass tests
Learning from existing code - Study and plan before implementing
Pragmatic over dogmatic - Adapt to project reality
Clear intent over clever code - Be boring and obvious

hi, i'm daniel. i'm a 15-year-old with some programming experience and i do a little bug hunting in my free time. here's the insane story of how I found a single bug that affected over half of all Fortune 500 companies:

say hello to zendesk

If you've spent some time online, you’ve probably come across Zendesk.

Zendesk is a customer service tool used by some of the world’s top companies. It’s easy to set up: you link it to your company’s support email (like support@company.com), and Zendesk starts managing incoming emails and creating tickets. You can handle these tickets yourself or have a support team do it for you. Zendesk is a billion-dollar company, trusted by big names like Cloudflare.

Personally, I’ve always found it surprising that these massive companies, worth billions, rely on third-party tools like Zendesk instead of building their own in-house ticketing systems.

your weakest link

Pompeia - Eliminadorzinho

Intro

E |------------------------------------------------|
A |------------------------------------------------|
B |------------------------------------------------|
D |9-9-9-9-9-9-9-9-9-9-9-9-9-9-9-9-9-9-9-9-9-9-9-9-|
A |------------------------------------------------|
E |------------------------------------------------|

Process, mgmt, collaboration:

Roadmap de estudos de SQL

Aviso: Muitas vezes detalhes de várias operações podem variar de banco para banco. Em questões onde fiquei em dúvida, este documento segue o funcionamento do PostgreSQL, pois é o banco que conheço melhor.

Pré-requisito: Álgebra Relacional básica

Antes de começar a escrever SQL, você precisa entender o modelo de como um banco de dados relacional funciona. Não precisa se aprofundar muito, mas você precisa entender como que dados e relacionamentos entre eles são representados. (Nota importante: Relacionamento e relação não são a

Difícil - Terno Rei

INTRO

e |------------------------------------
B |------------------------------------
G |------------------------------------
D |9-9-9-9-9-9-9-9-7-7-7-7-12-12-12-12-
A |------------------------------------

	// A nano dependent type-checker featuring inductive types via self encodings.
	// All computation rules are justified by interaction combinator semantics,
	// resulting in major simplifications and improvements over old Kind-Core.
	// Specifically, computable annotations (ANNs) and their counterpart (ANN
	// binders) and a new self encoding based on equality (rather than dependent
	// motives) greatly reduce code size. A more complete file, including
	// superpositions (for optimal unification) is available on the
	// Interaction-Type-Theory repository.
	// Credits also to Franchu and T6 for insights.

	defmodule Mix.Tasks.ConvertToVerifiedRoutes do
	@shortdoc "Fix routes"

	use Mix.Task

	@regex ~r/(Routes\.)(.)_(path\|url)\(.?\)/
	@web_module MyAppWeb

	def run(_) do
	Path.wildcard("lib/*/.*ex")

	defmodule Ecto.Atom do
	# MIT License
	#
	# Copyright (c) 2017 Matthieu Pinte
	#
	# Permission is hereby granted, free of charge, to any person obtaining a copy
	# of this software and associated documentation files (the "Software"), to deal
	# in the Software without restriction, including without limitation the rights
	# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
	# copies of the Software, and to permit persons to whom the Software is