theV

Your reliable engineering partner in critical blockchain and AI systems | Trusted by @StackRworld @arkivnetwork @dfinity @arcanaDigital @starknet

[theV @theveloperseu]

https://t.co/piWKfc2ar0

[theV @theveloperseu]

@sernique_ Coś szpąciliśmy z paperclipem od @dotta

[theV @theveloperseu]

https://t.co/qzIEPQ3bKb

[theV @theveloperseu]

@BarefootStudent 9 of them will fail. Happy to be in this 10%.

[theV @theveloperseu]

@Polymarket Great to see France taking a huge lead here!

[theV @theveloperseu]

Anthropic gave 16 AI agents $20,000 and 2 weeks.

No human wrote a single line of code.

They built a program that can compile the Linux operating system from scratch.

Here’s why the coordination matters more than the result.

Imagine 16 workers renovating the same house simultaneously. Without rules, they’d paint over each other’s walls. Solution: before starting a job, each agent writes their name on a sign-up sheet. If someone already claimed “fix the kitchen,” you pick something else. Simple file in a shared folder. First come, first served.

Any problems? Yes.

The system broke when they hit one massive task: compiling the Linux kernel. Think of it like 16 cooks trying to fix one broken recipe at the same time. Each one tastes the soup, adds salt, but the next cook doesn’t know salt was already added. They kept undoing each other’s work.

The fix was clever.

They brought in a professional chef (GCC, an existing compiler) to cook most of the meal. The AI agents only handled random portions. When something tasted wrong, they could pinpoint exactly which portion the AI messed up. Some would call that cheating. But the agents decided to do this themselves, no human told them to. And honestly, knowing when to use existing tools instead of reinventing everything from scratch? That’s what good engineers do too.

What they built:

100,000 lines of code. Can compile Linux, PostgreSQL, Redis, FFmpeg, and even run Doom. 99% pass rate on standard tests. What they can’t do: “Hello World” sometimes fails.

Now the reality check.

The GitHub repo has 41 open issues. Titles include: “can’t even compile linux as the description says,” “big words with nothing to back them up,” and simply “F*** off.” People who actually tried using the compiler found parser errors, missing tests, and broken basic features.

The methodology, 16 agents coordinating via git locks, splitting work, self-organizing, that’s genuinely forward-thinking. But the output today remains a toy, not a tool professionals would trust. The approach is the future. The result isn’t there yet. And that gap is exactly where the interesting work happens next.

------
source: https://t.co/nXHqZTdqIW

[theV @theveloperseu]

The V is for Victory – but only if it's shared.
Relax, @sama @DarioAmodei ✌️

[theV @theveloperseu]

https://t.co/X3HGsMNm4v

[theV @theveloperseu]

@Solofunk @MessariCrypto @luisri_ @DrxlEth @AvgJoesCrypto @0xbaba @maartjebus @adreon @redvelvetzip @tulipking @eric_turner Brawo i powodzenia na przyszłości. Dobrze widzieć takie sukcesy.

[theV @theveloperseu]

https://t.co/P88dPetQib

[theV @theveloperseu]

https://t.co/eStnTDUh1V

[theV @theveloperseu]

Today, we are at Crypto Talks Warsaw, discussing the future of the crypto market in an era of increasing regulation. We’re also exploring how the Baltic countries can cooperate to better serve and benefit their citizens.

[theV @theveloperseu]

https://t.co/NPmNBRLZJA

[theV @theveloperseu]

https://t.co/wAn6jG8FDR

[theV @theveloperseu]

Eurostack

[theV @theveloperseu]

https://t.co/Em72fZmArW

[theV @theveloperseu]

https://t.co/edP1YN61Bv

[Arkiv Network @arkivnetwork]

''The decentralized renaissance is coming, and you can be part of making it happen.'' - @VitalikButerin

This is the space [ ARKIV ] is a part of. Not fads, not short term narratives that take over CT. Web3 databases within an Ethereum infra tech stack.

[theV @theveloperseu]

The shift in AI development is being "manufactured" in real-time. Have you noticed the surge in "I haven't coded in weeks" posts? This is often a conspiracy of convenience.

On one side, Big Tech benefits from narratives that prioritize "AI replacement" over skill. They are building the habits they need to lock you into monthly enterprise subscriptions where you trade your autonomy for their tokens. On the other side, "AI Gurus" play on your fear of job loss, shilling "100-agent" setups that look great in a demo but fail in production.

The result is a knowledge scam. Companies are burning millions on AI subscriptions to "learn AI" from people who only know how to prompt, not how to build.

Here is the reality: If you are merely a "code writer", someone who outputs syntax without soul, Claude will replace you. But if you are an artist who treats code as a passion and a craft, you will not be replaced.

The worst case scenario is simply a change in your toolkit. You might need to switch to different instruments, but you will keep doing what you are passionate about: building production grade things that work.

At theVelopers, we see through the noise. We aren't prompt-pushers; we are AI mess debuggers and AI-code-artists.

We specialize in production grade engineering: turning vibe-coded prototypes into resilient, secure systems.

[theV @theveloperseu]

related links: .https://t.co/7XXRCvN6iq .https://t.co/qcVFXxT1N9

[theV @theveloperseu]

We all talk about how AI will improve our lives, but we rarely talk about the price tag of this change.

It’s not just the $20/month subscription; it’s the hardware paywall being built around us.

Memory prices have seen significant volatility since 2025 as manufacturers prioritize High Bandwidth Memory (HBM) for AI data centers over consumer components.

This pivot is forcing major PC manufacturers to adjust margins, with memory now accounting for a staggering portion of the total bill of materials.

This creates a "compute tax." If you can’t afford a high-end workstation with enough VRAM/RAM to run models locally, you’re forced to rent compute from the Big Three (AWS, Azure, Google).

In the future, we won’t just rent our software; we will be perpetual subscribers of compute. This effectively locks individual devs out of high-end local RAG or fine-tuning, trading ownership for dependency.