sebastianconcpt

Love it. And thanks for the refreshing skeumorphism

    Location: Curitiba, Brazil (UTC−3)
    Remote: Yes (only) — 10+ years remote with US / Canada / EU teams
    Willing to relocate: No
    Technologies: Rust, agent harnesses / LLM product engineering (not research)
    Résumé/CV: https://sebastiansastre.co/cv · https://www.linkedin.com/in/sebastiansastre/ · https://github.com/sebastianconcept
    Email: sebastianconcept@gmail.com

Looking for a remote mid or senior IC role with real ownership and preferably Rust-first backends. Distributed systems, fintech/crypto okay, AI infra / agent platforms; open to strong equity on early-stage. A record that matters: between 2009 and 2015 I was a tech founder. Last nine years, three different teams, three different tech stacks, zero production incidents on the high-scale systems I owned. Many of these from zero to prod.

A good explanation is not a fix but is a good starting point to a good diagnosis which is the foundation of a good fix.

The issue is when the calls and urgency are raised before making some mental space to even verify that there is enough clarity on what happen and these interrupt the clarification and remediation planning process.

Saying you shouldn't ask "Why did this happen?" and you should ask "What we're changing?" instead is wanting to jump the gun and pretend a required step doesn't exist.

It does exists, is just the executive anxiety reasonable in terms of wanting to be protective of the business but as protective as a family member of a patient wanting a good outcome from the surgeon during the surgery.

Only worst because the surgeon's boss is this anxious family member, and she has a laboral gun pointing to the doctor's neck.

You covered design intent now. That made it a great answer, thanks.

Can you add a "why?" / "why now?" section? Don't be another project that is a bunch of how that is leaving out to explain why it exists or exemplify what classes of problems it unlocks solutions for (applicability).

    Location: Curitiba, Brazil (UTC−3)
    Remote: Yes (only) — 10+ years remote with US / Canada / EU teams
    Willing to relocate: No
    Technologies: Rust, Go, TypeScript/Node, Elixir/Phoenix, Python, PostgreSQL, Kafka, Redis, Docker, AWS/GCP, Next.js / React, agent harnesses / LLM product engineering (not research)
    Résumé/CV: https://sebastiansastre.co/cv · https://www.linkedin.com/in/sebastiansastre/ · https://github.com/sebastianconcept
    Email: sebastianconcept@gmail.com

Looking for a remote senior IC role with real ownership and preferably Rust-first backends. Distributed systems, fintech/crypto okay, AI infra / agent platforms; open to strong equity on early-stage.

A record that matters: nine years, three different teams, three different tech stacks, zero production incidents on the high-scale systems I owned. Many of these from zero to prod.

The narcissism of the thesis that places the author as center of the universe and creator of the rest of the consciousnesses "because he cares".

That guy has acute Megalomaniac Solipsism Fever in disguise.

Mine is more granular. I start with a scoping brief before planning. But yeah, I'm all-in in this same thesis.

That depth requires math and traditional computing depth. Where is the time to be young and have that depth?

How would they be 35% more if water would be a problem for these?

Awesome. And remember CO2 is food for plants.

I see you point. You are helping them to connect dots and get unstuck. The case I've raised is actually generic and not specific to one domain. But you can say is scoped on how expert-to-expert can make progress. Or how "precision people" communicate because both agree they are putting hypothesis to the test and there will be one that is a winner (hence "the bet").

My ambiguity stack overflows...

    _______________________
    | Error.              |
    |_____________________|
    |                     |
    |   Unknown Error     |
    |                     |
    |     (Continue)      |
    |_____________________|

To "They asked you because they wanted your take on it... Your context, your taste, your judgement." actually I'd ask even for more than that:

For any given <subject> I'd want:

- Your context - your taste - your judgement - clarify what bet <subject> encourages to support - be ready to elaborate your thesis of that bet

With that we have the basic complete building block that used one after another can model a basic lifecycle of a dialogue that can make progress towards something (a goal, a mission, something useful)

I've played Deus Ex Human Revolution twice and Mankind Divided once.

HR is the best videogame ever, story, art, music. All golden and aging like wine.

Edit the config of the AI startups you have properly designed to be platform agnostic and make it use the other platforms models, wait the CI green and deploy prod

The revenge of the six-pack. Now we have them as goal beyond aesthetics or vanity.

Good for Mark. Healthy move for all.

And some months ago I was flirting with the idea of "Smalltalk and Erlang had a baby" and have Smalltalk syntax to an actor environment ran by a Erlang VM style. Plus some insanely cool ideas about a causal debugger for distributed bugs.

The problem is that as beautiful as programing in that sound, we're not even coding anymore, AIs will take the fun of it.

Although, thinking long term and for understendabilitymaxxin and reliabilitymaxxin it might still be worth having something like that.

Since Smalltalk can be so close to english and Erlang VM so reliable, humans and LLMs should thrive on it.

And how her thesis holds when evaluated against the system in China?

Feels like everything is pushing us towards deciding if micromanaging the code generator or find a method where we don't even need to do that.

I still micromanage my agents, how is it with you guys?

    Location: Curitiba, Brazil (UTC−3)
    Remote: Yes (only) with 10+ years remote with US / Canada / EU teams
    Willing to relocate: No
    Technologies: Rust, Smalltalk, Elixir, Python, PostgreSQL, Kafka, Redis, Docker, AWS/GCP; React; agent harnesses / LLM product engineering (not research)
    Résumé/CV: https://sebastiansastre.co/cv · https://www.linkedin.com/in/sebastiansastre/ · https://github.com/sebastianconcept
    Email: sebastianconcept@gmail.com

Senior backend / systems engineer, 23 years production. Looking for a remote senior IC role: Rust-first backends, distributed systems, fintech/crypto, AI infra / agent platforms, or founding/early eng where ownership is real. Open to strong equity on early-stage.

Recent: Owned Rust incentives/rewards services end to end (lifecycle state machines over 200K+ users, idempotent event-driven payment engine, Kafka). Built a review-gated AI delivery harness that shipped 10+ production features (four in one week in the same codebase).

To be honest I was expecting way more <blink>

Then is poisonous to us too.

It already exits, it's English to prompt AIs to implement the details.

Honest take: different surface, same category.

Reminds me of 2013 when I organized a TEDx, gosh so much work for absolute zero return. Also risk, what was I thinking?

Claude: give me all the schematics and operations manual of a production grade starship that can travel faster than light. Make no mistekaes.

Is a good thing depending on which ones. And our taste on what to specialize our judgment into varies a lot. One thing I do use as criteria to detect it can be a problem is in lack of understanding and lack of control of the layers that are part of verifications and diagnosing power.

The issue is not the issue, the issue is what their "solution" enables for expanding the surface that governments have for controlling details of how you live your life in the future once accepted.