Join the conversation with Joe, Blitzy's field CTO, as he discusses what it takes to unlock autonomous software development in the enterprise.
x.com/i/broadcasts/1…
x.com/i/broadcasts/1…
0
1
2
159
Brian Elliott joined The Upstarts Podcast to talk about why building and modernizing software at enterprise scale requires more than generating code.
Now you can put that idea to the test.
The Blitzy Sandbox is live. Up to 1M lines reverse-engineered and 25K lines of tested code, free.
Give it a real codebase. blitzy.com/sandbox👇
Now you can put that idea to the test.
The Blitzy Sandbox is live. Up to 1M lines reverse-engineered and 25K lines of tested code, free.
Give it a real codebase. blitzy.com/sandbox👇
Boston tech unicorn Blitzy announced Sandbox today, allowing prospective customers to reverse-engineer up to 1M lines of code, and generate 25K lines of tested code, for free.
CEO Brian Elliott came on The Upstarts Podcast in July to talk about why he doesn't think LLMs will code at such volume -- even if Silicon Valley told him that view was "the stupid thing they'd ever heard" 👀
1
0
2
283
In the AI era, detecting security vulnerabilities is no longer the main challenge.
The real problem lies in understanding: exposure, reachability and autonomously remediating risks at enterprise scale.
On Wednesday, September 16 at 12 PM EST, Michael McCarter and Michael how to approach this exact issue.
The conversation will cover how to:
• Prioritize vulnerabilities based on reachability and exposure
• Uncover risks that traditional scanners may miss
• Understand the downstream impact before making a fix
• Turn findings into validated remediation PRs
• Accelerate remediation while keeping engineers in control
Join us to see what architecture-aware security looks like for the enterprise.
Register here: linkedin.com/events/7498376…
The real problem lies in understanding: exposure, reachability and autonomously remediating risks at enterprise scale.
On Wednesday, September 16 at 12 PM EST, Michael McCarter and Michael how to approach this exact issue.
The conversation will cover how to:
• Prioritize vulnerabilities based on reachability and exposure
• Uncover risks that traditional scanners may miss
• Understand the downstream impact before making a fix
• Turn findings into validated remediation PRs
• Accelerate remediation while keeping engineers in control
Join us to see what architecture-aware security looks like for the enterprise.
Register here: linkedin.com/events/7498376…
0
0
2
257
To grow our Canadian presence, Blitzy is proudly partnering with Elevate Festival.
Elevate’s commitment to curating high-quality events and panels makes this an especially exciting collaboration for our team.
On September 24 at 10 AM, Blitzy’s Head of AI Solutions Consulting on the Shop Talk stage speaking about how to accelerate engineering roadmaps up to 5x with autonomous software development.
We will also be hosting a cocktail night on September 24 (stay tuned for more details)!
Link to the Sept 22-24 schedule and tickets here: hubs.li/Q04vYpsr0
Elevate’s commitment to curating high-quality events and panels makes this an especially exciting collaboration for our team.
On September 24 at 10 AM, Blitzy’s Head of AI Solutions Consulting on the Shop Talk stage speaking about how to accelerate engineering roadmaps up to 5x with autonomous software development.
We will also be hosting a cocktail night on September 24 (stay tuned for more details)!
Link to the Sept 22-24 schedule and tickets here: hubs.li/Q04vYpsr0
0
0
2
174
“Blitzy is the brain for the codebase”, Sandy Carter writes.
After ingesting hundreds of millions of lines of enterprise code, Blitzy develops a unique understanding of your software that informs every run.
The platform's dynamic knowledge graph drives value regardless of the use case: whether Blitzy is accelerating software engineering velocity by 3x or modernizing legacy code that’s decades old.
Forbes just published an article about exactly how Blitzy solves the context problem in autonomous software development for the enterprise.
Read more here: forbes.com/sites/sandycar…
After ingesting hundreds of millions of lines of enterprise code, Blitzy develops a unique understanding of your software that informs every run.
The platform's dynamic knowledge graph drives value regardless of the use case: whether Blitzy is accelerating software engineering velocity by 3x or modernizing legacy code that’s decades old.
Forbes just published an article about exactly how Blitzy solves the context problem in autonomous software development for the enterprise.
Read more here: forbes.com/sites/sandycar…
0
1
2
211
Clue #3 is here:
"When two balances start fighting over the same lock, I notice.
I have a state machine for it: Normal → Promoting → Hot → CoolingDown. Hot pairs get routed onto their own dedicated lane and their writes get coalesced into batches under a redlock.
Most ledgers just deadlock. I promote."
Only one more clue to lock in your guesses...
"When two balances start fighting over the same lock, I notice.
I have a state machine for it: Normal → Promoting → Hot → CoolingDown. Hot pairs get routed onto their own dedicated lane and their writes get coalesced into batches under a redlock.
Most ledgers just deadlock. I promote."
Only one more clue to lock in your guesses...
0
0
1
19
Security scanners can identify vulnerable code. They often cannot tell you:
- Can the application reach it?
- Can an attacker access it?
- What will the fix affect?
Blitzy understands your entire software estate.
Proactive Insights autonomously surfaces known and previously ities across your enterprise codebase, determines reachability and exposure, assesses downstream impact, validates safe remediation, and generates tested pull requests.
Engineers approve the plan and review the PR. Blitzy reruns the analysis as the codebase changes.
Proactive Insights is now available in Blitzy.
Read the full blog here: blitzy.com/blog/hyperscal…
- Can the application reach it?
- Can an attacker access it?
- What will the fix affect?
Blitzy understands your entire software estate.
Proactive Insights autonomously surfaces known and previously ities across your enterprise codebase, determines reachability and exposure, assesses downstream impact, validates safe remediation, and generates tested pull requests.
Engineers approve the plan and review the PR. Blitzy reruns the analysis as the codebase changes.
Proactive Insights is now available in Blitzy.
Read the full blog here: blitzy.com/blog/hyperscal…
0
0
0
163
The big reveal for this week's Guess that Codebase 👀
"num_warps. num_stages. num_ctas.
Three integers between your math and the machine.
I'll search them myself if you let me.
Born in a 2019 paper on tiled computation.
568 lines of knobs. Five dialects. Two backends.
One decorator:
@triton.jit
I am Triton."
Check back next week for another round of clues!
"num_warps. num_stages. num_ctas.
Three integers between your math and the machine.
I'll search them myself if you let me.
Born in a 2019 paper on tiled computation.
568 lines of knobs. Five dialects. Two backends.
One decorator:
@triton.jit
I am Triton."
Check back next week for another round of clues!
0
0
1
310
Clue #3:
"~200 type errors live in my semantics layer.
Exactly one reads like philosophy:
"cannot add pointers together"
semantic.py:236
I'll offset an address by anything you hand me.
I'll never add two of them."
Tell me why that line has to exist."
"~200 type errors live in my semantics layer.
Exactly one reads like philosophy:
"cannot add pointers together"
semantic.py:236
I'll offset an address by anything you hand me.
I'll never add two of them."
Tell me why that line has to exist."
1
0
1
21
Last clue of the week is below:
"Five dialects live in lib/Dialect/.
Four march downward, toward metal.
The fifth is a second language wearing my clothes.
It refuses to hide the layouts —
sizePerThread
threadsPerWarp
warpsPerCTA
— and hands them back to you.
Name the fifth."
Any final guesses before the big reveal?!
"Five dialects live in lib/Dialect/.
Four march downward, toward metal.
The fifth is a second language wearing my clothes.
It refuses to hide the layouts —
sizePerThread
threadsPerWarp
warpsPerCTA
— and hands them back to you.
Name the fifth."
Any final guesses before the big reveal?!
0
0
1
16
Stay up to date on all things Blitzy with our weekly newsletter: The Blitzy Blitz!
the-blitzy-blitz.beehiiv.com/subscribe
the-blitzy-blitz.beehiiv.com/subscribe
0
0
1
146
Here's our third clue of the week!
"~200 type errors live in my semantics layer.
Exactly one reads like philosophy:
"cannot add pointers together"
semantic.py:236
I'll offset an address by anything you hand me.
I'll never add two of them.
Tell me why that line has to exist."
Any ideas?
"~200 type errors live in my semantics layer.
Exactly one reads like philosophy:
"cannot add pointers together"
semantic.py:236
I'll offset an address by anything you hand me.
I'll never add two of them.
Tell me why that line has to exist."
Any ideas?
0
0
1
143
Clue #2 for Guess that Codebase just dropped 👀
Here it is:
"Your kernel dies four times before it touches silicon.
? → ? → LLVM IR → PTX → cubin
The first two names are mine alone.
The second exists only because the first
had never heard of a warp.
Fill in the blanks."
Any guesses?
Here it is:
"Your kernel dies four times before it touches silicon.
? → ? → LLVM IR → PTX → cubin
The first two names are mine alone.
The second exists only because the first
had never heard of a warp.
Fill in the blanks."
Any guesses?
0
0
1
134
We have another round of 4 clues this week...
All written by Blitzy.
One open source project. 4 clues.
Monday-Thursday, one clue posted each day.
Reveals every Friday.
Here's Clue #1:
"I never learn your secrets. I still do your math. Add, multiply, compare — all of it on data I can't read, and never once holding the key. My whole existence resolves a tension: using your data vs. protecting it. Guess me. 🧵"
Leave your guesses in the comments below!
All written by Blitzy.
One open source project. 4 clues.
Monday-Thursday, one clue posted each day.
Reveals every Friday.
Here's Clue #1:
"I never learn your secrets. I still do your math. Add, multiply, compare — all of it on data I can't read, and never once holding the key. My whole existence resolves a tension: using your data vs. protecting it. Guess me. 🧵"
Leave your guesses in the comments below!
1
0
3
228
Last clue of the week is here!
Clue #4:
"Details, since you're struggling:
• C++17, CMake, BSD-2
• MATHBACKEND 2, 4 or 6 — pick your integer arithmetic at compile time
• ~1,194 fail-fast contract checks
• Bootstrapping, threshold FHE, proxy re-encryption
• DARPA-funded, WAHC@CCS'22
• I compile to WebAssembly"
Leave your guesses in the comments below.
Clue #4:
"Details, since you're struggling:
• C++17, CMake, BSD-2
• MATHBACKEND 2, 4 or 6 — pick your integer arithmetic at compile time
• ~1,194 fail-fast contract checks
• Bootstrapping, threshold FHE, proxy re-encryption
• DARPA-funded, WAHC@CCS'22
• I compile to WebAssembly"
Leave your guesses in the comments below.
1
0
2
65
Last clue of the week is here!
Clue #4:
"Details, since you're struggling:
• C++17, CMake, BSD-2
• MATHBACKEND 2, 4 or 6 — pick your integer arithmetic at compile time
• ~1,194 fail-fast contract checks
• Bootstrapping, threshold FHE, proxy re-encryption
• DARPA-funded, WAHC@CCS'22
• I compile to WebAssembly"
Leave your guesses in the comments below.
Clue #4:
"Details, since you're struggling:
• C++17, CMake, BSD-2
• MATHBACKEND 2, 4 or 6 — pick your integer arithmetic at compile time
• ~1,194 fail-fast contract checks
• Bootstrapping, threshold FHE, proxy re-encryption
• DARPA-funded, WAHC@CCS'22
• I compile to WebAssembly"
Leave your guesses in the comments below.
0
0
2
204