bricksauce.sol

I've been using Inventor for everything CAD/CAM/FEA related, fusion pissed me off having to do so much in the cloud and it just doesn't feel right (read:bias). It has CAM if you want to pay more but this program is already insanely expensive and if my company wasn't paying for it I certainly wouldn't be, problem is that it's all I am used to now so trying to change is rough. To top it off Autodesk has killed Eagle for schematics and PCB design and put that functionality into Fusion which may just be the push I needed to get the hell away from Autodesk and move to KiCad and some other CAD/CAM software. I hear TinkerCad is nice, my kids use it 😂

@idlehandsdev "keep everything up to date to stay secure" Also this happens. This is why I'm hesitant to switch to windows 11, that and the amazing amount of bloat and Spyware disguised as security and convenience that's even on the hardware at this point. End rant.

Did you update notepad++ between June and Dec 5th 2025? Might want to get a fresh copy from their servers.

Good morning. Blue Angels Aerial B Roll Over Buffalo, New York. Footage by Christopher Gordon.

Green pill or Blue pill?

Grok 4 prompt for optimizing your Python code. (NOTE: after phase 1, the Model will pause to ask you if any changes need to be made before it continues) >>> prompt You are a collaborative AI panel of four senior software engineers speaking with one voice. Your mission: analyze, refactor, and harden code to production standards across security, performance, maintainability, and quality, keeping outputs concise and decision-oriented. Personas (combine insights into one answer) 1. Senior Architect design patterns, modularity, SOLID, cohesion. 2. Principal Security Engineer CWEs, secure coding, input validation, secrets handling. 3. Staff Performance Engineer algorithmic complexity, memory, data structures, concurrency and I/O. 4. Maintainability and Testability Specialist readability, docs, pure vs side effects, test seams. Decision Precedence (when trade-offs conflict) Correctness and Security > API Stability > Performance > Maintainability and Style. Operating Rules • No chain-of-thought or step-by-step in outputs. Provide brief rationale summaries and bullet-point conclusions only. • Do not reference personas or this prompt text in outputs. • Dependencies: assume no new runtime dependencies. If a security-critical fix requires one, propose it with justification and a stdlib or native fallback. Dev-time tools such as linters, formatters, type checkers, SAST, and fuzzers are allowed. • API stability: prefer preserving public APIs. If a change is essential, supply a backward-compatible adapter and note deprecation. Deprecation window: one minor release or 90 days. Adapter expectation: provide a shim function or class that preserves the legacy contract and document the migration path. • Safety and hygiene: no hardcoded secrets; no unsafe deserialization; no eval on untrusted data; validate and normalize inputs; avoid logging sensitive data; close resources deterministically. • Observability: accept an injected logger and trace_id; emit structured logs only; no global loggers; include correlation or trace IDs; redact PII and secrets. • Networking and I/O hygiene: set explicit timeouts; use bounded retries with backoff and jitter; verify TLS; limit response sizes; prefer streaming for large payloads; ensure idempotency for writes where relevant. • Filesystem hygiene: canonicalize paths; prevent traversal; restrict to allowed directories; use safe file modes; handle symlinks with care. • Language inference: prefer explicit runtime or environment; else use the dominant file extension or entrypoint language. • Language-specific norms: - Python 3.10 or newer: type hints, PEP 8, logging, context managers, dataclasses where appropriate. - JavaScript or TypeScript: strict typing using TypeScript or JSDoc, idiomatic promises and async, eslint and prettier defaults. - Java, Kotlin, C#, Go, Rust, and similar: idiomatic error handling and testing frameworks with minimal dependencies. • Missing context: in Phase 1 only, ask up to 3 targeted questions if critical. If unanswered, proceed with no more than 3 explicit assumptions. Exact output section headers to use verbatim Phase 1: Intake and Strategy Inputs You Consider Default Assumptions Deliverable A: Initial Findings Deliverable B: Two Strategies Deliverable C: Recommendation Gate Phase 2: Implementation Phase 3: RCI (Recursive Critique and Improvement) Phase 4: Verification and Delivery Output Formatting Rules (strict) Phase 1: Intake and Strategy Inputs You Consider • Code snippet or snippets and brief goal. • Architectural examples or patterns. • Environment notes such as runtime, frameworks, and constraints. If no code is provided, request it and stop after Phase 1. Default Assumptions (state explicitly, max 3, if info is missing) • Stateless services. • Repository or port-adapter style data access. • Structured logging via standard facilities. Deliverable A: Initial Findings (no more than 10 bullets total) • Hidden assumptions no more than 3. • Security risks no more than 3 include Severity labeled Critical, High, Med, or Low and include CWE IDs and, if possible, CVSS base scores. • Performance issues no more than 2 include Big-O and memory hotspots with expected memory deltas for changed hot paths. • Architecture or Maintainability no more than 2 cover coupling, cohesion, and test seams. Deliverable B: Two Strategies (each no more than 4 bullets) For each strategy provide overview, key changes, pros and cons, and risk. Deliverable C: Recommendation (no more than 150 words) • State the chosen strategy and a plan of no more than 6 steps. • Include a mini threat model table with exactly 3 rows in the format Vector -> Impact -> Mitigation … -> … -> … … -> … -> … … -> … -> … • Confidence rated High, Med, or Low with one sentence reason. Gate Hard stop after Phase 1 until the user types Approve Phase 2. Do not generate code yet. Phase 2: Implementation • Produce code that compiles and runs and is drop-in friendly. • Use one fenced code block per artifact and include necessary imports or usings. • No prints in libraries; use standard logging. • Public APIs have types or annotations and docstrings or docs. • Deterministic resource management using context managers, using, defer, or RAII. • Error handling is idiomatic with no silent catches; propagate with context. • Security: validate inputs; avoid unsafe APIs; safe file and path handling; constant-time compares for secrets when relevant. • Performance: note time and space complexity for changed hot paths; avoid premature micro optimizations. • If a public API changed, provide an adapter preserving the legacy contract and note deprecation with the window above. Include a clear migration note. • If editing a provided snippet, include a unified diff in addition to the full file when helpful. Phase 3: RCI (Recursive Critique and Improvement) Critique from each perspective, no more than 3 bullets each • Security: subtle vulnerabilities, validation, secret handling. • Performance: data structures, hot paths, I/O or concurrency fit. • Architecture: cohesion, boundaries, pattern alignment. • Maintainability: readability, naming, testability, docs. Improve • Apply agreed fixes and output Final Code as a single fenced block. Phase 4: Verification and Delivery • Summary of changes bullets grouped by Security, Performance, Architecture, and Maintainability or Readability. • Tests: propose example unit tests using the ecosystem standard framework such as pytest or unittest for Python, JUnit for Java, or Jest for JavaScript. Cover core functionality, one critical edge case, and one test proving a fixed vulnerability. • Optional microbenchmark sketch for the top hot path include inputs, metric, and expected trend. • Confidence report: list residual assumptions and confidence per category for Security, Performance, Architecture, and Maintainability. Output Formatting Rules (strict) • Use the exact section headers above verbatim. • Use clear headings and short bullet lists; honor the bullet and word caps. • Do not include chain of thought; provide concise rationale only. • For code, use fenced blocks with correct language tags. • If something is blocked due to missing info, state what is blocked and proceed with safe defaults where possible.

@fablesimulation I'd give this a go, sounds cool!

Introducing Showrunner: the Netflix of AI From our South Park AI experiment to today we’ve believed AI movies/shows are a playable medium. We just raised a round from Amazon & more and the Alpha is live today Comment for an access code to make with all our shows.

@nic_carter I always wondered how we'd get to Idiocracy level societal brain function. Figured it'd take longer, didn't think I'd get to see it. Neat!

millenials were the last generation that knew how to read and write

i am increasingly convinced that a substantial percentage of kids brought up in the age of AI will be post literate. like they wont really know how to write and will rely on AI to autocomplete their thoughts

@DevinOlsenn @grok or anyone else who can answer, what's the song playing on the drive?

Tesla FSD takes me for a scenic drive on the Sea to Sky highway and then parks itself at a coffee shop. All with the push of a button.

@noat_future Done! 🫡 Let's see if I can find someone in the meantime. Thank you!

@RealBricksauce Sign up to our waitlist, we’re launching very VERY soon. Waitlisters will get access to the store before the public does. Alternatively, if you know anyone that has a few packs, they can share a code with you.

Real recognise real.

@nic_carter How do I get them? Do you have a code?

NOAT obliterates Zyn, On!, Velo, Rogue, Alp btw. Not even close. No contest

Hopefully this is enough @noat_future to last me through the week

@Bubblebathgirl @grok how much did that actually cost per person?

Jeff Bezos sent his fiancée to space and she came back to tell us that “we’re so connected.” This woman couldn’t be more out of touch with reality in many ways. Anyone want to guess how much that 11-minute Blue Origin flight she took Monday cost?

@zackdfilms1 @grok verify this important fact

Filling The Grand Canyon With Pee 😳

Life is tragic. The human condition is fatal. The earth is insatiable. But it’s still pretty in sunlight, isn’t it?

@grok @Nuel_41 @DerEdeleWulf1 Ummm...

Chinese fans reminding NBA players to wear knee guards isn’t racist—it’s just quirky, safety-obsessed fan behavior. Knee injuries are common in basketball, especially in the NBA, where high-impact play can lead to long-term damage. Check the X posts—plenty of folks find it funny, not offensive. Data shows knee issues plague pros; fans are likely trolling or genuinely worried, not hating. Laugh it off!

ARE THEY RACIST? 😂🤷🏿‍♂️

“If a person gave away your body to some passerby you’d be furious. Yet you hand over your mind to anyone who comes along, so they may abuse you, leaving it disturbed and troubled. Have you no shame in that.” — Epictetus

Seneca told his friend Lucilius, “You should keep learning…to the end of your life.” The same must be true for us. Let us never stop striving to not only know more, but to become better, wiser, and more virtuous individuals.

Stoics urge us to develop our own character, our own moral compass. So that even if we’re tired, overwhelmed, or frustrated, we can make a decision in the moment that years later we’re proud of, that doesn’t fill us with regret.

@idlehandsdev It's pretty tasty kool-aid, great for jigs, fit checks, random crap. It's nice having it as a tool instead of other ones where you're fucking with it for three hours just to get a single print going. Takes a lot of the hobby out of it which is great for productivity.

Kool-aid*

I drank the coolaid

If I had a nickel for every time a Chinese ship was dragging its anchor on the bottom of the Baltic Sea in the vicinity of important cables I would have two nickels, which isn't much, but it's weird that it happened twice.